Product engineering studio · Nairobi
Scheduling that holds, records that survive an audit, and payments that reconcile. We build them, then we keep them running.
Our own product, rentiQ, is live.
An illustration of the kind of system we build. Not a screenshot.
01 / What we build
Underneath all four is the same job: keeping what actually happens in an operation and what its records say in agreement.
Portfolios where occupancy, arrears and upkeep all have to agree with each other, and the owner checking is often somewhere else entirely. We build the system of record for the whole operation, from the first lease to the month-end statement.
See the rentiQ build →When two things cannot happen at once, the calendar is the business. We build the engines that hold finite capacity against competing demand, refuse an impossible booking before it is made, and carry the result through to whoever needs telling and whatever needs charging.
Read the case study →Work that has to be proven, not just done. Structured capture in the field, qualifications that expire, findings that stay open until someone closes them, and a trail that answers who did what, when, and under whose authority.
Read the case study →Money arrives in more ways than it should: mobile money, bank transfer, and cash written down after the fact. We build the layer that turns all of it into one ledger that balances, including M-Pesa Daraja end to end, callbacks and failure modes included.
Also: rescue and modernization for systems that still earn money but nobody wants to touch, and DevOps and SLA support once the software is live. See every service →
Free, no call required
24 questions to run against your own booking or scheduling system, from double booking and resources other than people to cancellations, overrides and whether the money still agrees with the calendar.
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 / Fit
06 / 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.