When off-the-shelf is better
If your workflow is lead capture, pipeline stages, email tracking, tasks, and reporting, buy a CRM. The subscription will be cheaper than building and maintaining your own. Off-the-shelf is also better when you need fast deployment, a large plugin ecosystem, or sales team familiarity.
Customisation inside an existing CRM should be tried before bespoke development. Many problems are configuration problems, not software problems.
When custom CRM makes sense
A custom CRM is justified when the CRM is really an operations platform: complex quoting, booking, compliance checks, fulfilment workflow, customer portals, field teams, inventory, custom approval chains, or deep sector-specific data. It also makes sense when per-seat pricing becomes expensive at scale and the feature set you use is narrow but highly specific.
The strongest case is when CRM data must connect directly to proprietary business logic. If a salesperson action triggers delivery operations, document generation, billing, and customer communication, a custom system may reduce tool switching and errors.
What a custom CRM includes
A serious custom CRM normally includes contact and company records, pipeline or workflow stages, activity history, tasks, notes, file attachments, email templates, role permissions, reporting, import/export, notifications, and integrations with email, calendar, accounting, payment, or support systems.
The hidden cost is data migration. Old CRM data is often duplicated, inconsistent, and missing key fields. Budget time to clean and map it. Bad data moved into a new CRM is still bad data.
Cost and build phases
A focused custom CRM starts around £20,000-£45,000. A CRM with customer portal, workflow automation, reporting, and integrations usually costs £45,000-£120,000. Enterprise-grade systems with complex permissions, audit logs, and multiple departments can exceed £150,000.
Phase one should cover the critical workflow only. Add advanced reporting, automation, and integrations after users have proved the system fits their daily work.
| Scope | Typical cost | Timeline |
|---|---|---|
| Single-workflow CRM (contacts, pipeline, tasks) | £20,000 – £45,000 | 8–14 weeks |
| Operational CRM (portal, automation, reporting) | £45,000 – £120,000 | 4–8 months |
| Enterprise CRM (multi-department, audit logs, complex permissions) | £150,000+ | 8–14 months |
What UK businesses actually build custom CRMs for
The pattern repeats across sectors: field service and installation businesses need a CRM that also schedules engineers, tracks parts, and generates compliance certificates — a workflow HubSpot was never built for. Distribution and wholesale businesses need pricing tiers, credit limits, and order history tied directly to the sales record, not bolted on through an integration. Professional services firms (accountancy, legal, consultancy) need matter or case tracking, time recording, and document generation wired into the same pipeline stages their fee earners already work in. Healthcare and care providers need patient or client records with access controls and audit trails that off-the-shelf CRMs treat as an expensive add-on tier, if they offer it at all.
In each case, the common thread isn’t dissatisfaction with CRM software — it’s that the CRM needs to drive operations, not just track a sales conversation. That’s the signal worth testing for before committing budget.
Common mistakes in custom CRM projects
Avoid these before you scope a build:
Migrating off Salesforce or HubSpot without losing history
Data migration is where most custom CRM budgets get underestimated. Export every object you rely on — contacts, companies, deals, notes, attachments, email history, and custom fields — not just the ones visible in the default export. Map old pipeline stages to new ones explicitly rather than assuming a one-to-one match; most businesses discover their "real" sales process differs from what the old CRM's stages implied.
Run the new system in parallel with the old one for at least one full sales cycle before fully cutting over. This catches missing fields, broken automations, and edge cases that only show up with live deals moving through the pipeline, while giving the team a safe fallback if something doesn’t match expectations.
Ongoing cost after launch
A custom CRM doesn’t stop costing money at go-live. Budget for hosting and infrastructure (typically £50–£300/month depending on scale), a maintenance retainer for bug fixes and small changes (often 10–15% of the original build cost annually), and periodic feature additions as the business changes. This compares against CRM subscription costs that scale per seat — the crossover point where custom becomes cheaper is usually somewhere between 20 and 50 seats, depending on how expensive the equivalent off-the-shelf tier is.
Factor in who owns the codebase and who's on call if something breaks on a Friday afternoon. A CRM that runs the sales floor is now a piece of operational infrastructure, not a side project, and it needs the same support commitment as anything else the business depends on daily.
AyTech note: The safest projects start with a narrow, measurable workflow, then expand after real users prove the value. This keeps budgets controlled and gives Google, buyers, and stakeholders clearer proof of expertise.
Need a practical technical plan?
AyTech can review your requirements, map the risks, and turn the idea into a scoped delivery plan.
custom web application development