1. Executive Summary

RecipeMemoir is a web-first recipe manager built to be the thing Paprika never became: a place where a home cook's recipe collection turns into a gorgeous, shareable, permanently-owned family cookbook website, not a .paprikarecipes blob nobody outside the app can read.

Our wedge is import-and-publish. A user hands us their Paprika export (or a single recipe URL, or a page saved through our Chrome extension), and in minutes they have their own site at recipememoir.com/u/{handle}, built from one of 24 real, data-bound design templates across six taste families. We're not selling a database with a nicer skin. We're selling the thing Paprika structurally can't offer: a public, beautiful, portable home for a decade of family cooking.

We've done more than sketch this. The full self-serve loop shipped and went live on 2026-07-12: magic-link signup, Paprika-file or URL import, style picker, and a working personal site, plus feedback capture and a fake-door pricing page ($4/mo Home Cook, $8/mo Family) that measures willingness to pay before we build any billing. We proved the pipeline on hard data, not a demo: Annette's own 1,701-recipe archive (deduplicated down from 1,741), migrated out of Paprika's photo blobs into R2 storage with its photos, and nutrition panels computed from USDA data, macros and micronutrients, on nearly every recipe (the only gaps are novelty items like sugar-free bakes that USDA doesn't cover). The URL importer is verified live against three real recipe blogs, photos included.

We have no paying customers yet, and we're honest about that. The fake-door pricing page exists to find the right subscription price before we build a checkout: the model is decided (a subscription, not a one-time purchase), and we want real signal on what people will pay. What we do have is a working product with real data behind it, built on Cloudflare Pages, D1, and R2 for close to zero fixed hosting cost, which means we can run the beta and gather willingness-to-pay data for a long time without needing revenue to survive.

The near-term plan is not to chase growth. It's to recruit real beta testers beyond our own dogfood account, watch where they drop off in the funnel we just instrumented, learn what they'd actually pay, and only then turn the fake door into a real one.

2. Problem and Opportunity

The Trapped Collection

A home cook who has used Paprika for a decade has hundreds, sometimes over a thousand, recipes: family staples, a grandmother's handwritten card retyped years ago, clippings, tweaks noted in the margins. Paprika keeps this safe but locked. Its export is a technical .paprikarecipes ZIP file that nobody outside the app can open. There's no way to send a single recipe to a sister that doesn't look like a screenshot of a phone app. The interface has looked the same for close to a decade. It's a single-developer product, which is exactly why people trust it and exactly why they quietly worry what happens if that developer stops.

No Public Home for a Private Collection

Every recipe app in this category, Paprika, Mela, Plan to Eat, AnyList, treats the recipe collection as private data to be consumed inside the app. None of them treat it as something worth presenting. If a user wants to share their whole collection as a real website, with their own domain, their own voice, their own photos, there is nowhere to do that. Pinterest is lossy and ad-choked. WordPress is technically correct and practically out of reach for a non-technical home cook. Notion requires building your own recipe template from scratch.

The Opportunity

Nobody is competing to be the place a recipe collection becomes a public, beautiful, permanent family cookbook. Recipe.Site is the closest adjacency, and it's built for food creators monetizing subscribers, a different customer entirely. The whitespace is a product that starts where Paprika's users already are (their export file), and ends somewhere Paprika never goes (a real website they can hand to their kids).

3. Solution: What RecipeMemoir Does, End to End

1. Sign up. Magic-link email auth, no password. A new account gets an isolated collection instantly.
2. Import. Three paths, all live: upload a .paprikarecipes file (parsed client-side, batch-imported with photos), paste a single recipe URL (we fetch the page, extract the schema.org Recipe JSON-LD, and self-host the photo), or use our Chrome extension to send a recipe from any blog with one click.
3. Cleanup, optional and automatic. Auto-categorization tags each recipe by meal, protein, dish, cuisine, attribute, and occasion. An AI duplicate judge finds and flags true duplicate clusters (weighted first on ingredient-list completeness, not just title match) so an import from years of clipping doesn't carry its mess into the new site. A photo-triage tool sorts blurry photos to the front for an AI upscale or replace pass.
4. Pick a style. 24 real, data-bound templates across six taste families (from a Kinfolk-quiet minimal look to a warm gingham country-kitchen look), not mockups, actual working templates that render the user's own recipes and photos live as they browse the gallery.
5. Get the site. A pretty URL at recipememoir.com/u/{handle}, publicly viewable, with full-text search, faceted browse, and a print stylesheet that makes any recipe print cleanly on paper.
6. Enrich. Nutrition rings computed from a local USDA database of 95,775 foods (macros plus ten micronutrients on nearly every recipe; a few novelty items aren't in USDA), AI commentary modes on a recipe (a chef's voice, a family voice), unit toggling between metric and imperial, and a copyright-safe rewrite pipeline (draft, verify, escalate across three models) for any recipe pulled from someone else's blog before it's published publicly.
7. Take it further. A KDP cookbook PDF generator can turn the whole collection, or a curated subset, into a typeset book, useful for a gift, a memorial, or an actual self-published cookbook. Honest status: this exists as an internal tool today, not a button in the product yet; surfacing it as a paid feature is on the roadmap (Section 7).
8. Leave anytime. Export to PDF, JSON-LD, Markdown, or HTML whenever the user wants. We built the escape hatch on purpose.

For the user, it's upload, pick a look, done. Underneath, we're running a real multi-tenant data model, isolated per collection and proven not to leak between users in live testing.

4. Positioning and Differentiation

RecipeMemoir sits in a category with two failure modes: apps that manage recipes privately, and one adjacent product that manages recipes for creators trying to make money from an audience.

• Vs. Paprika: The incumbent, and the reason our import path exists. Reliable, well-loved, one-time-purchase, and structurally stuck: no web app, no AI, no public output, single developer. We start exactly where its users already are.
• Vs. Mela, Crouton, Pestle: Beautiful, Apple-native apps with no documented Paprika import and no public site output. They compete on taste, not on portability or presence.
• Vs. Plan to Eat, AnyList, Preplo, Samsung Food: Planning and grocery-list tools. Useful, but the recipe collection stays a private list inside a planner, never a public artifact.
• Vs. Umami / RecipeSage: The closest on export breadth (JSON, Markdown), the benchmark we measure our own export against, but neither publishes a designed public website.
• Vs. Recipe.Site: The only real adjacency, but it's built for creator monetization and subscriber paywalls. A different ICP entirely, one that wants an audience, not a family archive.
• Vs. Tandoor, Mealie: Open-source, self-hosted, genuinely feature-rich, but Docker-and-server setup is a wall for the exact non-technical home cook we're building for.

