01 — Intake / free triage

App built, app broken? I get it launch-ready.

Stuck on a Lovable, Bolt, or Supabase build? Paste your exact error for a free read on the cause and the fix path — auth, RLS, Stripe, deploys, env vars, broken production flows. If it needs hands-on work, I scope one blocker and you pay only after it works. No secret keys, no vague "try rebuilding" filler.

Supabase authRLSOAuth PKCENext deploysCRUD breaks

Fig. 01

Intake specimen — a broken build, annotated. This is the kind of failure the free diagnosis reads in seconds: the cause, the location, the fix path.

02 — Procedure

One scoped blocker, fixed. You pay only after it works.

$90 Launch Blocker FixOne scoped issue, fixed

Auth · RLS · Stripe · deploy · env · white-screen. You get a root-cause note, the fix applied (or exact patch), a verification screenshot, a "what changed" handoff, and one 48h follow-up. Pay only after it works — bigger work is quoted first.

Care Lite — after your fixKeep it from regressing

A post-fix upsell, not a cold offer: on-call maintenance for an app that keeps breaking after changes. $69/mo.

Care Pro — after your fixFaster lane + monitoring

For apps with real users: more frequent fixes, deploy/auth/Stripe monitoring, iteration support. $129/mo.

$0 until it works

You only pay once the fix builds and runs. No result, no charge.

Your code stays yours

No production secrets in chat — temporary access you revoke after.

Scoped, never open-ended

One clear blocker. Anything bigger is quoted before we touch it.

Proof on every fix

Root-cause note + a build/smoke check, not just "done".

03 — Case files

Every fix closes with proof, not a promise.

untrusted repos executed — we diagnose from the error, not your secrets

real Supabase / Next failure patterns on file

build + smoke

required before any fix is called complete

04 — Field notes

Fix guides from real stuck-builder errors.

These pages are seeded from the lead radar. They are written to help first, then route people to the diagnostic when the failure needs a second set of eyes.

Permission denied despite correct RLS, as supabase.auth.getUser() returns null on serverRead fix path Next.js 16 App Router PWA + Supabase SSR: infinite loading on mobile/PWA (manual service worker likely caching RSC/Flight)Read fix pathSupabase Google OAuth PKCE Flow: "both auth code and code verifier should be non-empty" ErrorRead fix path @supabase/ssr with Next.js App Router: map markers disappear after magic link loginRead fix path Why can’t my client-side Supabase auth read the session after middleware sets cookies in Next.js 16?Read fix pathCloudflare Pages Worker fetch() returns "error code: 1016" for Supabase REST API, only from DFW edgeRead fix path Next.js build fails: Type 'string' is not assignable to type after Lovable/Bolt exportRead fix path Supabase insert fails: new row violates row-level security policy (42501) on INSERTRead fix path Supabase RLS: infinite recursion detected in policy for relation (42P17)Read fix pathSupabase login works locally but the session is lost after deploying to VercelRead fix path Next.js cookies should be awaited / used cookies - Supabase SSR authRead fix path

05 — Questions

The things you're right to ask.

Is my code and data safe?

Yes. You never paste production secrets — you grant temporary access and revoke it the moment the fix is verified. We diagnose from the error first; the repo is only touched once you've scoped and agreed.

What if you can't fix it?

Then you pay nothing. It starts with a free 15-minute triage — if it's not something we can fix cleanly, we say so up front. And the $90 is only charged after you confirm it works.

How fast is it?

Most single blockers — auth, RLS, Stripe, a broken deploy — are turned around within 24–48 hours of getting access. Urgent launches, sooner.

What's included for $90?

One scoped issue: the root-cause note, the fix applied (or the exact patch), a verification screenshot, a "what changed" handoff, and one 48-hour follow-up. Full rebuilds and new features are quoted separately.