ECP Food — Product Documentation
All phases approved v1.0 MVP ← Ecosystem 🇧🇷 PT

ECP Food — FoodFlow

Complete documentation of the 4 product cycle phases — from strategic context to operations.

Product Vision
Premium food delivery marketplace for São Paulo

In 5 years, FoodFlow will be the reference platform for those seeking gastronomic delivery experiences in São Paulo and Brazil's major capitals — recognized for impeccable curation of artisan restaurants, a discovery experience that delights, and an integrated payment ecosystem that makes ordering food as pleasurable as eating it.

We will be the bridge between restaurants that care about quality and consumers who value what they eat.

North Star Metric
Completed Orders with Satisfaction / Week
Orders successfully delivered (no cancellation and no open complaint) per active week.
MVP Target: 630 orders/week (90/day). Year 1 Target: 6,300 orders/week (900/day).
Priority Segment
Gastronomic Explorer (C1)
22-35 years, A/B class, urban SP, income R$ 5-15k. Orders delivery 3-5x/week. Influenced by photos, reviews and badges. Average ticket R$ 50-80.
R$ 75bi
TAM
R$ 12bi
SAM
R$ 18mi
SOM
12
HITLs

Phase Timeline

Phase 01
Strategic Context HITL #1 Approved
OKR with 4 KRs (conversion 8%, repurchase 25%, ticket R$ 45, 50 restaurants), North Star (Completed Orders/Week), product vision, 5 principles, 4 competitors analyzed, 5 segments, OST with 19 opportunities.
Phase 02
Product Discovery HITLs #2-#6 Approved
13 prioritized opportunities, 14 hypotheses across 5 themes, low-fi and high-fi prototypes, 7 epics, 19 features, 51 user stories with BDD, 4 Cagan risks assessed.
Phase 03
Product Delivery HITLs #7-#10 Approved
DDD with 6 bounded contexts, 5 ADRs, Fastify API with 11 modules and 48 endpoints, 12 SQLite tables, React SPA, QA with quality score 82 and 142 test cases.
Phase 04
Operations HITL #11 Approved
Deploy strategy PM2 + Nginx + SSL, GMUD-001 for initial deploy, 5 SLOs defined, DORA metrics, monitoring with PM2 and Nginx logs.

Quick Access

Phase Summaries

Phase 01 — Strategic Context
OKRs, North Star and Premium Positioning

Definition of the strategic objective: “Validate that FoodFlow delivers a premium food delivery experience that consumers prefer over incumbents and that artisan restaurants adopt as their main channel in São Paulo”, with 4 measurable Key Results. Competitive analysis of 4 competitors (iFood, Rappi, 99food, Keeta) revealed a gap in premium UX and curation.

phase-01-output.json
Phase 02 — Product Discovery
Opportunities, Hypotheses and Structured Backlog

13 opportunities prioritized across 4 KRs. 14 hypotheses across 5 themes (Discovery, Checkout, Repurchase, Trust, Supply-side). Backlog with 7 epics, 19 features and 51 user stories with acceptance criteria in BDD/Gherkin. 4 Cagan risks assessed.

backlog.json
Phase 03 — Product Delivery
Architecture, API, Frontend and QA

DDD architecture with 6 bounded contexts (Identity, Catalog, Ordering, Payment, Delivery, Admin). Stack: Fastify 5.x + SQLite3 + React 18 + Vite + CSS Modules. API with 11 modules and 48 endpoints. 12 tables in DB. QA with quality score 82, 142 test cases and 6 bugs identified.

architecture.json qa-report.json
Phase 04 — Operations
CI/CD, GMUD and Deployment

Deploy strategy with PM2 + Nginx + Let’s Encrypt SSL on VPS. GMUD-FOODFLOW-001 for initial deploy at food.ecportilho.com. 5 SLOs (availability 99.5%, P95 latency 200ms catalog, 2s payment, error rate <0.5%, SSE <2s). DORA metrics with MVP targets.

ops-output.json GMUD-001.md