The ThriveMom Playbook

Put your app in the App Store.

I have ADHD, and I shipped one while raising three kids. Not a demo: a real product, with paying customers. Six lessons, and the exact method is yours.

Live in the Apple App Store Lifestyle & Productivity Real product, paying customers

ThriveMom's Chaos Catcher screen on iPhone. ThriveMom's daily check-in screen on iPhone. ThriveMom's features menu on iPhone.
Capture · get it all out
Heidi, who built ThriveMom.

Why me

If you can write a prompt, you can ship an app.

I'm Heidi. I have ADHD, and I built ThriveMom with Claude while raising three kids. Same constraints you have.

Most courses teach a demo built for the camera. I'm walking you through a real launch: every decision, every tradeoff, the method written down.

That's the thing for sale. Not the app. The way it got made.

What you get

Six lessons, one real launch.

The exact path I took ThriveMom from a rejected chatbot to live in the App Store, one real step at a time. Watch in order, or jump to the one that unblocks you today.

  1. Why I built ThriveMom Why I started building software when I wasn’t a developer. How a rejection from Meta turned into an approval from Apple. And why the app you end up launching is almost never the app you set out to build.
  2. The tools I actually used The AI tools I used for a year before building ThriveMom, and what each one is actually good for. Why Cursor was different. And why I started practicing with a friend’s website before building my own app.
  3. How Claude built the first feature How I built Chaos Catcher, ThriveMom’s first feature, inside Cursor with Claude. How I organized the project files so Claude worked faster and cheaper. And how to write prompts that produce code that actually works, not just code that looks like it works.
  4. The day I almost exposed my users’ data Why I tried three different sign-in methods before finding the right one. How Claude found a security problem I hadn’t noticed. And why I pushed back the app launch by a week when I discovered what was wrong.
  5. How I set up payments before the first customer How I decided ThriveMom’s price. Why you need two different payment systems (Stripe for web, RevenueCat for iPhone) and how to avoid getting rejected by Apple for mixing them. Why I set up payments before I had a single paying user. And the specific places RevenueCat made me lose entire days, so you don’t lose yours.
  6. The 5:57 AM approval and the business question What happened the morning my app finally landed on the App Store. Why approval wasn’t the end, but the start of a harder question. And the question I had to answer honestly, the one you’ll face too: what is this app, really, for you?

The honest fit

Who this is for.

You have an idea for an app. You've used ChatGPT, Claude, or Gemini and you can write a clear prompt. You're not afraid to read code Claude writes, even if you can't write it yourself. You want a real product with paying customers, not a side project that lives on your laptop. You're done with tutorials that promise everything and teach nothing specific.

If that's you, the method works. Six lessons, one real launch, every decision in the order I made it.

Three ways to build

Pick how you work.

Self-study

Watch and build it yourself.

$297

Founding price $197, first 25 seats.

  • 6 lessons (~45 minutes), each anchored on a real decision from the launch
  • The full Founder Asset Pack: CLAUDE.md template, BRAND.md template, 6-prompt build pack with anti-prompts, security audit pack, RevenueCat pre-flight, Apple submission checklist, first 30 days playbook, pricing worksheet
  • A reading map showing which asset to use when
  • Lifetime access, including future updates and new assets
Buy now

Done-with-you

Build it with me, one-on-one.

$1,500

Founding price $1,200 for the first 2. Three slots per cohort.

  • Everything in the cohort, including the full Founder Asset Pack
  • 90-min 1:1 strategy call before week one
  • A custom scoping doc for your app
  • 30 days of async Slack with me
  • Priority access to the cohort live sessions
Apply

The risk is mine

Watch it, and if it isn't what I promised, I'll refund you.

Self-study: 7 days, no questions. Cohort: 14 days, or before the first live session, whichever is later. Done-with-you: refunded any time before the 1:1 call. Simple.

Before you decide

Eight honest answers.

Do I need to know how to code?

No. You write prompts. Claude writes the code. You read it, approve it, ship it. By the end you understand the stack well enough to hire or direct a developer, but you never have to write it yourself.

How long until I ship?

The cohort runs four weeks. Most cohort buyers ship a beta by week six and a paid version by week eight. Self-study moves at your pace.

What stack do you teach?

The same one ThriveMom runs on: Cursor with Claude for building, plus ChatGPT and Gemini for design and research. Supabase for accounts and data, Stripe on the web, RevenueCat for iPhone payments, and Resend for email. The patterns transfer if you use a different stack.

What if I'm only building for the web, not the App Store?

The method is the same. Lessons 4 and 5 cover web auth, web payments through Stripe, and the database setup that works for both. The App Store-specific content (Lesson 6, the RevenueCat checklist, the Apple submission checklist) becomes optional reference. You won't waste time on it, and if you change your mind later, it's there.

What if Apple rejects my app?

Apple rejected me twice. The first time was a question I shouldn't have asked at onboarding. The second time was a missing EULA link and a misconfigured in-app purchase. Both were preventable. The Apple submission checklist in the asset pack lists every common rejection reason and how to avoid it. If you do get rejected, you'll have specific guidance for the resubmission.

Who is this NOT for?

If you already know how to ship software, this is too basic. If you want a no-code drag-and-drop tool, this isn't it: you'll be writing prompts and reading the code Claude generates. If you want a generic "build with AI" course, the specificity here will frustrate you. This is for one specific person: someone who wants to ship a real software product, with paying customers, using Claude and Cursor, and is willing to read the code she ships.

How is this different from a YouTube tutorial?

YouTube tutorials show a demo built for the camera. This is a post-mortem from a real launch. Every lesson is a decision I actually made, including the wrong ones. The asset pack (the templates, the prompts, the checklists) is what I use every day, not what I made up for the course. If you can find a YouTube tutorial that includes a production CLAUDE.md template, a 6-prompt build pack, and an Apple rejection-prevention checklist, take it. I haven't found one.

Why no free preview?

Because the method is the product, and free previews train buyers to wait. The first lesson is what convinces you the rest are worth reading. Giving it away undermines the whole training. If $197 founding pricing is a risk you can't take, this isn't the right purchase yet.

Mine is live.
Yours is next.

Cohort $497, self-study $297. Founding seats $397 and $197 for the first few. Cohort starts July 5.