Custom CRM or off-the-shelf? An honest decision guide.

Every week someone tells us their CRM "doesn't quite fit". Usually they're right. But not quite fitting isn't the same as needing a custom build — sometimes the honest answer is a better-configured subscription tool, and we'll say so on a scoping call.

Here are the five questions we actually use. Answer them for your own business and you'll know which side you're on.

1. Is your process the product, or just admin?

For some businesses the way work moves — enquiry to site visit to quote to contract to build stages to claims — is the business. The CRM has to model it exactly or people stop using it. For others, the CRM is a contact list with reminders, and any decent tool will do.

Test: draw your pipeline on a whiteboard. If it has more than one branch, stages that mean different things for different job types, or hand-offs between teams, a template will fight you. If it's a straight line with five stages, don't build.

2. How many workarounds are you running?

Count them honestly: the spreadsheet that tracks the thing the CRM can't, the Zap that breaks every quarter, the "we just put it in the notes field" habits, the report someone rebuilds every Friday.

Test: fewer than three workarounds — configure, don't build. More than five, and your team has already built a shadow system; a custom CRM just makes it real and reliable.

3. What does the subscription actually cost over three years?

Per-seat pricing looks cheap at five users. Then you add the automation tier, the reporting add-on, the integration marketplace app, the two extra seats for the admin and the part-timer. Add the hours someone spends administering it.

Test: write the real monthly number down, multiply by 36. If that figure is in the same range as a fixed-price build you'd own outright, the maths has already decided. If it's a fraction of it, stay put.

4. Do you need integrations the marketplace doesn't have?

Xero, Gmail and a web form — every tool does those. Your job-management app, a state licensing register, a supplier's quoting portal, SMS to site crews, a client portal with approvals — that's where off-the-shelf runs out, and the "solution" is usually another subscription and another Zap.

Test: list every system a deal touches from enquiry to final invoice. If more than two of them aren't in your CRM's marketplace, a custom build connects them directly.

5. Who owns the data if you leave?

Exporting from a subscription CRM gets you a CSV of contacts and, if you're lucky, deals. Notes, email history, attachments and automations rarely come with it. That's not an accident — it's the retention strategy.

Test: if the thought of leaving your current tool makes you wince because of what you'd lose, you don't own your data. A custom CRM sits in a database in your own cloud account; leaving Nexoro means changing who supports it, nothing else.

The scorecard

Three or more in the right-hand column and a custom build is worth a scoping call. Three or more on the left and the better move is an afternoon configuring what you have — we can help with that too, and it's a smaller job.

What "custom" actually means at Nexoro

Not six months and a surprise invoice. A fixed price agreed after a free 30-minute scoping call, a design you sign off before any code, releases your team is using within weeks, and a system — code, database, hosting — in your name from day one. The full process is here; the PPI build is what it looks like in practice.