Every business in Kenya is already a digital business — whether or not it has decided to be one. Customers search before they call. They check a website before they visit. They send a WhatsApp message and expect an answer in minutes, not on Monday. The question is no longer whether you have a digital presence; it is whether the one you have is working for you or quietly costing you.

Motolabs Kenya exists for the businesses caught in the middle of that shift. We build the websites, automations and internal tools that let a small team operate like a much larger one.

The gap we set out to close

There are two things an SME in Nairobi can typically buy. At one end there is the cheap template — five thousand shillings, live in a weekend, indistinguishable from a thousand others, and impossible to change once the person who built it stops replying. At the other end there is the enterprise agency, with a discovery phase longer than most businesses' runway and a quote to match.

Neither serves a growing company with real customers and a real budget. What that company needs is a partner who moves quickly, builds something genuinely good, and hands over something they can keep using and extending for years.

The gap was never talent. It was access — to teams who take a twelve-person business as seriously as a twelve-hundred-person one.

What we actually build

We deliberately keep our surface area narrow so that we're excellent at the things we do ship. In practice, that comes down to four categories of work:

  • Websites and landing pages that load fast, rank well, and convert — built on React and TypeScript, not on a page builder that degrades the moment you edit it.
  • E-commerce and payments, including M-Pesa flows that Kenyan customers already trust and understand.
  • Automations that remove repetitive work: lead routing, quotation generation, invoicing, follow-up sequences, and reporting.
  • Internal tools and dashboards, so the people running the business can see what is happening without exporting another spreadsheet.

What working with us looks like

The first conversation is not a pitch. It is us trying to understand where the business actually loses time and money, which is frequently somewhere other than the thing that prompted the call. A client comes to us for a redesign and we find that the real cost is the four hours a week someone spends copying enquiries out of an inbox and into a spreadsheet. The redesign still happens; it just stops being the most valuable part of the project.

From there we work in short, visible cycles. You see something running in a browser within the first fortnight, not a deck. That matters because software is genuinely difficult to evaluate in the abstract — people can tell you precisely what is wrong with a working screen, and almost nothing useful about a wireframe of the same screen.

We are also candid when the answer is not to build. Several of our best conversations have ended with a recommendation to configure an existing tool properly rather than commission anything from us. That costs us a project and earns a relationship, which has turned out to be a reasonable trade.

Built to be handed over

A surprising number of digital projects fail not at launch but six months later, when the business wants to change something and discovers it cannot. We treat that as a design constraint. Content is structured so it can be edited. Code is typed, reviewed and documented. Analytics and search visibility are set up on day one rather than retrofitted after the first quiet quarter.

Practically, that means every engagement ends with a written handover: what was built, how it is deployed, where the credentials live, and what the person inheriting it needs to know to change something safely. It is unglamorous documentation that takes us a day to produce and routinely saves a client weeks.

The measure of our work is not how it looks the week it ships. It is whether, a year later, the business is still getting compounding value out of it — and whether they came back to build the next thing with us.

Where this goes next

This journal is where we'll write down what we learn as we go: the design decisions that changed a conversion rate, the search strategies that actually moved rankings, the parts of our stack we would choose again and the parts we would not. No abstractions, no theory for its own sake — just the work, described plainly.

If you're building something in Kenya and the digital side of it is holding you back, that is precisely the problem we set out to solve. We'd like to hear about it.