How to choose between a custom system and an off-the-shelf CRM

Every few weeks someone asks us to build them a CRM. Most of the time we talk them out of it — and the reasoning is worth sharing, because the decision is rarely as close as it feels from the inside.

Start by separating the process from the tool

The instinct to build usually comes from frustration with a specific tool, not from a genuine mismatch with the market. Before comparing options, write down the ten steps your team actually performs between a lead arriving and an invoice being paid. Mark each one as standard (any CRM does this) or specific (only your company works this way).

If eight or nine of those steps are standard, you are buying. The remaining one or two get solved with a custom integration on top of a bought platform — a fraction of the cost of building the whole thing.

The cases where buying wins

• Your sales process resembles other companies in your sector.
• You need it working within a quarter.
• Your team is under twenty people and headcount is growing faster than process complexity.
• You value integrations with the wider ecosystem more than exact fit.

The cases where building wins

• Your core operation is the differentiator — production planning, field logistics, regulated workflows.
• Per-seat licensing scales against you: hundreds of occasional users, each needing a paid seat.
• You have already bought a platform twice and hit the same wall both times.
• Data residency, audit or regulatory requirements the vendor cannot meet.

If you cannot name the specific thing off-the-shelf software prevents you from doing, you are not ready to build.

Run the five-year number, not the sticker price

A SaaS CRM at €90 per user per month across 40 users is €43,000 a year, or €216,000 over five years — before integration work, before the consultant who configures it, before the workarounds. A custom system might cost €120,000 to build and €25,000 a year to run. The comparison flips somewhere around year three, and it flips sooner the more seats you add.

That said, the custom number carries risk the SaaS number does not: it depends on the project going roughly to plan and on you keeping a development relationship alive. Price that risk honestly instead of assuming it away.

The hybrid answer almost everyone should take

Buy the CRM. Build the twenty percent that is genuinely yours as a separate service, connected through the CRM's API. You get the ecosystem, the mobile apps and the vendor's ongoing development, plus exact fit where exact fit matters. When we do CRM work, this is what roughly three quarters of engagements end up looking like.

Two questions to answer before you commit

First: if this system disappeared tomorrow, could the business still operate for a week? If not, you are building something operationally critical and should budget for support accordingly. Second: who owns it internally? Custom software without an internal owner decays faster than any licence renewal.

If you want a second opinion on where your process sits, we run a short paid audit that produces exactly this comparison for your numbers.