Product Brief — FoodFlow Home (Marketing Homepage + SEO)

PRISM product #2. Mode: checkpoint (Ben sees every stage; gates are creative/strategic only). Pipeline entry: RESEARCH. Date: 2026-06-12. Source: Ben's request + grounding in the FoodFlow codebase and research docs.

What

A marketing homepage (and the SEO layer around it) for FoodFlow — Ben's existing, live product at food.jungohub.com. The site's job is to explain FoodFlow, rank for the right searches in Hebrew and English, and convert visitors into signups.

This is a marketing site for an existing product, not a new app. The app already exists (Lovable + Supabase, project djzszthclllrkainctvi).

The product it markets

FoodFlow is a Hebrew-first meal planning + recipe marketplace — "Shopify for nutritionists":

• For nutritionists/trainers (B2B): seed their practice with recipes and meal-plan templates, share them with clients, demonstrate professionalism. First customer: Ravit (nutritionist).
• For home cooks (B2C): save recipes, plan weekly meals, auto-generate shopping lists, share within a household, browse the community marketplace.
• Bilingual (he/en) with full RTL. AI recipe import (URL/image/text). Households with invite codes.
• Strategic blue ocean (per competitive research 2026-06-09, adversarially verified): zero Hebrew-native competition for the nutritionist tooling space in Israel; global competitors (Practice Better, Healthie) are English-only and US-focused.

Why now

• The app is live but has no public front door: no marketing homepage, no SEO presence, no organic acquisition channel. Content seeding (50 recipes, 10 templates, master-ingredient expansion to ~1500) is in flight — the marketplace is about to have real content worth indexing.
• The Israeli market gap is open now; whoever ranks first in Hebrew for this category defines it.

Audience (to be sharpened in VISION)

1. Israeli nutritionists/dietitians/trainers looking for client tools (Hebrew searches).
2. Israeli home cooks looking for meal planning / recipes / shopping-list tools.
3. Secondary: English-speaking equivalents of both.

Constraints & givens

• Languages: Hebrew AND English (Ben's explicit decision). Hebrew-first.
• Live app: food.jungohub.com — homepage must link/convert into it. Domain strategy (same domain vs. dedicated marketing domain) is an ARCH-stage decision.
• Brand divergence rule applies: must not look like Prism Core or ben-portfolio (indigo/light/film aesthetics are taken). FoodFlow has its own existing seeds: orange #FF6B35 / teal #4ECDC4, warm kitchen tone — BRAND stage may evolve but not ignore them.
• SEO is a first-class requirement, not a polish item: keyword strategy (he+en), technical SEO, structured data (Recipe/Organization schema), AI-SEO (LLM citability).
• The existing in-app landing page (Lovable, prompt 2) is a placeholder, not the answer.

Success criteria (draft — finalized in SPEC)

• Ranks/indexes for target Hebrew keywords in the nutritionist-tooling + meal-planning space.
• Converts: clear signup path into food.jungohub.com for both personas.
• Lighthouse ≥ 95 across the board (factory standard set by ben-portfolio).
• Both language versions complete; hreflang correct; RTL flawless.

Key open question for VISION gate — ✅ decided (see vision/gate-decisions.md)

The product serves two personas (nutritionists B2B / home cooks B2C) and the strategy doc points B2B. Who is the homepage's primary persona? This decides the hero, the keywords, and the entire information architecture. → Ben decides at VISION.

Source documents

• Codebase: ~/foodflow (Flutter MVP), ~/foodflow-supabase-link (web)
• ~/Documents/foodflow-competitive-research-2026-06-09.md (verified competitive research)
• ~/Downloads/foodflow-v2-full-summary.md (build state, v2)
• ~/Downloads/foodflow-h9-v3-master-ingredients-handoff.md (current v3 state, positioning)
• ~/Downloads/foodflow-content-creation-handoff-2026-06-05.md (content strategy, Ravit)