Adisoma Labs · Product engineering
I build the systems your business runs on, and make sure they keep running.
Billing, banking, ERP, point of sale, field operations. I start from what your business needs to achieve, build for the conditions you really work in, and leave you with a system your own team can run.
- building production systems
- 8+ years
- delivered and running
- 20+ systems
- billing, banking, payments
- Money-critical
- developers mentored and coached
- Teams trained
What you are actually hiring
A developer
writes the code you specify.
If the spec is wrong, you get the wrong thing, built well.
A consultant
advises on what you should build.
Often leaves before anything works in production.
A product engineer
owns the outcome, from the problem to the running system.
Understands the business, designs, builds, ships and stays accountable.
The gap
Most software projects disappoint in the same five places.
None of these are about talent. They are about habits. Here is what usually happens, and what I do instead.
- 01
Built to the spec, not the goal.
I start from what must change in your business.
Fewer manual steps, faster month-end, no lost revenue. We agree the outcome first, then decide what to build. Sometimes the answer is less software.
- 02
Delivered, then abandoned.
Handed over so it stays alive.
Documentation, monitoring and alerts, and training for the people who will run it. You are never held hostage by the person who wrote the code.
- 03
Built for perfect conditions.
Built for the ones you actually have.
Patchy networks, payment reversals, bank APIs that time out, staff using a system for the first time. These are designed for on day one, not patched in production.
- 04
Jargon instead of decisions.
Plain language and clear trade-offs.
You hear what each option costs, what it risks and what it buys you, so you can decide with confidence instead of nodding along.
- 05
Scope and budget drift.
A short discovery, then visible progress.
A written plan and price for the first phase, then working software you can try every two weeks. Progress you can see, not promises.
What I offer
Four ways I can help.
Not sure which one you need? That is normal. Start with a short discovery and we will find out together.
Core business systems
The system your daily operations depend on, built to be trusted.
- ERP
- ERPNext
- Point of sale
- Procurement
- Billing
- E-commerce
Money and integrations
Money moves correctly every time, and you can prove it.
- Payment systems
- Core banking
- Bank integrations
- Mobile money
- Reconciliation
AI and analytics
AI that does a real job in your workflow, and numbers people act on.
- AI integrations
- Model training
- Dashboards
- Reporting
Team uplift
Your developers learn to build and run world-class systems themselves.
- Mentoring
- Engineering standards
- Code review
- Lead coaching
Sound familiar?
Find the problem that sounds like yours.
Every one of these is a system I have built and put to work in a real business. If one sounds like your week, you are in the right place.
Field teams
Your team says they are in the field. Can you see it?
Plan each person's route and visits for the day, see everyone on a live map, and get proof of every visit: a check-in, photos and the customer's signature. It works even where there is no signal.
You stop guessing, and good work finally gets noticed.
See how it works →
Payments
Money comes in from mobile money, cards and the bank, and nothing matches.
One system that accepts payments from every channel, pays out when needed, and matches every payment to the right customer and invoice automatically.
No double charges, no missing money, no month-end detective work.
See how it works →
Point of sale · SumsPOS
Sales get lost when the internet drops, and the stock never adds up.
A till that keeps selling offline, takes cash, card and mobile money, and updates your stock with every sale.
Every sale counted once, and you always know what is on the shelf.
See how it works →
Running the business · ERP
Finance, stock, staff and purchasing all live in different places.
One system to run the whole business, set up around how you already work instead of forcing you to change.
One set of numbers everyone trusts, and reports in minutes, not days.
See how it works →
Procurement
Choosing suppliers feels like guesswork, and every decision gets questioned.
One clear process: find suppliers, check they qualify, run tenders, sign contracts and rate how well each supplier delivers.
Fair decisions, a full paper trail, and better suppliers every year.
See how it works →
Internet providers
Chasing customers to pay, then switching them off by hand?
Customers pay and are connected automatically. When their plan runs out they are paused, and the moment they pay again they are back online.
Revenue collects itself, and your team stops babysitting accounts.
See how it works →
Banking and lending
Your savings or lending business has outgrown its spreadsheets.
Accounts, loans, savings and repayments in one secure system, connected to your bank and to mobile money.
Books that always balance, and answers ready when auditors ask.
See how it works →
Marketing · Adisoma
Your ads and social media are spread across too many apps.
Plan, post and track every campaign on every channel from one screen.
You see what is working, and spend only where it pays.
See how it works →
Online stores
A customer paid online, but the item was already gone from the shop.
An online store connected to your real stock, payments and deliveries.
Customers get what they ordered, and you stop apologising.
See how it works →
Data and AI
You have plenty of data, but still no clear answers.
Simple dashboards that answer the questions you actually ask, and AI that takes repetitive work off your team's hands.
Decisions based on facts, and hours back every week.
See how it works →
Your problem is not on this list?
Tell me about it anyway. Most good work starts that way.
How we work
No surprises. You always know where things stand.
- Step 1
Understand
A short discovery to map your process, risks and goals. You get a written plan and a price for the first phase, and you can stop there if it is not a fit.
- Step 2
Design
Screens and flows tested with the people who will use them, before any heavy building. Changing a drawing is cheaper than changing code.
- Step 3
Build in the open
Working software every two weeks. You try it, give feedback and see exactly where the budget is going.
- Step 4
Hand over and stay
Documentation, monitoring and training for your team, with ongoing support available if you want it.
Mentoring and coaching
I also make your team better.
The best system is one your own people understand. I train and coach developers and tech leads to build, ship and run software at a world-class standard, on your real codebase, not in a classroom.
- Designing systems that survive real load and real failures
- Testing and code review habits that catch bugs before customers do
- Shipping small, safely and often
- Working with business stakeholders in plain language
Questions
The questions people ask before they call.
Who owns the software when the project is finished?
You do. The code, the data and the accounts it runs on are in your name, and you get the documentation needed for any competent team to take it over.
What if you disappear halfway through?
Work is delivered in two-week pieces that you can see and use, the code lives in your own repository from day one, and everything is documented as it is built. You are never left holding something only one person understands.
Can you work with our existing system or our own developers?
Yes. Many projects connect to systems a business already runs, and I often work alongside in-house developers, mentoring them so they can run the system afterwards.
How long does a project take?
A first useful version is usually measured in weeks, not months. The short discovery at the start gives you a realistic timeline for your case before you commit to the build.
How much does it cost?
It depends on the problem, so there is no price list. After a free 30-minute call and a short discovery, you get a written plan with a clear price for the first phase, and you can stop there if it is not a fit.
Do you work with clients outside Kenya?
Yes. Adisoma Labs is based in Nairobi and works with teams worldwide, remotely and in your time zone for the meetings that matter.
Start a project
Tell me what is not working.
The quickest way is WhatsApp. Write a few lines below and it opens with your message ready to send.
- 1You tell me what is not working, in your own words. No brief needed.
- 2We have a 30-minute call. You leave with an honest view, even if it is not me.
- 3If it is a fit, you get a written plan and a price for the first phase.
Prefer email? [email protected]
Nairobi, Kenya. Working with teams worldwide.