Process
Consult. Design. Build. Run. Each phase ends with something you can hold.
This is the same four-phase shape the parent company runs in South Africa, with the Zimbabwe checks added: channel realities, licensing, fiscalisation and currency. Nothing is built before the scoping document says what, why and what it needs.
- 01
Consult — find the one thing
A 20–30 minute call (or the worksheet first, which makes the call shorter). We map one real process: what triggers it, what should happen, who decides, what "done" is. We say out loud if it is not worth automating yet.
You get: a one-page note with the candidate first build and the questions to answer.
- 02
Design — the scoping document
Flow diagram, the rules, the exceptions, the approval points, the systems touched, the data handled (with your data-controller obligations noted), the fiscal boundary if invoices are involved, and the currency rules. A fixed price for the build comes out of this, not before.
You get: the scoping document and a fixed build quote.
- 03
Build — on your accounts
Everything is set up in accounts you own (Meta, CRM, hosting) so you are never locked to us. Test with staff phones and copies of real data. Templates submitted to Meta early because approval takes time.
You get: a working system on real traffic, a runbook, and a named person on our side.
- 04
Run — pilot, then improve
Two to four weeks with a person watching every handover and every exception. Weekly list of what the system could not do. Then a monthly cadence: metrics, tuning, the next small build. You can stop at any month.
You get: a monthly report with the numbers that matter for your build (reply time, handled rate, no-shows, hours saved).
What moves the timeline
- Meta business verification. One to three weeks and outside anyone's control; we start it on day one of the build.
- Your answers. Price lists, policies, who approves what. The build waits for these more than for code.
- Systems without an API. A sheet connects in a day; a desktop accounting package with no API needs a bridge.
- Data state. Contacts across five phones take a week to normalise and merge.
- Public holidays and school terms. Real, and we plan pilots around them.
What we will not do
- Build before the scoping document is agreed.
- Auto-approve anything touching money, credit or a complaint unless you have decided it should be.
- Issue fiscal invoices from automation; that step stays on your FDMS-integrated device.
- Send marketing messages to people who have not opted in.
- Lock you in: accounts, data and flows are yours.
Next step
Scope it before you book it
Fill in the scoping worksheet (five minutes, no sign-up). It produces a summary you can paste into WhatsApp or email, so the first call starts with the actual work.