Built in the last quiet months before the world went indoors.

Merut Tech Solutions began in Nairobi in 2019 — in the strange, unsettled period when nobody yet knew what was coming, but everybody could feel something shifting. That timing shaped the way we think about software, about distance, and about what technology is actually for.

Our Origin

A company that started with a question

We did not set out to build a company. We set out to answer a question: what does software actually look like when it has to work from anywhere, for anyone, without a helpdesk walking down the corridor to fix it?

That question turned out to be more consequential than we expected. Between the end of 2019 and the middle of 2020, the entire premise of how businesses operated — where work happened, how customers paid, how teams coordinated — was being rewritten in real time. Every assumption we'd carried about how software reaches people, how it's supported, how it survives contact with an organisation that suddenly had no physical centre, was being tested at once.

We started by building small, unglamorous systems for businesses that needed them. A stock tracker for a shop that had three branches and no unified view of its inventory. A payment reconciliation tool for a distributor whose finance team was drowning in M-Pesa confirmation messages. An internal workflow tool for a logistics company whose dispatchers were coordinating by phone and WhatsApp because nothing else worked across their routes.

Each project taught us the same lesson, and it's one that has shaped every decision since: the value of a system is not in its architecture, but in how gracefully it survives the mess of the real world. Power cuts. Unreliable internet. Staff turnover. Suppliers who change formats mid-year. Regulators who shift requirements. The companies we admire most are the ones whose software was designed by people who assumed all of this would happen.

By 2021 we had grown from a two-person operation into a small team of engineers, analysts, and deployment specialists. By 2022 we were working with clients in three countries outside Kenya. By 2023 our focus had sharpened toward the areas where we believed the next decade of value would be created: applied artificial intelligence, statistical analysis, and end-to-end software systems that own the full problem rather than a slice of it. Today we are a team of over fifty, distributed across Nairobi and beyond, working with organisations that range from single-location retailers to multi-country operators.

We remain, in the end, an engineering company. The business side matters — it has to, or nothing survives — but the thing we actually care about is whether the systems we build hold up when they're asked to do something they weren't explicitly designed for. That, more than anything, is what we measure ourselves against.

Leadership

The two people who started it

MM

Methuselah Misati

Co-Founder · Technical Direction

An engineer first and a systems thinker second, Methuselah leads the technical architecture across everything we build. His particular obsession is with the unglamorous parts of software: what happens when a network drops mid-transaction, how state survives a server restart, why a system that works for ten users so rarely works for a thousand without being redesigned from the ground up.

He is a firm believer that the hardest engineering problems are rarely solved by adding complexity, and that most production failures can be traced back to assumptions that were never questioned during design. The systems he has built over the last decade share a common thread: they assume things will go wrong, and they are honest about it.

He works closely with our engineering teams on architecture reviews, system observability, and the long, patient craft of making software that quietly does what it promises.

Systems architecture Distributed systems Reliability engineering
RN

Ruth Ngugi

Co-Founder · Strategy & Operations

Ruth brings the operating discipline that keeps technical ambition grounded. She is the person who asks, before any project begins, what specific problem is being solved and how we will know whether it has been. Her background sits at the intersection of business operations and data — an unusual combination that gives her a rare instinct for where value is actually being created inside a company.

She has led engagements across retail, distribution, and professional services, and is most at home in the early conversations with clients when the problem is still fuzzy and nobody has decided yet whether software is even the answer. Her view is that a surprising number of technology projects would be better served by a difficult conversation than by a development team.

Within Merut, she owns the relationship between what clients say they need and what our teams actually build — the translation layer where most projects either succeed or quietly fail.

Business analysis Client strategy Operational design
50+ Team members across engineering, analytics, and delivery
50+ Systems in production worldwide
9+ Markets served across three continents
2019 Founded in Nairobi, Kenya
We are not interested in building software that looks impressive in a demo. We are interested in building software that a business can depend on for five years, through three managers, two regulatory changes, and one unexpected growth spurt.
Methuselah Misati · Co-Founder, Merut Tech Solutions
Where We Are Going

Four commitments that shape the next decade

01 · INTELLIGENCE

AI as infrastructure, not spectacle

We are not interested in artificial intelligence as a demonstration. The version of AI that matters to us is quieter: models that read a handwritten prescription correctly on the first try, systems that flag an unusual payment pattern before it becomes a fraud case, pipelines that extract meaning from documents no human has the patience to parse one by one.

Our work in this area is deliberately unglamorous. We embed intelligence into the systems businesses already run, so that the value is felt operationally rather than announced at a keynote. The measure of a good model, in our view, is not how it performs on a benchmark, but whether the person using it notices it is there.

