NILSON
← Home

Code Rescue · application repair

Your AI says everything works.Are you sure?

A button that does nothing. A sign-up that crashes. An error nobody can explain. Send me your application: I’ll help you find what’s blocking it.

Get my app diagnosedHow it works
  • Every request read by a person
  • Written quote before any payment
  • Never a password

See what I can fix ↓

Code Rescue report · excerptFictional example: what one report entry looks like.

#1 Payment captured, access not granted

High risk
Reproduced
Yes, in production, 3 attempts out of 3
Observed
Stripe confirms the payment; the account stays on the free plan.
Expected
Pro access is active within a minute.
Root cause (confirmed)
Production used the local webhook secret: every event was rejected (HTTP 400).
Verification
Passed: test payment in production, access granted in 4 s.
Tests
2 added: invalid signature, event delivered twice.
Limitations
6 customers who paid before the fix need reactivating (list provided).

For applications built with

  • Lovable
  • Cursor
  • Claude
  • Bolt
  • Replit
  • Next.js
  • Supabase
  • Stripe

Names describe the tools involved — no partnership, no affiliation.

01 — Sound familiar?

Sound familiar?

Common situations in applications generated or accelerated with AI. Common, not automatic: yours may have none of them.

02 — What I can fix

The defects that stop an application from doing its job.

Identifiable functional defects in an application that already exists. Not a redesign, not a new feature.

  • Login and sessions

    Sign-up, login, password reset, sessions that expire or get mixed up, redirect loops, Google or GitHub sign-in.

    Supabase Auth · Auth.js · Clerk · Firebase Auth

    Describe this problem →

  • Payments and access

    Checkout, webhooks, subscriptions: access that does not follow the payment, an event processed twice, an amount that does not match.

    Stripe Checkout · Billing · webhooks

    Describe this problem →

  • Database and permissions

    Queries that fail, data that disappears, access rules (RLS) that block real users or let too much through, broken migrations.

    Supabase · PostgreSQL · Firebase

    Describe this problem →

  • Buttons, forms and states

    A button that does nothing, a form submitted twice or never, missing validation, an endless spinner, data that never refreshes.

    React · Next.js · Vite

    Describe this problem →

  • APIs, webhooks and emails

    API calls that fail or hit rate limits, misconfigured keys, unverified webhooks, emails that never arrive.

    REST · webhooks · Resend · SendGrid

    Describe this problem →

  • Deployment and environments

    It works locally, not in production: environment variables, a broken build, an updated dependency, caching, domains, CORS.

    Vercel · Netlify · Node.js

    Describe this problem →

  • Regressions and recurring errors

    Every fix breaks something else, an error comes and goes, a page slows down: I find the cause, then pin the right behaviour with a test where it makes sense.

    Tests · logs · reproduction

    Describe this problem →

03 — How it works

Four steps. Nothing is paid before the third.

  1. Step 1 : You describe the problem.

    Four short steps: what isn’t working, what should happen, your stack, your email. No access, no password.

  2. Step 2 : I review it myself.

    I read your request, ask what is missing, then confirm the scope and the package. If it is not a fit, I tell you.

  3. Step 3 : Written quote, then access.

    Scope, exclusions, acceptance criteria, price, timeline. You pay online when you accept; code access is set up at that point, with your agreement.

  4. Step 4 : I fix and verify.

    The fix within scope, the behaviour verified, tests where they make sense, and a report that says what is solved — and what is not.

04 — Pricing

Three packages. A written quote before you pay.

Starting prices, in CHF. The final price is written in the quote, after your request has been reviewed: nothing is charged on the strength of the form alone.

Bug Diagnostic

You don’t know where the problem comes from. I find it and explain it.

from CHF 149

Fixed price once the scope is confirmed

For founders who cannot identify the source of a specific problem.

Timeline
2 business days after access is set up
After delivery
1 rework round after your review

Included

  • Review of one bounded reported issue
  • A reproduction attempt, where feasible
  • The likely root cause, explained plainly
  • Severity and business impact
  • The recommended fix and its size
  • A written diagnostic in your project space

Not included

  • The fix itself (quoted afterwards)
  • Unlimited debugging or other issues

No fix period (no code delivered)

Describe my problem

Code Fix

One identified functional defect, fixed and verified.

from CHF 490

Fixed price once the scope is confirmed

For one clearly identified functional defect.

Timeline
3 to 5 business days after access is set up
After delivery
1 rework round after your review

Included

  • A defined reproduction scenario
  • Remediation of the agreed scope
  • Regression verification of the affected behaviour
  • Code delivered by the agreed method (pull request, branch, patch)
  • A short verification report
  • Handoff notes

Not included

  • Several or unlimited fixes
  • New feature development
  • Infrastructure migrations

Defects in the delivered work fixed for 14 days

Describe my problem

Stability Sprint

Several related issues, handled within a bounded scope.

from CHF 1’490

Always quoted

For several related technical issues within an agreed scope.

Timeline
Per quote, usually 1 to 2 weeks
After delivery
2 rework rounds after your review

Included

  • A prioritised defect list
  • A defined remediation scope
  • Regression tests on the critical paths
  • Better error handling where it matters
  • Delivery documentation
  • A clear list of unresolved risks

Not included

  • Rebuilding the application
  • New features
  • Infrastructure migrations, unless the quote says so

Defects in the delivered work fixed for 30 days

Describe my problem

A complex problem is assessed before any quote. I promise no repair before I have examined the code.

05 — The report

