From client project to product: the origin story of Business Toolkit, ClientFlow, and BusinessOS
None of our products started as a product idea. Every one of them started as someone else's problem, solved once, then solved again for a different client — until it was worth packaging.
We get asked a version of the same question every time we mention Digital Products: "if you're a custom software shop, why are you building off-the-shelf tools too?" The honest answer is that we didn't set out to. The products found us.
The pattern that kept repeating
Custom work has a quiet inefficiency built into it: the same underlying problem shows up across completely unrelated clients, wearing a different industry's clothing each time. A funeral home needs to track a case from first enquiry to final invoice, with policies, payments, and staff assignments along the way. So does a clinic. So does an events company. The vocabulary changes — "policy" becomes "booking" becomes "engagement" — but the shape of the workflow is identical.
Rebuilding that shape from scratch for every client is how you end up paying full price, every time, for something that's 90% solved before you start. That inefficiency is the entire reason our Digital Products line exists.
ClientFlow: the first one
ClientFlow came directly out of watching small and medium businesses run their entire operation across a spreadsheet, a shared inbox, and whoever happened to remember a client's history. It isn't an enterprise CRM scaled down — it's built for the business that has outgrown sticky notes but doesn't need (or want to pay for, or wait months to configure) something built for a thousand-seat sales org. Lead in, quote out, project tracked, invoice paid, client portal for everything in between. One workflow instead of four disconnected tools.
BusinessOS: built from one implementation, useful for many
BusinessOS is the clearest example of the pattern. It grew out of a real system we built for a client with genuinely complex case management needs — policies, applications, staff assignment, client communication, the works. Partway through that build it became obvious the underlying platform wasn't specific to that one client's industry at all. Any service business managing complex client cases — applications, approvals, ongoing records — needed the same bones. So we generalised it: one core platform, configured per industry rather than rebuilt per industry. SchoolOS and EstateOS followed the same logic for education and property.
Business Toolkit: the free layer
Not every product needs to start as a paid one. Business Toolkit is a collection of practical calculators, generators, and templates aimed at South African business owners — VAT and PAYE calculators, invoice and quote generators, the small utilities that every small business needs and none of them want to pay for individually. It's free at the core, with a Pro tier for the businesses that want more: saved documents, AI-assisted generation, custom branding. It exists to be useful first and a funnel second.
Why this matters for how we work
Every product on our roadmap started life as a real system solving a real client's real problem — nothing here was dreamed up speculatively in a strategy meeting. That's a deliberate constraint, not an accident: it means anything we license has already been proven under the pressure of an actual business depending on it, before a second client ever sees it.
Curious whether one of these already solves 90% of what you'd otherwise commission from scratch? See what's live and what's in planning.