34-Day Launch Curriculum → July 31 Launch

Your ICP might be "people who want to budget better" — far too broad. Margolis's concept: the bullseye customer is the tiny, specific subset of your market most likely to adopt first. For budgeting apps this is often a person with a trigger event: just got their first real paycheck, just got married and merged finances, just got out of debt and wants to stay out, or just failed at YNAB because it felt like homework. People with a fresh, burning financial pain try new tools. People with a comfortable routine do not.

The corollary — Fitzpatrick's Mom Test — is that when you talk to these people you will be lied to, kindly. "Oh that sounds great, I'd totally use that" is worth nothing. The three rules: talk about their life, not your idea; ask about specifics in the past, not opinions about the future; talk less and listen more. So instead of "Would you use a budgeting app that does X?", you ask "When was the last time you looked at your spending? Walk me through that." If they haven't recently tried to solve the problem, they won't buy a solution to it — Fitzpatrick's rule of thumb.

For your app: do not interview your friends, do not interview other founders. Find 5–8 people in your bullseye (r/personalfinance, a local meetup, your network's "person who's always stressed about money"). The goal of tomorrow's implement day is not to validate your idea — it's to map their actual money behavior and the words they use to describe their pain, so your landing page and DMs sound like their inner voice, not your marketing voice.

Harry Dry's three rules of memorable copy — visualize, falsify, be unique — are exactly what a budgeting app needs. "Visualize" means your claim should paint a picture ("see exactly where last month's $400 went" beats "powerful spending insights"). "Falsify" means make a concrete, checkable claim ("connects to 12,000 banks in under 60 seconds" beats "fast bank sync"). "Be unique" means a line only you can say — the Volvo-speedometer-move. Generic copy ("take control of your finances") is what every budgeting app says; it signals "me too" and gets you ignored next to YNAB's cult.

But copy for a money app carries an extra burden: trust. People are giving you read access to their bank accounts. Your page must signal credibility through specifics — founder photo and story, real screenshots not mockups, a clear "your data is encrypted / read-only / we can't move your money" section, and the human reason you built this (Day 13's build-in-public ethos, but compressed into your About). Storytelling — "I built this because I kept failing at YNAB and losing my spouse's receipts" — outperforms feature lists for trust. People don't trust feature matrices; they trust a person who had the same problem.

Structurally, use the PAS shape for the middle of the page (Problem-Agitate-Solution) and a single, repeated call to action. The hero carries your 7-word value prop from Day 2. Every section should answer the reader's silent question: "is this for someone like me?" — which is why your bullseye language (from Day 4) belongs on the page, verbatim.

Campbell's key reframe: pricing is the most important lever you have, and it's almost never set deliberately. Most founders copy a competitor or pick a round number. His framework has four decisions: (1) packaging — how many tiers and what's in each; (2) value metric — the primary unit that determines how much a customer pays (for budgeting this is often "accounts tracked," "household members," or "months of history"); (3) price point; (4) promotions/discounts.

For a consumer budgeting app the market has already set anchors you should respect: YNAB ~$109/yr, Monarch ~$100/yr or ~$15/mo, Rocket Money "pay what you want" from ~$6/mo, Copilot ~$95/yr. Going far above these without a dramatically better wedge is death. Going far below signals "cheap/toy." A safe opening for a new entrant targeting first-100: a generous free tier (to drive the manual engine + PLG) + a $7–12/mo or $59–79/yr paid tier that unlocks the wedge value.

The packaging decision matters more than the number. Campbell warns: don't just dump features into a pricing table with checkboxes — that educates no one and makes people calculate instead of feel. Frame tiers by who they're for ("Solo" vs "Couples" vs "Household") and by the outcome. A freemium structure that lets people experience the core habit (categorize this week's spending) for free, then pay to unlock depth (net worth, forecasting, shared budgets) is the standard consumer-finance pattern — and it sets up your PLG activation work on Day 19.

This video is the spine of your entire launch. Mahadevan's three steps map almost perfectly onto a budgeting app:

1. Find where demand is aggregated (the watering hole). Don't go into the desert hoping thirsty people wander by. Go to where budgeters already gather and are already complaining about their tools: r/personalfinance, r/Budget, r/ynab, r/Fire, r/personalfinancecanada, the Bogleheads forum, personal-finance TikTok/YouTube comment sections, Facebook budgeting groups. Search these for "budgeting app" and "YNAB alternative" — you'll find live demand. The takeaway: a quick win is literally searching Reddit for your wedge phrase and finding people already asking for exactly what you built.

2. Become the expert, not the salesperson. This is the part most founders violate. Do not jump in pitching your app. Answer their question, solve their problem, provide value with no ask. If your profile/footprint makes clear what you build, the right people will ask you. The frame: you're a solution-solver, not a shiller. You build trust up front, and even non-buyers give you the objections and questions that sharpen your pitch for the next 100.

3. Make a founding-members killer offer. The first customers need a reason to bet on an unknown app. "Founding member" pricing, lifetime deal, direct founder access, a hand-written onboarding — these aren't discounts of value, they're hustle. Mahadevan knew his first 100+ customers by name because they were all in his WhatsApp. For a budgeting app, the analog might be: free first year + a 20-min onboarding call with you + a private "founding members" feedback channel. You can't do this at 10,000 customers. You don't need to. You need it for 100.

Paired with YC's broader "do things that don't scale" doctrine: manually recruit, manually onboard, manually handhold. It feels inefficient. It is the only thing that works at zero-to-one for consumer SaaS.

The counterintuitive heart of YC's first-users guidance: you are not persuading, you are searching. Most people will never be a startup's first customer — that's fine. Your job is to find the rare person who either (a) has a burning, current money problem your wedge solves, or (b) loves trying new tools. These people exist in every community. They self-select by their behavior: they're the ones posting "I hate YNAB's interface, is there anything better?" or "just got married, how do couples actually budget together?"

Reach them with targeted personal outreach, not mass marketing. A billboard won't reach a Gustav. A thoughtful DM to the person who just posted their budgeting frustration will. The DM is short, references their specific situation, offers help (not a hard pitch), and — critically — makes your founding-members offer when they're warm. This is the manual engine running for real.

The second YC principle that feels wrong but is right: charge real money early. The goal of your first customers is not revenue, it's feedback — and paying customers give you sharper, more honest feedback than free users ever will. An angry customer paying $7/mo will tell you exactly what's broken. A free user will just vanish. So when you recruit your first 5–10 via DMs, ask them to pay (with your killer offer). The signal is worth more than the $70.

Lavingia's metaphor: the internet is a spectrum and each person is tuned to their own radio frequency. Your job isn't to "find customers" — it's to build a radio station (consistent content in a distinctive voice) that attracts people already on your wavelength. For a budgeting app, your station broadcasts: your build progress, your own money habits, lessons from user interviews, the YNAB-features-you-hate-and-why, the wedge you're betting on. People who resonate become fans; fans become customers and referrers.

The reason this matters doubly for a money app is trust. People hand over their financial data to a stranger. A founder who shows up publicly, with a face, building openly, answering hard questions, and admitting mistakes is dramatically more trustable than a polished anonymous landing page. Building in public is, in effect, a continuous proof-of-character.

Lavingia also warns against relying on a single launch moment ("did the tweet go viral or not"). Instead, build a recommendable, long-lasting presence — one phrase or idea people associate with you (your "minimalist entrepreneur" equivalent). For you it might be "the budgeting app for people who fail at budgeting" — repeatable, ownable, sticky. The compounding asset is your audience, built one genuine post at a time.

The killer insight from Vasco's SaaS-SEO approach for a budgeting app: bottom-of-funnel "money keywords" convert, top-of-funnel "what is a budget" terms don't. The 5% of people actively ready to choose a tool search for things like "YNAB alternative," "Monarch vs YNAB," "budgeting app for couples," "free Rocket Money alternative," "budget app for irregular income." These are low-volume but high-intent — exactly the people you want.

The three page types that capture this intent: (1) Alternative pages ("YNAB alternative," "Monarch alternative") where someone searching a competitor's name + "alternative" finds you positioned as the better option for a specific wedge; (2) Comparison pages ("YourApp vs YNAB") covering features, pricing, pros/cons honestly; (3) Informational pages that provide more useful detail about competitors than the competitors do themselves. Add clear CTAs throughout and, where possible, an interactive element (a "find your budgeting style" quiz) for engagement.

For your first 100, you don't need to win SEO long-term — you need a few of these pages live and indexed before launch so that when you drive attention (via Product Hunt, Reddit, build-in-public), the search funnel is primed. And the act of writing a genuinely useful "YNAB alternative" page forces you to sharpen your positioning (Day 1–2 work made concrete). Pair with AI-search visibility: get mentioned in listicles and "best budgeting app" roundups that LLMs cite.

Martell's framework targets a 10–25% trial-to-paid conversion (most founders sit at ~2% because they do nothing). The sequence: (1) Welcome — show what you got and the one action that matters; (2) Training — teach the core habit (categorize this week's spending), not feature tours; (3) Offer to help — proactively reach to at-risk/quiet users; (4) Make an offer — a time-bound, activity-referenced conversion push ("you've categorized 3 weeks of spending — lock in founding-member pricing through Friday").

For a consumer budgeting app, two extra beats matter. First, the waitlist→beta→paid arc (Greg Isenberg's staged-beta model from Day 27): your waitlist email isn't "we launched" — it's an invitation to a limited beta at a founding price, creating scarcity. Second, retention nurture: budgeting is a habit, and habits need reminding. A weekly "here's where your money went this week" email both delivers value and pulls people back into the app — directly reducing the churn that kills budgeting apps (people stop because they stop opening it).

The key principle across all of it: each email answers "what's the next most valuable step for this user right now?" — not "what do we want to tell them?" Match the message to where they are (just signed up / haven't connected a bank / categorized once then vanished / trial ending). Measure activation rate, trial-to-paid, and 30-day retention — not open rates.

Bush's core idea: most onboarding is a value-destroying detour. Users sign up curious and you immediately ask them to fill a profile, verify email, watch a tour. The Bowling Alley Framework says: identify the one "straight line" from sign-up to first value, then add bumpers (like lane guards in bowling) that gently redirect anyone drifting off it.

For a budgeting app, the straight line is almost always: signup → connect one bank → see this week's transactions auto-categorized → realize where your money went. That last beat is the activation moment — the "oh, THIS is why I needed this" feeling. Everything before it is friction; everything that delays it kills conversion. Cut the email-verification step (or make it non-blocking), defer the profile, get them to connect a bank in under 60 seconds.

The bumpers are the product cues that keep people on the line: a single tooltip pointing to "connect your bank," an empty-state that shows a preview of what they'll see, a conversational nudge if they stall. Not a 12-item checklist (Bush: "a 12-item checklist isn't a checklist, it's a to-do list the user didn't ask for"). Pick the 3–4 actions that reliably lead to activation and guide those. Activation isn't a signup event — it continues into the inbox (ties to Day 17's nurture).

Balfour's reframing cuts against how most founders think: they obsess over acquisition and treat retention as an afterthought. His point: retention is the center of the growth engine. Higher retention increases word-of-mouth acquisition (retained users have more time to invite others) and increases monetization (longer LTV means more you can spend to acquire). For a budgeting app this is doubly true — the product only works if people keep using it, and a budgeting app with a churn problem is a leaky bucket no amount of acquisition can fill.

For your first 100, retention tactics are simple and manual: a weekly email pulling people back in (Day 17), a founder check-in DM to anyone who goes quiet, and — the community piece — a small shared space where your founding members talk to each other. Not a marketing community; a "founding members" Discord/channel where you share roadmap, they share wins ("paid off my first card using this"), and they help each other. This does three things: increases retention (people feel part of something), generates referrals (members invite friends into the inner circle), and produces the testimonials and use-cases you'll need for launch.

The bigger Balfour lesson: don't treat acquisition, retention, and monetization as separate teams/projects. A retention improvement (people stay longer) directly funds more acquisition (higher LTV → more you can spend on the watering-hole hustle). At your stage this just means: every implement day should ask "does this make people stay, or only come?"

Walling distinguishes strong vs weak viral loops in SaaS. Strong: the act of using the product exposes new people to it (Calendly, DocuSign — you send a link, the recipient sees the brand). For budgeting, the strong loop is shared budgets / couples: when one partner invites another to view or co-manage a budget, the second person sees and potentially adopts your app. This is a genuine network effect — design for it (easy invite, the invitee gets a great first-run experience).

Beyond product virality, two engines for a budgeting app: (1) explicit referral — "invite a friend, you both get a free month" (the Dropbox model, adapted). Keep it simple and bilateral. (2) Creator partnerships — the PF creator niche (Graham Stephan, Caleb Hammer, Nischa, Monarch-minded reviewers, smaller "budgeting coach" accounts) is massive and unusually sponsor-friendly because budgeting tools are exactly what their audience wants. For first-100, ignore the mega-creators (too expensive) and target micro-creators (5–50k followers) with an affiliate or free-year-for-feature deal. One good micro-creator feature can deliver 20–40 highly-trusting signups.

The unifying principle (from Adam Robinson / Plausible's Marko Saric): real word-of-mouth can't be bought or faked — it comes from a product that makes people win, then they talk. Engineer the conditions for it (shared budgets, referral incentive, creator exposure) but don't expect virality to substitute for a product people love.

Balfour's Four Fits framework warns against the "try every channel" trap. A channel only works when it fits all four: product-market fit (the channel reaches people who want your value), product-channel fit (the channel's format suits your product — e.g. SEO fits research-heavy budgeting decisions), channel-model fit (the channel's CAC works at your $7–12/mo price — paid ads often don't, at consumer pricing), and model-market fit (your unit economics work in your market).

For your first 100, this collapses to a simple bet: pick 1–2 channels where budgeters already gather and your format suits them. The obvious high-fit candidates: (a) Reddit/community watering holes (you're already there from Day 10), (b) PF content + SEO (Day 15–16, high intent), (c) PF micro-creators (Day 23–24, trust transfer), (d) build-in-public (Day 13–14, compounding audience). Paid ads almost never fit consumer-SaaS first-100 economics — defer them.

The AARRR funnel (Acquisition → Activation → Retention → Referral → Revenue) lets you see where you're leaking. And the "one metric that matters" discipline (from the growth-literature): for the next week, pick one — most likely activation rate (what % of signups reach your Day-19 activation moment) — because if activation is broken, every other effort is wasted. Track it crudely if you must; track it.

Mint.com is the canonical budgeting-app growth case — Noah Kagan was employee #4 and lays out the actual marketing plan that took Mint from 0 to 1,000,000 users in 6 months (and a $170M acquisition). The transferable lessons for your first 100: a relentless focus on the pre-launch waitlist and blog/content engine, heavy "edgy" personal-finance content that sparked shares, a massive launch-day coordinated push, and a product that delivered an immediate "wow" (seeing all your accounts in one place). You're not chasing 1M — you're chasing 100 — but the principle (build demand before you open the doors) is identical.

Greg Isenberg's waitlist playbook operationalizes exactly that, in four steps: (1) Edgy sales content on your build-in-public channel — posts that lead with a sharp POV on money/budgeting and tease the product via a soft CTA or comments link; (2) Drive to a waitlist, creating validation + scarcity; (3) Launch a beta to the waitlist with an early-bird founding price (e.g. first 100 at $59 lifetime or 50% off); (4) Iterate with that cohort — calls, feedback — then a second cohort at a higher price, then public launch. The math from a real example: 3,624 waitlist → ~20% conversion → ~$20K MRR month one. Even at 1/20th that scale, you have your 100.

For your timeline: you've been building the audience since Day 13. Today you finalize the waitlist mechanism and the beta-cohort offer that you'll open on launch day. The waitlist isn't a vanity metric — it's your controlled-release valve that converts scarcity into paying founders.

On Product Hunt: the recurring advice from operators is that upvotes matter far less than positioning, messaging, differentiation, and a clear CTA. Before you hunt, write a one-pager: what the product is, the problem, why your solution is radically different from incumbents, features→benefits, who it's for, and the one CTA (sign up / founding offer). If your positioning work from Days 1–2 is solid, this writes itself. Coordinate your warm audience (build-in-public followers, community members, interview subjects) to engage in the first few hours — momentum compounds.

Common launch mistakes to avoid: (1) launching cold with no warmed audience (your build-in-public + community work prevents this); (2) over-promising a "big day" and under-delivering, then going quiet; (3) treating launch as the finish line instead of the start of sustained acquisition; (4) not having analytics in place so you can't tell what worked; (5) ignoring the quiet majority who signed up but didn't activate (your Day 17/19 work addresses this).

The quiet-launch contingency (the most important mental prep): a soft launch is the norm, not a failure. If Jul 31 doesn't pop, the playbook is: (a) don't panic and don't go silent — keep posting, keep recruiting; (b) diagnose which stage leaked (acquisition? activation? conversion?) using your one metric; (c) run a "second launch" ~2 weeks later targeting a different watering hole or with a sharpened offer; (d) mine your existing users for referrals and testimonials — 10 happy users beat 100 cold signups. Most products that "made it" had a quiet first launch and a strong second one.