CRM · 6 min. readNew
Custom CRM vs HubSpot or Zoho: When Building Your Own Makes Sense
Most businesses should keep adapting a good off-the-shelf CRM. Building your own makes sense when the process, the integrations or a client portal are central to the business, and the workarounds cost more than a build.
The short answer
Most businesses should keep adapting a good off-the-shelf CRM. Building your own makes sense when your process, your integrations or a client-facing portal are central to how the business works, and the workarounds now cost more than a build would.
HubSpot and Zoho are capable tools, and many businesses run well on them. This article is not about whether they are good. It is about fit: what happens when a business has shaped its work around a CRM for a few years, and the CRM has started to shape the work back.
Working around a CRM has a cost: hours spent copying figures between tools, enquiries that slip between systems, and decisions made without the full picture. This guide is for that stage. You already have a CRM, the team works around it every day, and you are wondering whether to keep adapting it, extend it, or replace it with something built for you.
Signs you have outgrown your CRM
Outgrowing a CRM rarely happens all at once. It shows up as small workarounds that quietly become part of the routine. These are the signs worth taking seriously:
- Spreadsheets kept alongside the CRM. Quotes, stock, orders or commissions live in a spreadsheet because the CRM has nowhere sensible to put them, and someone copies figures between the two.
- Quoting or approvals the tool can’t model. Your proposals depend on measurements, options, margins or sign-off steps, and the CRM can only hold them as notes or attachments.
- Several tools stitched together. Enquiries arrive in one place, proposals are written in another and invoices in a third, with connectors passing data between them. When one connection breaks, it can go unnoticed for days.
- Clients asking for their own view. Customers or investors email to ask where their order, project or portfolio stands, because there is nowhere they can check for themselves.
- Marketing you can’t trace to signed work. You can see which campaign produced a form fill, but not which one produced a signed contract or a paid invoice.
One of these on its own is usually a set-up problem. Several together, every week, suggest that the CRM’s model of your business no longer matches the business.
The options in between
Replacing a CRM is not the only answer, and it is rarely the first one to try. Between living with it and building your own, there is a range of options:
- Change the set-up. Custom fields, pipelines, stages and automations solve more than people expect, especially if the CRM was set up quickly years ago and never revisited.
- Add integrations. A connector or middleware between the CRM and your accounting, payments or advertising tools can remove a lot of copying by hand.
- Move to a higher plan. Some of what you are working around may sit in a plan you are not on. Check the vendor’s current plans on its own site, because they change.
- Build alongside it. A custom tool or a client portal can sit next to the CRM, so the CRM keeps doing what it does well and the custom part handles what it can’t.
- Replace it. A CRM built around your process, with the integrations and the client view designed in from the start.
Be fair to the middle options. They are cheaper, quicker and less disruptive than a replacement, and for many businesses they are enough. The case for replacing is strongest when you have tried them and the same problems keep coming back in a new form.
What to weigh before you decide
When the middle options are not enough, the decision usually comes down to five questions.
Does it fit how work actually moves?
Write down how work moves through the business, from first enquiry to paid invoice. Then mark every step the CRM handles well, every step it handles badly, and every step that happens outside it. If most of the important steps sit in the last two groups, the tool is the wrong shape for the business.
What does it need to connect to?
List the systems the CRM has to talk to: accounting, payments, advertising, stock or supplier data. An off-the-shelf CRM may connect well to the popular ones and not at all to the specialist ones. A custom build can connect to the systems you choose, but every connection is something that has to be built and then kept working.
Do your clients need to log in?
If clients need to see their own orders, documents or portfolio, ask whether that view should come from the same data your team uses. A portal attached to a separate system tends to drift out of step with it.
Where is your data, and how does it leave?
Whichever route you take, ask the supplier plainly: where is the data held, who can access it, in what format can it be exported, and what happens to it if you stop paying or move to someone else? These questions matter as much for a custom build as for a subscription, and the answers should be in writing.
What does it cost over several years?
A subscription is usually priced per user, so it grows with the team and the plan. A custom CRM costs more at the start, then needs hosting, maintenance and changes for as long as you use it. Compare the two over several years rather than one, and include the hours your team spends on workarounds today. Upkeep is a real cost: software that nobody looks after builds up technical debt.
How a custom CRM is scoped
A custom CRM should not start with screens. It starts with the process.
- Map the process. How enquiries arrive and are qualified, how proposals are written and approved, how work is delivered and invoiced, who does each step and what they need to see.
- Define the data. The things the business tracks, such as clients, leads, proposals, orders, products and payments, and how they relate to each other. This is where off-the-shelf tools most often force a compromise, and where a custom build has to get it right.
- Agree the integrations. Which systems the CRM reads from and writes to, and which one is the source of truth for each piece of information.
- Build in stages. Start with the part that causes the most work today, put it in front of the team, and shape the next stage around what they learn. A first stage that people use is worth more than a complete specification that never ships.
When the CRM no longer matches how work moves, see Sales & CRM for where connected systems and AI can help, and Systems Integration for connecting the CRM to the tools you already use. A custom build is one option, not the default. Each project is quoted after we scope what it needs to do.
The takeaway
Keep your off-the-shelf CRM for as long as it fits, and spend time on its set-up and integrations before you spend money on a build. When the workarounds have become the process, write them down. That list will tell you whether you need a better set-up, a custom tool beside the CRM, or a CRM built around how your business works.
If you are at that point, see an illustrative example of one enquiry moving through connected systems, from first contact to completed project, with people approving the important steps. Then tell us what your CRM needs to do: Discuss your AI strategy.
In short
This guide is for an established business that already uses HubSpot, Zoho or a similar CRM and keeps working around it. Signs of outgrowing a CRM include spreadsheets kept alongside it, quoting or approvals it cannot model, several tools stitched together, clients asking for their own view, and marketing that cannot be traced to signed work. Before replacing it, the options in between are changing the set-up, adding integrations, moving to a higher plan, or building a custom tool or client portal alongside it. The decision rests on fit to the process, integrations, a client portal, where the data is held and how it can be exported, and cost over several years. A custom CRM is scoped by mapping the process, defining the data, agreeing the integrations and building in stages. Where the CRM no longer matches how work moves, DBETA starts by mapping the process, then helps adapt and connect the current CRM or scopes a custom build, quoted after scoping.
Questions about this article
When the process, the integrations or a client portal are central to how the business works, and the workarounds around the current CRM cost more than a build would. For most businesses, a good off-the-shelf CRM with a careful set-up is enough.
Where the data is held, who can access it, what format it can be exported in, and what happens to it if you stop paying or move to another supplier. Ask the same questions of a subscription and of a custom build, and get the answers in writing.
It depends on the process, the data and the integrations, so we quote custom CRMs after we scope what the system needs to do. Compare any quote with your current subscription over several years, plus the time your team spends on workarounds.