UK · Oxford · Remote

Vibe-coded app stuck halfway?
I'll ship it.

AI code rescue for UK companies. Senior contractor who fixes, finishes and hardens apps built with Claude, Cursor, Lovable, v0 and friends. Production-ready code from AI prototypes — without throwing away what already works.

10+ years shipping production software · Lead Developer at Cap Energy · daily Claude Code user

The problem

AI got you 80% of an app. The other 20% is where products live or die.

Almost every "AI built our app in a weekend" story hits the same wall. Here is what I get called in to fix.

It works on the demo. Not on real users.

Edge cases, concurrent writes, weird inputs — the moment real traffic arrives, things start falling over.

No auth, no payments, no email.

AI tools love the visible 80%. The boring critical plumbing — sessions, billing, transactional email, audit trails — is missing or fragile.

Deploy is held together with string.

No CI, no migrations, secrets in the repo, one server that nobody dares touch. A single bad PR away from a long evening.

Nobody on your team understands the code.

The AI wrote it, the founder pasted it in, and now there is a 12,000-line codebase with no shared mental model behind it.

Services

Pay down your vibe debt, four ways

Pick the one that fits where your project actually is. Most engagements start with the audit.

Code rescue audit

Fixed-fee, ~1 week. A senior pair of eyes on your AI-generated codebase.

  • Architecture, security and maintainability review
  • Concrete punch-list of what to fix before launch
  • Effort estimates so you can plan the rebuild realistically

You inherited a vibe-coded prototype and need to know what you're actually shipping.

Finish-the-MVP build

Take your AI prototype the last mile to a real product.

  • Wire up auth, payments, email and the boring-but-critical bits
  • Replace fragile AI-generated patterns with code that scales
  • Ship to production with monitoring and a working CI pipeline

The demo wows on your laptop but breaks the moment a real user touches it.

Production hardening

Make a working app safe to leave running unattended.

  • Logging, error tracking, alerting and uptime monitoring
  • Database migrations, backups and rollback procedures
  • Security review: input validation, authn/authz, secrets, rate limiting

It's live, it's earning, and you're lying awake worrying about it.

Ongoing AI-assisted partner

A senior engineer in the room with your AI tools.

  • Pair with you (or your team) using Claude Code, Cursor, Copilot
  • Review AI-generated PRs before they reach main
  • Codify guardrails so your team can move fast without breaking things

You want to keep moving at AI speed without the technical debt catching up.

Who you'd be working with

Hi, I'm Nathan.

I'm a senior developer based in Oxford. I spend my days shipping production software — and using the same AI tools your prototype was built with. That gives me a useful double perspective: I know why AI-generated code looks the way it does, and I know what production traffic does to it.

Read more on my personal site: nathancollins.dev.

  • 10+ years shipping production web software
  • Lead Developer at Cap Energy
  • Led teams of 3–8 engineers; mentor for junior devs
  • Daily user of Claude Code, Cursor and Copilot
  • Stack-pragmatic: TypeScript, Vue/Nuxt, C#/.NET, F#, PostgreSQL, Azure
  • Open-source contributor (Zed F# extension, Neovim config)
How it works

From "help" to shipped, in four steps

  1. 01

    Discovery call

    30 minutes, free. You show me the codebase and the pain. I tell you honestly whether I can help and what shape the engagement should take.

  2. 02

    Audit week

    Fixed-fee deep read of the code, infra and dependencies. You get a written punch-list and effort estimates you can act on with or without me.

  3. 03

    Fixed-scope proposal

    Based on the audit, a clear quote with milestones, deliverables and a delivery date. No timesheets, no surprise invoices.

  4. 04

    Ship and hand over

    I do the work, ship it to production, and hand over documentation so you (or your team) can keep moving.

FAQ

Things people ask before they get in touch

What does "vibe coding" actually mean?

Vibe coding is what people now call building software by describing what they want to an AI (Claude, Cursor, Lovable, v0, ChatGPT) and shipping whatever it generates. It is brilliant for prototypes and brutal for production: the code often works on the demo and falls over the moment real users, real data, or real edge cases turn up.

Can you fix code generated by Claude, Cursor, Lovable or v0?

Yes — that is exactly the work. I use the same tools daily, so I can read AI-generated code quickly, spot the patterns that will bite you in production, and rewrite the parts that need rewriting without throwing away the parts that work.

Do you only work with UK companies?

I am based in Oxford and work primarily with UK-based companies — same time zone, UK contract law, UK invoicing in GBP. I will take occasional EU work where the timing is sensible. US clients welcome for short async engagements.

How quickly can you start?

Audits usually start within 1–2 weeks of the discovery call. For genuine "live and on fire" situations I will try to clear the next available slot — get in touch and tell me how urgent it is.

Will I be locked in to working with you long-term?

No. Every engagement ends with documentation and a handover so that you, your team, or another contractor can pick up where I left off. The point of the rescue is to leave you with a codebase you control.

What stack do you work in?

TypeScript, Vue/Nuxt and Node on the front and middle; C#/.NET and F# on the backend; PostgreSQL and SQL Server for data; Azure and Docker for infrastructure. I am stack-pragmatic — if your AI tool generated a React + Next.js + Supabase app, I can work in that too.

Can I just keep using AI to fix it myself?

Often, yes — and I will tell you so on the discovery call if that is what I think. The trap is that AI is excellent at generating code and merely competent at understanding why existing code is broken. Once a codebase has accumulated a few rounds of AI patches on top of AI patches, an experienced human eye is usually what unblocks it.

Get in touch

Book a call, or send me the details

Discovery calls are 30 minutes and free. If you'd rather write it out, the form goes straight to my inbox.

Book a discovery call

Pick a slot that works for you. UK time.

Embed not loading? Open Cal.com directly.

Send a message

Reply usually inside one working day.