From almost works to launched.
Your AI-built app, secured, finished and launched. Fixed price.
Secure checkout via Stripe · Refund policy
Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.
Illustration: a mountain range drawn in text characters, with a flag planted on the highest summit.
The problem
Almost works is the expensive part.
- Demo works, production does not
- Real users, real money, real data
- No one has read the code
Illustration: an unfinished highway bridge, its two sections not yet joined.
- 01
“It's 80% done. The last 20% won't move.”
> The easy parts are generated. The hard parts need decisions.
- 02
“Every fix breaks something else.”
> Duplicated logic and no tests, so each prompt fixes one copy and leaves the others.
- 03
“I can't read my own code anymore.”
> Thousands of lines that nobody has ever reviewed.
- 04
“Payments go through, but nothing updates.”
> Stripe webhooks missing, unverified or failing quietly.
- 05
“Anyone can read my database.”
> Row-level security off, or too open on key tables.
Trial audit scope
What I check.
Seven areas where AI-generated apps break once real users and real money arrive. I read the code and the configuration by hand, then test the flows.
Illustration: a stack of balanced stones.
- 01
Row-level security and authorization
Can user A read or change user B's data? I check every table policy and every API route, including the ones the UI never calls.
Supabase · RLS - 02
Auth flows
Sign-up, login, password reset, email change, session expiry, OAuth redirects and role checks, in production, not just on localhost.
Sessions · OAuth - 03
Exposed secrets
API keys in the client bundle, in the repo history or in public env files. Service keys that should never leave the server.
Keys · Env - See all 7 checks
Sample report
What you get back.
Every finding has a severity, the fix and what changes after it. The Trial finds them and fixes what fits in the 14 days. A monthly plan fixes the rest. This sample uses a fictional demo app, so you can see the format before you buy.
Audit report · demo-app
sample Fictional demo app, used to show the format. Not a client.
Lovable · Supabase · Stripe
Illustration: a beetle, as in a bug found in the code.
- 2 critical
- 1 high
- 1 medium
- 1 low
-
Profiles table readable by anyone
- Before
- RLS disabled on public.profiles. The anon key returns every row, including emails.
- Fix
- Enable RLS. Add select and update policies scoped to auth.uid() = id. Grant select and update on the table to authenticated.
- After
- Anon select returns 0 rows. Users only see their own profile.
-
Webhook accepts unsigned events
- Before
- The webhook handler trusts the request body. A forged event can mark an order as paid.
- Fix
- Verify the Stripe signature. Store event ids and skip duplicates.
- After
- Forged events get a 400. Replays are ignored.
- See all 5 findings
Pricing · USD
Fixed prices. Published.
Start with the 14-day Trial. If there's work left after it, take a monthly plan: a flat price, one task at a time, pause or cancel anytime.
Illustration: an ibex standing sure-footed on a cliff ledge.
- 00
Free Teardown
A 5 to 10 min recorded review of your live app's public surface.
- Screen recording with voice-over
- What a stranger can see and break from the outside
- Max 5 per week
Free
48h
- 01 Start here
14-day Trial
I audit one app, codebase, site, store or cloud account, then fix what can be fixed in the 14 days.
Fee credited to your first month if you start a monthly plan within 14 days of the Trial ending.
- Findings ranked by risk, in the first 5 business days
- Fixes for what fits in the 14 days, at the Limited pace
- A written plan for the rest, and 1 walkthrough call
$995
14 days, one time
Start · $995Secure checkout via Stripe · Refund policy
Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.
After the Trial, a monthly plan
Builds, fixes and CTO work all run on a monthly plan. Start one within 14 days of the Trial ending and the Trial fee is credited to the first month.
- Limited plan $1,995 a month · the slower lane, 4 seats
- Full plan $4,995 a month · first in line, 1 seat
The Trial guarantee
If the audit in the 14-day Trial doesn't find at least 5 concrete, actionable issues, the Trial is free.
Illustration: a calm sea drawn in text characters, slowly moving.
Portrait of Badii Boutar, drawn in text characters.
About
Built with AI. Finished by an engineer.
I'm Badii Boutar, a senior full-stack engineer with 7+ years of experience. I work alone, so the person you talk to is the person who does the work.
I led a platform migration for Clyso, a German tech company, added AI features to a live client product, and built Peeps, one of the most popular apps on Overwolf. I also built my own e-commerce platform that ran live stores with checkout and payments.
I use Claude Code every day. That's how I know where AI-generated code breaks: auth and session edge cases, missing row-level security, unverified Stripe webhooks, leaked keys and the same logic written three times.
- 11 Companies since 2019
-
-
-
-
-
-
-
-
-
-
-
- Built with
-
-
-
-
-
-
-
- Location
- Tunisia · CET (UTC+1)
- Online
- 09:00 to 20:00 CET
- Overlap
- Full EU day · US East Coast mornings
- Billing
- Registered business · USD, EUR or GBP invoices
How I work with your code
Safe to say yes.
Illustration: a bee gathering pollen on yellow flowers.
- 01
Fixed scope
You know what is included and what it costs before I start.
- 02
Code stays in your GitHub
I work in your repo, on branches you can review.
- 03
IP assigned on payment
Everything I write for you is yours once the invoice is paid.
- 04
Read-only access first
The audit needs read access only. Write access comes later, if at all.
- 05
NDA on request
Ask, and I sign one before you share anything.
FAQ
Questions.
Illustration: a statue of a seated man, deep in thought.
01 Do you need my passwords?
No. I never ask for your personal logins. You invite me as a collaborator on GitHub and your backend, with the lowest access that works. For the audit, that is read-only.
I only get write access when we start fixing, and you can remove it at any time.
02 What do you need from me to start?
For the audit: a read-only invite to your code (GitHub) and to your backend (for example your Supabase project), plus a few lines on what the app does and what worries you.
No passwords. Anything else I need, I ask by email.
03 What if my app isn't built with Lovable or Bolt?
That is fine. The audit covers web apps on a modern JavaScript or TypeScript stack, such as React, Next.js, Node.js, Supabase, Firebase or PostgreSQL, whether they were written by hand or with any AI tool.
Not sure your stack fits? Email me before you buy and I will tell you.
04 Lovable already scans my app. Why do I need this?
Lovable’s built-in scans are a good first pass, and you should run them. They read your code and configuration and flag what looks risky. Lovable’s own docs say they cannot guarantee complete security.
A scan does not use your app the way a customer does. It does not send the same Stripe webhook twice, or click a reset link in production to see where it lands. I read the code and the configuration by hand, then test the flows that matter for your app.
05 Will you rebuild my app?
No, not by default. I fix what you have. If part of it cannot be saved, the audit says so and explains why, with a price, before any work starts.
06 Who owns the code?
You do. The code stays in your GitHub, and all IP is assigned to you once the invoice is paid.
07 What happens after launch?
Every task ends with a handover doc, so you or another developer can take over. If you want me to keep it running, a monthly plan covers monitoring, backups, updates and fixes, one task at a time.
08 How do payments work?
The 14-day Trial is paid upfront. Monthly plans are billed from the day you start, and you can pause or cancel anytime before the next billing date.
Payments are processed by Stripe, and show on your card statement as BADII.STUDIO. Invoices are issued by Pan African Center for Entrepreneurship, in USD, EUR or GBP. Refunds follow the refund policy at badii.studio/refunds.
09 What time zone are you in?
I am based in Tunisia, CET (UTC+1), and online 09:00 to 20:00 CET. That is a full overlap with Europe and the morning on the US East Coast.
Start
Find out what stands between you and launch.
Start the 14-day Trial: your problems ranked in the first 5 business days, then fixes for what fits in the 14 days. Not ready yet? Ask for a free teardown.
Secure checkout via Stripe · Refund policy
Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.
Prefer to talk first? Book 30 min or email badii@badii.studio
Free teardown
48h · max 5 / week