Custom CRM or off-the-shelf? A checklist for deciding

Whether to build a custom CRM is one of the most common questions we hear, and the honest default answer is: probably not yet. A good off-the-shelf CRM is cheap to start, well tested and full of features you would never think to build. Building your own should be a decision you can justify, not a reflex.

But there are real cases where it is the better call. Here is how to tell which one you are in.

Start with the default

If your sales process looks roughly like leads, qualification, proposal, won or lost, an existing CRM will fit. Configure the pipeline stages and fields, connect email and your forms, and get on with selling. You can move faster, and you will benefit from years of product work you did not pay for.

Signs an off-the-shelf CRM is fighting you

• You keep a spreadsheet next to it for the things it cannot hold.
• Your data does not look like a sales pipeline. You track cases, policies, rentals, batches, projects or patients, and you are forcing them into "deals" and "contacts".
• People have workarounds for the workarounds. Fields reused for something else, notes with secret codes, steps that live only in someone's head.
• The important logic lives outside the CRM, in a tangle of automations that break whenever someone edits a field.
• Per-seat pricing hurts. You need everyone from the field team to the warehouse to see the data, and the licence cost grows with every person.
• Your process is your advantage, and a generic tool would flatten it.

One sign alone is not a reason to build. Several at the same time is.

Compare the real costs

The row people underestimate is maintenance. Software is never finished: people join, processes change, browsers update, libraries need upgrades. A custom CRM without someone responsible for it will slowly rot. Budget for that from day one.

The middle path

Often the best answer is neither. Keep an off-the-shelf CRM for what it does well, and add:

• an automation layer that keeps data in sync and handles follow-ups,
• a small custom app for the one part that does not fit, such as a quoting tool or a field-team screen, that reads and writes to the CRM through its API.

You get most of the fit at a fraction of the cost, and you can still replace either piece later.

When custom clearly wins

• Your data model is unusual and central to the business.
• The workflow is a real competitive advantage and needs to be exactly right.
• You need deep integration with other systems, such as billing, inventory or WhatsApp, in one place.
• You have data residency or compliance needs that a hosted tool cannot meet.
• You have many users who only need a narrow view, so per-seat pricing makes no sense.

A short checklist before you decide

1. Have we tried configuring a mainstream CRM properly, not just installing it?
2. Can we list the specific things it cannot do, and what each one costs us per month?
3. Do we know who will own and maintain a custom system after launch?
4. Would a small custom app plus automation solve 80% of it?
5. Do we have written-down workflows, or are we still working out how we sell?

If you cannot answer the last question, sort out the process first. Software cannot fix a process that nobody has agreed on.

If you are stuck between the two, describe how your team sells today and we will tell you whether custom is worth it, even if the answer is no.