How we scope, quote and deliver

Before you talk to us, go and use one. Mobile money collection, single sign-on, record-level permissions, WhatsApp at scale, escrow, document signing, applied AI: each is running in one of our own products, and the capability list tells you which.

Working software you can sign into tells you more about how a team builds than any deck we could send you.

We do not quote from a brief on a call. The sequence is:

1. 01You describe the problem, who has it, and what has been tried.
2. 02We work through it with you until the scope is written down and you agree it is right.
3. 03You get a written quote in kwacha against that scope, with what is and is not included.
4. 04Work starts once scope and quote are both agreed.
5. 05You see working software as it is built, not at the end.

If the scoping conversation shows that one of our own products already does the job, we will say so. It is a smaller sale and a better outcome.

Business software for the Zambian operating context: collecting money through the rails people here use, working over WhatsApp, producing reporting the ZRA accepts, and standing up to an enterprise security review. That is where our own products live, so it is where our judgement is worth paying for.

Outside that, ask. We would rather turn work down than learn on your budget.

The same team that built and runs our own products. Nothing is subcontracted, and you deal with the people writing the software rather than an account manager.

Every engagement is priced per scope, in kwacha, in writing, before work begins. Where a scope is genuinely fixed we price it fixed and say so in the quote. For what the products themselves cost, see prices.