# The Passion Table — Refined Business Idea

## Executive thesis

**The Passion Table is a concierge-led subscription service that gives newly relocated urban professionals reliable daily food from the day they move in.**

The launch product is **The Landing Kit**: a 7- or 14-day package of two fresh meals per day, fixed delivery windows, dietary onboarding, daily feedback, and optional pantry essentials. The first pilot is deliberately restricted to one dense micro-market in **Delhi — Saket, Hauz Khas, and Greater Kailash**.

The long-term ambition remains larger: become the trusted operating layer for daily urban food. The near-term business, however, should be proven through one urgent customer problem, one geography, one operating model, and paid repeat demand.

## What the repository already establishes

The existing product work has four strong foundations:

1. **Category framing:** daily food is positioned as infrastructure rather than restaurant discovery.
2. **A high-intent entry wedge:** people moving homes or cities have immediate food continuity needs.
3. **A subscription operating model:** predictable demand can improve menu planning, procurement, kitchen capacity, and route density.
4. **A quality philosophy:** small-batch production, creator identity, capped capacity, and feedback loops are treated as core product features.

The repository currently stretches these foundations across relocators, office workers, households, native apps, investor tooling, and future physical venues. That breadth is useful as a vision, but it is too wide for first-market validation.

## The launch decision

For the next six weeks, The Passion Table should behave as one business:

> **A paid relocation-food concierge for professionals moving into Delhi.**

Everything else is postponed until this wedge demonstrates renewal, contribution margin, and operational reliability.

## The customer

### Primary customer

A 24–45-year-old professional who is:

- moving to Delhi for a new role;
- shifting into an apartment or co-living property;
- temporarily without a functioning kitchen, cook, pantry, or trusted food routine;
- willing to pay more than restaurant-delivery averages for reliability, health, and reduced setup friction.

### Buyer and distribution partners

The end user may buy directly, but efficient acquisition should come through:

- relocation agencies;
- apartment brokers and property managers;
- co-living operators;
- corporate HR and People teams;
- employers onboarding transferred hires;
- premium movers and home-setup services.

## The job to be done

> “When I move into a new home or city, give me dependable meals immediately so I can focus on work and settling in instead of rebuilding a kitchen routine.”

The customer is not buying menu variety. They are buying **continuity, trust, and one fewer moving problem**.

## The product: The Landing Kit

### Core offer

| Plan | Included | Pilot price |
|---|---|---:|
| 7-Day Landing Kit | 14 meals, fixed delivery windows, dietary onboarding, daily feedback | ₹4,900 |
| 14-Day Landing Kit | 28 meals, fixed delivery windows, dietary onboarding, daily feedback | ₹8,900 |
| Pantry Start add-on | Basic spices, staples, and storage essentials | Priced after selection |
| Cookware support | Rental, refundable-deposit, or partner purchase option | Never bundled free |

### Product rules

- One launch geography.
- Two meals per day.
- Limited weekly menu.
- Fixed delivery windows.
- Explicit dietary exclusions, not unlimited customization.
- One primary kitchen partner plus one backup.
- WhatsApp concierge as the operating interface.
- Paid reservation before service confirmation.
- Daily one-tap feedback.
- No marketplace browsing.

### Customer experience

1. Customer opens the pilot page from a partner, referral, or direct campaign.
2. Customer selects 7 or 14 days, move-in date, neighborhood, diet, and delivery windows.
3. The page creates a structured request and hands it to WhatsApp.
4. Concierge confirms serviceability, menu, start date, and payment.
5. Customer receives the next day's meal card and delivery window.
6. Customer rates each day; issues are recovered before the next delivery.
7. On day 5 or day 11, concierge offers an extension or transition plan.

## Supply and operating model

The business should not begin as an open creator marketplace. It should begin as a tightly managed service.

### Pilot supply

- One FSSAI-compliant primary kitchen or culinary partner.
- One backup kitchen with overlapping menu capability.
- A maximum daily allocation defined before sales open.
- Standard recipes, portions, packaging, dispatch cutoffs, and temperature checks.
- Batch production planned from subscription demand.
- Delivery routes grouped by narrow time windows and neighborhood clusters.

### Operating objects

The minimum operating system needs only five objects:

1. **Lead** — source, neighborhood, start date, plan, dietary needs.
2. **Subscriber** — payment status, active dates, meal windows, preferences.
3. **Meal allocation** — menu, kitchen, batch, quantity, substitutions.
4. **Delivery** — pickup, route, ETA, handoff, exception.
5. **Feedback** — score, issue type, recovery action, renewal signal.

A spreadsheet or lightweight database is sufficient until repeat demand is proven.

## Business model

### Revenue

