Skip to main content
Noria Technologies

Before it holds real money

You built something. Will it survive real customers?

An AI tool will build you something that looks finished. It will not mention that one customer can open another one's records, that the same person can be charged twice, or that nobody has ever checked whether the backup works. We look properly, and we tell you in plain words.

Two depths
a verdict, or the full review
3 - 10 working days
from start to written report
Yours
the report, whatever you do next

What it costs

Two depths, depending on the decision in front of you

Triage answers one question: is this safe to put in front of customers. Deep answers what to do about it, in enough detail for a developer to work from, and checks the fixes afterwards.

Triage

3 working days

KES 95,000

USD 950 billed internationally

A written verdict, the risks ranked by what they cost you, and a straight go or no-go on launching. Enough to make the decision in front of you.

Deep

8 - 10 working days

KES 260,000

USD 2,600 billed internationally

The full review, a remediation plan detailed enough for a developer to work from, and one re-test after the fixes land so you know they actually worked.

half to start, half on the report

What it is measured against

One customer changing a number in the address bar and seeing another customer's invoice is a personal data breach. Under the Data Protection Act 2019 the Office of the Data Protection Commissioner can issue a penalty of up to KES 5,000,000 or one percent of your prior-year turnover, whichever is lower, plus up to KES 10,000 a day until it is put right - before you count the rebuild, the notifications, and the customers who read about it.

That is the number this review is priced against. Not the day rate.

Why people call us

If one of these sounds like you, you are in the right place

None of this means you did anything wrong. It means whoever - or whatever - built it was never going to tell you what got left out.

  • You built it with an AI tool and cannot tell whether it is safe to open to customers
  • The person who built it has gone quiet, and nobody else has looked at it since
  • It works when you show it to people, but you have never watched a real customer pay
  • Your M-PESA numbers and your system numbers do not agree at the end of the month
  • It has got slow and nobody can tell you why
  • A bank, an investor, or a big customer asked you a security question you could not answer
  • You are about to spend real money on advertising and need to know it will hold

The checklist, in full

Six things we check, worst first

This is the whole list, written for the person paying rather than the person fixing. Go through it against your own system first. If none of it worries you, you do not need us.

Security

Whether someone can get in who should not, and whether one customer can see another one's details.

  • Can one customer open another customer's records?
  • Can a normal user reach your admin screens by changing the web address?
  • Are passwords, M-PESA credentials, or keys sitting somewhere they can be found?
  • Do logins and password resets actually work the way you think they do?
  • What can a staff member who has left still get into?
  • What customer details are you keeping, and do you actually need them?

Money

Whether every payment is recorded once, correctly, and agrees with your statement at the end of the month.

  • Can one customer be charged twice for the same thing?
  • Can a payment come in and never be recorded?
  • Can a payment be recorded when the money never actually arrived?
  • Can your M-PESA or bank statement and your system be made to agree?
  • What happens with refunds, part payments, and overpayments?
  • Are prices and totals worked out on your side, or trusted from the customer's phone?

Speed

Whether it is quick now, and whether it stays quick once a year of real records has built up.

  • How long does your main page take to open on a phone, on mobile data?
  • What gets slow first as your records grow from hundreds into thousands?
  • Does the customer sit and wait for slow work, or does it happen quietly in the background?
  • Are your pictures and pages sized for the connection your customers actually have?
  • At what point does it stop feeling quick and start feeling broken?

Staying up

Whether it keeps working when you are busy, and what happens on the day it does not.

  • What breaks first when a hundred, a thousand, or ten thousand people use it?
  • Would you hear it had gone down from a warning, or from an angry customer?
  • If an update breaks something, how quickly can it be put back?
  • What stops working if one server, one service, or one person is unavailable?
  • What does an hour of downtime actually cost your business?

Your records

Whether you can get your business back after the worst day, and whether the records are genuinely yours.

  • Do backups exist, and has anyone ever actually used one?
  • How much work would you lose - hours, or days?
  • What would one deleted record or one wrong command cost you?
  • Can you take your own records out and walk away?
  • Where are they kept, and who else can reach them?

Whoever comes next

Whether you are free to hire anyone to work on this, or stuck with whoever built it.

  • Can another developer pick this up without starting again?
  • Does anything check that a change has not broken something else?
  • What parts are already out of date or no longer supported?
  • How much of it only exists in one person's head?
  • What will hosting and the other monthly bills cost as you grow?

