← Notes

27 July 2026 · 6 min read

Custom CRM vs off-the-shelf: how to choose

We build custom CRMs, so treat the following with appropriate suspicion — and then notice that most of it argues against hiring us.

The honest position is this: most businesses should buy a CRM, not build one. The off-the-shelf products are mature, cheap relative to a build, and someone else maintains them. Custom only wins in specific circumstances, and it is worth knowing whether you are actually in one.

Buy off the shelf when

• Your sales process looks broadly like everyone else's: leads come in, you qualify them, you quote, you win or lose.
• You need it working this month.
• Your team is under about ten people and growing slowly.
• Nobody on your team wants to own a piece of software.

If that is you, pick a mainstream product, spend the saved money on actually using it properly, and revisit in two years.

Build custom when

• Your process is genuinely unusual. Not "we like it our way" — actually structurally different. Multi-stage approvals, unusual pricing rules, work that belongs to sites rather than companies.
• You are paying per seat for features you never touch. At a certain headcount, subscription costs cross over a build, especially when most users need read-only access.
• The CRM has to talk to something specific. A production system, a scheduling tool, an industry database that no off-the-shelf product integrates with.
• The data is the business. If your customer records are your competitive advantage, owning the system outright starts to matter.
• You have been forced into workarounds. The clearest signal of all: your team has a shadow spreadsheet next to the CRM because the CRM will not do something essential.

The question that settles it

Ask your team: what do you do outside the CRM, and why?

If the answer is "nothing much", buy off the shelf. If you get a list — spreadsheets, a shared inbox, a whiteboard, a WhatsApp group — that list is your actual requirement, and it is the thing generic software failed to cover.

What a custom build should include

If you do go custom, the scope should cover more than screens:

1. The pipeline as it truly runs — mapped from observation, not from the org chart.
2. A deliberate record design. Only fields somebody will genuinely fill in. Every optional field nobody completes is future confusion.
3. Automation of the forgettable. Follow-ups and handoffs that no longer depend on one person remembering.
4. Training until it sticks. A CRM nobody uses is worse than no CRM, because now the data is split across two places.
5. An export. You should be able to get all your data out, in a usable format, without asking anyone's permission.

Point five matters more than it sounds. It is also a fair question to ask a subscription vendor before you commit.

The honest trade-off

Custom software has no upgrade path you did not pay for. Off-the-shelf products improve while you sleep; a bespoke CRM improves when you commission it to. In exchange you get something shaped exactly to your work, with no per-seat pricing and no vendor deciding to sunset a feature you depend on.

Neither is universally right. But if you cannot articulate the specific thing the generic tools cannot do, that is a strong sign to buy rather than build — and any studio worth commissioning will tell you the same.