Custom CRM or HubSpot, Zoho and Salesforce? A decision framework for growing businesses

"Should we build our own CRM?" is usually the wrong first question. The right first question is: what is the sales and delivery process we need the system to model, and can a platform express it without us fighting the tool every day?

Here is the framework we use in discovery. It applies equally to CRM, ERP and the business operating systems that combine both.

Question 1: Can the process be configured, or must it be coded?

Platforms like HubSpot, Zoho and Salesforce are enormously configurable: pipelines, custom objects, automations, permissions. If your process is "lead comes in, gets qualified, becomes a deal, becomes a customer, gets invoiced", a platform will model it well and you should use one.

The trouble starts with the exceptions that define your business: quotes that depend on measurements from a site visit, approval chains that change by contract value, pricing that depends on inventory, jobs that split across crews, partner commissions calculated on collected cash. Each can often be forced into a platform, but every forced fit is a workaround someone has to maintain.

Rule of thumb: if more than a third of your core workflow needs workarounds, custom software is on the table.

Question 2: What is the total cost over five years, honestly?

Platform costs scale with seats and tiers, and the tiers you need tend to be the expensive ones. A twenty-person team on a mid-tier CRM plus add-ons for quoting, automation and reporting can easily spend more over five years than a custom build would cost, and they still do not own the data model.

Custom software costs more up front and requires a maintenance agreement, but seats are free and the system does exactly what the business needs. The honest comparison includes licences, add-ons, consultants to configure the platform, the staff time spent on workarounds, and the maintenance budget for custom work. Do the arithmetic for your numbers; it rarely comes out the way the sales deck says.

Question 3: Who owns the data and the logic?

With a platform, your data is exportable but your automations, reports and custom objects are not portable. Leaving means rebuilding. With custom software, you own the code, the database and the documentation, and you can change vendors.

That matters more than it sounds. Businesses are bought, merged and restructured. The ones with portable systems have options.

Question 4: What else must the system talk to?

Make the list: accounting, phone system, website forms, calendars, field apps, e-commerce, payment providers, marketing tools. Platforms have ready-made connectors for the common ones. Custom systems integrate through the same APIs, with the advantage that the integration can be shaped around your data instead of the connector's assumptions.

If a critical integration does not exist for a platform, the price of the platform just went up by the cost of building it anyway.

Question 5: Is there an owner on your side?

Any system, custom or platform, fails without someone inside the business who owns it: decides on changes, trains new staff, keeps the data clean. If nobody can own it, pick the simplest platform setup you can live with and revisit in a year.

The hybrid path most businesses should take first

In our experience the best answer is often neither pure platform nor pure custom:

1. Run the standard parts (contacts, pipeline, email) on a platform.
2. Build the parts the platform cannot model (quoting engine, customer portal, field workflow, specialised reporting) as custom software integrated with it.
3. Keep the custom parts small and well documented, so they can grow or be replaced without touching the rest.

This gets you a working system quickly, keeps costs proportionate, and lets you learn exactly which pieces deserve a bigger investment.

Signs you have outgrown the platform

• Staff keep a parallel spreadsheet "because the CRM can't do X".
• Reports need a consultant or an export to Excel every month.
• Add-on costs are rising faster than revenue.
• Customers cannot see their own status without calling.

If two or more apply, it is worth a structured look. Request a consultation and we will assess your current setup and recommend platform, custom or hybrid, in writing, before any build is proposed.