Skip to main content
Noria Technologies

The build

Built to be used every day, not demonstrated once.

The same people work out what you need, build it, and pick up the phone a year later when something needs changing. Nobody hands you over to a stranger.

Fixed price
set by discovery, then it holds
4 - 12 weeks
for a typical build
Same people
from the first call to a year later

What you get

What we build for you

Customers, orders, stock, invoices, payments - built around how the work already moves, by people who are still here next year. The same people work out what you need, build it, and pick up the phone a year later when something needs changing. Nobody hands you over to a stranger.

Payments that add up

Every payment recorded once, matched to the right invoice, and agreeing with your statement at month end without anyone matching rows by hand. Mobile money, card, bank transfer, and cash - whatever your customers actually use. This is the hard part, and the part we do most.

Operations software

The thing your staff open every morning - customers, orders, approvals, stock, and the reports you need to make decisions. Built around how the work actually passes between people.

AI where it earns its place

Reading supplier invoices and IDs so nobody retypes them, sorting incoming messages, drafting replies, and helping match payments. It works from your own records, and a person approves anything involving money.

Messaging inside the workflow

WhatsApp and SMS that go out on their own when something happens - invoice sent, payment received, order on the way - so nobody is typing the same message forty times.

Secure, fast, and still up when you are busy

Screens locked properly rather than just hidden, pages that stay quick after a year of records, backups we have actually tested, and a warning that reaches us before it reaches your customers.

Written to be handed over

Written down and organised so the next developer can pick it up. You can export your records whenever you want, and how you would leave us is agreed before you ever need to.

How it runs

What happens, step by step

You will not be passed to a team you have never met, and nobody green is going to inherit it and guess. The people in the first meeting are the people who build it.

01 Discovery first, always We do not quote a build off a phone call. The scope, the data model and the price come out of the discovery week, and the fee for it comes off this invoice.
02 Follow the work through How a customer moves through it, who hands what to whom, who approves what, and the awkward cases - agreed before they get expensive to change.
03 Build it The system, the payments, the messages, and the parts that run on their own - written so the next person can look after it.
04 Go live and hand over Everything important tested, notes written for your team, the first days watched closely, and Care running from the day it goes live.

When you should not buy this

If what you need is billing the same customers every cycle - invoices, metered water, waste collection, arrears - we will point you at BillGrid instead of quoting you for a build. It is our own software, it already does this, and it costs a few thousand shillings a month instead of a few hundred thousand once.

What it costs

We do not publish a build price

Any number we printed here would be either a guess we would have to correct later or a floor we would spend the first call defending. Both of those come out of your budget.

A build is quoted once, in full, at the end of a discovery week - a fixed price and a fixed date, with the discovery fee credited against it in full if you start within sixty days. Until then the honest answer to "what does it cost" is that nobody knows yet, including us.

And after it goes live

Every build includes twelve months of Care, written into the contract from the start - monitoring, security patching, and backups we restore and check rather than assume. The things that break after launch are not a separate problem to solve later; they are the reason handing software over unwatched is not something we do.

Before you commission a build

If what you need is billing the same customers every cycle - invoices, metered water, waste collection, arrears - we will not quote you for it, because BillGrid already does it for a few thousand shillings a month. A build earns its price when the work around the billing is the hard part, when it has to live inside a system your staff already use, or when it has to talk to something specific to your business.

How the money works

The terms, before you ask for them

None of this changes once we start. It is here rather than in a contract you read at the end, because these are the three things people wish they had asked about earlier.

Paid 40 / 40 / 20 Forty percent to start, forty at the halfway point, twenty on acceptance - and acceptance means it does what the discovery pack said it would, not that it is merely switched on. Nobody is asked to pay for a build in advance. The last fifth is ours to earn after you have used the thing.
Changes quoted before they start Anything outside the agreed scope is priced at KES 40,000 a day, quoted and signed before a line of it is written. Nobody gets an invoice for work they did not agree to.
Care from day one Twelve months of Care is written into the contract, and the first month is invoiced with the final build payment. We do not hand over a system with nobody watching it.

Before you commission

What people ask about builds and payments

M-PESA reconciliation is the part most people have been burned by before, so it has a section of its own.

