World Safety Index
Launch with nothing critical open
Barry Allen never wrote a line of code. The travel-safety app he built with AI has 8,000 users. Three weeks before he exhibited at Web Summit, with investors waiting, he had one question: can I trust my app?
- Founder who is not technical
- Built with Base44
- Deadline: Web Summit, 12 November
The context
World Safety Index gives travellers a safety score for 189 countries, with AI briefings, emergency features and a duty-of-care plan for companies that send employees abroad. Barry Allen built all of it himself, with an AI tool. He is a carpenter by trade, he lives in Ireland and he works alone. 8,000 people use the app and three companies pay for it.
In October 2026 he had a deadline. On 12 November he would exhibit at Web Summit, and investors had already been in touch. His app tells people it keeps them safe, so a flaw found by an investor, or by a traveller in trouble, would cost him far more than a meeting. He had no engineer to ask. “With Web Summit so close, I can’t have anything not right with my app.”
The first check showed what he could not see from inside his AI tool: three critical problems, in an app people rely on when they travel.
The response
A first check from the public link
BWorlds’ agents read the app the way a visitor’s browser does, with no access to the code. They found three high-severity problems. Each one came with an explanation in plain words and a prompt written for his AI tool.
Barry fixes, BWorlds verifies
He pasted the prompts into Base44 and published. Four days after the first report, the most serious one was fixed. The recheck turned up two more of the same kind, and he fixed them the day they were reported. BWorlds checked every fix on the live app. Then he stopped adding features: “I won’t build another thing until after Web Summit.”
The code connected, the app watched
He then connected his code for the full audit: security, reliability, costs. It found more, and he worked down the list in order of priority: 18 problems fixed in all. Since 4 November, BWorlds has watched the app 24/7: uptime, errors, sessions.
- 23 OctFirst check from the public link3 high
Three critical problems, each with its fix prompt.
- 27 OctFirst fix by BarryVerified live
The most serious problem is closed.
- 29 OctCode connected, full audit
Security, reliability, costs. One list, in order of priority.
- 4 NovThe app is watched 24/7Watching
Uptime, errors, sessions.
- 12 NovWeb SummitNo critical flaw
The stand, and the investors.
The results
No critical flaw on the day of Web Summit
Three were found three weeks earlier, at the first audit.
- 18 problems fixed by Barry himself.
- 4 days from the first problem reported to its fix verified.
- The investor’s audit of the app: passed.
What else changed
- Every fix was verified on the live app before Web Summit.
- Barry exhibited at Web Summit on 12 November and met his investors with an app he could trust.
- No developer was involved. Barry applied every fix himself, in his AI tool.
What we learned
A deadline is what makes a founder act on what an audit finds.
“Massive shout-out to Emmanuel at BWorlds. He’s done some incredible work looking into my app.”
A deadline coming up? Know what is wrong with your app before your investors do.


