Your vibe-coded app almost works. I’ll get it the rest of the way.
Want to work with an experienced software engineer to ship your app built with Cursor, Bolt, Lovable, Replit Agent, or other AI and vibe coding tools?
I’m spinning this up now and taking early clients soon. Drop your email and I’ll reach out when spots open.
No spam. I’ll email you when I’m taking clients and occasionally with useful stuff before that.
Sound familiar?
You used AI to build something real. A SaaS app, an MVP, something you’ve been thinking about for years. It works in the preview. It even looks pretty good. You’re maybe 80% of the way there.
Then it stops cooperating.
- You ask the AI to fix one thing and it breaks two others. You fix those and the first thing breaks again. You’ve been in this loop for days.
- It works on your screen but won’t deploy, or breaks the moment a real user touches it.
- You showed it to a developer friend and their face told you everything.
- You can feel there’s something wrong with the code but you can’t see it, and re-prompting isn’t getting you anywhere.
- You’ve been “almost done” for weeks and the momentum you started with is gone.
You built something real. The tools just ran out of road before you did.
What I bring to this
Nine years as a professional software engineer. My day job is full-stack dev in Node.js, React, and PostgreSQL, which is what most of these AI tools spit out. I can read what Cursor or Bolt wrote, spot the parts that’ll break under real use, and fix them without torching everything you’ve already built.
Most of what I’ve seen in AI-generated codebases is actually fine. There’s usually a handful of things that are quietly, specifically wrong, and once those are sorted, the rest holds up. You don’t need a $40k agency rewrite. You need someone who can tell the difference between code that works and code that just appears to.
I should be upfront: you’d be one of my first clients for this. I’ve written production code for close to a decade, but this particular service is new. What that means for you is more of my time for less money while I build a portfolio. I’m pricing early projects to be a no-brainer because I want to earn referrals, not maximize my first invoice.
How it works
Every project starts with a free code audit. I read through your codebase and tell you, in plain English, what you’ve got, what’s broken, and what it would cost to make it launch-ready. No commitment after that. If the honest answer is “this needs more than I can do,” I’ll say so.
If we move forward, the scope is defined and the price is fixed before any work starts. Here’s the kind of thing I’d typically handle:
Pricing
Code Audit
Free
Always. No strings.
Rescue Project
$1,500 – $5,000
Fixed price. Defined scope. Clear timeline.
You’ll know the exact number after the audit, before you commit to anything. No hourly billing.
Early clients get better rates. I’d rather do great work at a discount and build a track record than squeeze margins on day one.
What happens if you don’t fix this
You already know. The project sits at 80% for another month. You try re-prompting a few more times. Maybe you hire someone off Upwork and they quote you $10k to rewrite the whole thing from scratch, which sounds wrong because most of it works. Eventually you move on to something else and the app you built just sits there.
Or someone else ships the same idea. Or you get a security scare. Or an investor asks for a demo and you have to explain why the checkout flow breaks on mobile.
Questions you’d probably ask
Interested?
I’m getting this off the ground now. Get on the list and I’ll email you when I’m taking projects.
I’ll only email you when there’s something worth saying.