An empty folder to an app on sale, in eight steps.

One thing is genuinely unavoidable and everything else has a free tier that lasts longer than your first app will need. The ninety-nine dollars is the unavoidable one, so it is listed first.

I checked these prices in August 2026, and they move. Treat this as the shape of the bill rather than a quote, and check each one before you rely on it.

For: you have an app, and something is wrong with it. Or you are about to submit, and want to know what Apple will flag before Apple flags it.

Point it at your App Store Connect account and it reports what is actually true, rather than what the web interface implies. It catches the failure that cost me eighteen days: a version reading WAITING_FOR_REVIEW while no live submission holds it. If you are shipping your first app, you will not hit that one. It is already checked for.

It only ever issues GET requests. By construction it cannot change a listing, cancel a submission or touch a price, which is what makes it safe to hand to an agent.

For: you already have a project, and you release it over and over.

The fastlane lanes behind every release I ship. Manual-signing export that survives a certificate wipe, TestFlight distribution, submission with in-app purchases attached the way Apple actually requires, and the analytics report requests you have to create before you launch rather than after, because Apple records nothing about the days before you ask.

Each lane exists because the manual version of it failed at least once on a real release.

For: you have never shipped an app, and you want a build on TestFlight this week.

The run above is real: 23 files, a generated project, and a green test suite before a line of your code exists.

Extracted from shipping CardHabit and Lab Tycoon, both live on the App Store, and still what I use.

The two tools above are free and they are not for you yet. Both of them operate on a project, and you do not have one. That is the actual gap this fills: it creates the project those two tools need before there is anything to point them at.

You start with an empty folder and a description of the app you want. It scaffolds the project, wires the release pipeline in from the start, sets up signing, and gives Claude Code the skills to walk you through all eight steps above rather than working them out from first principles. Your first TestFlight build takes about an evening. You will need an AI coding agent alongside it, Claude Code or Cursor or any tool that reads an AGENTS.md; that is the twenty-dollar line in the bill above, and the skills are what it runs.

Everything on this page ships inside it: the release commands, the checks and the agent skills, assembled and tested on my own releases. The thirty-three days at the top of the page is what these steps cost me to learn alone. The price buys the version where the mistakes are already made.