What was built
The client-acquisition process of a German tax and advisory firm, rebuilt in Pipedrive. The Neumandatsprozess starts with a qualification form and ends with an onboarded client, and every step in between had been someone's memory.
| Area | Description |
|---|---|
| Qualification form | A multi-step web form that stores every answer against the Pipedrive person, organisation and lead, rather than collapsing it into a note |
| Classification routing | Answers drive an A / B / C / Absage classification, each with its own follow-up path |
| Pipedrive structure | Fields, pipelines and stages designed around that qualification model |
| Reception path | A Gesprächsleitfaden so an enquiry arriving by phone is scored the same way as one arriving by form |
| Telephony | 3CX connected to Pipedrive for the practice |
| Inbound sync | Contacts, organisations and won deals synced from the firm's PraxisMachen channel into the new account, with a webhook for live lead creation |
| Offer & onboarding | Offer creation and the post-meeting onboarding form, feeding master-data collection and the feedback and review step |
The pricing side is its own problem: tax-service offers follow StBVV Zehntelsätze, so the offer engine has to calculate from the statutory schedule rather than from a price list.
Tech stack
| Technology | Role |
|---|---|
| Pipedrive | CRM, leads, qualification, pipelines |
| Make.com | Form intake, routing, the PraxisMachen sync |
Project stats: 37 tasks, ~26h, running since May 2026.
Zuletzt bearbeitet
- 2026-09-02 Tax service (Steuerberatung) offer pricing — StBVV / Zehntelsätze engine Open
- 2026-09-01 Reception phone-entry path for scoring (Gesprächsleitfaden) Open
- 2026-08-31 Finish DRS form dev and test Pipedrive lead creation Done
- 2026-08-30 M1 — Lead Capture & Qualification (Web → Pipedrive) Open
- 2026-08-30 Lead scoring & qualify/disqualify engine Done
Weitere Projekte dieses Kunden
DATEV MCP
An MCP server wrapping the DATEV Connect API, so the accounting data a German firm keeps in DATEV is reachable from an AI assistant instead of only from the DATEV client. Reads are the primary use;…
Case Study lesenWas wir gebaut haben
- Endpoint inventory
- Client & master data
- Multi-tenancy
- On-prem agent
- Cloud deployment
- CI/CD
Kanzlei MCP
A team-facing MCP layer so the firm's staff move CRM and operational data through Claude instead of clicking through the Pipedrive interface. Only supervisors work in the CRM UI; everyone else gets…
Case Study lesenWas wir gebaut haben
- Tool surface
- Inbound sync
- Alerting
- Meeting notes
- Deployment
- Onboarding