Built with AI. Checked before launch.
A fixed-scope check of your AI-built or inherited app: security, money, speed, uptime, records and handover. You get a written go or no-go.
Read-only access to the code and about an hour of your time. Nothing goes offline.
3 days
working days for Triage: a written go or no-go
8-10 days
working days for Deep: a fix plan and one re-test
The problem
AI tools do not tell you what they left out
An AI tool builds something that looks finished. It will not mention that one customer can open another’s invoice, or that nobody has restored a backup.
Under Kenya’s Data Protection Act 2019, a personal data breach can draw a penalty of up to KES 5,000,000 or one percent of prior-year turnover, whichever is lower. Up to KES 10,000 a day can follow until it is put right.
- You built it with an AI tool and cannot tell if it is safe
- The developer who built it has gone quiet
- You have never watched a real customer pay
- Payment and system totals disagree at month end
- A bank, investor or large customer asked a security question you could not answer
Deliverables
Six areas, one plain report
Every finding is sorted by what it costs you and when it must be dealt with, in words you can forward to whoever fixes it.
A report a non-engineer can read
Three lists: fix before you take another shilling, fix this quarter, and fine to leave alone. Technical detail sits at the back for the developer.
Security
Whether someone can get in who should not, and whether one customer can see another’s details.
Money
Whether every payment is recorded once and agrees with your statement at month end.
Speed
Whether it stays quick after a year of real records.
Staying up
What happens on your busiest day, and on the day it fails.
Your records
Recovery after the worst day, and who owns the data.
Whoever comes next
Whether any developer can work on it, or only the one who built it.
The checklist
Every question we ask
The same written list every time, so the report is a decision and not an opinion. Go through it yourself first.
| Area | Question |
|---|---|
| Security | Can one customer open another customer’s records? |
| Security | Can a normal user reach admin screens by editing the web address? |
| Security | Are passwords, payment credentials or keys stored where they can be found? |
| Security | Do logins and password resets behave the way you think? |
| Security | What can a staff member who has left still open? |
| Security | Which customer details do you keep, and do you need them? |
| Money | Can one customer be charged twice for the same thing? |
| Money | Can a payment arrive and never be recorded? |
| Money | Can a payment be recorded when the money never arrived? |
| Money | Can your mobile money and bank statements and your system be made to agree? |
| Money | How are refunds, part payments and overpayments handled? |
| Money | Are prices and totals worked out on your side, or trusted from the phone? |
| Speed | How long does the main page take to open on a phone on mobile data? |
| Speed | What slows down first as records grow from hundreds into thousands? |
| Speed | Does the customer wait for slow work, or does it run in the background? |
| Speed | Are images and pages sized for your customers’ connections? |
| Speed | At what point does it stop feeling quick and start feeling broken? |
| Staying up | What breaks first at 100, 1,000 or 10,000 users? |
| Staying up | Would you hear of an outage from an alert, or from a customer? |
| Staying up | If an update breaks something, how fast can it be rolled back? |
| Staying up | What stops if one server, one service or one person is unavailable? |
| Staying up | What does an hour of downtime cost the business? |
| Your records | Do backups exist, and has anyone restored one? |
| Your records | How much work would you lose: hours, or days? |
| Your records | What would one deleted record or one wrong command cost? |
| Your records | Can you take your own records out and leave? |
| Your records | Where are they stored, and who else can reach them? |
| Whoever comes next | Can another developer pick this up without starting again? |
| Whoever comes next | Does anything check that a change has not broken something else? |
| Whoever comes next | Which parts are out of date or no longer supported? |
| Whoever comes next | How much of it lives only in one person’s head? |
| Whoever comes next | What will hosting and other monthly bills cost as you grow? |
We need read-only access to the code, and about an hour of someone’s time to explain what it should do.
Process
From access to a written answer
Fixed price, fixed scope and fixed date. Half to start, and the balance when the report is in your hands.
Give us read-only access
Access to the code, and about an hour of your time to walk us through what it should do.
We work the checklist
Security, money, speed, staying up, your records and handover, on a copy of the system.
Report and a call
Triage ends with a go or no-go in 3 working days. Deep adds a fix plan and one re-test after the fixes.
You decide what next
Fix it yourself, hand it to your developer, ask us to quote, or do nothing. The report is yours.
Next steps
After the report
Custom systems
For problems you want fixed properly. We pick up where the AI tool stopped.
AI-Built App Security: Eight Checks Before Customers Arrive
What AI coding tools routinely leave out, and how to check yours.
Questions
Launch Check questions
We built our app with an AI tool. Is that a problem?
Not by itself. AI tools build workable software. The trouble is what they leave out because nobody asked. Nobody checks whether one customer can open another’s records, whether a payment can count twice, or whether a backup was ever restored. A Launch Check looks for those gaps before real customers do.
What does a Launch Check look at?
Six areas, worst first: security, money, speed, staying up, your records, and whether another developer could take the system over. The full question list is published on this page. Go through it against your own system first. If none of it worries you, you probably do not need us.
How is this different from asking a developer to have a look?
A developer looking casually tells you what they would have done differently. We work through the same written checklist every time, and the report sorts every finding into fix now, fix this quarter and leave alone. You get a decision you can act on, not an opinion about coding style.
Do we have to hire you to fix what you find?
No. The report is yours to keep. Many people hand it to their own developer, and that is a good outcome. If you want us to do the fixing, we quote for it separately and only when you ask. The Launch Check fee never depends on what you decide afterwards.
What if you find nothing serious?
We say so, in writing. You will have paid to stop worrying about the system, which is a fair result and happens more often than people expect. A clean report is only worth something if it is honest, so we never pad a report with invented work.
The person who built our system has disappeared. Can you take it over?
Usually, yes, and it is common. We start with a Launch Check, so you know what you have inherited before spending more on it. We need access to the code and to the accounts it runs on. If you cannot get those back, tell us early, because it changes the plan.
Will the check disturb our customers?
No. We work from a copy of the system and from read-only access to the code. We never test against your live system while customers are using it, and nothing needs to go offline. Your customers keep paying and using the software as normal while the check runs.
Find out before your customers do
Show us what you have built. You get a written report and a call to go through it, then you decide what happens next.