Custom systems, automation, payments, and AI
We replace the spreadsheets, the retyping and the chasing with software that does it itself - and AI where it genuinely earns its place. Built by people still here the year after launch.
Free, thirty minutes, and you leave knowing whether you need us. Already built something and worried about it? Have it reviewed first.
What we build
Most of what we build is operations and automation. If what you need is not on this list we will say so on the first call rather than three weeks in.
Customers, orders, stock, approvals, and the reports you make decisions from. Built around how the work already passes between people, not around a template.
The steps nobody should be doing by hand - chasing, checking, filing, sending. Automated where the rules are clear, and left alone where judgement is needed.
Reading supplier invoices and IDs so nobody retypes them, sorting what comes in, drafting replies. A person still approves anything that moves money.
Mobile money, card, bank transfer and cash, recorded once and matched to the right invoice - so the month end agrees with your statement without anyone going down it line by line.
What a build covers in full, including the parts about security, speed, and being handed over properly.
Where you are now
The argument is different depending on whether you have software already. Both of them end somewhere useful, including the ending where you do not need us.
Still on spreadsheets
Orders in WhatsApp, stock in a book, invoices in Excel, and one person who knows where all of it is. It works. It also means every new customer adds a little more typing, and the month end takes the same three days it always did.
What changes is capacity: the same team handles more, because the work that never needed a person stops needing one.
Already running something
It was built for a smaller business, or by somebody who has moved on, or quickly by an AI tool. Now it is slow, nobody will touch the risky parts, and half the team keeps a spreadsheet alongside it anyway.
We read it before we say anything. Sometimes the answer is a rebuild; more often it is three fixes and the thing has years left in it.
How we work
Nobody can price a system honestly off a phone call, so we do not try. You buy a week of the people who would build it, and you leave with a fixed price - whether or not you spend it here.
Change your mind on paper, not in week nine.
The expensive mistakes in a build are all made in the first week, by people in a hurry: the wrong shape for your records, the integration nobody checked, the word 'finished' meaning two different things to two people. We go looking for them while they still cost nothing to fix.
What you walk away with
And then, depending on what it finds
Not sure which one you need? and we will tell you which one fits - including when the answer is that you do not need us at all.
What usually goes wrong
These are the calls we actually get, in the order they cost the most. None of them show up while somebody is still building it. All of them show up once you have real customers.
Every one of these happens after the invoice is paid, which is what Care is for. Already built something and want it checked instead? The whole review checklist is published, so you can go through your own against it for free.
Our own software
Zana and SiteBooks are ours. Real invoices going out, real M-PESA coming in, real wages being paid, every day. Whatever we know about what breaks once customers show up, we learned it the expensive way, on our own money.
The operating system for recurring revenue
If you bill the same customers every month, Zana is the system you run it on. Raise the invoice, collect it by M-PESA, card, or bank, chase whoever has not paid, and pay your own suppliers - all on one ledger, so what a customer owes you is always a single number.
The reconciliation nobody else does
Upload the M-PESA or bank statement you already get - CSV, Excel, or a scanned PDF. Zana reads every deposit, proposes the invoice it settles, and leaves only what it cannot prove for a person to decide. Re-uploading an overlapping statement never double-posts a payment.
kinds of business on one ledger
accounts in a single billing run
a month to start
Build with confidence, manage with clarity
Construction management for contractors and the diaspora clients paying for the build. Time-stamped site photos, budgets tracked against the BOQ, milestone payments, and M-PESA payroll for casuals - so a client in London can see what happened on site this afternoon.
Built for builds you cannot visit
The hard problem in construction here is not scheduling - it is trust across eight time zones. SiteBooks is shaped around that: a foreman logs progress in under a minute on 3G, and the person paying for it reviews the evidence from their phone before bed.
first, by design
payroll for casuals
is the target, not an edge case
If Zana already does what you were about to pay us to build, we will tell you.
Honest, opinionated posts on payments, communication, and the operations behind them.
M-PESA STK delays, mandatory account creation, missing guest checkout, broken mobile UX, and the friction that turns a hot WhatsApp lead into an abandoned cart.
Read moreDaraja callbacks are not always reliable. When to poll the Transaction Status endpoint instead, how often, and how to avoid duplicate ledger entries.
Read moreWhy cPanel-bundled email is losing you customers, real costs of staying, and how to migrate to Google Workspace, Microsoft 365, or Zoho Mail without losing a single email.
Read moreTell us what is slowing the business down and we will come back with what would fix it, how long it takes, and what it costs. If the answer is that you do not need us, we will say that instead.
Or reach us directly
Weekdays, and we answer the same day.
No matching results
Try M-PESA, WhatsApp, website, email, or contact.
How we work together
Aria
Noria assistant
Hi, I'm Aria. Tell me what is going wrong - a website you need, an app you are not sure about, or M-PESA that will not add up - and I will point you to the right thing.