02 · ANALYSIS

Analysis that earns its place

Most businesses are not short of data. They are short of clarity. The dashboards that get looked at are the ones built by people who understand which question is actually being asked — not the ones with the most panels, the most colours, or the most elaborate filters.

We approach analytics as a discipline of subtraction. What is the smallest amount of information that changes a decision? Everything else is decoration. Our analysts work alongside the businesses they serve long enough to understand what a good month actually looks like — because the number on a screen means nothing without that context.

03 · STATISTICS

Statistical rigour behind every claim

There is a version of data work that produces confident answers to badly framed questions. We try hard to avoid it. Statistical thinking — sampling, distributions, confidence, uncertainty — is not academic decoration in our world. It is the difference between a forecast that helps a business plan and a forecast that quietly misleads it.

When we tell a client that a product is likely to stock out in the next thirty days, we want that statement to mean something measurable. We are comfortable saying "we don't know" when the data does not support a conclusion, and we think that honesty is more valuable in the long run than a well-presented guess.

04 · DELIVERY

End-to-end ownership of the problem

There is a version of the software industry in which work is handed between teams like relay batons — an agency designs, a contractor builds, a third party maintains, and the business is left holding the consequences. We have deliberately chosen the opposite model.

From the first conversation about what a client actually needs to the day a system is retired, we own the full arc. Design, engineering, data, deployment, hardware, and support sit under one roof. This is slower to scale than pure outsourcing, and it is the only model we are willing to stand behind. It means we cannot blame anyone else when something goes wrong — which, we have found, is the only reliable way to make sure it does not.

Reach & Backing

Based in Nairobi. Working wherever the problem is.

Our headquarters are in Nairobi, along Thika Road, and they will stay there. But the systems we build do not recognise borders. A POS deployment in Nairobi and a data pipeline in Manchester are not different businesses — they are the same engineering discipline applied to different operating realities.

Over the last several years, our client base has expanded well beyond East Africa. Today a meaningful share of our work originates outside the continent: retail operations in the Gulf, analytics engagements in Europe, software partnerships in North America. This is not a marketing claim — it is a consequence of remote-first delivery having become normal, which suits the way we were built from day one.

We are also backed and supported by a set of partner organisations whose names we choose not to publish on this page. Some are large. Some are deliberately quiet. All of them are serious about the work, and their confidence in us is not the kind that shows up in a press release — it is the kind that shows up in the operating capital and the long-term commitments that let us take on projects we might otherwise have to decline.

What we care about, in the end, is not the logos we could list. It is whether the systems we ship are still running years later, in businesses that have grown past what their founders originally imagined. That is a harder thing to demonstrate, and a more meaningful one.

How our work is distributed today

  • East Africa — our home market. Retail, logistics, pharmacy, hospitality, and manufacturing across Kenya and neighbouring countries.
  • Europe — analytics and data engineering engagements, primarily in the UK and the Nordics.
  • North America — software partnership and delivery work with organisations scaling internal systems.
  • Middle East — retail and payment integration projects across the Gulf.
  • Partnerships — backed by a set of long-term partner organisations we work with quietly and deliberately.
How We Think

Six things we believe about software

01

The last 5% matters most

Any team can get a system to 95%. The remaining 5% — edge cases, failure modes, what happens when the network drops — is where trust is earned or lost. We spend a disproportionate amount of time there.

02

Data outlives software

Applications come and go. The data they generate does not. We design schemas, exports, and migrations as though the system will be replaced in five years — because it probably will be, and the data must survive the transition intact.

03

Boring technology, applied carefully

We are not early adopters by temperament. We choose tools that have stood the test of production use, and we choose them deliberately. Innovation belongs in the problem being solved, not in the framework being used to solve it.

04

Systems should degrade, not fail

Everything breaks eventually. The question is whether it breaks loudly and completely, or quietly and partially. We build for the second — because a system that keeps working, even at reduced capacity, is worth more than one that is theoretically perfect until it isn't.

05

The operator is the real user

The person using the software every day is not the person who commissioned it. They are the person whose job gets harder or easier depending on the decisions we make. We design for them first, and for the dashboard view second.

06

We'd rather be trusted than impressive

We have lost pitches to firms with prettier decks and shinier demos. That is fine. The clients we retain are the ones who care about whether the thing works in eighteen months — and that is the game we are playing.

If this sounds like the kind of team you'd want building your systems

We'd like to hear about what you're working on. Book a call — we'll ask about the problem, not the pitch deck. If we're not the right fit, we'll say so.

Shopping Basket