DELIVERY PROCESS
How we work.
Seven steps, in this order, on every project we take. The detail below is what each one produces, what we need from you, and roughly how long it takes.
Free 20-minute call. We will tell you honestly if we are not the right fit.
THE PROCESS
Seven steps. No surprises.
Step three is where most projects go wrong elsewhere, so it is the one with a weekly demo attached.
01
Discover
We learn how you actually work, not how the manual says you should.
- You get
- A written summary of how your process actually runs, including the workaround nobody documented.
- We need
- Two hours with the people who do the work, not only with the people who manage it.
- Typically
- 3 to 5 working days
02
Plan
A written scope with fixed pricing and dates. You approve before we start.
- You get
- A scope document with a fixed price, fixed dates, and what is explicitly out of scope.
- We need
- One decision-maker who can approve it, and your accountant for anything financial.
- Typically
- 3 to 7 working days
03
Build
Weekly demos. You see progress, not status reports.
- You get
- A working system you can log into, demonstrated every week from week one.
- We need
- One hour a week from one person, and your real data to test against.
- Typically
- 2 weeks for a website, 6 to 10 weeks for an ERP
04
Deploy
We migrate your data and go live outside working hours.
- You get
- Your data migrated and reconciled, and the system live. Cut-over runs outside working hours.
- We need
- A signed-off opening balance and an agreed date to stop capturing in the old system.
- Typically
- One evening, plus the following morning on site
05
Train
Your team, in person, until they are comfortable.
- You get
- Training per role on your own data, and a written guide your team keeps.
- We need
- Your team, in a room, for two hours per role. This is the step clients try to skip.
- Typically
- 1 to 3 days depending on how many roles
06
Support
Named contact. WhatsApp included.
- You get
- A named contact on WhatsApp, a response-time commitment, and a monthly check-in.
- We need
- Somebody on your side who owns the system internally.
- Typically
- Ongoing, from go-live
07
Scale
The system grows as you do.
- You get
- A quarterly review of what is now slowing you down, and what is worth building next.
- We need
- Twenty minutes a quarter.
- Typically
- As long as it is useful
THREE RULES WE DO NOT BEND
What makes the process hold.
Weekly demos, from week one
You see the system, not a status report. A project that cannot be demonstrated in week one is a project that is not being built yet, and you should know that in week one rather than in week six.
The scope is a document, not a conversation
What is in, what is out, what it costs, when it lands. Changes are priced and approved before they are built. This is what makes a fixed price honest rather than a trap for one of us.
Go-live happens outside working hours
Data migration and cut-over run in the evening or over a weekend, so nobody loses a trading day to our schedule.
QUESTIONS
The five we are asked before every project.
What happens if the project runs late?
We tell you in the weekly demo where it first slips, not at the deadline. If the delay is ours, the price does not move. If it is caused by something we need from you and did not get, we reschedule and say so plainly at the time.
Can we change the scope halfway through?
Yes, and most clients do. A change is written up with its cost and its effect on the date, and you approve it before we build it. What we will not do is absorb changes silently and hand you a different invoice at the end.
Who owns the code you write for us?
For custom software, you do, as set out in the contract. For our own products you hold a licence and your data remains yours, exportable at any time.
Do you work on site or remotely?
Discovery, training and go-live are on site where you are in reach of Harare. Build is remote with weekly demos. Implementation across the rest of Zimbabwe is remote, with on-site training by arrangement.
What do you need from us to start?
One decision-maker, two hours with the people who do the work, and access to your current data. Projects stall on the second of those far more often than on anything technical.
BEFORE THE FIRST CALL
Three things make the first twenty minutes useful.
The process that hurts
One specific thing — the month-end close, the fee arrears report, the enquiries nobody answered. Specific beats broad every time.
What it costs you now
Hours, errors or money. A rough figure is enough. It is what tells us whether building anything is worth it.
Who decides
If the person who can approve a scope is not on the call, we will need a second one. Better to know that before we book the first.
NEXT STEP
Start at step one.
Discovery is a conversation, not a commitment. If what you need is smaller than you thought, we will say so and tell you what it should cost.
Free 20-minute call. We will tell you honestly if we are not the right fit.