Focus Built for Kenyan & African SMEs
Custom software, smart automation, and AI-powered tools — designed around the real constraints of small and medium businesses in Kenya and across Africa.
Focused on clarity, simplicity, and long-term maintainability.
Context
Core focus
Local context first
Most SaaS treats mobile money as an edge case, so reconciliation becomes somebody's Sunday. We design around how money actually moves here — the statement formats, the partial payments, the reference that doesn't match anything.
Automation that helps small teams operate like larger ones — fewer manual handoffs, clear workflows, and systems your staff can run day to day.
Connectivity is not guaranteed. We design for offline-tolerant flows, sync, and operations that keep working when the network does not.
Three capabilities, delivered independently or together — depending on where you are and what you need.
Backends, APIs, and SaaS products built for operational complexity. Event-driven architecture, USSD/mobile-first systems, data pipelines.
Replace manual processes with systems that run themselves. Particularly relevant for businesses dealing with M-Pesa transaction volumes and reconciliation.
AI agent workflows, LLM integration, and model fine-tuning for businesses ready to move beyond rule-based automation.
Every engagement is shaped by these — not as ideals, but as constraints we build within.
Every project produces ADRs and runbooks alongside the code. When something breaks at 11pm, your team should know why it was built this way — not just how.
The right system is one the people responsible for it can understand, debug, and extend. Clever solutions that only one person can maintain are liabilities.
We design for 3–5 year horizons. That means making trade-offs explicit, choosing boring technology where possible, and building for the team that will inherit this — not just the deadline.
Audriam works best with teams that want to understand the systems they're building — not just have them built.
Choose the profile that fits you.
Every full engagement follows the same four stages — so you always know where you are and what comes next.
We audit the current system (or lack of one), talk to the people who use it, and produce a discovery document that maps what exists, what's broken, and what needs to be built.
Before any code, we design the system. Architecture Decision Records document every significant choice and the trade-offs considered — so the decisions are legible long after the build is done.
We build to the design. Code is documented, tested, and structured so your team can read and maintain it. No black boxes.
We don't disappear after launch. We stay close through the first weeks, document what changes and why, and make sure your team can own what was built.
A focused audit of your current system — what's working, what's a risk, and what should change. A low-commitment starting point.
Discovery through handoff. The full four-stage process for new systems or significant rebuilds.
A standalone engagement for businesses ready to add AI workflows, LLM-powered features, or automation to an existing system.
No pitch, just a real technical discussion about your system.
Get in touchAlongside client work, Audriam builds its own products — proof that the approach works, and tools designed specifically for East African businesses.
A property management platform for multi-unit residential estates in Kenya. Today it runs the operational side of a gated community: who is on site, who lives in which unit, which guard is on shift, and which provider is at the gate. In live testing with real estates — the gate is where it earns its keep.
In development
A tool for SMEs drowning in M-Pesa statements and manual reconciliation. It parses bank and M-Pesa statements, matches transactions against invoices, and uses AI categorisation to surface what needs attention.
Deep dives on architecture decisions, trade-offs, and lessons learned — not vanity metrics.
Featured
Replace the gate notebook. Log every entry and exit in under thirty seconds on a cheap Android phone, keep residents, households, vehicles and staff in one model, and give owners, agents, guards and occupants each exactly their slice of it.
We focus on systems your team can maintain — documentation and ADRs alongside the code, not a black box.
Detailed write-ups ship on the blog as we publish them.
Rent configuration, invoicing, payment matching and arrears for the same platform. Schema and module specs are written; nothing is built. The write-up covers why money is stored as integer minor units, and why multi-tenancy had to land first.
Each case study focuses on architecture decisions, trade-offs, and lessons learned rather than UI polish or growth metrics.
Decision log
Technical decisions, architecture trade-offs, and lessons learnt — written as I build. No newsletter cadence, no marketing. Just a notification when a new post goes up.
Notes in progress: why estate multi-tenancy had to come before the finance module, storing money as integer minor units, and running a Kenyan DPA 2019 consent gate in production. Written when they're ready, not on a schedule.
New posts appear here and on /blog as they ship.
Get notified when a new post goes up.
Subscribe via emailNext step
If you're dealing with manual processes, reconciliation headaches, or a system that's grown past what it was designed for — let's talk. No pitch, just a real technical conversation about your situation.