What you get back

Three lists, not a pile of problems

A report you cannot do anything with is worth nothing. We sort everything we find by what it costs you and when it has to be dealt with, in words you can forward to whoever does the fixing.

Fix before you take another shilling

Things that lose money, expose customer details, or cannot be undone. Usually a short list, and usually a few days of work rather than months.

Fix this quarter

Real problems that are not on fire yet. They get worse as customers arrive, so they get a date rather than a shrug.

Fine to leave alone

Things another developer would want to rewrite and your business should ignore. Saying so is the point - it is how you know the rest of the list is real.

Access we need: Someone needs to give us read-only access to the code, and about an hour to walk us through what it is meant to do.

What you get

What the review covers

A review of software you built with AI, inherited, or quietly stopped trusting - before it holds real money. An AI tool will build you something that looks finished. It will not mention that one customer can open another one's records, that the same person can be charged twice, or that nobody has ever checked whether the backup works. We look properly, and we tell you in plain words.

A report a non-engineer can read

Everything we find written in plain words, ordered by what it costs you if it goes wrong. The technical detail goes at the back, for whoever does the fixing.

Severity, not a wall of text

Three lists: fix now, fix this quarter, and leave alone. Most of the reports we write are shorter than people are expecting.

What it costs at scale

What your monthly bills will look like at a hundred, a thousand, and ten thousand customers - and the point where the numbers stop working.

A second opinion you own

The report belongs to you. Take it to your own developer, your investor, or another company. You are under no obligation to hire us for the fixing.

How it runs

What happens, step by step

Fixed price, fixed scope, fixed date, and split in half so the balance only falls due when the report is in your hands. You get something you can act on - whether you act on it with us, with your own developer, or not at all.

01 You give us a look Read-only access to the code, and about an hour of your time to walk us through what it is supposed to do.
02 We go through it Against the checklist on this page - security, money, speed, staying up, your records, and whether anyone else could take it over.
03 We sit down and go through it A written report and a call to talk it through. You decide what happens next, including doing nothing.

When you should not buy this

If we find nothing serious we will say so, and you will have paid to stop worrying about it. That is a fair result, and it happens more often than people expect.

Before you book

What people ask about reviews

The seven we get most often. The full set, including everything about builds and payments, is on the FAQ page.

We built it with an AI tool. Is that a problem?
Not by itself - AI tools build workable things. The problem is what they leave out, because they are not asked. Nobody checks whether one customer can open another one's records, whether the same person can be charged twice, or whether the backup has ever been tested. That is what the audit is for.

What exactly do you look at?
Six things, worst first: security, money, speed, staying up, your records, and whether anyone else could take it over. The full list of questions we work through is published on the audit page - go through it against your own system first, and if none of it worries you, you do not need us.

How is this different from just asking a developer to have a look?
A developer looking casually will tell you what they would have done differently. We work through the same written list every time and give you a report sorted into fix now, fix this quarter, and leave alone - so you get a decision you can act on rather than an opinion.

Do I have to hire you to fix whatever you find?
No. The report belongs to you. Plenty of people take it to their own developer, and that is a perfectly good outcome. We quote separately for fixing, and only if you ask.

What if you find nothing serious?
We say so, in writing. You will have paid to stop worrying about it, which is a fair result and happens more often than people expect. We would rather tell you it is fine than invent work.

The person who built my system has disappeared. Can you take it over?
Usually yes, and it is common. We start with the audit so you know what you have inherited before spending anything more on it. What we need is access to the code and the accounts - if you cannot get those back, say so early, because that changes the answer.

Can you check it without breaking anything or disturbing customers?
Yes. We work from a copy and from read-only access. We do not test on your live system while real customers are using it, and we do not need to take anything offline.

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. Build - Built to be used every day, not demonstrated once. Customers, orders, stock, invoices, payments - built around how the work already moves, by people who are 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.

Better you find out than your customers

Show us what you have built. You get a written report and a call to talk it through, and you decide what happens next - including nothing.

  • Fixed price, whatever we find
  • Three days, or eight to ten
  • The report is yours, with no lock-in

Or reach us directly

Weekdays, and we answer the same day.