Product engineering studio
A senior product engineering studio in Nairobi. We take companies from idea or legacy system to running, revenue-ready software.
Our own product, rentiQ, is live.
An illustration of the kind of product we build. Not a screenshot.
01 / What we do
We design and build multi-tenant products: data model, application, billing, and the admin side that keeps them running.
Pipelines, environments, and infrastructure set up so a deploy is routine and a rollback is one command.
A retainer that keeps software patched, monitored, and answered for, with response times written down.
For systems that still earn money but nobody wants to touch. We stabilise first, then modernise in steps you can pause.
We run our own SaaS, rentiQ, on the same stack and the same discipline we sell, M-Pesa integration included. The lessons come back into client work.
02 / Our own product
Property management SaaS
We built rentiQ as a system of record for rental money and everything attached to it. Payments arrive either automatically through the client's own M-Pesa Paybill or by hand from a caretaker with a cash box, and both go through one allocation engine that applies them to the right invoices in the right order, flags anything ambiguous for a two-click resolution, and leaves an audit trail. Around that core sit the operations of a rental business: buildings and units, lease lifecycles, maintenance tickets, staff roles and permissions, a tenant portal, and a reporting suite written for the Kenyan market first.
03 / How we work
The first call is free and takes 30 minutes. If we go ahead, a paid scoping engagement turns the idea into an architecture, a build sequence, and a cost you can plan against. The written plan is yours whoever builds it.
Senior engineering, small increments, tests and CI from the first commit. You see working software every week, not a status report.
Production infrastructure, monitoring, backups with a restore we have watched work, and a handover that leaves you able to run it without us.
A support retainer keeps it patched, watched, and answered for, with response times written down and a monthly report you can read in five minutes.
04 / Engagement models
Charged per project
One agreed scope, one price, one delivery date. Quoted after scoping, when we both know what is being built.
Charged per hour
An hourly rate against a monthly ceiling you set. For work whose scope genuinely cannot be known in advance.
Charged per month
A monthly fee for response times, patching, monitoring, and a set number of engineering hours. Three tiers, compared below.
05 / Start here
Bring an idea, a system that has outgrown itself, or a product that needs someone to keep it running. The call is 30 minutes and costs nothing. The paid scoping engagement, the one that produces your build plan, only comes after it and only if you want it.
We reply within one business day.