Yes, you can have a CRM built around how your business actually works, and own it outright. It makes sense when your process does not fit a sales pipeline, when you are paying for seats that people barely use, or when the data has to live in your own database. If your process is the ordinary pipeline of enquiry, quote, follow-up and close, a subscription CRM is usually the better call, and I will tell you so.
What can a custom CRM do that an off-the-shelf one cannot?
It can model the things your business actually deals in. WeCoza, which I built for a training provider, tracks learners, classes, attendance and QA visits. None of those is a deal moving through a pipeline, and forcing them into one is where off-the-shelf CRMs start costing more in workarounds than in seats.
Your rules can be enforced where nobody can skip them. On WeCoza a class cannot go live until its agent order is complete, and the database itself refuses anything else. I wrote up why the data lives in Postgres for exactly that reason.
Each person gets only the screen they need. A field agent can see just their own jobs while a manager sees the whole operation, and you stop paying a monthly seat for someone who only ever opens one form.
And it connects straight to what you already run: Payfast or Yoco for payments, WhatsApp for reminders and confirmations, The Courier Guy for deliveries, and your accounting system.
How does a custom CRM get built?
- It starts with a short call, where you describe how the work actually flows, including the parts nobody likes. Within 48 hours you have a fixed price in writing.
- The data model comes before any screens. The people, records and rules are written down in a form you can read without knowing SQL. On WeCoza that is a hand-maintained schema file the client reviews, so when requirements change we talk about tables and relations.
- You see working software every week, with your real data in it, so a wrong assumption costs a week rather than a quarter.
- At handover you get documentation your next developer can use, and code you own.
What drives the cost?
- Every kind of user needs its own screens and permissions, so more roles mean more build.
- What it connects to matters most. A payment gateway with good documentation is quick. An old system with no API takes longer, and you should hear that before the work starts, not in week three.
- Data already sitting in spreadsheets nearly always needs cleaning before it can move.
- A report that answers a real business question needs the data model designed for it from the start, so decide on reporting early.
- Running it afterwards costs something too: hosting, backups and changes as the business moves.
Should you build or buy?
A subscription CRM charges per user per month, and the big names, HubSpot and Pipedrive among them, bill in US dollars. It is cheap to start and grows with every seat you add. A custom CRM costs more up front and has no per-seat fee; what you pay afterwards is hosting and upkeep.
Buy when your sales process is the ordinary pipeline and the team is small. Build when the process itself is what sets you apart, or when you are paying seats for people who need one screen.
There is a middle route that suits plenty of businesses: keep the CRM you already pay for and connect it to your other systems through its API, so that orders, invoices and support tickets all land in one place. That is an integration job rather than a build.
What does POPIA expect of a CRM?
Whether you build or buy, you are the responsible party under the Protection of Personal Information Act, and the CRM is where most of your customers’ personal information lives. The Act asks for these things in particular:
- a lawful reason for holding each record, and proof of consent where consent is your reason (section 11)
- no more information than the purpose needs (section 10), kept no longer than it needs (section 14)
- a way to show someone what you hold on them, and to correct or delete it on request (sections 23 and 24)
- reasonable security measures (section 19), and a written contract requiring the same of whoever hosts or processes the data for you, whether that is a CRM vendor or a developer (section 21)
- an opt-out on every direct marketing message (section 69)
- a lawful basis for moving data out of South Africa, which applies to any CRM hosted offshore (section 72)
That is the Act’s text in plain words, not legal advice. A custom CRM can be built around these from the first table. With a subscription, check that the vendor gives you export, deletion and an operator agreement before you sign.
Sources
- Protection of Personal Information Act 4 of 2013, as gazetted
- The estimate above is drawn from ranges published by South African developers, including Muon Software, CodeLab One and Bizvino, read on 19 October 2026