Skip to main content
+254 729 448 449
Noria Technologies

Three ways to work with us

Start From KES 8,500

Website, business email, and the basics for a small team.

Rescue KES 55,000

Check the app you built with AI, took over, or stopped trusting.

Build From KES 150,000

A system built around how your business actually works.

Nairobi, since 2020

A small team that builds the part other people find hard.

Noria builds payment systems, operations software, and AI workflows for businesses in Kenya and East Africa - and runs two products of its own on exactly the same rails.

building software
Since 2020

building software

we build, run, and bill on
2 products

we build, run, and bill on

working across East Africa
Nairobi

working across East Africa

How we got here

Building our own software changed how we build everyone else's

It is one thing to ship a client project and move on. It is another to be the person awake when a payment callback stops arriving on the last day of the month.

Noria started the ordinary way - building websites and systems for businesses in Nairobi that needed something better than what they had. The work that kept coming back was always the same shape: money arriving through M-PESA, and nobody able to prove that what the paybill received matched what the books said.

So we built Zana, first for ourselves. It bills our customers, reconciles our own statements, and chases our own arrears. Every retry, duplicate callback, and mismatched deposit was ours to fix on our own time. That is the difference between having read about a failure mode and having lost a weekend to one.

SiteBooks came from the same instinct pointed at construction - contractors running sites in Kenya for clients who are in London or Toronto and cannot come and look.

The result is that when we tell you a system will hold up under real money, we are not making a claim about our process. We are telling you what ours already survives.

What we have worked on

Payments and financial workflows

Years of work on systems where a mistake in the money is expensive and visible. Reconciliation, idempotency, and the failure cases that only show up in production.

Customer communication at scale

SMS, WhatsApp, and email wired into business events - delivery tracking, opt-outs, and the operational realities of sending in this market.

Operations and reporting

Moving teams off scattered spreadsheets and onto systems that produce numbers a manager can act on and an auditor can follow.

Running production software

Two live products of our own, with the on-call, the incidents, and the month-end pressure that come with them.

How we work

Four things we will not trade away

These are not values on a wall. Each one has cost us money at least once, which is the only test that means anything.

We run what we sell

Zana bills our own customers on M-PESA every month. When we say we know what breaks under real money, it is because it broke for us first, at our own cost.

The business problem, then the technology

We scope around what is actually costing you time or money. The stack is an implementation detail, and we will not sell you one you do not need.

Written to be handed over

Tests, documentation, and a codebase another engineer can pick up. Your data exports, your accounts stay in your name, and the off-boarding checklist is written before you need it.

We will talk you out of things

A template instead of a build. Zana instead of a quote. Nothing at all, if the audit comes back clean. Every lane on this site names the case where you should not buy it.

Fit

Who we suit, and who we do not

We would rather you worked this out on this page than three weeks into a project.

A good fit

  • Money moves through the system, and being wrong at month end is expensive
  • There is a named person who can make decisions and answer questions
  • You want the thing maintained after launch, not just delivered
  • You would rather hear an honest no than an agreeable yes

A poor fit

  • Nobody owns the project and the requirements change with whoever is in the room
  • The goal is the cheapest possible version and nothing after that
  • You need a large team on site from next week - we are small, deliberately
  • The decision has already been made and you want an engineer to agree with it

Want to see if we are a fit?

Tell us what is slowing the business down. We will recommend the right next step, the expected timeline, and a budget range - usually within 24 hours.

  • Free 30-minute call
  • Scope, timeline, and budget range
  • An honest answer about fit

Or reach us directly

Weekdays, and we answer the same day.