Start from the Work, Not the Tool

Most disappointing AI projects start from a product demonstration and look for a problem to fit it. Useful projects start from a real piece of work, described honestly, and ask which parts of it a machine should do. That is slower on day one and much faster by month three.

People Stay Responsible

AI can prepare, sort, draft and check at a speed no team can match, but it cannot be held responsible. Customers, staff and regulators expect a person to stand behind what a business says and does. Systems should be designed so that the person is in the right place: approving the few things that matter, not checking every trivial step.

Built for How Businesses Here Work

Businesses in Kenya and across Africa run on mobile messaging, mobile money, mixed languages and small teams that wear many hats. Tools designed elsewhere often assume email-first customers, card payments and large IT departments. Automation should fit the way work is actually done here.

Ownership Matters

A business should own the systems it depends on: the accounts, the data, the instructions and the documentation. Dependency on a single supplier is a risk, however good that supplier is.

Honesty About Limits

AI is useful and overhyped at the same time. Trust comes from being clear about what AI can't do, telling customers when they're talking to a machine, and only publishing claims you can back up. That goes for us and for the businesses we work with.

How We Choose What to Work On

A good project is one where the benefit is clear, the risk is manageable and the business is ready to own the result. When a workflow is not ready, because the process is unclear or the information is not written down anywhere, the honest advice is to fix that first.

Working Together

  • Everyday words in every document
  • Decisions written down and signed off before work starts
  • The people doing the work involved in the design
  • Short, regular updates, never long silences

Why Kenya and Africa First

Built for local businesses: We build for the way Kenyan and African businesses work, including the tools and payment methods they already use. Systems should fit local working habits, languages and customer expectations rather than forcing a business to adopt new ones. Starting from how the business already works keeps change manageable for staff.

Close to our customers: Being based in Kenya means working in the same time zone and context as the businesses we build for. Shared context makes it easier to understand how the work really runs, from customer habits to local rules. Problems can be discussed and resolved within the same working day.