Home / How we work
Most implementation projects go wrong in the same two places: nobody agreed what done meant, and nobody saw the work until it was finished. We run a four-step cycle designed to remove both, and we run it forward deployed: inside your team, on your real data.
Book a call if you want one, or just send the form. We reply within one business day. POPIA-compliant.
Every project runs four steps: discover, design, implement, embed. We agree scope and price in writing before building, show working software every fortnight, and train your team to own the result. Most projects go from scope to live in six to twelve weeks.
We sit with the people who run the process and map it as it works today, not as the org chart says it works. Then we put a number on the friction: hours lost, errors caught late, revenue sitting in a queue.
You get a written picture of the current state and an agreed definition of what success looks like in numbers, before anyone talks about tools.
We decide what to build against what to configure. Sometimes the answer is a SaaS platform you already pay for and nobody set up properly. Sometimes it is custom software. Usually it is a hybrid, and we will tell you which without a preference for the more expensive option.
Scope and price are fixed at the end of this step. If we discover something mid-build that changes the scope, that is a conversation before it is an invoice.
Build, configure, integrate, test. Every fortnight you see the actual working system, not a status report on a slide. That cadence exists so that if we have misunderstood something, you find out in week four rather than week twelve.
We test against real data and real edge cases from your business, because the exceptions are usually where manual processes hide.
Training for the people who will use it, documentation for the people who will maintain it, and credentials in your name on accounts you control. The system belongs to your business, not to us.
We support it for 30 days after go-live. After that you can carry on alone, keep us on a retainer, or call us when something changes. All three are fine.
Which one fits depends on whether you have a defined problem, a continuing need, or a team that needs extra hands. We will recommend the cheapest one that solves it.
One defined problem, one agreed price, one delivery date. The default for a first engagement, because it caps your risk while you find out whether you want to work with us.
A set number of days a month for businesses digitising several processes in sequence, or who want the systems we built kept current as the business changes.
An engineer works inside your team for a defined period, using your tools and your stand-ups. For businesses with in-house capacity that needs implementation experience alongside it. How forward deployed engineering works.
All three are priced in rands. Send us the process and we will tell you which one you need.
Six to twelve weeks from scope to live for most engagements. Smaller pieces move faster: the billing and invoicing automation on our results page went from scope to live in three weeks. If something genuinely needs longer than a quarter, we will say so at the design step rather than discovering it halfway through.
It depends on the process, so we will not pretend there is a list price. What we can commit to: the price is fixed before any building starts, and it is quoted in rands. The conversation that gets you to a number costs nothing. Most first engagements are scoped deliberately small so you can judge the work before committing to more.
We stop and talk about it. A change that adds real work gets re-quoted and you decide whether it is worth it. A change that we should have caught during discovery is on us. What does not happen is a surprise invoice at the end.
Yes. Accounts, credentials and code sit in your name on infrastructure you control. We hand over documentation written for whoever maintains it next, including if that person is not us. We would rather you stayed because the work is good than because you are locked in.
Our focus is South African SMEs and mid-market firms, because that is the operating environment we understand: POPIA, loadshedding, ZAR pricing against dollar-denominated tools. We will take work elsewhere when there is a good reason, but it is not what we are built for.
It means the engineer who builds the solution works inside your business, with the people who run the process, on your real data and systems, until it is live and your team can run it. Every engagement model above works this way; the forward deployed model simply makes the time in your team the whole engagement. See the full explanation, with a six-question test, or how the service works.
Four questions about the process are enough for us to tell you whether it is worth automating, how we would approach it and roughly what it costs in rands, and to be straight with you if it is not worth doing.
Book a call if you want one, or just send the form. We reply within one business day. POPIA-compliant.