One option isn't a market.

How this started

For the record — July 2026, the incident that made me look. It's the footnote, not the argument.

I ordered a four-sandwich platter from a big franchise in Motor City. The cheese was missing from all four. Nothing was toasted. When I asked, I was told everything had been made correctly — and offered a remake in the same breath.

That's what made me look. Not the cheese — the logic.

A kitchen that can't say "we missed that" can't get better, no matter who's working the counter.

And to be clear: this isn't about the person at the counter, and it isn't about shutting anyone down. People working a lunch rush understaffed, measured on speed, penalized for waste — they're set up to fail. The system is the problem. And a system nothing competes with never has to change — which is why this project exists, and why it's ours, not mine.

It's not the people. It's the incentives.

And incentives only stay this bad where nothing competes with them. A neighbourhood with one default option has no quality mechanism — no competitor to lose your lunch to, so nothing pushes back.

• Money leaves the food first.Franchise royalties and ad fees come off the top of every sale — before rent, before wages, before ingredients. Cost-cutting lands on the plate.
• Speed is measured. Accuracy isn't.Store metrics reward tickets-per-hour and low food cost. Nobody's bonus depends on your sandwich being right.
• Admitting a mistake costs the store.Remakes count against food-cost targets. Denial is the rational move — for the store, never for you.

The fork: same simple food, different system

In open source, when something's broken and the maintainers won't fix it, you fork it — take the idea, rebuild it right. That's this — and a fork only lives if people maintain it together. This one is maintained by the neighbourhood that eats from it.

• +
  A short menu. Fewer items, fewer failure modes, everything done properly.
• +
  Honest ingredients. Real cheese, real bread, nothing we wouldn't serve our own family. Suppliers named.
• +
  Open recipes. Every item has a published build sheet. You can see exactly what's supposed to be in your order — and check it.
• +
  Mistakes get owned. Wrong order = remade free, no interrogation. Every fix goes in a public changelog, like software.
• +
  We steer it together. Members vote on what we make and what we drop — and on format and location as the build takes shape.

Delivery-first, Motor City first. Small, local, accountable — run by the people it feeds, with your order checked before the lid closes.

Why franchise food slips

No villains here — just mechanics. Every claim below is generic franchise economics, and every one of them shows up on your plate.

1. It's a system output, not an accident.

   Your wrong order isn't bad luck or a bad employee. It's the predictable output of a system — and systems can be redesigned.

2. Money leaves the food first.

   A typical fast-food franchise sends 8–12% of gross sales to royalties and ad funds before a single cost is paid. The franchisor profits on gross; the franchisee survives on net. The only levers left are ingredient cost and labor cost — so portions shrink, substitutions get cheaper, steps get skipped. Invisible one order at a time, systemic in aggregate.

3. The people are set up to fail.

   Minimum staffing against lunch-rush throughput means skipped steps aren't laziness — they're triage. Turnover is high, so training amortizes to zero and the build lives in someone's head, not on a sheet. The person assembling your order gains nothing when it's right and loses nothing when it's wrong.

4. The accountability loop isn't one.

   Stores are measured on speed of service, food-cost percentage, labor-cost percentage. Order accuracy is unmeasured and unbonused. A remake counts against food-cost targets — so admitting a mistake has a price, and denying it is free. Denial is the rational move. "If nothing's wrong, there's nothing to fix" is the system talking.

5. You can't fix it as a customer.

   Staff rotate, managers rotate, your loyalty is anonymous to the people making your food. Refund friction is by design. The rational customer just stops ordering — and the store never learns why. And when it's the only default in the neighbourhood, you can't even switch: a market of one has no quality mechanism at all. Mediocrity is its resting state.

6. A closed loop looks like this.

   A small menu means fewer failure modes. Published build sheets mean accuracy is checkable by anyone. Blameless remakes, budgeted as cost-of-quality, make admitting mistakes free — so mistakes surface, and surfaced mistakes get fixed. A public changelog closes the feedback loop in the open. A kitchen steered by its own members plays a repeated game with the neighborhood — because it is the neighborhood.

7. Measure honesty, get honest food.

   Franchises optimized simple food for extraction and got exactly what they measured. Measure honesty instead, and you get honest food. That's not idealism — it's a different spec sheet. Help write it →

What do you wish existed?

Everyone has a simple-food letdown — the order that arrived wrong, the "fresh" thing that wasn't, the place that stopped trying. We're collecting them. Not to pile on any brand or any worker — no names needed — but because the pattern is the point, and your letdowns are the spec sheet for what we build. Signing on isn't joining a waitlist — it's early membership of the group doing the building: the list votes on menu, format, and location as they take shape.