RecipeRoots - Family Recipe Preservation

👤 Persona #1: Heritage-Seeking Hannah

Age Range: 42-52 | Location: Suburban, nationwide US | Occupation: Marketing Director, mid-sized company | Income: $85K-120K | Tech Savviness: High | Authority: Individual buyer

Background Story: Hannah grew up watching her grandmother cook Sunday meals for the extended family. Now that her grandmother is in her 80s with early dementia, Hannah feels urgent pressure to preserve these recipes before they're lost forever. She's organized and detail-oriented but overwhelmed by the scattered nature of family recipes—some on stained index cards, others in her mother's head, and a few in old emails. Her goal is to create a lasting legacy that her teenage children can access and continue.

Current Pain Points:

1. Recipe fragmentation: Recipes scattered across physical cards, texts, and memory—spends 3-4 hours weekly hunting them down
2. Vague instructions: "Add a pinch" or "cook until golden" leaves her guessing—wasted $200+ on failed attempts
3. Lost stories: The emotional context behind recipes (like her grandfather's immigration story) exists only in fragile memories
4. Deteriorating originals: Handwritten cards are fading and stained—fears permanent loss
5. No sharing mechanism: Cousins want access but current methods (scanning, emailing) feel impersonal

Goals & Desired Outcomes: Primary goal: Preserve complete recipe + story archive before her grandmother passes. Secondary: Enable her children to cook family dishes confidently. Emotional outcome: Peace of mind and family connection. Success metric: 50+ recipes with stories captured within 6 months.

Current Solutions: Uses Evernote for digital notes, Google Photos for scanning cards, but lacks integration. Spends 8-10 hours monthly on workarounds. Abandoned generic recipe apps—they ignore the storytelling aspect.

Buying Behavior: Trigger: Grandmother's health scare. Research: Facebook groups, Reddit r/Cooking, word-of-mouth. Criteria: Privacy, ease of capture, story features. Budget: $5-10/month. Barrier: Concern about learning curve during emotional time.

👤 Persona #2: Genealogy Enthusiast George

Age Range: 58-68 | Location: Rural, Midwest | Occupation: Retired teacher | Income: $50K-70K | Tech Savviness: Medium | Authority: Individual buyer

Background Story: George has spent 15 years building his family tree on Ancestry.com, documenting births, marriages, and migrations. He recently realized his family's culinary traditions—like his great-grandmother's pierogi recipe from Poland—are equally important cultural artifacts. He wants to integrate food heritage into his genealogy work but finds current tools inadequate for capturing recipes with context.

Current Pain Points:

1. Tool incompatibility: Genealogy platforms don't support recipe documentation
2. Geographic disconnection: Can't map recipes to ancestral origins effectively
3. Collaboration limits: Distant cousins have recipe variations but no way to contribute
4. Preservation anxiety: Worried paper recipes will be discarded after his death

Goals & Desired Outcomes: Primary goal: Create culinary branch of family tree. Secondary: Connect recipes to migration patterns. Emotional outcome: Cultural continuity. Success metric: 100+ recipes linked to family members and locations.

Current Solutions: Uses Ancestry.com notes field (inadequate), physical binders. Spends $200/year on binders and printing. Abandoned Paprika—too recipe-focused, not heritage-focused.

Buying Behavior: Trigger: Completing main family tree. Research: Genealogy forums, Ancestry user groups. Criteria: Integration potential, archival quality. Budget: $50-75/year. Barrier: Skepticism about digital longevity.

👤 Persona #3: Heritage-Curious Carlos

Age Range: 28-35 | Location: Urban, diverse cities | Occupation: Software engineer | Income: $90K-130K | Tech Savviness: High | Authority: Individual buyer

Background Story: Carlos is first-generation American whose parents rarely shared family recipes from Mexico. After his father's recent passing, he found a box of handwritten recipe cards in Spanish with measurements like "un chorrito" (a little splash). He wants to recreate these dishes to feel connected to his roots but struggles with vague instructions and lost techniques.

Current Pain Points:

1. Language barriers: Spanish instructions with cultural terms he doesn't understand
2. Technique gaps: Never learned hands-on methods like masa preparation
3. Isolation: No family left who can demonstrate techniques
4. Modern adaptation: Needs help converting lard-based recipes to vegetarian versions

Goals & Desired Outcomes: Primary goal: Cook authentic family dishes despite knowledge gaps. Secondary: Create modern variations for his food blog. Emotional outcome: Cultural pride and connection. Success metric: Successfully recreating 10+ family recipes.

Current Solutions: Uses Google Translate (inaccurate), YouTube cooking videos (not family-specific). Spends 5-7 hours per recipe attempt. Abandoned generic recipe apps—they lack cultural context.

Buying Behavior: Trigger: Father's passing. Research: Instagram food communities, Reddit r/MexicanCuisine. Criteria: Voice/video capture, substitution suggestions. Budget: $8-12/month. Barrier: Concern about privacy of family recipes online.

🍳 Scenario #1: The Fading Recipe Card Crisis

Context: Heritage-Seeking Hannah, Sunday morning, kitchen table, weekly ritual

Current Experience: Hannah spreads her grandmother's recipe cards across the kitchen table. Many are stained with decades of use, ink fading to near-invisibility. She squints at "Grandma's Apple Pie"—the sugar measurement is completely gone where a spill occurred. She calls her mother: "Do you remember how much sugar went in?" Her mother replies, "Just until it tastes right, honey." Frustrated, Hannah tries ¾ cup, but the pie is too sweet. She photographs the card with her phone, but the glare makes it unreadable. She spends 45 minutes trying to transcribe it into Evernote, guessing at missing ingredients. By lunchtime, she's only captured one recipe, feels guilty about the failed pie, and worries about the 50+ other cards deteriorating in the box. The emotional weight of potentially losing this heritage makes her anxious and overwhelmed.

Pain Points Highlighted:

• Physical degradation of recipe cards
• Time wasted: 45+ minutes for partial transcription
• Emotional: Anxiety, guilt, urgency
• Outcome: Incomplete recipe, failed cooking attempt

Job #1: Preserve family culinary heritage before it's lost

When: Facing mortality of elder family member
I want to: Capture complete recipes with stories and techniques
So I can: Ensure future generations can recreate and understand their food heritage

Functional: Digitize physical recipes, record oral histories, standardize measurements
Emotional: Feel peace of mind, reduce urgency anxiety, create meaningful legacy
Social: Be seen as family historian, connect generations through shared heritage
Current Alternatives: Scanning apps, note-taking apps, memory alone
Underserved Outcomes: Emotional context preservation, technique demonstration, family collaboration

Job #2: Recreate authentic family dishes despite knowledge gaps

When: Attempting to cook a family recipe with vague instructions
I want to: Get help converting subjective measurements to precise ones
So I can: Successfully recreate dishes that connect me to my heritage

Functional: Convert "pinch" to grams, suggest substitutions, provide technique guidance
Emotional: Feel confident, connected to roots, proud of cultural identity
Social: Share authentic family dishes with friends, honor ancestors through cooking
Current Alternatives: Guessing, failed attempts, generic recipe sites
Underserved Outcomes: Cultural context for measurements, family-specific technique guidance

✨ Scenario #1: The Fading Recipe Card Crisis - Resolved

With Solution Experience: Hannah opens RecipeRoots on Sunday morning and selects "Capture from Photo." She snaps a picture of her grandmother's stained apple pie card. The AI instantly extracts readable text, highlighting the faded sugar measurement with a "confidence low" indicator. She taps to correct it to "¾ cup" based on her mother's phone call. The app prompts: "Add the story behind this recipe?" Hannah records a 2-minute voice memo about Sunday dinners at Grandma's house. She tags her grandmother as the original creator and adds a photo of last year's family Thanksgiving. Within 10 minutes, she has a complete, preserved recipe with story, ready to share with cousins via a private family link. She feels relieved and connected, knowing this heritage is now safe for her children.