BMAD-METHOD/evals/bmm-skills/bmad-product-brief/files/forkbird-brief/brief.md

3.5 KiB
Raw Blame History

title status created updated
Forkbird Kitchen — Product Brief final 2026-02-14 2026-02-14

Forkbird Kitchen

What it is

A delivery-only ghost kitchen brand offering chef-driven plant-based meals in five US metros: San Francisco, New York, Los Angeles, Seattle, and Chicago. Launch operating model is direct-to-consumer through our own iOS/Android app and the major third-party marketplaces (DoorDash, UberEats, Grubhub).

Who it's for

Urban professionals aged 2845 who eat plant-based meals at least three times a week, value chef-driven food over chain alternatives, and order delivery 4+ times monthly. Initial geographic focus is dense neighborhoods within 3-mile delivery radii of partner kitchens.

We are not building for: families with children (different ticket size and ordering pattern), occasional plant-based eaters (price sensitivity too high for our positioning), or office lunch (different time-of-day operation).

Why it wins

Three things are deliberately stacked:

  1. Chef partnerships, not chef-as-marketing. Each metro has a named chef (with prior fine-dining or notable plant-based credit) who designs the rotating menu and earns equity in that metro's P&L. They are not endorsers; they are operators.
  2. Ingredient sourcing standards. Published per-dish: where it came from, how it was farmed, what portion of cost it represents. No dish ships if we can't source within 200 miles for ≥60% of ingredient weight. This is auditable, not marketing copy.
  3. Speed without cars. Average ticket-to-door is 28 minutes from order placement, achieved by tight delivery radii and dense order density per kitchen. Long delivery erodes plant-based texture more than animal protein — speed is product, not logistics.

Operating model

Five kitchens, one per metro, each leased space inside an existing food-prep facility. No customer-facing storefronts. App orders go through our stack; marketplace orders pass through their stacks. Menu rotates every six weeks per chef.

Pricing tier: $14$22 per entrée before delivery. We are deliberately at chef-driven positioning, not value positioning.

What's known

  • Demand validated through three pop-up dinners in SF and NY (Q4 2025). 480 covers, 78% repeat intent based on post-event survey.
  • Operating partner identified in each metro. Leases signed for SF, NY, LA. Seattle and Chicago in negotiation.
  • Three of five chefs signed; two in active conversations.

What's unknown

  • Whether ingredient-sourcing transparency is a differentiator at point of sale (in-app) or only in marketing. Our hypothesis is "both" but we have not tested in-app.
  • Marketplace economics. DoorDash takes 1530% depending on tier; we are modeling the lower tier but have not negotiated.
  • Whether the 3-mile radius holds outside SF/NY (lower density in LA/Chicago).

Risks

  • Chef churn. If a metro chef leaves, the metro brand loses its anchor. Mitigation: equity vesting over 24 months, named-chef terms in operating agreement.
  • Sourcing cost volatility. 60% local-within-200-miles can spike with weather/supply disruption. We have not modeled the worst case.
  • Marketplace dependency. If DoorDash terms shift adversely, our blended margin is at risk. We are deliberately building the owned-app channel to reduce this dependency.

Success criteria for first 12 months

  • 4 of 5 metros operating profitably at the unit level (kitchen + chef + delivery economics) by month 9
  • 30% of orders through owned app (vs. marketplaces) by month 12
  • Chef retention 100% through year 1