RecipeMemoir beta tester prospects: end users only

Researched live 2026-07-20. Retargeted same day by Annette's call: no bloggers or recipe-site owners (the export-your-collection wedge can read as competitor-enabling to publishers). Every prospect here is an end user: someone who loves collecting recipes but doesn't publish them. Public info only, no phone numbers.

The headline: 39 Reddit users actively complaining about their recipe app (all end users, all DM-able), a literal Paprika users Facebook group, family-recipe-preservation and genealogy communities where people are hand-building family cookbooks already, and beta platforms that deliver exactly this demographic.

Start here: the top 8 actions

1. Reddit-DM u/oflandandsea_053, who wrote: "If you ever want feedback or testing, let me know. QA/QC and API testing are some of the things I do all day."
2. Reddit-DM the other 9 starred users below, a few per day (Reddit rate-limits new DM senders).
3. Post in r/PaprikaApp: competitor devs post there openly and get warm receptions. Be transparent that you're the builder.
4. Ask to join the Paprika App Recipe Sharing Network Facebook group and message the admin.
5. Post in the three purpose-built beta subreddits (r/alphaandbetausers, r/betatests, r/TestMyApp): their members sign up to test apps.
6. Set up a free Product Hunt "Coming Soon" page to collect waitlist emails.
7. Post in the Preserving Family Recipes and Heirloom Cooking group and the r/Genealogy family-recipes crowd: people hand-building family cookbooks are the dream users, and nobody else recruits there.
8. When free channels have validated the pitch, consider a paid BetaTesting.com cohort targeted at "cooks at home, 45-70" (needs your spend OK).

1. Reddit: 39 people already asking for your product (Charlie can DM with your OK)

Every one of these was found complaining about Paprika, Copy Me That, ReciMe, or the whole category within the last 18 months. None of them run a recipe site; they're collectors. The top 10 to message first:

The other 29 (with thread links and quotes) live in the source threads: Best Alternative to Paprika3, Modern Alternatives to Paprika, Alternative to Copy Me That, Pantry + recipe management, Paprika sync errors megathread, Recommendations on recipe apps, Is Paprika 3 still the go-to?, and more. Full list: u/haltingpoint, u/jordanisplaying, u/OneWayTraveler, u/No_Kangaroo6917, u/KenoKitten, u/Agitated_Ad4737, u/ttaarr033, u/texpoodles, u/Mathematician024, u/grapebeyond227, u/bebeklein, u/Sarcas666, u/neonpablo, u/Hoogs, u/LizzrdVanReptile, u/Ok_Hat_3414, u/yarnjen, u/apharmasis, u/PeachZZZZZZ, u/CatteNappe, u/TastyDuty, u/mcflurvin, u/MagmaManatee, u/Itsfxckingkade, u/tolzino, u/Rheila, u/bad-trajectory, u/kabadisha, u/JumpingCoconutMonkey.

Where posting is allowed

• Yes, purpose-built: r/alphaandbetausers (must be testable now, tag title [Web, Beta]), r/betatests (use [opportunity] tag), r/TestMyApp (frame as bug-hunt), r/SideProject (high traffic, feedback posts are the core content).
• Yes, best audience: r/PaprikaApp. No written rules; competitor devs (Umami, ReciScan, Deglaze) post openly and get warm receptions. Be transparent that you're the builder.
• Comment only, never post: r/Cooking (ads banned, but disclosed indie devs answering "what app?" threads get upvoted), r/selfhosted (comment in recipe-manager threads).
• Hard no: r/EatCheapAndHealthy ("no app testers" is an explicit rule), r/MealPrepSunday, r/foodhacks.
• Community norms: always disclose you're the builder (the community rewards transparent builders and torched a shill in the ReciMe thread), and pace DMs to a handful per day.

2. Facebook groups of home cooks and recipe keepers (post from your account; Charlie writes the copy)

• Paprika App Recipe Sharing Network: literal Paprika users. Ask the admin first; "I built a Paprika-import tool, looking for testers" framed as help usually flies.
• Preserving Family Recipes and Heirloom Cooking: people digitizing grandma's recipe box by hand. The emotional-moat audience.
• Vintage Recipe Project: recipe-card collectors, digitization-minded.
• General home-cook groups: Awesome Recipes Share Group, Our Recipes, Meal Prep Motivation, and the huge Instant Pot Community (a Paprika vs Recipe Keeper thread already ran there). Check each group's rules in-app before posting.
• Genealogy groups on Facebook: search "genealogy" and "family history" groups; the family-cookbook angle is on-topic there and nobody else is recruiting in them.

3. Communities of recipe collectors beyond Facebook and Reddit

• Genealogy wedge: r/Genealogy family-recipes thread; genealogists actively compile family cookbooks by hand.
• Hungry Onion (where Chowhound's community migrated): passionate home cooks, older skew. Ask mods before any promo.
• Houzz Cooking forum: decades-old recipe card collections; recurring "how do you store recipes" threads. Participate first, promo frowned on.
• Permies organizing-recipes thread: real people describing binder and index-card systems.
• MetaFilter Projects ($5 account): self-posting your own project is explicitly allowed, and MeFi's recipe-manager Ask threads show the audience is there.
• Self-hosters (Mealie and Tandoor Discords): they run their own recipe manager but many want a beautiful hosted option for sharing with family. Borderline case: they're users, not publishers, but lower priority than the groups above.

4. Beta platforms and waitlist channels (these deliver end users by design)

• Product Hunt "Coming Soon": free, collects waitlist emails now, compounds into a stronger launch later.
• BetaTesting.com: the only guaranteed-volume option. Paid (a few hundred dollars minimum), 450k+ verified consumers, can target "cooks at home, 45-70." Waits for your explicit OK since it costs real money.
• Betabound (Centercode's opt-in consumer tester community): managed, more formal, also paid.
• IndieHackers, Peerlist, MicroLaunch, Uneed: free, a handful of signups each; audiences skew techie but they test as end users.
• Show HN: "I turned my 1,600 Paprika recipes into a beautiful website" fits HN's personal-story norms. Must be try-without-signup.
• Press that reaches end users (not outreach to creators, just coverage): Rich DeMuro / KTLA wrote "Best Apps to Save Your Recipe Collection" and his audience is exactly recipe-collecting consumers; The Sweet Setup keeps an evergreen "best recipe manager" page; Family Tree Magazine publishes family-cookbook how-tos to genealogists.
• Skip: BetaList (~$39 to submit, mixed reviews). Erli Bird is dead (folded into BetaTesting.com).

5. Message templates

Reddit DM

Facebook group / admin

Family-recipe / genealogy communities

Five Reddit angle variations matched to what each person actually said (rug-pull, abandoned-app, grandma's-recipes, subscription-fatigue, import-from-anywhere) are ready; Charlie personalizes each message before sending.

Removed by design: bloggers and creators

The first version of this page included 32 food-blogger emails and about 30 Instagram/TikTok creators. Annette cut them on 2026-07-20: people who run recipe sites may feel threatened by a tool that lets anyone turn a recipe collection into a website of their own, so pitching them as beta testers risks starting relationships on the wrong foot. That research is preserved in the git history of this page if a creator-partnerships play ever makes sense later, on different terms.