Our differentiation, concretely:

1. The only documented Paprika-to-website import path. No competitor has built this migration bridge, and it's table stakes for our entire wedge.
2. Public, designed, data-bound personal sites. Not templates you fill in by hand. Real pages that render a user's own recipes and photos the moment they pick a style.
3. The full memoir chain. Import, cleanup, publish, enrich with nutrition and commentary, export to a printed KDP cookbook. No competitor has built more than one link of this chain.
4. Built so you can leave. Full data export in four formats, at any time, for free. Most subscription software maximizes the cost of leaving. We minimize it on purpose, because it's the trust signal that gets a skeptical Paprika loyalist to try us.

5. Target Market and Beachhead (ICP)

Primary ICP: The Family Archivist. Ages 45 to 75, peak 52 to 65, about three-quarters women, household income $80K to $250K, US/Canada/UK/EU. She has 200 to 1,500 recipes built up over a decade or more in Paprika, a recipe box, or bookmarks. She's not shopping for recipe software. She's triggered into action by something specific: Paprika goes quiet for a year, a relative dies and preservation suddenly feels urgent, or a friend shares a RecipeMemoir site and she wants her own. Her dream outcome is simple and emotional: to give her family a real, permanent home for the recipes, and to finally feel that a decade of cooking is safe and shareable rather than trapped in an app.

Secondary ICP: The Frustrated Paprika Power User. 500-plus recipes, loves the web clipper, actively searches "Paprika alternative" out of accumulated frustration with per-platform repurchase, no web app, and a dated interface. She converts on migration ease and a clean web experience, not on AI features.

Also core: The Recipe Collector. Not everyone in this market is preserving family recipes. A large share simply loves collecting recipes, full stop, and has for decades. This is Annette's own origin story: she started building her collection back before the internet went mainstream, trading recipes with other cooks on Prodigy and AOL. These collectors, whether their trove is clipped magazine pages, screenshotted blog posts, or a thousand Paprika entries, want exactly what the archivist wants: one beautiful, searchable, permanent home for something they've poured years into. They aren't a niche; they're the reason anyone keeps a recipe collection at all, and RecipeMemoir is built for them just as much as for the family preservationist.

Explicit non-target for v1: professional food creators who need subscriber paywalls and monetization tooling. That's Recipe.Site's customer, not ours.

Beachhead: the honest starting point is that we do not yet have a warm audience to switch on. Annette's newer publications (SmartStrongAlive, NotTooOldForAI, and others) are brand new and don't have a readership we can market to yet, so the seed can't come from a founder list. The first testers come from direct outreach to the places the target user already gathers (home-cook and family-recipe Facebook groups, r/paprikaapp, genealogy groups), and the dogfood proof, a real 1,701-recipe personal archive Annette built for herself before asking anyone else to trust the product, is the credibility asset a cold community won't give a random new app. From there it widens along family-cookbook-intent search terms where we have a genuinely differentiated answer.

6. Market Size

Our sizing is directional, anchored to actual pricing in the category rather than a headline industry figure, since the closest comparable apps (Paprika, Plan to Eat, AnyList, Preplo, ReciMe) show us what this market is already willing to pay.

• Total Addressable Market (TAM): The broad recipe-and-meal-planning app category, spanning Paprika, Plan to Eat, AnyList, Whisk/Samsung Food, and dozens of smaller apps. This category has proven paying demand for a decade (Paprika alone has sold across multiple platforms since the early 2010s) but is not our real market: most of it is planning and grocery-list software, not publishing software.
• Serviceable Addressable Market (SAM): Home cooks with a large, multi-year recipe collection (200-plus recipes) who are active Paprika users, former Paprika users, or people actively searching for a Paprika alternative. Using comparable subscription pricing in the category ($5.95 to $8/mo, $49 to $80/yr, up to $59.99/yr at the high end) as an anchor, and a conservative estimate of hundreds of thousands of long-tenure Paprika households across English-speaking markets, our SAM is a market plausibly worth tens of millions of dollars annually at category-standard pricing, even before counting the adjacent "want a public site" demand that no competitor currently serves at all.
• Serviceable Obtainable Market (SOM): Our Year 1 to 3 target, built from the same subscription anchors as our own pricing.

• Assumption: a beta-to-paid conversion funnel, seeded by founder-audience distribution and Paprika-frustration SEO, can realistically reach 1,000 to 3,000 paying households by Year 3, a rounding error against the broader Paprika install base.
• Math at our live fake-door price points: 1,000 subscribers blended across $4 and $8/mo tiers at roughly $6 average equals about $72,000 ARR. 3,000 subscribers at the same blend equals about $216,000 ARR.
• Conclusion: our initial SOM is modest and deliberately so. It reflects a self-funded, founder-led beta gathering real willingness-to-pay signal before scaling spend, not a growth-at-all-costs plan.

7. Revenue Model and Pricing

RecipeMemoir's live pricing is a fake door, on purpose. As of the 2026-07-12 ship, recipememoir.com/pricing shows three tiers and takes no payment information anywhere:

• Free Beta (current): full access to import, styles, nutrition, and commentary. This is what every beta tester gets today, and beta testers are promised a full year of continued free access regardless of what pricing we land on.
• Home Cook, $4/mo: a personal site, all styles, imports, nutrition, and commentary modes.
• Family, $8/mo: up to five collections under one account, a shared cookbook, and print exports.

Clicking a paid tier logs a pricing_click funnel event against that tier and shows a friendly "you're on the list, beta stays free for now" message. Nothing is charged, because nothing is chargeable yet. The model itself is decided: RecipeMemoir will be a subscription, not a one-time purchase, because it's a tool people use every time they cook, not a product they buy once. What the fake door is still learning is the right price and tier mix, not whether to charge monthly.

Secondary monetization already scoped, not yet built:

