About
Ruskins AI Consulting LTD builds and integrates the operational software organisations depend on daily — from the point of sale through to the models that read what it produces. Not dashboards about the work. The systems the work runs through.
What we build
Retail, food service, multi-outlet
The till is where the business meets its customer, and where its data starts. We build point of sale that holds up on a busy counter — fast entry, offline tolerance, stock that reconciles — and that feeds the rest of the stack instead of sitting apart from it.
Inventory, procurement, finance, payroll
Most organisations do not need a larger ERP. They need one that matches how they actually work. We build and integrate the pieces that carry real operational weight, and connect them so a figure means the same thing in every department that reads it.
Hotels, lodges, serviced apartments
Reservations, rates, housekeeping, folios and the nightly close — one system, one source of occupancy. Built for properties that need the front desk, the restaurant and the back office to agree without anyone retyping anything.
Entities, relationships, lineage
Some questions are about relationships, not rows: who is connected to whom, how a change propagates, where a figure came from. We model those domains as graphs and build the pipelines behind them, so the questions can be asked directly rather than approximated.
Applied, evaluated, in production
AI built against a specific problem and measured against a specific baseline — extraction, classification, forecasting, and agents that act inside your own systems. If a simpler method does the job, we say so and build that instead.
How we operate
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.
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.
Systems are documented and handed to teams who can run them. A dependency on us is a design flaw, not a business model.
Single-tenant by default, with data residency and retention agreed in writing at the start. Kenya DPA 2019 compliant.
The name
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.
Whether you are a startup or an established organisation, the first conversation costs nothing and usually clarifies more than a proposal would.