Custom CRM vs HubSpot, Zoho and Pipedrive for a South African small business
I build custom CRMs, so you'd expect me to tell you to buy one. Sometimes you shouldn't. Here's how to tell which side of the line your business is on — with the trade-offs the sales pages leave out.
A CRM is the software where your leads, clients and deals live: who they are, where each one is in your process, and what happens next. Every business that sells anything has one — even if, today, it's an inbox and a WhatsApp group. The question is whether to rent a packaged one or build one around how you actually sell.
Start with the honest case for the packaged tools
HubSpot, Zoho and Pipedrive are good products. They exist because thousands of businesses have a similar enough sales process that one piece of software can serve them all. If these describe you, buy one and stop reading:
- You need it working today. Sign up, import a spreadsheet, and you have a pipeline this afternoon. A custom build takes about two weeks for a proven system — fast, but not this afternoon.
- You want marketing automation with it. Email sequences, landing pages, lead scoring, ad integrations. The big platforms have spent years on this. It would be foolish to rebuild it for you.
- Your process is standard. Lead → qualified → proposal → won, a handful of fields, one or two people. The free tiers were designed for exactly this, and free is hard to beat.
- You have a sizeable sales team that already knows one of these tools. Retraining people is a real cost that never appears on a quote.
Where they start to hurt
The same things that make a packaged CRM quick to start make it expensive to live with for a certain kind of business — and South African small businesses are disproportionately that kind.
Per-seat pricing, in dollars
Packaged CRMs charge per user per month, priced in US dollars. The free tier is generous right up until you need the one feature that isn't on it — then everyone who logs in moves to a paid seat. Ten people on a mid-tier plan is a meaningful monthly bill that rises every time the rand moves and every time you hire. You pay for growth twice.
Your process bent to fit their boxes
Every packaged CRM has stages, fields and a vocabulary. You can rename some of them. You can't make a security company's "site survey → risk assessment → PSIRA compliance check → quote" feel natural in software designed around "demo booked". Teams respond by keeping the real process in a spreadsheet next to the CRM — at which point you have two systems and trust neither.
Integrations that almost work
The CRM knows about the deal. Your quoting knows about the quote. Your invoicing knows about the invoice. Getting one to talk to the other means a middleware tool, another subscription and a joint that breaks quietly every few months. The three tools were never designed as one system, because they aren't one.
Where the data lives
Your client list sits on servers you've never seen, under terms you didn't write, with export tools that get harder to find as you go up the tiers. For POPIA that's usually fine on paper; in practice it's worth knowing that you can take all of it out on a Tuesday afternoon if you want to.
The honest case for a custom CRM
A custom CRM is small and exact. It has your stages, your fields, your probabilities and your sign-offs — nothing you'll never open. Mine is priced per business, not per seat: setup from R4,999, then from R2,499 a month, however many people log in, with hosting, support and backups included. It's built to hand a won deal straight into a quote and then an invoice without retyping, because those are one system, not three.
It's the right call when:
- Your process is genuinely yours. Inspections before quotes, compliance steps, multiple sign-offs, a handover to operations that keeps getting lost.
- You're paying per seat and growing. The maths flips fast: a custom monthly that doesn't change when you hire beats a per-seat bill that does.
- You want the CRM, quoting, invoicing and job tracking to be one thing — typed once, carried through.
- You want one person who knows exactly how it works, rather than a help centre and a ticket queue.
Be clear about what you're buying
"So if I build a custom one, I own it?"
You own your data — always, exportable at any time in standard formats, and if you ever cancel you get a full export and your access ends. The system itself is licensed to you for as long as the plan runs, in the same way a packaged CRM is; the difference is that this one was shaped around you and never charges per seat. Owning the source code outright is a separate buyout, and I'll say so plainly rather than let anyone assume otherwise. If you want to see what you'd actually be logging into, the custom CRM page has a working demo — click around it before you talk to me.
A fair way to decide
- Write your real sales process on one page, in your own words. Count the steps that don't map onto "lead, qualified, proposal, won".
- Count the people who need to log in, now and in a year. Multiply by a per-seat price in rand at today's rate.
- List what the CRM needs to hand off to — quoting, invoicing, job cards — and whether "we'll export a CSV" is really acceptable.
- If the first list is short and the second number is small, buy the packaged tool. If either is long, the custom one will cost you less and fit better — and I'd rather tell you which it is in 20 minutes than sell you the wrong one.
Not sure which side of the line you're on?
Twenty minutes, your process on a page, and a straight answer — including "buy the packaged one".