Building a CRM That Fits Your Business

Why we usually talk clients out of it

CRM is a solved category. The products are mature, cheap relative to a build, and they handle the hundred small things — email sync, mobile, deduplication, reporting — that take months to reproduce.

So when someone asks us to build one, the first conversation is about what specifically their process needs that no product provides. Occasionally the answer is compelling. Usually it is that the previous CRM was configured badly.

Why CRM projects actually fail

1. Salespeople will not use it. The single biggest cause, and it is about effort per entry, not features.
2. Data was migrated dirty. Duplicates and stale records destroy trust in week one.
3. It was configured for management reporting. Twenty required fields serving a dashboard nobody selling cares about.
4. Nobody owns it. After go-live, configuration drifts and nobody maintains the picklists.

Every required field you add to a CRM form is a small tax on every deal. Charge it only where the revenue depends on the answer.

Making it worth using

The system has to give the salesperson something before it asks them for something. Their diary, their pipeline, the last email, the account history — visible without effort.

• Automatic email and calendar capture — no manual logging
• Mobile that works properly, because updates happen in a car park
• Two required fields, not twenty
• Their own pipeline view first, the management view second
• One-tap logging of a call outcome

When extending is the right answer

Common and sensible. Keep the CRM for contacts, activity and pipeline, and build the specific thing it cannot do — a quoting engine with your pricing rules, a configurator, a scheduling layer — writing back into it.

This is usually £8,000–£25,000 rather than the £60,000+ of a replacement, and you keep the ecosystem, the mobile apps and the integrations.

The rare case for building

• Your sales process is genuinely nothing like a pipeline of opportunities
• The CRM is the operational system, not just a sales tool
• Data residency rules exclude every viable product
• Per-seat licence costs at your headcount exceed a build within two years

We have built two. Both were businesses where the customer record was the operational core — scheduling, delivery, compliance and billing all hanging off it — and no CRM product was ever going to be that.

Migrating data without poisoning the well

1. Deduplicate before migrating, with a rule everyone has agreed
2. Do not bring records with no activity in three years — archive them
3. Map fields explicitly; do not dump free text into notes
4. Import a sample of 200 first and have the sales team check it
5. Keep the source export indefinitely

Salespeople judge a new CRM in the first week. If the first three records they open are duplicates with stale details, no amount of subsequent quality recovers it.

Frequently asked questions