Kigs Apex has not raised money. CashTrace and Rentisha were built, and continue to be built, on revenue from advisory and engineering work. That is a normal arrangement and an unstable one, and it is worth being direct about how we manage it.
The failure mode is well documented
A services business that intends to become a product business usually does not. The mechanism is not dramatic. Client work has a deadline and an invoice attached; product work has neither. When the two compete for the same week, the deadline wins, and it wins every week until the roadmap is a document nobody opens.
Nobody decides to stop building the product. It just never becomes this week's most urgent thing.
What we take on
The filter is whether the work makes the products better, and there are two honest ways that happens.
The first is technical overlap. Work involving M-Pesa integration, WhatsApp Business messaging, or KRA compliance leaves us better at the things Rentisha and CashTrace already do. We learn the failure modes of a payment rail on somebody else's schedule, and both products get the benefit.
The second is proximity to the customer. Engagements with Kenyan SMEs and property operators are the closest thing a bootstrapped company gets to sustained user research. You see the spreadsheet people actually maintain, rather than the one they describe. Several product decisions came from watching how a business really reconciles payments, which no interview would have surfaced.
What we turn down
Staff augmentation, where we would supply engineers to work inside somebody else's system on somebody else's roadmap. The money is fine and the learning does not compound.
Work that requires becoming expert in a domain we will not stay in. Depth is the asset; renting it out in a direction we are not going costs more than the invoice covers.
Anything that would make one client large enough to have an opinion on the product roadmap. That is the point at which you are no longer a product company with clients; you are a contractor with an unusually elaborate side project.
How we keep it bounded
Engagements are scoped with defined endpoints rather than open-ended retainers, so the default is that work concludes rather than that it continues by inertia. Product work gets time that is planned rather than left over. And when a client relationship starts to feel structurally permanent, that is treated as a signal to examine, not as a success.
The honest summary is that this is a phase and we would like it to end, not because the work is bad, but because the destination is a company whose revenue comes from the software it operates. Advisory work is what buys the time to get there, and the discipline is in remembering which one is the point.