QuezziesFree 15-min triageBuilt with Lovable, Bolt, Cursor or Replit?
The Launch-Blocker Sprint: I take the one problem blocking your customers, launch or revenue (broken sign-ins, payments, leaking data, failed deploys) and get it working in production. We agree what “done” means before you pay a penny. It passes, or you get a full refund and keep the work.
15 minutes, no pitch. You show me the blocker, I say yes or no on the call.
You already tried the AI tools, that's how the prototype exists. You're not paying for code an LLM can write. You're paying for an engineer to enter the real codebase, diagnose it, integrate the systems, deploy it, test it, and take responsibility for a pass or fail outcome.
One sprint, everything below, one fixed price. No retainer, no hourly meter, no scope creep.
A contractor at a normal day rate bills three weeks to do this, with no fixed price and no guarantee. An agency costs more and starts next month. But the real comparison isn't the price: it's what another month of not shipping costs you.
We agree the acceptance test before any work starts. If it doesn't pass within three working days, you get a full refund and keep every change I've committed. The risk is mine, not yours.
I run two sprints a month alongside my own company. When this month's two are booked, the next slot is next month. Next slot: w/c 3 August, 2 of 2 open.
Day 0
You show me the blocker. I say yes or no on the call. If it's yes, we write the acceptance test together, the sentence that defines done, and you reserve the slot.
Days 1 to 3
I work in your repository: diagnosis, implementation, focused tests, deployment to production, and a written handover of exactly what changed.
After
If the delivered outcome breaks within seven days, I fix it. No retainer, no meter. Then I hand you the Ship-Ready Report so you know what's next.
A good fit if
Not for you if
“Done” is a sentence we write down before you pay.
If it passes, the sprint passed. If it doesn't, you get your money back. Examples of a real outcome:
Case // data isolation
Any signed-in organisation could retrieve another organisation's records, even by guessing direct IDs. I scoped every read and write to the active organisation and proved it with adversarial tests: a second tenant attempting enumeration and direct-ID retrieval now gets nothing. Shipped through CI to production in two days.
Case // auth + release integrity
Internal service tokens authorised every request when unset, and builds couldn't be verified after deploy. I made every credential fail closed with constant-time checks, signed the artifact chain so tampered builds are refused, and made renders byte-reproducible. Regression tests pin all of it.
I'm Louis Newman, and you work with me directly: senior engineer, no handoffs, no juniors, no account manager. I build with the same agentic tooling that produced your prototype (Claude Code, Codex, Cursor-class workflows) every day, at the frontier. Which is exactly how I know where they break.
Shipped: Shift · Luna.ai · Threat Tracker · Priceable.ai · Magnetite.ai · Optimise Your Marketing
The 12 things that block AI-built apps from launch, data leaks, broken payments, deploys that only work on your laptop, and how to check yours in 20 minutes.
Yes. If you can show me the app and say what should happen in plain English, I handle the rest. The acceptance test is written in your words, not mine: "a customer can pay and gets access" is a perfectly good one.
You already did, that's how the prototype exists. An AI writes code; it doesn't enter your real repository, diagnose why production breaks, integrate the systems, deploy it, and take responsibility for a pass-or-fail outcome. That last part is what you're buying.
Because you're buying an outcome, not my time. We agree the acceptance test up front, so the price can't drift and neither can the scope. If it takes me longer than planned, that's my problem, not your invoice.
I'll tell you on the free triage call, before you pay. If it can't be given a concrete three-day acceptance test, I'll say so and point you somewhere better suited. One repository, one outcome per sprint.
Any stack. The deep end of my experience is TypeScript, React/Next.js, Node, Cloudflare, Stripe and Postgres, which is what most AI tools generate, but the sprint isn't limited to it. I work with the same agentic tooling that produced your prototype (Claude Code, Codex, Cursor-class workflows), and it reads any codebase. If I don't think your blocker fits a three-day acceptance test, I'll tell you on the free call and it costs you nothing.
Yes, read/write access to the one repository we're fixing, plus whatever deploy and service access the outcome needs. You keep ownership of everything delivered on payment in full.
Yes. I'll sign your NDA before seeing anything, or provide mine. Access is scoped to the one repository and the services the outcome needs, secrets stay in your infrastructure (I never copy them out), and access is revoked the day the sprint ends. Your IP is yours: everything I write is work for hire, owned by you on payment.
No claim form, no argument. If the acceptance test we agreed doesn't pass within three working days, I refund the full amount through Stripe, same rails you paid on, and you keep every change I've committed. The test is written down before payment, so there's nothing to dispute.
Book the free 15-minute triage or send me two sentences about what's blocked. You'll get a yes, a no, or one question within a working day.
Two sentences is enough: what should happen, what happens instead, and the deadline. I reply within a working day, usually faster. Or book the free triage call.
Fixed £4,500 · 3 days · pass-or-refund · next slot w/c 3 August
P.S. Two sentences is all it takes: what should happen, what happens instead, the deadline. Worst case, you get a free diagnosis of exactly where your app is broken. Best case, it's shipped by Friday.
Fixed £4,500 · pass-or-refund · next slot w/c 3 August