How do you decide what to build?
We start with what is going wrong, not with a list of features. Then we follow the work through - how a customer moves in, who hands what to whom, who approves what - and build around that. If a smaller version would fix the problem, we say so.

How long does a system take to build?
Most take between four and twelve weeks depending on how much of the business it touches. We break it into stages so something useful is working early rather than everything arriving at the end.

Do we own the code?
Yes, once the work is paid for. You get the code, the accounts, and the ability to hand it to any other developer. We do not keep anything back as leverage.

Can it work with the systems we already use?
Usually. Accounting packages, M-PESA, spreadsheets your team will not give up, school or clinic software you already pay for. If something has no way to connect, we will tell you before you commit rather than after.

What if what we need changes halfway through?
Some change is normal and we plan for it. Big changes shift the date or the price, and we tell you which before doing the work rather than presenting it afterwards. Anything settled in the first two weeks is cheap to change; the same change in the last week is not.

Will our staff actually be able to use it?
That is most of the job. We build around how your team already works instead of expecting them to change, we train them before go-live, and we watch the first weeks closely. A system nobody uses is a failed system, however well it is built.

Do you build mobile apps?
Sometimes, but we usually talk people out of it. A site that works properly on a phone does the same job, costs less, and needs nobody to download anything. A real app makes sense when you need the camera, GPS, or to work with no network - field teams and delivery, for example.

We bill the same customers every month. Do you build that?
We will point you at BillGrid instead. It is our own software and it already does invoices, metered water, waste collection and arrears, for a few thousand shillings a month rather than a few hundred thousand once. We only quote a build when the work around the billing is the hard part.

Payments and M-PESA

Can you put M-PESA into my website or system?
Yes, and this is most of what we do. The customer gets the prompt on their phone and approves it, the payment records itself against the right order or invoice, and both of you get a receipt. Card and bank can sit alongside it.

Paybill or till - which do I need, and can you help me get one?
A till suits over-the-counter selling. A paybill suits invoicing, where each customer has an account number so payments identify themselves. We advise on which fits and help with the Safaricom application, though the account has to be in your business name and the approval time is theirs, not ours.

What happens when a payment fails or gets stuck halfway?
This is the part most systems get wrong. Money arriving twice must not be counted twice, a message going missing must not lose the payment, and a customer closing their phone mid-way must not leave a half-finished order. We build and test for all three, because they happen every week rather than never.

My M-PESA statement and my books never agree. Can that be fixed?
Yes, and it is the most common thing we get called about. BillGrid takes what lands in your paybill, till or bank, works out which account and invoice each payment settles, and leaves only what it genuinely cannot match for a person to decide.

Can the system pay people out, not just take money in?
Yes. Paying suppliers, staff, or refunds straight to mobile money or a bank account, with approvals and daily limits so one person cannot move money alone. Casual wages on a construction site work exactly this way in SiteBooks.

Who pays the transaction charges?
Safaricom and the card processors charge their own fees and those go to them, not to us. We do not add a percentage on top of your collections. We will show you what the charges look like at your volume so there are no surprises.

Is it safe to take payments through a system you build?
Card details never touch your system - they go straight to the processor. For M-PESA, the safety questions are whether prices are worked out on your side rather than trusted from the customer's phone, and whether a payment can be recorded without the money arriving. Both are on our audit list and both get tested.

Every question we get asked is on one page, if you would rather read the lot.

Not what you needed?

Discovery - Change your mind on paper, not in week nine. A week with the people who would build it, working out what actually needs building - before anyone writes code you paid for. Review - You built something. Will it survive real customers? A review of software you built with AI, inherited, or quietly stopped trusting - before it holds real money. ERP - One system for the books, the stock and the payroll. Accounts, stock, sales, purchasing, payroll and eTIMS on one system, set up, connected and looked after by people still here next year. Care - The year after launch is when it breaks. Monitoring, tested restores, patching, and a person who answers - monthly, from the day you go live.

Tell us what is slowing the business down

Nothing gets quoted off a phone call. The call is free and tells you whether discovery is the right next step - including when the answer is that something you can just buy would fix it.

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

Or reach us directly

Weekdays, and we answer the same day.