Research

Production, Not Experience: A Look at Distributed Food Manufacturing

A working idea, not a settled plan — an exploration of a structural contrast, not a claim about any specific business.

Two different things a restaurant can be

Most food-service businesses sell an experience: a room, a service style, a sense of occasion, built around a meal that takes an hour or more. A much smaller category sells something narrower — a product, made on-site, sold quickly, with the experience stripped down to almost nothing. These aren't better or worse than each other. They're structurally different businesses, with different costs, different risks, and different ways of using a space.

What the full-experience model actually costs

Consider a well-regarded flagship restaurant that recently underwent its first major renovation in over three decades — a deliberate choice to seat fewer people, not more, in service of a longer, single-format tasting menu experience: several hours, a five-figure-per-table price point once wine pairings and add-ons are included, a required deposit just to book. That's not a criticism — it's an honest description of what "experience" as a product costs to deliver, and what it charges to cover that cost.

The same restaurant group's other recent venture — a second location built on similar ambitions — closed after just fifteen months, its owners citing "the high costs of operating in the current environment," despite critical acclaim and industry recognition. A full-experience model, done well, can still be economically fragile: the fixed costs of staffing, service, and room don't shrink just because a location is new.

A narrower alternative

A model built around one or two products — made on-site, sold for takeaway or brief on-site consumption, with minimal seating and minimal service staff — carries a fundamentally different cost structure. Less square footage devoted to dining room, fewer front-of-house staff, faster turnover per transaction, and a production process (baking, roasting) that can run on a schedule independent of when customers are actually in the room. It trades the revenue ceiling of a full-experience model for a much lower cost floor.

Micro-Factory Unit Economics: What a Two-Item Menu Changes

A working idea, not a settled plan — grounded in public financial filings, not a claim about any specific business's future results.

The question

Does shrinking a food-service concept down to a narrow, production-focused format — smaller footprint, minimal seating, a handful of products made on-site — actually change the economics, or is it just a stylistic choice? Two publicly traded companies' own financial disclosures offer a real, if imperfect, answer.

Two very different boxes

A large, full-service, casual-dining flagship format typically runs 7,000-10,000 square feet, does an average of roughly $12 million a year per location, and — critically — spends about 35 cents of every revenue dollar on labor. A much smaller, production-forward beverage format runs on the order of 500-1,200 square feet (much of it drive-thru lanes, with most locations offering no seating at all), averages roughly $2 million per location, and spends closer to 27 cents of every dollar on labor.

The smaller format gives some of that labor advantage back in ingredient/packaging cost — it runs a few points higher on food and beverage cost than the full-service comp. Net, though, combined prime cost (food plus labor) still comes in several points lighter for the smaller, more production-centric format.

Where the difference really shows up: density

The more striking pattern shows up in revenue per square foot — and it holds up inside a single company's own portfolio, not just across two different companies. One large casual-dining operator runs several formats at once: its flagship (7,000-10,000 sq ft) generates a bit over $1,100 per square foot of "productive" space; its own smaller fast-casual format (3,000-4,000 sq ft, more than half of sales off-premise) is the highest-density format in its entire portfolio, generating meaningfully more per square foot on roughly a third of the footprint. The small-format beverage comp, built almost entirely around production rather than dining space, runs denser still.

The pattern, read plainly: within this dataset, smaller and more production-focused formats generated more revenue per square foot, not less — the opposite of the intuition that a bigger dining room means more revenue.

Pre-opening cost: the biggest gap of all

The full-service flagship format disclosed pre-opening costs of $1.0-1.5 million per new location. The small-format beverage comp disclosed roughly $180,000 per new location in the same fiscal year — six to eight times lighter. Build-out cost follows a similar logic: a smaller box, with less dining-room fit-out, costs less to open in absolute terms even before accounting for the per-square-foot rate.

Traffic tells its own story

In the same fiscal year covered by both companies' filings, the full-service flagship format lost transaction volume — offset only by raising prices — while the small-format comp grew transaction volume materially. That's a single fiscal year, not a structural law, but it's a real, filed data point worth sitting with.

What this doesn't prove

This is two companies, two fiscal years, and formats that don't map perfectly onto a fresh-bread-and-coffee concept — there is currently no comparable public company running a fresh-bread-forward, bakery-cafe format at scale to compare against directly (the one that used to exist stopped filing public financial reports after going private). The labor and COGS percentages above are consolidated, filing-level figures, not a location-by-location breakdown, and neither company runs anything resembling a break-even, cooperative operating model — both figures above describe conventional for-profit chains, which is a different economic starting point entirely.

No Milk, No Fridge? The Regulatory Question Behind a Two-Item Menu

A working idea, not a settled plan — shared as an open question, not a claim about what any specific business will do.

The question

A food-service concept built around exactly two products — fresh bread, fresh coffee — raises an unusual question: does a menu that narrow actually need refrigeration equipment at all?

It's a more precise question than "how do you handle milk without a fridge." Framed correctly, it's this: does refrigeration-equipment regulation apply to a food premises categorically, or only to the specific food it handles?

What the code actually says

Refrigeration is not a blanket prerequisite of a food-service permit — it is triggered by the food a business actually serves. Frameworks across North America converge on a similar structure: food that requires temperature control to limit pathogen growth gets a specific technical label — the FDA Food Code calls it "TCS" (Time/Temperature Control for Safety); Ontario's provincial food-premises regulation uses "potentially hazardous food," with a parallel "low-risk food" category for everything else. In both frameworks, the refrigeration-equipment requirement is written to attach to that category of food specifically — not to every food premises regardless of menu.

Plain, unfilled bread and black brewed coffee both fall outside that category under the sources reviewed. If that's the entire menu — and stays the entire menu — the textual trigger for mandatory refrigeration equipment plausibly doesn't fire.

That's a reasonable reading of the code language. It is not a confirmed regulatory outcome for any specific location — no source reviewed showed a health department explicitly pre-approving a zero-refrigeration permit on this basis, and local inspectors retain discretion in plan review. Any business exploring this path would need direct, written pre-permitting confirmation from its actual local health authority before relying on it.

The milk question, resolved

The presumed "hard problem" — can a coffee shop legally decline to offer milk at all — turns out not to be a legal problem. No code reviewed requires a food-service establishment to carry any specific item, including dairy. Menu composition is a business decision; food codes regulate how food is handled, not what must appear on the menu. The real question a narrow-menu, no-dairy model has to answer isn't "is this legal" — it's whether customers accept a coffee shop that doesn't offer milk.

Where this gets harder

A model like this only holds if the menu actually stays narrow in practice, not just on paper. A few things would pull refrigeration back in: any dairy-based filling, glaze, or cream added to a baked good; any milk exception offered on request; and, notably, jarred preserves — which, while often shelf-stable themselves, can trigger a separate manufacturing-process regulatory track entirely independent of the refrigeration question, if they're made on-site rather than resold pre-made.