Most CRM rollouts are treated as software deployments — install, configure, train, done. The companies that succeed treat it as architecture: how does revenue data flow in, where does it leave, and what depends on it downstream?
The pattern we keep seeing
A growing business buys a CRM. Twelve weeks later, the platform is live. Eighteen months later, half the team has stopped using it, deal data lives in spreadsheets, and the leadership team is reviewing pipeline numbers that nobody trusts.
This isn’t a software failure. It’s an architecture failure.
Three things that almost always go wrong
1. The CRM is configured around an idealised process, not the actual one. Sales teams adapt to what works. If your stages don’t match how your reps actually qualify deals, they’ll route around the tool.
2. There’s no downstream connection. When a deal closes, what happens? In a configured-only CRM, somebody manually creates an invoice. In an integrated one, Books knows. So does Inventory. So does Analytics. The CRM stops being a database and starts being the front door to the execution system.
3. The reports answer the wrong questions. Dashboards show what’s easy to query, not what’s load-bearing for the business. If your CFO can’t tell you cash position from your CRM data, your CRM isn’t connected.
The fix isn’t more configuration
You can’t configure your way out of an architectural problem. Before you touch a CRM screen, answer three questions:
- What revenue data needs to enter the system, and from where?
- What downstream systems depend on that data the moment a deal moves stages?
- Who needs to see what, when, and in what form, to make better decisions?
Get those answers right and the configuration is straightforward. Skip them and you’re building another database your team will route around.
What this looks like in practice
In every Cogens engagement we run, the CRM build is the last 30% of the work. The first 70% is mapping the business — current-state workflows, decision rights, integration points, data flows. By the time we open Zoho CRM, we know exactly what to build, and so does the client.
That’s why our CRM implementations don’t get abandoned. They were never just CRM implementations.