- 7- and 14-day Landing Kit packages.
- Pantry, snack, beverage, and cookware add-ons.
- Partner-funded or employer-sponsored relocation packages.
- Extension into recurring workweek lunch subscriptions after the initial kit.

### Pilot economics hypothesis

These are targets to validate, not claimed actuals:

- Blended revenue per meal: **₹318–₹350**.
- Kitchen, ingredient, delivery, packaging, support, and recovery cost: **at or below ₹230 per meal**.
- One-time onboarding and starter-pack cost: **at or below ₹450 per subscriber**.
- Contribution margin before acquisition cost: **20%+ during the pilot**, improving with route density.
- Acquisition payback: **within the first package for partner-referred customers**.

Cookware should be rented, sold through a partner, or secured by a refundable deposit. Giving cookware away inside the base package would undermine the economics.

## Go-to-market

### Channel priority

1. **B2B2C relocation partners** — the strongest path because customer intent already exists.
2. **Corporate onboarding** — People teams can offer the kit to transferred or newly hired employees.
3. **Property and co-living partnerships** — place a QR code and welcome offer at move-in.
4. **Referral loop** — reward successful introductions with meal credit.
5. **Direct search and social** — useful for learning, but not the primary scale channel.

### Pilot message

**Moving to Delhi? Your first 7 or 14 days of meals are handled.**

This is clearer and more urgent than explaining “daily food infrastructure” to a first-time customer. The infrastructure narrative remains valuable for investors and long-term positioning.

## Six-week validation plan

### Week 1 — Supply readiness

- Select the primary and backup kitchen.
- Cost every menu item.
- Define packaging and delivery SOPs.
- Set daily capacity and stop-sell rules.
- Configure the WhatsApp concierge workflow.

### Week 2 — Partner and customer discovery

- Interview 15 recent relocators.
- Secure at least three distribution partners.
- Test the offer and pricing with paid reservation language.
- Refine menu and service windows.

### Weeks 3–4 — Paid pilot

- Serve 10–15 subscribers.
- Track every delivery, issue, cost, and feedback response.
- Run no more than two menu paths per meal window.
- Contact any customer scoring below 4/5 on the same day.

### Weeks 5–6 — Repeatability test

- Grow toward 25–30 cumulative paid subscribers.
- Test extension from 7 days to 14 days or a workweek plan.
- Compare direct and partner acquisition.
- Decide whether the model should continue, change, or stop.

## Decision gates

Proceed to a second micro-market only when the pilot reaches all of the following:

| Metric | Minimum signal |
|---|---:|
| Paid customers | 25 cumulative |
| On-time delivery | 95%+ |
| Meal complaint rate | Below 3% |
| Average meal rating | 4.3/5+ |
| 7-day customers extending or converting | 35%+ |
| Contribution margin before CAC | 20%+ |
| Referral or partner-sourced customers | 50%+ |

If reliability and contribution margin are healthy but extension is weak, revise the offer. If reliability is weak, do not add geography or products. If contribution margin is structurally negative, change price, menu, delivery model, or kit scope before further development.

## Defensibility

The initial product is operationally copyable. The defensible asset is built over time through:

- dense neighborhood demand;
- trusted relocation and employer distribution;
- kitchen performance data;
- customer preference and renewal data;
- reliable menu and capacity forecasting;
- standardized quality and recovery systems;
- a locally recognized trust brand.

The moat is not an app. It is the ability to make daily food dependable in a specific micro-market.

## Expansion sequence

1. Delhi Landing Kit.
2. Recurring workweek lunch extension for successful customers.
3. Employer-sponsored Corporate Fuel plans.
4. Adjacent Delhi micro-markets.
5. Household plans after delivery and menu operations are repeatable.
6. Creator tooling only when multiple kitchens require coordination.
7. Physical eating joints only after neighborhood density and brand trust justify fixed assets.

## What not to build yet

- Another native consumer app.
- An open marketplace of home chefs.
- Unlimited menu choice or customization.
- Multi-city logistics.
- A full household-replacement product.
- Physical dining locations.
- AI features without a measured operational decision they improve.
- Investor-facing complexity that does not increase paid demand.

## Core business idea in one paragraph

**The Passion Table sells a smooth first two weeks after relocation.** It partners with trusted local kitchens and relocation channels to provide newly moved professionals with two dependable daily meals, fixed delivery windows, dietary onboarding, and optional pantry setup. Customers purchase a 7- or 14-day package through a simple web-to-WhatsApp concierge flow. Subscription demand enables better batch planning and route density; partner distribution lowers acquisition cost; daily feedback protects trust. Once this model earns repeat demand and positive contribution margin in one Delhi micro-market, it can expand into recurring workday meals, employer programs, and eventually broader household food infrastructure.