Firme.RESCUE

RESCUE · Fixing AI-built apps

Built an app with AI and it got stuck? I unstick it in days.

You built it with Lovable, Bolt, v0, Base44, Replit or Cursor. It worked — until it didn't. I find the problem, tell you in writing what's wrong, and give you a fixed price to fix it. No hourly billing, no surprises.

First reply within 48 h No calls, all in writing

From "I don't know what's wrong" to "fixed and running", with every step on the record.

Platforms

I rescue apps built with these tools

With five of them I get the full code and fix it as if it were mine. With Base44 only the front end reaches GitHub; if the fault is in the data or the server logic, the diagnosis tells you whether a migration is needed.

Lovable Bolt v0 Base44 Replit Cursor

Is your app on Base44? Base44 exports only the visible part to GitHub (the front end: buttons, screens, text). The database, user sign-up and internal functions stay on their servers and can't be touched from GitHub. If the problem is in the front end, I fix it just like with the other tools. If it's in the data or the server, the diagnosis tells you plainly: what's needed is migrating it to your own system, with no lock-in. That's the Rebuild package. I tell you in the diagnosis, no commitment.

Pricing

Fixed prices. No hourly counters.

You know the cost before I write a single line of code. You approve, I work.

Diagnosis

€149

I review your code, reproduce the issue, and send you a written report: what's wrong, why, and a fixed price to fix it. Within 72 h of getting access to your code. In a hurry? 48h for +€99, billed only if I accept the rush.

The diagnosis is a product, not a coupon: it doesn't come off the repair price. The report is yours either way — whether you hire the fix or not.

The countdown starts when I have access to the code, not when you pay.

The diagnosis tells you which of these four you need. You don't choose — what's wrong with your app does.

Emergency Fix

€590

5 days. “Just fix it.”

One bug: the one the diagnosis names. I fix it, hand it over as a Pull Request you approve before it goes live, and a 2-minute video walking you through it.

Not included: anything else that turns up along the way. Another bug is another package.

Security Pass

€1,290

7 days. “Is it safe?”

Row-level security switched on, with real policies on every table (RLS). Secrets moved out of the repository, with rotation documented. Every API route that returns data requires authentication. I review sessions, redirects and roles. Closing report with before and after.

Not included: pentest, certified compliance or SOC2.

Launch Pass

€2,490

10–14 days. “Put it into real production.”

Everything in the Security Pass, plus a deploy that actually works: environment variables, build, domain and SSL. I resolve the critical- and high-severity findings from the diagnosis and set up basic error monitoring.

Not included: new features, redesign or scaling to 10,000 users.

Rebuild

from €6,000

3–5 weeks. “It's dead.”

I keep what genuinely works —the UI and your real business logic— and rewrite the scaffolding underneath. Data migration included. Clear scope, fixed price.

Note: €6,000 is the floor for a small app. Most land between €8,000 and €15,000.

14-day guarantee: if the same issue comes back within 14 days of delivery, I fix it at no cost. The code's change history is my notary record: everything I touch is logged there.

Security — yours and mine

House rules

Three non-negotiable conditions, and all three protect you.

House rules

1. Invitation-only access, never passwords.

You invite me with two clicks to the tools where your app lives: GitHub (the code) and, only if the fault requires it, Supabase (the data) or Stripe (the payments). Always as a guest with limited permissions, everything logged, and you revoke my access when we're done. I never ask for passwords or access to your money.

2. Honest 14-day guarantee.

If what I fixed fails again, I fix it free. One limit: after delivery, if your AI tool touches the files of the fix again (it's logged in the code history), that part loses the guarantee — the AI can step on my work without you noticing. If you want to keep using your tool with a safety net, the monthly maintenance plan is available. Ask for details and pricing →

3. Your data and your users' data.

I work on a copy with test data whenever possible. If real data has to be touched, we first sign the data protection contract required by EU law (GDPR). Without that paper, I don't touch data.

How it works

Four steps, all in writing

No calls, no shared passwords, no access to your billing.

Step 1

You describe the problem

Which tool you built it with, what fails, what error message you see, and what you've already tried.

Step 2

You invite me to the code

You give me collaborator access to your GitHub repository. Not sure how? I'll send the 2-minute guide.

Step 3

Diagnosis and fixed price

For €149 you get, within 72 h, the report: what's wrong and what it costs to fix. The countdown starts when I have access to the code, not when you pay. You approve before I touch anything.

Step 4

Fix and delivery

You get the proposed change to approve, a video showing it works, and clear instructions. 50% on delivery.

FAQ

What people ask before we start

If your question isn't here, write to me and I'll reply in writing within 48 h.

I'm not technical and I don't know what GitHub is. Can I still hire you?

Yes. Most of my clients aren't technical: that's why they built their app with AI. I send you a 2-minute guide, with screenshots, to invite me to the code from your specific platform. If you get stuck, we sort it out in writing.

What if my app can't be fixed?

The diagnosis tells you honestly. If rebuilding it is more worthwhile than patching it, I give you a fixed price for the rebuild and migrate your data. The decision is always yours, with the information in front of you.

Do you charge by the hour?

No. Fixed price before we start, always. If it takes me longer than expected, that's my problem, not yours.

Why don't you do calls?

Because calls don't fix code. Everything in writing means you can reread every agreement, every update and every instruction whenever you want. And every hour I don't spend in meetings is an hour working on your app.

Can I keep using Lovable/Bolt after the fix?

Yes, it's your app. But here's an honest warning: the AI can modify the fix without telling you. Everything is recorded in the code history, so if it happens, it shows. If you want to keep using your tool with a safety net, the monthly maintenance plan is available. Ask for details and pricing →

Do you see my users' data?

I work on a copy with test data whenever possible. If real data has to be touched, we first sign the data protection contract required by EU law (GDPR). Without that paper, I don't touch data.

Start

Request your diagnosis

A few details, and within 72 h you know what's wrong with your app and what it costs to fix. The countdown starts when I have access to the code, not when you pay.

Step 1 of 3: your code and what fails

I need to see the code to diagnose it. Paste the link to your repository.

No repo yet? In Lovable: Settings → GitHub → Connect Repository. Two minutes. In Bolt: the GitHub icon, top right.

⚠️ Base44 only exports the visible part to GitHub. If the fault is in the data or the server, it usually means a migration: that's Rebuild, not a fix.

Step 2 of 3: turnaround and data

Two details that set how I handle your case.

How soon?
Is there real personal data in the app?
⚠️ I work with a copy of test data. Touching real personal data requires a data protection contract first (GDPR, art. 28).

Step 3 of 3: where do I write to you?

I reply within 72 h of getting access to your code with the diagnosis and the fixed price.

Your request: Reviewing...
Your email app opens with the message already written. You just press send.

Or write directly to rescue@firme.dev