Home / How we work

Fixed scope, fixed price, and no black boxes.

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.

No sales call, no calendar booking. We reply within one business day. POPIA-compliant.

From problem to live system.

Discover

Week 1 to 2

We sit with the people who actually 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.

  • Process mapping with the team doing the work
  • Cost of the current process, quantified
  • Success criteria agreed in writing

Design

Week 2 to 3

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 or hybrid, with the reasoning
  • Tool costs evaluated on ZAR total cost of ownership
  • Fixed scope and fixed price, signed off

Implement

The bulk of the engagement

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.

  • Fortnightly demos of working software
  • Tested against your real data, not sample data
  • Built to survive interrupted connectivity

Embed

Go-live plus 30 days

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.

  • Team training and written documentation
  • Accounts and credentials in your name
  • 30 days of post-launch support included

Three ways to engage us.

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 actually solves it.

Fixed scope

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.

Retainer

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.

Embedded

We work 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.

All three are priced in rands. Send us the process and we will tell you which one you actually need.

Contact us
Would rather just talk it through? Book a 20-minute call.

Questions we get asked first.

How long does a typical implementation take?

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.

What does it cost?

It depends on the process, so we will not pretend there is a list price. What we can commit to is that the number is fixed before any building starts, it is quoted in rands, and 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.

What happens if the scope changes mid-project?

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.

Do we own the system when you are done?

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.

Do you work with businesses outside South Africa?

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.

Start with the discovery step.

Four questions about the process is 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.

No sales call, no calendar booking. We reply within one business day. POPIA-compliant.

Contact us
Would rather just talk it through? Book a 20-minute call.