
Software & systems
Custom systems for the work your business actually does, not a package you have to bend around.
Who it's for
You are probably here because
-
01
You are running the business on spreadsheets, and they no longer agree with each other.
-
02
You bought a package and spend more time working around it than using it.
-
03
Two systems hold the same data and neither is trusted.
-
04
The person who understands the current system is about to leave.
What's included
What you actually get.
The common brief is not 'build us software'. It is 'four branches keep separate spreadsheets and month-end takes a week'. We start from the work, not from the software.
Inventory, POS and distribution
Stock across branches, dispatch, barcode picking.
School, clinic and SACCO management
Enrolment, records, billing, statements.
HR, payroll and field-force tools
Leave, attendance, field data capture.
Workflow and approval systems
Who approves what, and the audit trail behind it.
Integrations
M-Pesa, ERP, KRA eTIMS, and whatever else already holds your data.
Legacy migration and rewrites
Moving off something that still works but nobody can maintain.
How it runs
Each stage, and what it produces.
-
01
Discover
We sit with the people doing the work and watch the current process.
Output
A written process map and a shortlist of what to automate first.
-
02
Specify
Data model, screens, roles, integrations and a fixed quote.
Output
A technical specification.
-
03
Build
Two-week cycles, each ending in a demo against real data.
Output
Working software you can check.
-
04
Handover
Training, documentation, credential transfer, then support.
Output
Ownership, and a support contract if you want one.
What you are handed
- Source code and database schema, documented
- An administrator guide and a user guide
- Every credential and access route, transferred
- Thirty days of post-launch fixes
Technology
Proof
One project, in full.

Stock and dispatch system for a regional distributor
Four branches on separate spreadsheets, month-end taking a week.
One day
Month-end close
Four branches tracked stock in separate spreadsheets. Dispatch errors were routine, nobody could see group stock in one place, and month-end close took a week of reconciliation that one person held in their head.
One day
Month-end close
Four
Branches on one system
Single view
Group stock
Commercials
How buying this works.
Engagement
Discovery sprint, then a fixed-price build in milestones.
Price
On request, after scope
What sets the price
Number of user roles, how many systems it must talk to, how much existing data has to be migrated and cleaned, and how much of the current process is written down.
Data migration is the item most often underestimated. We price it separately and honestly.
Every project is quoted after we understand the scope. You will have a written, fixed quote before any build work begins. No open-ended billing.
Questions
Answered plainly.
Yes. The repository and every credential transfer to you on final payment. You are never locked to us to keep running what we built.
Yes, after a paid two-day audit. We read the code, run it, and give you a written opinion on whether to continue it or restart, with the cost of each.
You, on your own account, or us under a care plan. Either way the account is in your name and you hold the credentials.
Yes, via Daraja: STK push, C2B, B2C and reconciliation. We have shipped all four and we will tell you which fits your flow.
Thirty days of fixes are included, then a monthly care plan if you want one. Support is the product, not an upsell.
Yes. We can also supply engineers into your team on a day rate if that suits you better than a fixed-price project.
Often bought alongside
Build
Get a scoped quote for your system
Tell us what the spreadsheets are doing and we will tell you what to replace first.
We reply to every enquiry within one working day.