Build or Buy? Choosing a CRM When Off-the-Shelf Almost Fits
Subscription CRMs are cheap until you need them to match how your business actually sells. A practical framework for deciding when to configure, when to extend, and when to build.
The question is almost never "do we need a CRM". It is "do we bend our process to fit the tool, or bend the tool to fit our process". Both answers are defensible; picking the wrong one is expensive either way.
Start with the workflow, not the feature list
Write down how an enquiry actually moves through your company today — who touches it, what they decide, what they need to see. Most teams discover their process has three or four steps that no standard pipeline models: a technical feasibility check, a costing approval, a sample dispatch.
Buy when your process is ordinary
If leads arrive, get qualified, get quoted and close — a configured off-the-shelf CRM will serve you well and cost a fraction of custom work. Resist the urge to customise it into something unrecognisable.
Build when the process is the differentiator
Manufacturers with drawing revisions, sample approvals and rate contracts usually hit the ceiling of a generic CRM within a year. At that point the monthly per-seat cost plus the workarounds plus the spreadsheets running alongside it often exceed what a purpose-built system would have cost.
The middle path most people miss
Keep the standard CRM for contacts and pipeline, and build only the module that is genuinely yours — the costing engine, the production tracker — connected through APIs. You get custom where it matters and pay nothing to rebuild what already works.
Whichever route you take, decide on the basis of your workflow document. A demo will always look convincing; your process will not lie.