• KDP cookbook export as a paid product: a per-export fee or an unlimited monthly tier, positioned around gift occasions (Mother's Day, a wedding cookbook, a memorial book).
• White-glove custom design, $200 to $400 one-time: for non-technical users who want a fully custom-designed site rather than picking from the 24 templates.

We will not build a checkout until the fake-door data, plus direct beta-tester feedback (also live via the feedback tool shipped in the same release), gives us a real answer on which model converts.

8. Unit Economics

Because we have zero paying customers, this section is illustrative and built from comparable pricing and our actual infrastructure costs, not from observed billing data.

• Infrastructure cost per user is close to zero at our current scale. The whole stack runs on Cloudflare Pages, Pages Functions, D1, and R2, chosen specifically because their free and low-volume tiers cover a beta of hundreds of users without meaningful spend. This means we can run a long beta and gather signal without revenue pressure forcing a premature pricing decision.
• Illustrative subscriber value: at the live fake-door price points, a Home Cook subscriber at $4/mo is $48/yr; a Family subscriber at $8/mo is $96/yr. Blended across an assumed 70/30 Home Cook to Family mix, that's roughly $58/yr per paying household.
• Retention assumption: recipe software shows unusually strong loyalty once a user's data lives in the system. Paprika users report staying for years specifically because migrating 400-plus recipes elsewhere is painful, the same data-gravity effect we intend to benefit from once a user has imported their own collection and picked a style.
• CAC: not yet measurable, and honestly harder than the plan first assumed: Annette's newer publications are brand new with essentially no readership to market to yet, so there's no warm list to lean on. Early acquisition instead comes from direct, near-zero-cost outreach to the communities where the target user already gathers (home-cook and family-recipe groups, r/paprikaapp, genealogy groups), plus family-cookbook-intent SEO, which is also near-zero marginal cost.

Honestly, the real unlock here isn't a unit-economics model, it's the fake-door and feedback data we just turned on. We'll have a far more honest version of this section once beta testers start clicking pricing tiers and telling us what's missing.

9. Go-to-Market

Phase 1: Dogfood Proof + Direct Outreach (Now)

Annette's own site, at recipememoir.com/u/annette, with her real 1,701-recipe collection, is the proof artifact: "I built this for myself first" is a harder trust signal to fake than any ad copy. There's an honest correction to the original plan here: we don't have a warm founder audience to seed from. Annette's newer publications are brand new with no readership yet, so the first testers come from direct outreach to the communities where the target user already is (home-cook and family-recipe groups, r/paprikaapp, genealogy groups), one at a time. Social handles are already registered at @recipememoir across Pinterest, Instagram, TikTok, YouTube, Facebook, and LinkedIn for when we're ready to post.

How to launch (added 2026-07-20)

A specific gap the marketing field guide (Section 28) surfaced: the plan had phases but no launch method. The verified doctrine, adopted here:

• Launch is a repeatable act, not one big day. Plan to launch the same product many times, to different audiences and on different angles (the founder list, then a subreddit, then a seasonal gift push), rather than staking everything on a single reveal.
• One or two channels at a time, matched to the buyer, worked until proven or dead. Five channels done thinly is the classic flop pattern, and it's the same one-channel discipline already in Section 18.
• Don't gate the launch on a waitlist number. The "you need 200 to 500 signups first" rule was refuted in verification. A waitlist is fine to build, but not a prerequisite to shipping.
• Watch leading indicators, not launch-day signups (a vanity metric): time to first published site, return-after-publish, and the top support objection. These are already the Section 16 scorecard.

Speaking to women 45-75 (added 2026-07-20)

The audience research carries one clear rule: this reader finds age-targeted advertising condescending and dislikes health-decline framing, and responds when she's the hero of the story, reached through emotion and meaning rather than persuasion tactics. For RecipeMemoir that means the message is always "preserve what matters to your family," never anything that hints at fading memory or getting old. It's the plan's voice (warm, plain, no hype) pointed at this specific reader.

Phase 2: Family-Cookbook SEO (reweighted 2026-07-20)

This phase was originally "Paprika-frustration SEO." The red-team (Section 27) killed that framing with live keyword data: switcher terms like "paprika app alternative" get about 10 US searches a month, far too thin to carry a channel. The real volume sits in gift-and-keepsake intent: "make a family cookbook" runs about 320 monthly searches and spikes to 590 to 720 in November and December, with "family recipe book maker" around 110. So the SEO play now targets the family-cookbook cluster, timed to the holiday spike, while Paprika switchers get reached where they actually gather (the communities in Phase 4) plus a couple of cheap evergreen migration-doc pages that can rank on the tiny switcher terms without carrying growth expectations.

Phase 3: The Referral Loop

Every published site carries a quiet "Built with RecipeMemoir" footer link, so the moment someone shares their site with family, we get free discovery from the recipients. This is the same mechanic that made the original "sent my mom a link, she cried" story spread in our own research.

Phase 4: Community and Platform Expansion

Paprika-frustrated communities (Reddit's r/paprikaapp and similar), food blogger and genealogy/family-history communities where recipe preservation framing resonates directly, and the App Store once an iOS app exists in v2.

The near-term, concrete step is simpler than all of that: get real beta testers using the live funnel beyond our own dogfood account, which as of this writing has not yet started (beta-tester recruiting is explicitly gated on Annette's go-ahead).

10. Defensibility and Moat

1. The proven Paprika import pipeline. Not a claim, a working pipeline verified against 1,701 of Annette's own recipes and their photos, pulled out of Paprika's proprietary photo blobs. Nobody else in the category has documented doing this.
2. The memoir chain. Import, cleanup, publish, enrich with nutrition and AI commentary, and (via an internal tool) export to a printed book. Competitors have, at most, one link of this chain (Umami's export, Mela's design, Recipe.Site's public pages). We have the rest working end to end on real data, with the print-book export still an internal tool rather than a shipped feature.
3. The copyright-safe rewrite pipeline. A multi-model draft, verify, and escalate process exists specifically so recipes pulled from someone else's blog can be republished on a user's personal site without the legal exposure that a naive scraper-and-republish tool would carry. No competitor appears to have thought about this at all. Note (updated 2026-07-21): the pipeline covers text only. Photos stay fully copyright-protected, so a photo scheme, now live in production, completes the moat: public visitors see a friendly placeholder (which doubles as a family nudge to add a real photo), the original stays visible behind an optional family-only site password, and the owner gets a one-click replace queue with AI generation.
4. The anti-lock-in trust stance. Full export to PDF, JSON-LD, Markdown, and HTML, for free, at any time. Most SaaS products maximize the cost of leaving. We deliberately minimize it, which is precisely the credibility gap a Paprika loyalist, scared of losing a decade of family recipes to a single developer's decisions, actually needs closed.
5. The dogfood proof. A founder who cooks, whose own 1,701-recipe archive is the live test case, in a category historically built by developers who don't cook. That's a harder thing for a funded competitor to fake than any feature.

11. Competitive Landscape

Our wedge is the empty middle column nobody else occupies: the only product that both imports cleanly from the incumbent and publishes a genuinely beautiful, data-bound public website from that import.

12. Risks and Assumptions

• Pricing is unvalidated. We have a fake door, not a confirmed price. Mitigation: the fake-door page and feedback tool are already live and collecting signal before we build any billing infrastructure.
• We have not yet recruited real beta testers. Everything proven so far is on Annette's own dogfood account plus internal test imports. Mitigation: beta-tester recruiting is the explicit next gated step, not a someday item.
• Free-to-paid conversion is unproven in this category for a personal, non-monetizing use case. Recipe.Site's paying customers are creators earning from subscribers; our customer earns nothing from their site, only meaning. Mitigation: lean on the data-gravity effect (400-plus recipes imported creates high switching cost) and the anti-lock-in stance as trust-builders, not just cost of leaving.
• Nutrition data quality is not yet signed off. Macro and micronutrient panels are computed, not manually verified, and known limits exist (servings=1 whole-batch recipes read high). Mitigation: explicit "Estimated from ingredients" caveat shown in the UI; multi-tenant nutrition rollout is deliberately held until Annette signs off on quality.
• Copyright exposure on imported recipes. Publishing a recipe copied from someone else's blog carries legal risk if done naively, and the exposure includes photos, which stay protected even though ingredient lists aren't. Mitigation: the rewrite pipeline (draft, number-check, judge, escalate) handles the text, and the photo scheme, now live (public placeholder, family-password visibility, owner replace queue), closes the photo side. This is done, not pending (Gate 0 in Section 22, closed 2026-07-21).
• Founder bandwidth. Annette runs 8-plus active projects simultaneously. Mitigation: the build queue runs in parallel worktree lanes with standing deploy authorization, so build velocity does not depend entirely on her active attention every day.
• Mobile timeline is undefined. No iOS or Android app exists; the product is explicitly web-first by design. Mitigation: this is a locked, deliberate sequencing decision, not an oversight, and the web product is the validation gate before any native build begins.
• Competitor response. A funded planning app could add Paprika import or a public-site feature. Mitigation: our defensibility is the full chain (import, publish, enrich, print, export) plus a genuine dogfood proof, both slow and specific to replicate quickly.

13. Roadmap and Milestones

Phase 1: v2 Self-Serve Beta, COMPLETE (through 2026-07-12)

Tenancy, magic-link auth, Paprika and URL import, per-user styled sites, onboarding funnel, feedback and fake-door pricing all shipped and live-verified. This phase is done, not aspirational.

Phase 2: Real Signal (Now, Next 60 to 90 Days)

• Recruit actual beta testers beyond the dogfood account (currently gated on Annette's go-ahead).
• Watch the funnel instrumentation for real drop-off data: signup, import, style pick, site view, pricing clicks.
• Ship remaining design polish: three gap styles (dark moody, true minimal, scrapbook country), the "meet the cook" bio block, and finish the in-progress micronutrient rollout.
• Get Annette's sign-off on nutrition data quality before rolling it out multi-tenant.

Phase 3: Pricing Decision and Checkout (Following Real Signal)

• Set the subscription price and tier mix from real pricing-click and feedback data (the subscription model itself is decided; a one-time purchase is ruled out).
• Build actual billing and flip the fake door to a real one.
• Decide the custom-domain workflow for published sites (subdomain-only versus bring-your-own-domain).

Phase 4: Distribution Expansion

• Launch family-cookbook-intent SEO content (the reweighted Phase 2 in Section 9) and the referral-loop measurement.
• Open the Chrome extension and URL importer more broadly beyond internal testing.

Phase 5: Platform Expansion

• iOS app planning begins once the web product's conversion funnel is validated with real paying users, not before.
• Evaluate whether NutriForge, the nutrition-API sub-project built from RecipeMemoir's own USDA pipeline, spins out as a separate business or stays inside RecipeMemoir.

14. Financial Projections (Illustrative, Directional)

These projections are built entirely from comparable category pricing and a conservative beta-to-paid conversion assumption. We have zero paying customers today. These are assumptions to illustrate a plausible trajectory, not a forecast, and should be read alongside the pricing risk in Section 12.

Assumptions: Year 1 reflects a slow, deliberate beta-to-paid conversion after the pricing decision lands, seeded almost entirely by founder-audience distribution. Blended price rises modestly as the Family tier mix grows. KDP and white-glove revenue begins once print export ships as a paid product, assumed Year 2. Infrastructure cost is assumed negligible at this scale given the Cloudflare Pages, D1, and R2 stack already in production.

Immediate Next Steps

1. Get Annette's go-ahead to recruit real beta testers beyond the dogfood account, and open the funnel to them.
2. Let the fake-door pricing page and feedback tool run for a real sample size before touching the pricing decision.
3. Finish the in-progress micronutrient rollout and get nutrition-quality sign-off before enabling it multi-tenant.
4. Ship the three remaining gap styles and the "meet the cook" bio block, both explicitly gated on Annette's design input.
5. Once real signal exists, set the subscription price from it and build the actual checkout.

15. How the Money Actually Works

Strip away everything else and the profit engine is one line: subscribers, times blended price, times months they stay, minus costs that round to zero. Because the Cloudflare stack costs almost nothing at our scale, we don't have a cost problem to manage. We have three levers: how many people convert, what they pay, and how long they keep paying. Every hour spent on this business should map to one of those three.

Price from evidence, not politeness

The pricing playbook we're following comes from the Simon-Kucher school (the "Monetizing Innovation" framework): learn willingness to pay before building billing, and be able to finish the sentence "we priced it at X because customers told us Y." The fake door is that discipline in working form. Two additions worth making during beta:

• Ask the direct questions. In every beta interview, ask: at what monthly price would this feel like a bargain, at what price would you hesitate, at what price is it out of the question? Five or ten honest answers from real Family Archivists beat any amount of modeling.
• Test higher anchors, not just $4 and $8. The bigger risk here isn't overpricing, it's underpricing (the classic "minivation" failure: right product, priced too timidly). A woman preserving her mother's recipes isn't shopping on price. Consider adding a $6/$12 fake-door variant to see whether click rates even move.

Three tiers, with visible fences

When the checkout becomes real, use a three-paid-tier menu, not two. People avoid extremes: with three options, most pick the middle, and the top tier makes the middle look reasonable even if almost nobody buys the top. A plausible menu: Home Cook ($4 to $6/mo), Family ($8 to $12/mo, multiple collections and shared cookbook), and a Legacy tier above it that bundles an annual printed-book credit and white-glove touches. Healthy distribution once live: no more than about a quarter of buyers on the cheapest tier, and at least one in ten on the top one. If more than half pick the cheapest, the cheap tier is carrying too much and needs features moved up. And every tier difference must pass a ten-second test: a buyer should see instantly what the next tier adds.

Why subscription, not a one-time price

Paprika trained this audience to expect buy-once, so a one-time price is the obvious temptation. Annette has ruled it out, and the logic is the product itself: RecipeMemoir isn't a thing you buy and finish, it's the recipe database you cook from every week, replacing the cards and the Paprika app. Recurring value earns recurring revenue. A one-time price would also sell our best, longest-staying customers cheap, since recipe software keeps people for years once their collection is loaded. The one nod to the buy-once instinct:

The open question isn't the model, it's adoption: does the everyday-use thesis hold? The subscription is justified by people cooking from RecipeMemoir week after week, so the beta instruments exactly that, return-and-reuse in weeks 3 and 4 after a tester publishes. Annette's conviction is that they will, because the product replaces the cards and the app they already reach for daily. Bob's read on this is invited in Section 29.

Annual plans and price integrity

• Always offer annual at roughly two months free (Home Cook at $40/yr against $48 monthly-billed). Annual buyers churn far less and the cash arrives up front.
• Never discount the sticker price after launch. Discounting teaches people to wait for sales and quietly reprices the whole base. When something needs a push, use time-boxed founding offers, added value (a free print credit), or gift promotions instead. If sales ever disappoint, the rule is three non-price fixes before any price cut.

The second and third revenue engines

• Printed cookbooks are the natural high-margin add-on, and they're seasonal by nature (Section 24). Price per book or as a credit inside the Legacy tier.
• White-glove custom design ($200 to $400 one-time) monetizes the customer who wants it done for her. A handful a month is real money at our scale, with no code to write.
• Custom domains (her-name.com instead of a /u/ path) can ride inside Family or Legacy as a fence rather than a separate charge.

16. The Numbers That Matter

A business stays manageable when it's watched through one small set of numbers on a schedule, instead of anxiously and randomly. This is the weekly scorecard: one page, fifteen minutes, every week, ideally auto-emailed so it arrives without anyone remembering to run it. If a number can't change a decision, it doesn't belong on the page.

The jargon, once, in plain words. MRR is monthly recurring revenue; ARR is that times twelve. Churn is the percentage of payers who cancel in a month. LTV (lifetime value) is blended monthly price times the average months a customer stays: at $6 blended and 3% monthly churn, average tenure is about 33 months, so LTV is roughly $200. CAC is what it costs to acquire one customer. The classic health test is LTV at least three times CAC, and at near-zero CAC from owned channels we pass it trivially, which is exactly why paid ads wait until organic is proven.

The north star deserves a sentence. The single number that best predicts this business working is collections published and shared with at least one other person. A shared site means the emotional job got done, and every share is also free distribution. Everything upstream (signups, imports, styles) exists to make that number move.

17. Retention Is the Business

At $4 to $8 a month, no acquisition channel saves a product people quit. Retention decides everything downstream: LTV, how much we can ever spend on acquisition, the valuation multiple in Section 19. The good news is this category has unusually strong natural retention (nobody wants to move 400 recipes twice), and our job is mostly to not squander it.

The first session decides the first year

Data gravity only works after the data arrives. The single most important product goal is that a new user's first session ends with her recipes imported and her site on screen. Measure minutes from signup to first published page and drive it down relentlessly. Anyone who signs up and doesn't import within 48 hours gets one warm, specific nudge (not a drip campaign).

The lifecycle, sketched

• Day 0: "Your site is live" with the link and one sharing suggestion.
• Day 3: one styling tip (try two other styles, your recipes rebind instantly).
• Day 7: the share prompt: send it to one person who'll recognize the recipes.
• Ongoing: a "from your own collection" email surfacing a seasonal recipe she already owns. Her own grandmother's pie showing up the week before Thanksgiving is retention no discount can buy.

The churn you don't see: failed payments

Industry-wide, failed payments cause roughly 20 to 40% of all subscription churn, and expired cards (about 42% of those failures) are largely recoverable with retries and a friendly email (Dodo Payments' analysis, Kaplan Group's 2025 statistics roundup). For an audience where cards expire and get reissued constantly, this could quietly be our largest churn line. The merchant-of-record platforms in Section 21 handle retry logic and card-updater emails out of the box, which is one more reason to use one.

The month-to-month playbook when a card fails, spelled out so it's policy and not improvisation:

• Before it fails: when a card on file is expiring, send one heads-up email the week before renewal. Cheapest fix in the whole chain.
• When it fails: smart retries over the following week (roughly days 1, 3, 5, and 7; the MoR schedules these), plus automatic card-updater so reissued cards often fix themselves silently.
• Two friendly emails, not a collections tone: "Your card didn't go through, your cookbook site is completely safe, here's the update link." The family archive is never used as a threat.
• Grace period, about 14 days: the site stays fully live the whole time. If the card never recovers, the account moves to the same read-only-plus-free-export state as a voluntary cancel. Nothing is ever deleted.
• Watch one number: the recovery rate on the scorecard (target 60% or better). If it slips, fix dunning before touching anything else, because this is the cheapest revenue in the business to save.

When someone cancels

• One-question exit survey (what made you cancel?), never a guilt trip.
• One save offer, matched to the reason: pause the plan, drop to a cheaper tier, or switch to annual. One offer, then let her go graciously.
• Never hold the data hostage. On cancel, the site goes read-only and export stays free forever. It's our stated trust stance, and it also makes coming back painless, which people do.
• Win-back note at 60 days, once, warm, with whatever shipped since she left.

18. Customer Acquisition Playbook

The discipline that keeps acquisition manageable: one channel at a time, worked until it's proven or dead, before opening the next. Spreading thin across five channels is how solo-founder products stall. And from day one, ask every signup "how did you hear about us?" (one optional field), because guessing at attribution later is misery.

Word of mouth deserves its own line: the product's emotional payoff (sending the link, mom crying) is inherently tellable. The referral footer captures it passively; the day-7 share prompt in Section 17 nudges it actively. Both cost nothing and compound.

19. What Makes the Business Worth Something

Whether or not you ever sell, build as if a skeptical buyer will read the books someday. The properties a buyer pays extra for are the same ones that make the business low-stress to own: predictable revenue, low churn, clean records, and the ability to run without its founder chained to it. Do this right and you get options: sell it, hand it to an operator, or keep it as cash flow. Do it wrong and you own a job.

How small software businesses get valued

Small subscription software typically sells for a multiple of revenue or profit. Current market data: micro-SaaS under $1M ARR generally trades around 2.5 to 4 times ARR (or 4 to 6 times seller's discretionary earnings), with the broader bootstrapped median near 4.8x ARR in 2026 (Axial's 2026 SaaS multiples guide, Aventis Advisors' multi-year dataset, Livmo's 2026 breakdown). Read directionally, not as gospel: if the Year 3 base case in Section 14 lands (about $175K revenue, nearly all of it profit on this cost structure), that's plausibly a $400K to $700K asset at conservative small-company multiples. The point isn't the precise number. It's that a modest subscriber base, retained well, becomes real net worth.

What moves the multiple

One habit ties this section together: keep the scorecard history forever. Eighteen clean months of weekly metrics is exactly the artifact that makes diligence painless and multiples defensible, and it costs nothing to keep.

20. Running It Without It Running You

You run eight-plus projects. This business has to fit inside that reality or it fails for reasons that have nothing to do with the market. The design target: once the beta stabilizes, RecipeMemoir takes four to five focused founder-hours a week, and everything else is automated or delegated.

What only Annette does

• Taste and design calls (the wedge is gorgeousness; that judgment doesn't delegate).
• The pricing decision and other one-way doors.
• The public voice: launch posts, community outreach, anything signed with your name.
• Partnership conversations with actual humans.

What Charlie and automation do

• All building, deploying, and QA (standing deploy authorization already covers this).
• Metrics collection and the Monday scorecard email, fully automated, registered in ROUTINES.md like every recurring job.
• Support triage: drafted replies for your one-click approval, and a help-doc page written for every question that gets asked twice.
• Content drafts for the SEO channel, on your editorial approval.

The cadence

• Weekly, 30 minutes: read the scorecard, make at most one or two decisions from it.
• Monthly, an hour: deeper look; check the decision gates in Section 22.
• Quarterly: reread this document and update it in place. A plan nobody rereads is decoration.

Support, honestly scoped

At beta scale, support is a trickle, not a flood. One support address, an honest two-business-day reply promise, help docs as the first line, and fast gracious refunds (a $4 refund costs less than any argument, and the merchant of record makes refunds one click). A decision log (one page, every locked call with its date and reason) keeps past decisions from being relitigated every few months, which is its own kind of time protection.

The Not-Doing list

Manageability is mostly what we refuse to do. No native apps before paid validation. No custom features for one loud user. No new acquisition channel while the current one is unproven. No billing before Gate 3. No style repaints without cause. When something new and shiny appears, it goes on the feature board, not into the build queue.

21. Legal, Tax, and Admin Foundations

None of this is exciting, and all of it is cheaper before the first paid charge than after. The sequence:

• Form the LLC and open a separate bank account before the first dollar moves. Clean books from day one is a tax necessity, a liability shield, and the single biggest diligence gift to any future buyer.
• Use a merchant of record for billing. Plain-words definition: a merchant of record is a company that legally sells the product on our behalf, which makes global sales tax, VAT, invoicing, refunds, and card-retry logic their filing problem, not yours. Paddle and Lemon Squeezy (now Stripe-owned) both charge about 5% plus 50 cents per transaction, versus plain Stripe where fees are lower but every tax jurisdiction is our job (FintechSpecs' 2026 comparison, GlobalSolo's fee breakdown). At our scale the 5% is cheap insurance against a genuinely miserable admin burden; revisit if ARR ever makes the fee delta serious money.
• Terms of service and privacy policy before charging anyone. Put the data-ownership promise in writing (your recipes are yours, export is free, forever), state the deletion policy, and note that analytics are cookieless.
• Copyright hygiene. Register a DMCA agent (the copyright.gov filing costs a few dollars) and publish a takedown process. Users affirm they have rights to what they publish, and the rewrite pipeline stays mandatory before any imported-from-elsewhere recipe goes public.
• Email compliance. Every marketing email needs a working unsubscribe and a postal address. The newsletter system already being opt-in-only puts us on the right side of this by design.
• Keep a beta promise ledger. "Beta testers get a year free" is a real commitment with real dates. Track who was promised what, so the year is honored precisely and billing never surprises an early believer.

22. Scenarios and Decision Gates

Gates keep us honest: predefined evidence thresholds that trigger decisions, so choices get made by data instead of by mood on a random Tuesday.

The three paths

• Bear: after a genuine distribution effort, paying households stall under 100. The move is graceful: keep the product alive as your own tool and a portfolio proof (near-zero costs make that painless), stop investing new effort, and protect your other projects. Written here in advance so it reads as a plan, not a failure, if it happens.
• Base: the Section 14 trajectory. Steady founder-audience seeding plus SEO compounding to a few hundred, then a couple thousand households.
• Bull: one channel meaningfully outperforms (a share loop catching, an SEO page ranking big). Then and only then: revisit pricing upward, consider contract help for support and content, and pull the iOS decision forward.

23. Adjacent Markets Already in Reach

Each of these is a marketing angle first and a feature later, if ever. None requires new product to start testing as a campaign.

• Community fundraiser cookbooks. Churches, schools, and teams have bought group cookbooks for generations; it's one of the oldest proven print markets in America. A "group cookbook" collection is a natural Family-tier extension, and one enthusiastic church volunteer brings fifty contributors with her.
• Genealogy and family history. A recipe in grandma's phrasing is a primary source. Genealogy societies and Facebook genealogy groups (already in the beta target list) treat preservation as the whole point, and "the family recipes, preserved like the family tree" speaks their language natively.
• Memorial and legacy. A memorial cookbook is one of the most meaningful gifts a grieving family can make, and the KDP pipeline already produces it. This one is marketed gently or not at all: content and word of mouth, never targeted ads.
• Weddings and showers. "Recipes for the couple," gathered from both families into one printed book and site, is a bridal-shower ritual waiting for better tooling. Gift certificates fit here too.

24. The Annual Rhythm

Recipe traffic and gift buying are fiercely seasonal, which is a gift to a small operation: we know when the moments come, and campaigns get planned about six weeks ahead of each. Print deadlines are hard deadlines; a December cookbook ordered late arrives in January.

25. First Login and the Ah-Ha Moment

The ah-ha moment in this product is specific and singular: the second a woman sees her own recipes, in her grandmother's own titles, wearing a design that looks like a real cookbook site. Not our demo data, hers. Everything about the first login exists to reach that second as fast as possible, and everything about pricing exists downstream of it.

Should there be a walkthrough? Mostly no.

Skip the classic modal tour (the overlay with six "Next" bubbles). For this audience it reads as an obstacle between her and her recipes, it gets dismissed unread, and it teaches nothing at the moment of need. Use these instead:

• A three-step checklist that lives on the dashboard until it's done: Import your recipes, Pick your style, Share your site. Each step is a button, not an explanation. Progress it visibly (1 of 3, 2 of 3). This is the walkthrough, disguised as doing.
• Empty states that teach. Before any import, the collection page shows one sentence and one action ("Your recipes will live here. Upload your Paprika file or paste a recipe link."), not a blank table.
• One clear next action per screen, larger text than feels necessary. The 45-to-75 audience punishes clutter and rewards obviousness.
• Contextual hints only at the moment of need (a one-line tip next to the style picker the first time it's opened), never as an upfront tour.
• Returning users and new features: a quiet "What's new" note on the dashboard, dismissible, never a forced tour. Someone who logs in monthly shouldn't be greeted by a tutorial.

Engineering the ah-ha

• Show the site during import, not after. The import progress screen should preview real recipe cards rendering as they land, so the wow starts before the last recipe finishes.
• Land on her site, not on a dashboard. The first thing after import completes is her styled site, full screen, with her photos. Admin screens can wait.
• Put the style switcher one tap away from that first view. Watching her own recipes rebind across three designs in ten seconds is the moment people describe to friends, and it's also the feature no competitor can demo at all.
• Measure it: minutes from signup to first site view, and share events in session one. Those two numbers are the ah-ha, quantified (they're already the activation and north-star lines on the Section 16 scorecard).

How the ah-ha becomes a subscription

Never gate the ah-ha itself. If the wow sits behind a paywall, nobody feels it, nobody shares it, and the referral loop starves. The free experience should deliver the moment in full: import, one styled site, sharing. What the subscription buys is what the moment makes her want next: permanence and gifts. All 24 styles instead of a starter set, the printed book, the family password, multiple collections, her own domain. The pricing prompt appears right after wow events (first share, first style switch, first print preview), phrased as protecting and extending something she now loves, and never as a gate slammed in front of it. That sequencing also keeps the fake-door data honest: a pricing click that arrives seconds after a share event is a real signal, not a stray tap.

26. The Marketing Video Playbook

One hero video for the landing page, cut down into short vertical clips for everything else. The structure below exists to protect the video from the classic failure: demoing everything and selling nothing.

The 60-to-90-second hero video, beat by beat

• Open on the payoff, not the problem (first 5 seconds): a gorgeous finished site scrolling slowly, real family recipes, one spoken line: "This is my mom's recipe box now."
• The before (5 to 10 seconds): the recipe box, the stained index cards, the decade-old Paprika screen. No mockery, this stuff is beloved; that's the point.
• The magic trick (the heart of the video): drag the Paprika file in, watch the counter climb, and cut straight to the site appearing. This is the wedge on camera, and it's the sequence no competitor can film.
• The style switch: the same recipes rebinding live across three or four designs in a few seconds. Second-biggest wow, visually irresistible.
• The share: the site opening on a phone, a text going to family. This is where "I sent my mom a link, she cried" lives, shown rather than claimed.
• The keepsake: the printed cookbook as a physical object on a kitchen table. It grounds the whole thing in gift-giving.
• The close: the URL, one trust line ("your recipes, always yours, export anytime"), free beta invitation. One call to action, at the end, quietly.

Which features to demo, and which to leave out

In the hero video, in this order: Paprika import speed, the instant styled site with her own photos, live style switching, sharing to a phone, the printed book. That's it, five beats.

Deliberately not in the hero video: nutrition rings, AI commentary, auto-categorization, the duplicate judge, unit toggling, Cook Mode. They're real differentiators, but seven features in ninety seconds is how a video demos everything and sells nothing. Each of those gets its own 15-to-30-second feature clip later, one clip, one feature, for social and for the help docs.

The landing page and pricing page are conversion instruments (added 2026-07-20)

The video drives attention; two pages convert it, and each has its own craft the plan shouldn't leave to chance:

• The landing page: one headline and one call to action above the fold, the finished-site payoff shown immediately (not described), the trust line ("your recipes, always yours"), and the dogfood proof. No second ask competing with the first.
• The pricing page is one of the highest-converting pages you have, so it gets real attention: one clear primary tier (the middle one), honest annual-versus-monthly options, and, once billing is real, a trial with a visible timeline showing exactly when it ends and what happens. Trial-timeline clarity measurably lifts conversion and cuts surprise cancellations.
• Web billing is worth defending: selling on the web instead of through an app store avoids 15 to 30% platform fees, reduces payment-failure churn, and can lift lifetime value 30 to 50%. It's independent confirmation that the web-first and merchant-of-record calls (Sections 15 and 21) are right.

Production notes

• Record the real product with the real 1,701-recipe collection. Polished fake-data screencasts read as ads; a real archive reads as proof. The dogfood story is the credibility asset, so film it.
• Annette's voice, and her on camera for the open and close if she's willing. For the founder-audience seed wave, her voice is the trust signal; a faceless product video throws that advantage away.
• Captions on everything. Most social viewing happens with sound off, and the audience skews toward readers anyway.
• The vertical cuts: the import-to-reveal sequence alone, 15 to 30 seconds, is the Pinterest, Facebook, and Instagram unit. The style-switch sequence is the second cut. Both come free from the hero footage.
• Seasonal re-skins: the same hero footage with a Mother's Day or Christmas open ("this year, give her the family recipes") feeds the Section 24 calendar without new production.

How to use this document

Part I is the map. The scorecard in Section 16 is the dashboard you actually look at weekly. The gates in Section 22 are the brakes that keep decisions honest. Reread the whole thing quarterly and edit it in place; the plan should always describe the business we're actually running, not the one we described in July.

27. What Could Break This: Our Own Red-Team

Before showing this to anyone, we ran a deliberate attack on the plan's load-bearing assumptions: the claims that, if false, break the whole thing. Each one gets the strongest version of why it might be true, then the honest attack, then something we can do about it. Two of the attacks use fresh evidence pulled the day we wrote them (live keyword data and the actual state of US recipe copyright law), not opinion. This is the section built for a skeptical reader, and it's meant to be argued with.

#1: People will pay monthly, indefinitely, for a job that feels finished

#2: "Copyright-safe" is doing more work than the pipeline actually does

#3: Paprika-frustration SEO is a real acquisition channel

#4: The founder audience will seed 50 to 100 beta testers

Status (2026-07-21): Annette confirms this attack is essentially right. There's no warm founder audience yet, the newer publications are brand new. So community outreach isn't a fallback after a founder wave, it's the primary seed channel from day one, worked one community at a time.

#5: Fake-door clicks measure willingness to pay

What's well-reasoned (the review's own verdict)

• The cost claim holds. Near-zero infrastructure on the Cloudflare stack is true at beta scale, and it genuinely buys unlimited patience, the plan's best structural advantage.
• The honesty is real, not decorative. Zero customers, unvalidated pricing, and an unproven conversion path are stated plainly, with mitigations already live.
• The gate structure is the right machine. Predefined evidence thresholds making decisions instead of moods is exactly what protects a founder running eight projects.
• The seasonal calendar just got independent confirmation. The November and December spikes in "make a family cookbook" search volume showed up in someone else's data.
• The bear case written in advance (fall back to portfolio-asset-plus-personal-tool, near zero carrying cost) is genuinely rare planning hygiene and makes the whole bet asymmetric in a good way.

What the red-team couldn't assess (the known blind spots)

• The seed audience. This is now answered, and not in the plan's favor: Annette confirms there's no warm founder audience yet, so the seed has to come from cold community outreach. The open piece is which community converts best.
• Marginal AI cost per active user. Commentary modes, the three-model rewrite pipeline, and photo upscales all cost real tokens per use. At 1,000 active users this may still round to nothing or may be the first real cost line.
• KDP print margins. Year 2 and 3 projections include print revenue with no cost-per-book assumption behind them.

Red-team sources: Google Ads search-volume data via DataForSEO (pulled 2026-07-20, US, English); US Copyright Office Circular 33, Copyright Alliance on recipes, and the NYC Bar Association.

28. What Outside Best Practice Taught Us

We also pressure-tested the plan from the other side: not "what's wrong with our logic" but "what does the wider world of software and consumer-subscription marketing know that we might have skipped?" We ran a multi-source sweep of current practice, fact-checked each claim, then held it against all 26 sections. Most of what the field teaches, the plan already covered. Four real gaps turned up, and all four are now folded into the sections above, so this is the short version of what changed and why.

• A real launch method. The plan had marketing phases but no answer to "how do you actually launch?" The verified doctrine: a launch is a repeatable act, not one big day, and you work one or two channels matched to your buyer rather than five thinly. One myth got killed in checking: you do not need a 200-to-500-person waitlist first. (Now in Section 9.)
• How to speak to women 45 to 75. The plan had a warm, plain voice but nothing about this audience's psychology. The finding: this reader finds age-targeted advertising condescending and dislikes decline framing, and responds when she's the hero of the story. For us that means "preserve what matters to your family," never anything that hints at fading memory. (Now in Section 9.)
• Email as an acquisition asset, not just lifecycle mail. The plan covered emails to existing users, but not a lead magnet that turns a curious visitor into a subscriber we own, which for this age group is the highest-ROI channel there is. A natural one already sits in the product: "rescue your recipe box in five minutes." (Now in Section 18.)
• The landing and pricing pages as conversion instruments. The plan treated the video and the pricing strategy well but not the pages themselves. The pricing page is one of the highest-converting pages a product has, and a clear trial timeline measurably lifts conversion. (Now in Section 26.)

Three things the sweep confirmed we already had right: web-first billing (it avoids 15 to 30% app-store fees and can lift lifetime value 30 to 50%), tracking time-to-first-value over vanity signups, and treating retention as the whole game. And one caution it kept surfacing, which the red-team raises too: consumer subscription is genuinely harder than business software. Churn runs higher and prices run lower, and the thing that separates survivors is one cheap, efficient growth channel plus people who come back after the first job is done.

Courses worth taking (honest prices)

Prices checked directly. For our stage (solo, bootstrapped, new to SaaS specifically), the two free options plus one $299 course cover everything needed; the four-figure programs are built for a different stage and are worth skipping for now.

Prices verified 2026-07-20. HubSpot Academy and YC Startup School confirmed free at the source; MicroConf ($299), Demand Curve, CXL, and Reforge from the courses' own pages.

YouTube channels to learn from

Every channel and subscriber count below was verified live on 2026-07-20, ranked by fit for our exact case: consumer product, bootstrapped, solo founder.

If you watch only three videos

• Rob Walling, "Why to Avoid B2C SaaS at All Costs". Start here. It's honest counter-programming for our exact model, and it names the traps to design around, the same warning the red-team's #1 assumption raises.
• Rob Walling, "How to Find Your FIRST 10 SaaS Customers". Our immediate problem: six repeatable strategies, and a warning against building more before marketing what we have.
• Y Combinator, "The Best Way To Launch Your Startup". The launch-repeatedly doctrine that filled the plan's biggest gap (now in Section 9).

One trap the research caught: the official @MicroConf YouTube handle now points to a nearly-empty relaunched channel, so the links above go to Rob Walling's personal channel, the real home for that content. Fact-checking method: three independent reviewers per claim, majority rules; a few data points were flagged "reported, not fully verified" when a session limit cut the run short, and the gap analysis leans on the fully-verified ones.

29. Open Questions for Bob

Bob, this is where your read is worth the most. These are the questions we can't answer from the desk, ranked roughly by how much rides on them. If you only push on a few things, push on these.

• Does the everyday-use thesis hold? I've decided on subscription, not one-time, and my reasoning is that RecipeMemoir becomes the recipe database people cook from daily, replacing Paprika and the recipe cards, so they keep using it and keep paying. The risk isn't the pricing model, it's whether people truly adopt it as their everyday cooking tool instead of publishing a site once and drifting off. What would you watch in the beta to know it's genuinely sticking?
• Where do the first real users come from? Honestly, I don't have a warm audience to switch on, my newer publications are brand new with no readership yet. So the first testers have to come from cold outreach to communities (home-cook and family-recipe groups, r/paprikaapp, genealogy groups). Is that a strong enough starting channel, or is there a warmer path we're not seeing?
• Are we pricing too timidly? The bigger risk in this category is usually underpricing, not overpricing. A woman preserving her mother's recipes isn't shopping on price. Should the fake door be testing $6 and $12 instead of $4 and $8?
• What's the real cost of the AI features at scale? Hosting rounds to zero, but the commentary, the three-model rewrite pipeline, and photo generation all cost real money per use. At a thousand active users, is that still nothing, or the first real cost line we haven't modeled?
• Are the printed-book margins real? The Year 2 and 3 numbers include print revenue with no cost-per-book behind them yet. Before we lean on that line, it needs honest math. Does the gift-book economics actually work?
• Is the whole thing worth the opportunity cost? I run eight-plus projects. Even in the good case this is a modest business (a few hundred, maybe a couple thousand households). The plan argues that's fine because costs round to zero and the bear case is graceful. Do you agree the downside is really that contained, or are we underweighting the cost of my attention?

And anything you think we've overlooked that isn't on this list is exactly what we most want to hear.