Custom CRM vs Off-the-Shelf: HubSpot, Salesforce or Bespoke?

Every growing company reaches the point where its CRM either becomes the backbone of the business or the thing everyone quietly works around. Here is when HubSpot or Salesforce is the right call, when a bespoke system earns its keep, and what each really costs.

Should a small business use a custom CRM or HubSpot?

Most small businesses should start with HubSpot, Salesforce or a comparable off-the-shelf CRM, and only consider building custom once they have a process worth protecting. The right question is not which option is better in the abstract, but whether the way your company works is a genuine advantage or simply a habit.

If your sales motion is conventional — leads come in, someone qualifies them, deals move through four or five stages, contracts get signed — you will not out-build HubSpot's contact management, email sequencing or reporting for anything close to its price.

The calculation changes when the CRM is not really the problem. Many companies are not struggling with contacts and deals at all; they are struggling with what happens after the deal: quotes, jobs, approvals, invoicing, delivery. Off-the-shelf CRMs are built for the front of the funnel, and no amount of configuration fixes pain that sits behind it.

When is off-the-shelf software the right choice?

Off-the-shelf wins when you need to be live in weeks, when your process fits a standard pipeline, and when you want to plug into an ecosystem of integrations rather than build them. HubSpot and Salesforce have earned their positions honestly, and for a company under roughly 20 users with a conventional sales process, they are usually the correct decision.

Their real strengths are worth naming precisely:

• Speed to start. A HubSpot Starter account can be running the same afternoon. Salesforce takes longer to configure well, but a competent partner can have a small team live in four to six weeks.
• Ecosystem. Both have thousands of native integrations: calendar, telephony, e-signature, accounting, marketing automation. If you are trying to build a B2B marketing pipeline, HubSpot in particular gives you forms, email, landing pages and attribution in one place.
• Hiring and upkeep. Your next sales manager already knows the tool, and both vendors ship features monthly that you would otherwise pay to build.

The costs are equally concrete. HubSpot Sales Hub Professional runs at roughly £80 to £90 per seat per month, with Enterprise above £130 per seat, plus a mandatory onboarding fee in the low thousands. Salesforce Sales Cloud moves from around £20 per user on Starter to £130 or more on Enterprise, and the features mid-sized companies actually want — workflow automation, custom objects, decent reporting — live on the higher tiers. The tier jumps are the trap: the moment you need one Enterprise feature, every seat moves to Enterprise pricing.

The subtler cost is process. Every off-the-shelf CRM has an opinion about how a business should operate, and your team will gradually bend to match it. That is expensive when it forces a job-based or project-based business into a deal-based mould.

When does a custom CRM or management system win?

A custom CRM or bespoke management system wins when your process is genuinely unusual, when licence costs are rising faster than revenue, or when the team is running the real business in spreadsheets and messaging threads around the CRM rather than inside it. Of the three, the third symptom is usually the most reliable signal.

Look for these patterns:

• The spreadsheet shadow system. Sales lives in HubSpot but operations lives in a 40-tab Excel workbook, and someone spends every Monday reconciling the two. That reconciliation is a system you are already paying for, just badly.
• Seat inflation. You have 35 people who need to see records but only eight who work deals, and you are paying full seats for all of them. Bespoke systems have no per-seat licence; adding a user costs nothing.
• A process that is your edge. If the way you quote, schedule, approve or deliver is what clients choose you for, it should not be constrained by a generic tool. Field services, agencies with complex production workflows and distributors with bespoke pricing rules are classic cases.
• Data you cannot get out. When the board report requires three exports and a pivot table, the tool is no longer serving the business.

What a bespoke system is not: a from-scratch rebuild of HubSpot. The best builds are narrow and deep. They own the distinctive parts of the business — jobs, quotes, approvals, client portals, operational reporting — and integrate with commodity tools for the rest. Nobody should rebuild Xero.

What does a custom CRM actually cost?

A focused bespoke CRM or management system for a small or mid-sized UK company typically costs between £15,000 and £60,000 to design and build, followed by ongoing support of roughly 10 to 20 per cent of the build cost per year. The wide range reflects scope: a clean client-and-jobs system with a portal sits at the lower end; a full operational platform with approvals, scheduling, invoicing integration and role-based reporting sits at the upper end.

The fair comparison is over three to five years, not year one. Take a 25-person company on HubSpot Sales Hub Professional at around £85 per seat per month:

• Year one: roughly £25,500 in licences plus onboarding.
• Five years: around £127,000, before the price rises that have historically run well ahead of inflation, and before a single Enterprise-tier upgrade.

A £40,000 build with £6,000 a year in support costs around £64,000 over the same period. Bespoke is not automatically cheaper — at ten seats the arithmetic favours HubSpot — but at 20 or more seats, or with any Enterprise feature in play, custom usually pulls ahead by year three.

Add the hidden line items to the off-the-shelf side: the coordinator reconciling spreadsheets, the integration subscriptions patching gaps, and the time lost when a one-minute process takes fifteen. None of it appears on a licence invoice.

How do you build a custom system without it becoming a mess?

Custom systems become a mess when they are scoped by feature wishlist rather than by workflow, when nobody owns the data model, and when the build is treated as a one-off project rather than a living product. All three are avoidable.

The method we favour on custom systems and CRM work:

1. Map the real process first. Not the org chart, and not the process the founder describes; the one the team actually follows, including the workarounds. The workarounds are where the requirements live.
2. Design the data model before the screens. Clients, jobs, quotes, people, approvals and their relationships. Get this right and the interface follows; get it wrong and every feature fights it.
3. Build the narrowest useful version. One workflow, end to end, in production within eight to twelve weeks. Ship, watch people use it, then expand.
4. Integrate, do not replicate. Accounting stays in Xero, email stays in Google or Microsoft, signatures stay in DocuSign. The bespoke system orchestrates them.
5. Plan for support from day one. Budget for it, name an owner inside the company, and agree how changes are prioritised. A system nobody maintains decays within eighteen months.

The same discipline applies whether you redesign or rebuild your website or replace an internal system: the question is which parts are broken and which are simply old, and the answer is rarely everything.

The takeaway

Off-the-shelf CRMs are the correct default for most small businesses, and HubSpot and Salesforce deserve their reputations for speed and ecosystem. The case for bespoke opens when your process is genuinely distinctive, when seat counts push licence costs past what a build would have cost, or when the real business is already running in spreadsheets around the tool. Judge it over five years, scope it around workflows rather than wishlists, and build only the parts that make your company different.