A report that says what is fixed. And what is not.

Every engagement ends with a remediation report in your project space, printable. For each issue:

  1. An identifier
  2. Reproduction steps
  3. Observed behaviour
  4. Expected behaviour
  5. Root cause, or documented uncertainty
  6. Files and components affected
  7. Risk level
  8. Proposed remediation
  9. Changes made
  10. Verification performed
  11. Regression tests
  12. Remaining limitations
  13. Delivery reference (pull request)
  • A test that was not run is never marked as passed.
  • An issue I could not reproduce is reported as such, never as fixed.
  • What remains open is listed, with the reason.

Diagnosis

Describe what’s broken.

Four steps, three minutes. No access, no password: only what you can see. I read every request myself and reply within 24 hours, Monday to Friday.

Already sent a request? Find my project space

Without JavaScript, every step shows on one page.

What isn’t working?
Describe the problem.

Copy the text you see (screen, console). Remove keys and passwords: anything that looks like one is removed anyway.

What is the impact for you? Optional
Tell me about the application.

Nothing is analysed automatically.

Public or private. Do not grant any access now: it is arranged after qualification, if needed.

Technologies, if you know them Optional
Where is the application at? Optional
How urgent is it? Optional
Where should I send my reply?

A question, a written proposal, or a reasoned no if it is not a fit.

06 — Access and security

Your code, your keys, your customers: nothing more than needed.

No secrets in the form
No password, API key, environment variable or customer data. If you paste one by mistake, it is removed before anything is stored — rotate it anyway.
The repository is never opened automatically
The link you give is not cloned, executed or analysed by a robot. Code access is arranged after qualification, with your explicit agreement: an invitation to that one repository, removed at the end.
Nothing is deployed without your written approval
Delivery is a pull request, a branch or a patch. You stay in control of what goes to production.
Test keys, test environment
I work with test keys and, where possible, a copy or a test environment. A non-disclosure agreement (NDA) is available before any access.

07 — The right service

Code Rescue repairs. Other services do something else.

  • It works badly: bugs, crashes, broken integrations.

    Code Rescue

  • It works, but it looks dated or confusing.

    Design Rescue →Page in French

  • It works and looks good, but visitors don’t convert.

    Conversion Rescue →Free scan of the page

  • You launch soon and want to know what blocks it.

    Launch Rescue →Free self-assessment on the page

  • You want to check it yourself first, for free.

    ShipCheck →Free checklist, in French

  • The product is live and the work is wider than a few defects.

    AI Product Rescue →

  • The problem is bigger than a few defects: architecture, a rebuild.

    Product engagement →

08 — Who does the work

Me. Not an agency, not a robot.

I am Danilson Ramos, a product engineer in Zürich. I build and run Next.js, Supabase and Stripe applications in production, with real payments and real users.

The person who reads your request is the one who fixes the code and signs the report. No subcontracting, no middleman.

Products I built and maintain:

See the work →More about me →

Frequently asked questions

  • Can you fix code generated by Lovable?

    Yes. Lovable usually produces a React (Vite) application with Supabase, which is ground I know well. To fix it I need the code: Lovable can sync the project with a GitHub repository, I work on that repository and the fix comes back as a pull request. Same approach for Bolt, Replit, Cursor, Claude Code or code written with ChatGPT.

  • Can you work on a private GitHub repository?

    Yes, after qualification and with your agreement: you invite me as a collaborator on that one repository (access removed at the end), or you share a copy. The form asks for no access, and the link you put in it is never opened automatically.

  • What if the problem cannot be reproduced?

    I say so in the report, with what I tried, what I ruled out and what would help reproduce it (logs, steps, a test account). An issue that was not reproduced is never presented as fixed. When that is clear from the start, a Bug Diagnostic is the right package, not a fix.

  • Can you fix Stripe or Supabase integrations?

    Yes, they are among the most common requests: unverified or double-processed Stripe webhooks, access that does not follow the payment, Supabase row-level security that blocks real users or lets too much through, Supabase Auth sessions. I work with test keys, never your production keys.

  • How are changes delivered?

    As a pull request or a branch on your repository (or a patch if you prefer), with the report in your project space. The delivery method is written in the quote. I deploy nothing to production without your written approval.

  • Do I need to provide production credentials?

    No. No password, no production key, no export of your customer data. I work on the code and a test environment; if extra access is genuinely needed, it is agreed in writing, limited to what is necessary and removed at the end.

  • Is there a guaranteed fix?

    No, not before I have examined the code: nobody honest can promise to repair something they have not seen. What is guaranteed: a written scope, acceptance criteria and a truthful report. If the delivery does not meet the criteria in the quote, I rework it; if I cannot, you are refunded. The rules are in the terms.

  • How is pricing determined?

    The packages give a starting price: Bug Diagnostic from CHF 149, Code Fix from CHF 490, Stability Sprint from CHF 1’490. The final price depends on what the review shows — number of defects, size of the code, access, risk — and it is written in the quote before any payment. A complex problem is always assessed before it is priced.

  • Which technologies do you work with?

    Mostly TypeScript and JavaScript: Next.js, React (Vite), Node.js, Supabase and PostgreSQL, Stripe, Vercel, Netlify, Firebase. No native mobile apps. If your stack is outside that, I tell you before any quote.

Show me what’s broken.

Reading your request and replying costs nothing. You only pay when you accept a written quote.

Get my app diagnosed

A question first? Email me: danilson.daveigaramos.pro@gmail.com