Know what's safe, what's risky, and what to fix first.
A fixed-price review of your live, AI-built product against your next commercial milestone. You get a plain-English NOW vs LATER roadmap, and it's useful even if you hire someone else to do the work.
£1,950 FIXED · 5 WORKING DAYS FROM ACCESS · FOUNDER-LED
A good fit if
- Your product is live and was built largely with AI tools or prototype builders
- It has users, payments or customer data
- A milestone is coming: first customers, an enterprise pilot, due diligence or a launch date
- There's nobody experienced you can ask whether it's ready
Probably not the right start if
- You're pre-launch with no users, date or budget. An Onion Sprint is a better start.
- You want a rebuild decided in advance. The review recommends what's needed, not what sells the most work.
- You need a formal penetration test or compliance audit.
Five areas, judged against your milestone.
Not against an abstract ideal. A pilot with a bank needs different things from a seed round or a consumer launch.
Ownership
Who controls the repository, hosting, domains, third-party accounts and API keys, and whether a new developer could take over.
Security
Authentication, who can see whose data, how secrets are stored, and how payments are handled.
Reliability
What happens when something fails: error handling, backups, monitoring, and whether you'd know.
Performance
What slows down or breaks first as usage grows, and roughly what that would take to fix.
Deployment
How changes reach production, whether one can be rolled back, and whether there's anywhere safe to test first.
Four things, in plain English.
Risk map
Every significant finding, marked as safe, risky or blocking, with a plain explanation of why it matters to a customer or investor.
Milestone assessment
A direct answer to the question you actually have: can this product support what you're about to do?
NOW vs LATER roadmap
What to fix before the milestone, what can wait, and what to leave alone.
Founder walkthrough
A call to talk it through, so you can explain the findings to investors, customers or a new developer.
What the roadmap looks like
An illustrative example, not a real client.
| Finding | Why it matters | When |
|---|---|---|
| Any logged-in user can read other customers' records | One customer could see another's data. An enterprise buyer's security team will test this first. | NOW |
| Failed payment webhooks aren't logged | Failed charges would go unnoticed until customers complained. | NOW |
| No staging environment | Every release goes straight to customers. Fix before the launch date. | NOW |
| Duplicated code across three screens | Slower to change, but it works and isn't exposing anyone. | LATER |
| Framework you wouldn't choose today | Works fine. Switching would cost weeks for no customer benefit. | LATER |
About a week from access to answers.
Short call
30 minutes on the product and your milestone. If the review isn't the right move, I'll tell you.
Access
You send read-only access to the code and hosting setup. I'm happy to sign an NDA first.
Review
I go through the product against your milestone. 5 working days from the day I have access.
Walkthrough
You receive the written report and we talk it through, including what to do next.
What I need from you
- Read-only access to the code repository
- A read-only view of your hosting and deployment setup
- A named milestone and a rough date
- Someone who can answer questions about how it was built, usually you
I don't need access to customer data.
Included, and not included
- The review, report and NOW vs LATER roadmap
- The founder walkthrough call
- Code changes or fixes. That's the Hardening Sprint below.
- A rebuild
- Penetration testing or formal security audits
- Compliance certification such as SOC 2 or ISO 27001
- Open-ended advisory access
Production Hardening Sprint
If the review finds blockers, I fix the few that matter for your milestone. It's a separate, fixed-scope engagement, and you're under no obligation to do it with me.
Fixed scope
One defined milestone and a short list of agreed fixes. If the scope grows, we agree a new one instead of letting hours drift.
Acceptance checks
Each fix has a check you can see pass before it counts as done.
Production code
Working changes in your live product. Typical areas: authentication, data handling, deployment, monitoring, performance, or one fragile component.
Scoped and priced after the review, at a fixed price. Not open-ended development.
Three ways forward after the review
Take it and run
The report stands on its own. Do the work yourself, or hand it to any developer you trust.
Production Hardening Sprint
I fix the critical items that block your milestone, to agreed acceptance checks.
Fractional CTO
Ongoing technical decisions and reviews, with scope, access and response times agreed upfront. See how it works.
Questions
Is this just a code review?
No. A code review checks code quality. This checks whether the product can support a specific commercial milestone, and ranks every finding by whether it matters for that.
Will you tell me to rebuild it?
Only if a rebuild is genuinely the cheapest safe route, which is rare. The NOW vs LATER roadmap exists to stop unnecessary rebuilds.
I'm not technical. Will I understand the report?
That's the point. It's written for founders in plain English, and the walkthrough covers anything that isn't clear.
What if you find nothing serious?
Then you know, and you can say so to investors and customers. That's a perfectly good outcome.
Is my code safe with you?
I only need read-only access, and I'm happy to sign an NDA before you share anything.
My product isn't live yet.
Start with an Onion Sprint instead. It builds the real core first, so there's something solid to review later.
What's your next milestone?
Tell me what's changed commercially, and when. £1,950 fixed, 5 working days from access.