Vibe Code Review

Built with AI.
Ready for a second opinion.

AI coding tools have made it possible for almost anyone to build something that looks and behaves like a real product, and I think that's genuinely brilliant. But there's a gap between code that works in a demo and code that's ready for real users, real data and real consequences. That gap is where I come in.

Book your first hour, £90 →

Anyone who's used Cursor, Lovable, Bolt, Replit or any of the others to build an app or a website, and now wants somebody with ten years of commercial experience to take a proper look before it meets the public.

That might be because you're worried about bugs, because you're ready to launch and want a sanity check, or because you've hit a wall and can't work out why. All three are common and none of them are a reason to feel daft.

I think it's great that you've built something, and how it got made isn't really the point. What it needs next is the bit worth talking about.

I go through the codebase and use the app the way a real user would, and the way a rather less friendly one might.

  • Bugs and broken flows, including the ones that only show up once real people start using it
  • Security and data handling, because AI-generated code has a habit of leaving APIs open, exposing data or skipping authentication checks entirely
  • Code quality and structure, so you know whether this scales or turns into a tangle you'll regret in six months
  • Launch readiness, covering hosting, environments, domains, error handling and everything else that gets forgotten first time round

If you want to keep building afterwards, I can take it on. Fixing what I found, adding what's missing, or just being a developer you can ring when something needs doing. Equally, take the findings and run with them yourself. Both are fine by me.

You don't need to understand every technical detail for this to be useful. I'll translate everything into terms you can actually make decisions with, walk you through it on a call, and give you a written summary you can go back to. You'll never be left with a list of technical terms and no explanation.

The assessment is honest in both directions. If your project is in good shape I'll tell you, and if it needs serious work before anybody should see it, I'll tell you that too, along with exactly what that work involves.

It isn't only the code either. I'll give you a view on the usability, on how the thing will age, and on the overall feel of it, because those tend to matter as much as what's under the bonnet.

How it works

This starts small on purpose. One hour, a fixed price, and an honest answer at the end of it about what you're actually dealing with.

01. You book the first hour

Pay £90 for the first hour and send me a link to your repo or your staging site. No onboarding, no forms, and no commitment past that hour.

02. I get the lay of the land

I go through what's been built, work out how it hangs together, and start listing anything that needs attention. This part is usually quicker than people expect.

03. I use it properly

Then I use the thing as a real user would, and as somebody with worse intentions might, which is usually where the more interesting problems surface.

04. We talk it through

At the end of that first hour you get an honest summary of what I found and a clear estimate of how much work is in front of you. On a call, rather than in a document you have to decipher on your own.

05. You decide

Take the findings and fix them yourself, or keep me on at £90 an hour. No pressure either way, and you'll know exactly what's involved before committing to anything further.

06. Getting it live

If launching is the goal, that's the most common thing to follow a review. I'll handle the whole launch process and point you at hosting that suits the project and the budget.

"Alex is the reason you should use a human rather than a bot to build your website."
Jack Izzard, Founder, Gallia Communications
Frequently Asked Questions

Some things people often ask me:

Does it matter which AI tool I used?
Not at all. Cursor, Lovable, Bolt, Replit, ChatGPT or a bit of everything, the code is the code. I review what's there, not how it got there.
Do I need the code in a Git repository?
It helps, but it isn't essential. If you've got a GitHub or GitLab repo, share it. If not, I can work with whatever you have and get it into version control as part of the job.
How many hours will it take?
Depends on the size of it. A straightforward site or small app might be two or three hours. Something more complex takes longer. You'll get an honest estimate before I start, and I won't run the clock without keeping you informed.
What if I only want help with one specific thing?
That's fine. You don't have to commit to a full review. A bug you can't crack, a feature that won't behave, one area you're uneasy about, I'm happy to just look at that.
Is my code kept confidential?
Yes. Everything you share is treated as confidential, and I'm happy to sign an NDA if you'd rather have that in writing.
Next Step

Ready for that second opinion?
Book the first hour below and I'll come back to you within 24 hours to kick things off. If you'd rather ask a question first, send me an email.

People who trust me