Insurance
Two years
Claims and queries that went unanswered for hours turned into customers who left. The bottleneck was never the people — it was a process that could not absorb the volume arriving at it.
About
Built from watching the same thing go wrong.
Ruskins AI Consulting LTD exists because of a pattern that showed up in three unrelated industries — and because the tools to fix it properly finally exist.
Founder
Philip Kamau
Founder & Chief Architect · BSc Actuarial Science, University of Nairobi
Across a decade in insurance, retail and the non-profit sector I kept meeting organisations with good people and sound offerings, held back by their inability to respond at the speed their customers expected. Every delayed reply was revenue leaving. That is the problem this company was built to solve.
- 10+
- Years in data and analytics
- 30+
- Businesses served
- 6+
- African markets
The route here
Three sectors, one recurring failure.
Retail
Two years
Customers arrived by phone, email, social media and in person, and the channels did not talk to each other. Work fell between them, and the gaps were invisible until a sale was already lost.
Non-profit
Six years
Managing risk across six African markets, with thousands of beneficiary calls a day and transactions spread across borders. At that scale, manual verification is not merely slow — it leaves openings that get exploited.
The pattern
Across all three
Three unrelated sectors, one recurring failure: processes overwhelmed by their own volume, with the cost passed to whoever was waiting at the other end. The fix was rarely more staff. It was better systems, and honest measurement of whether they worked.
How we operate
Four things we hold to.
Start with the problem
We do not lead with technology. Every engagement starts with the business problem, and sometimes ends with the conclusion that software is not the answer to it.
Say what will not work
The most valuable thing a consultant can tell you is which parts of your plan are unlikely to survive contact with production. We would rather lose the work than take it on false terms.
Build for handover
Systems are documented and handed to teams who can run them. A dependency on us is a design flaw, not a business model.
Your data stays yours
Single-tenant by default, with data residency and retention agreed in writing at the start. Kenya DPA 2019 compliant.
The name
Why Ruskins.
Named for John Ruskin, the nineteenth-century critic who argued that the quality of work and the quality of a society are the same question. He was writing about stonemasons, not software, but the argument transfers intact.
It is a high bar to name yourself after, and a useful one. It rules out the shortcuts that look like savings at the point of sale and turn up later as someone else’s problem.
Let’s talk about your work.
Whether you are a startup or an established organisation, the first conversation costs nothing and usually clarifies more than a proposal would.