LeanCare Health & Wellness
LiveHealthcare — Jacksonville, Florida
Website and digital presence for a patient-centred family medicine practice, covering primary care, telehealth, behavioural health and weight management.
Nairobi · Building for East Africa and beyond
ERP, point of sale, stock control, hospital and claims platforms — built to your operation rather than configured from a template, and deployed into live use. Every one of them is AI-native, and connects to agentic AI systems we build alongside them.

What we do
AI-native by design
AI-native is a claim about architecture, so here is what it means in practice. The data model, the event stream and the permission system are designed so an agent can read the operation and act on it safely — with a record of what it did and the authority to do only that.
Then we build the agents. That is the difference between a vendor who sells you an ERP and leaves the AI question to somebody else, and one team that ships the operational system and the intelligence running on it.
Where these run
Not a list of markets we would like to enter. These are operations running on systems we built. Anywhere a business tracks stock, staff, patients, claims or customers the same foundations apply — so if your sector is not named here, the answer is still probably yes.
Selected work
A sample. Most of what we build runs inside client operations and is not ours to show.
Healthcare — Jacksonville, Florida
Website and digital presence for a patient-centred family medicine practice, covering primary care, telehealth, behavioural health and weight management.
Hospitality — Kenya
A property and venue management system for hotels, safari camps, lodges and event venues, with M-Pesa payments and KRA eTIMS fiscalisation built in.
How we engage
We start with the problem you actually have, not the technology we would enjoy building. That usually means sitting with the people doing the work and reading the data before proposing anything.
Small releases you can see and correct, rather than a long silence followed by a reveal. You review working software throughout, not slide decks about working software.
Into live operations, with documentation, a team that knows how the system behaves, and a clear account of its limits. The goal is a system that runs without us in the room.
Most useful first conversations start with a problem rather than a brief. Describe yours and we will tell you plainly whether this is work we should take on.