The AI Tool Builders Fix Kit
Built for solo founders building and selling AI tools, AI apps and SaaS products.
Pieter Levels runs a multi-million-dollar business on plain PHP and jQuery — the stack was never the edge. This kit finds where the money leaks in your own work and gives you the steps and the words to close each one.
Opens secure checkout. Instant download after payment. 30 days to ask for a refund — refund policy · terms
The 11 leaks it covers
6 you can close it · 1 the other side owes it · 4 a pro decides
- EU users can bring the EU AI Act and GDPR to a US solo builderWhere to look first: Check whether people in the EU can sign up or use your tool, and whether you already have EU users.Keep it from coming back: Before launching in a new country or adding a feature that collects personal data, update your data list and ask whether new rules come with it.You can close it
- US duties that apply at any size: image takedowns and under-13 usersWhere to look first: Answer two questions in writing: does your tool make, host or share images of people? And could a child under 13 sign up, or has anyone told you they're under 13?Keep it from coming back: Before you add any feature that makes or hosts images of people, or opens sign-up to everyone, run the two questions again.You can close it
- Tool built on a provider feature with a shutdown date you haven't checkedWhere to look first: List every model, API and platform feature your tool calls, with the exact model or endpoint name.Keep it from coming back: Check your dependency list against every provider's deprecations page once a month, and before you build on any preview model.You can close it
- Months spent rebuilding when the gap was that nobody knew the tool existedWhere to look first: Nothing recovers the time already spent. Here is how you stop it recurring. For two weeks, log your hours each day in two columns: building, and getting in front of users (posts, demos, emails, calls, listings).Keep it from coming back: Before any rebuild, look at your build-vs-outreach log and the reasons real users gave. Code only fixes what they said.You can close it
- AI-generated code may not be copyrightable; undisclosed registration is at riskWhere to look first: Keep a record of what you wrote yourself: your design notes, the code you wrote or substantially reworked, how you chose and arranged AI output. Commit history with clear messages helps.Keep it from coming back: Log your own creative decisions and edits as you build, not after. That record is what a registration rests on.You can close it
- Platform subscriptions plus metered model costs never added into one numberWhere to look first: Pull last month's bank and card statements and list every charge for this tool: hosting, builder platforms, automation tools, model API bills.Keep it from coming back: Set a spending alert on every metered service the day you sign up, and total the whole stack once a month.You can close it
- Listed price vs what actually lands after store fee, billing fee and processor feeWhere to look first: Take your last month of payouts from each store and your payment processor. For each sale, write down the price, every fee taken, and what landed.Keep it from coming back: Before you set or change a price, run it through every fee layer for each store you sell in. Re-check fee pages when a store announces a change.The other side owes it
- The marketplace holds your users and billing, and you can't reach them without itWhere to look first: List every place people find and pay for your tool, and for each one, write down who holds the user's email and who takes the payment.Keep it from coming back: Before you launch on any new marketplace, write down who holds the user contact and who takes the money. Don't launch anywhere you can't build at least one direct line to your users.A pro decides
- Marketing that implies buyers will earn money, which brings FTC earnings-claim rulesWhere to look first: Go through your site, listings, ads, emails, videos and social posts. Mark anything that says or suggests a buyer will make money: a figure, 'passive income', a screenshot of earnings, a testimonial about income.Keep it from coming back: No new ad, page or post goes live with an income claim unless you hold written proof of typical results.A pro decides
- Nothing set aside for taxes from tool sales and payoutsWhere to look first: Open a separate savings account used only for taxes.Keep it from coming back: Move the tax share the day each payout lands. Put the 1040-ES due dates on your calendar at the start of the year.A pro decides
- Turning off provider filters or editing output can void the copyright indemnityWhere to look first: Write down which model providers and plans you use. Some indemnities only cover paid use.Keep it from coming back: Before turning off any filter or adding any post-processing step, check it against your provider's indemnity exclusions.A pro decides
Free: one full leak from this kit
No sign-up, no email. Here is leak 1 of 11 exactly as it appears in the kit, so you can see what you get before you buy.
EU users can bring the EU AI Act and GDPR to a US solo builder
You can close it- Check whether people in the EU can sign up or use your tool, and whether you already have EU users.
- If it's a chatbot or agent, tell users plainly at the first interaction that they're talking to an AI. That duty under the EU AI Act has applied since 2 August 2026.
- If it generates images, audio, video or text, find out whether your model provider already marks output as AI-generated. Tools already on the market before 2 August 2026 have until 2 December 2026 for that marking.
- For GDPR, write down what personal data you collect, why, and how long you keep it, and post a privacy notice.
- Ask a privacy attorney whether you need an EU representative and what else applies. If you'd rather not take this on, you can block EU sign-ups. That's a business choice.
Your part: Decide with your attorney what applies, add the notice, and make any change to who can sign up.
First-message AI notice for a chatbot: 'Hi, I'm [BOT NAME], an AI assistant made by [BUSINESS NAME]. You're chatting with an AI, not a person. [HOW TO REACH A HUMAN, IF OFFERED].' Questions for a privacy attorney: 'I'm a US solo builder. My tool [DESCRIBE]. EU users: [YES/NO/UNSURE, HOW MANY]. Data collected: [LIST]. 1) Does GDPR apply to me, and do I need an EU representative under Article 27? 2) Which EU AI Act Article 50 duties apply to my tool? 3) What's the minimum I need in place now?'
Before launching in a new country or adding a feature that collects personal data, update your data list and ask whether new rules come with it.
What this kit can't decide for you: Whether GDPR or the AI Act applies to your tool is a privacy attorney's call. Art. 27 wording taken from a secondary summary; confirm against EUR-Lex. The 2 Aug 2026 and 2 Dec 2026 dates are confirmed by two independent secondary sources (Baker Botts, Calmara), not yet against the Official Journal text.
That's 1 of 11. The other 10 come the same way in the kit: steps, words to send, a habit to keep each one closed.
Opens secure checkout. Instant download after payment. 30 days to ask for a refund — refund policy · terms
What people in this work look up
When people building and selling AI tools go looking for answers, they search things like “stripe fees”, “openai api cost”, “saas pricing models” and “app store fees”. Those searches turn up forms, averages and other people's numbers. This kit starts from your own records instead: the 11 places money leaks in this work, where to look first and the words to send to close each one.
What you get for each leak
- Numbered steps to close each leak
- Your part, spelled out
- Words you can use: letters and scripts, ready to send (fill in the brackets)
- A habit that keeps each leak from coming back
- An honest line on what the kit can't decide for you
A page from the kit
Questions people ask
How much do Stripe, app store and billing fees take from an AI tool?
More than the listed price suggests. Store fee, billing fee and processor fee each come off before money lands. The kit has you line up the listed price against what actually arrives, fee by fee.
How do I figure my real OpenAI API cost per user?
Add the platform subscriptions and the metered model costs into one number per month, then divide by paying users. Most builders never total them, so the price never covers the real cost.
Does the EU AI Act apply to a US solo builder?
It can, if people in the EU can sign up or already use your tool. The kit lists what to check first and which questions to bring to a privacy attorney.
What it can't decide for you
This kit works from your own records. It doesn't give legal, tax, licensing or financial advice, and it never tells you what to charge. Where a CPA, attorney, insurer or state board makes the call, the kit says so and gets your records ready for them.
15-page PDF · instant download after payment · Code VYR-KIT-CYRUS-01
Opens secure checkout. Instant download after payment. 30 days to ask for a refund — refund policy · terms
Use Jobber or Housecall Pro? Run the free leak check — it reads your job export in your browser and shows the money leaks the software doesn't flag. Nothing is uploaded.