An analogy, deliberately. The figures are chosen to make the structure visible rather than to match any real scheme, and they are not reconciled against actual benefit rates. Every number on the page is computed from the input set at render time, so the worked example can be changed without rewriting the argument, and a reader who thinks an input is wrong can say which one.
Pre-read · before instruction 03
Fifteen pounds, a million people, and nobody eating badly
Every instruction in this study is a version of one problem: a resource that is adequate in aggregate and useless when it is fragmented, and an argument about who is allowed to aggregate it. This page states that problem as a working model, with the inputs exposed, so it can be argued with by moving a number rather than by disagreeing with a paragraph.
Chapter 1 · A budget spent in full, and people still hungry
The problem, stated plainly
One principal is responsible for feeding a million people every day. Three meals each, fifteen pounds a head. The money exists, it is budgeted, and it is spent in full.
The current arrangement transfers the fifteen pounds to each person and lets them feed themselves. It is simple, it respects their choices, and it does not work, because fifteen pounds buying for one, shopping for one and cooking for one does not put three adequate meals on a table. So the budget is fully spent and some people are still hungry.
That is the cleanest definition of waste available anywhere in this study. Complete expenditure, partial outcome, and nothing on any ledger showing that anything went wrong. No line item says "purchasing power destroyed by fragmentation", so nobody is accountable for the largest number in the system.
The alternative is to engage an agent. Feed as many people as possible, adequately. There is no extra budget. Keep the balance. Everything below is what that instruction actually requires, and what it is worth.
Chapter 2 · Derived, not asserted
What it takes
The first result is the one that restructures everything, and it comes out of a single input nobody thinks to ask about: how long a person occupies a place while being fed.
Ninety minutes of dwell against a two hour service window means the seats required are roughly three quarters of the people. Building that is not a difficult capital project, it is an impossible one, and if it were built the facility cost would consume the budget before anybody ate.
So the ninety minutes has to happen somewhere the agent does not pay for, which turns out to satisfy the other constraint as well, because the place people most want to be is where they already are. That forces production, collection and consumption apart. They are assumed to sit in one building only because that is what a restaurant is.
Production then goes where land and labour are cheap, since nobody visits it. Collection goes everywhere people already are, and a collection point is not a kitchen, it is a counter or a locker borrowed from somewhere with existing footfall. Consumption happens at a desk, at home, on a bench, on the participant’s own time and at the agent’s zero cost.
| What it takes | How many | Where the number comes from |
|---|---|---|
| Meals a day | 3,000,000 | Every person, every meal, every day. |
| Seats, if they eat where you serve | 750,000 | 90 minutes of dwell against a 2 hour window. At 4 square metres a cover that is 300 hectares of dining room, which is why consumption has to happen somewhere you do not pay for. |
| Production units | 14 | 2,000,000 hot meals a day at 150,000 per unit. The rest is ambient and needs no kitchen. |
| Collection points | 2,085 | One point clears 1,200 people in a window. Throughput alone wants 834; proximity multiplies it by 2.5, because you place for a short walk rather than for utilisation. |
| Staff | 8,262 | 4,667 in production at 80 meals a labour hour, 2,335 on collection with 50% of points unstaffed lockers, 1,260 in support. |
In plain words: the seats you need are the number of people multiplied by how long each one sits, divided by how long the service runs. Collection points work the same way: how many people one counter gets through in a window, divided into the population, then multiplied up because you place them for a short walk rather than for a full queue.
derived: every figure above is computed from the inputs at the top of this page and from nothing else. The inputs are a worked example rather than a measurement, and the point of printing them is that you can move them and watch the answer move
Chapter 3 · Why the obvious design does not survive
The three constraints, and what each one forbids
Scale economics want few sites, many covers each, and a narrow menu. All three constraints attack exactly that, which is why the naive answer fails and why the real one is interesting.
Dwell time forbids seating, as above. It is the constraint that does the most structural work and the one least likely to appear in a specification.
Proximity forbids consolidation. People will not travel far, so collection points are placed for a short walk rather than for utilisation, and average occupancy of those points sits well below capacity. That is not inefficiency, it is the price of the constraint, and it should be costed as such rather than optimised away.
Choice forbids the narrow menu, and this is the one that looks fatal and is not. People want variety in dishes, not in ingredients. A narrow set of components combining into a wide apparent menu keeps the purchasing power intact while giving real choice, which is the arithmetic every assembly line food operation runs on.
And pre ordering makes choice nearly free. If people choose ahead, production matches demand exactly, waste collapses, and forecasting stops being guesswork. The price is that they decide in advance, which most people will accept for food they actually want. That single mechanism resolves the tension between choice and scale, and it does something more important that the next chapter but one depends on.
Chapter 4 · A perpetuity that can be damaged but not renewed
What it is worth
Two rules turn this from a contract into an annuity. The agreement never renews, continuing as long as people want to be fed, and the base is replenished against death but not against departure. So the only thing that can shrink the business is a participant deciding they are not being fed properly. Death is free for the revenue, and as the table shows it is not free for everything.
Revenue is therefore a direct function of service quality, forever, and nothing else touches it. There is no acquisition, no growth and no renegotiation. There is only not losing people.
Which makes the value of one participant the number that should run the entire operation, and it is not the fifteen pounds. It is the whole remaining perpetuity, and it dwarfs the cost of almost any effort to keep somebody. No annual budgeting process will ever produce that conclusion, because it weighs a permanent loss against a monthly cost line and the two are not on the same scale.
It also puts the risk at the worst possible moment. Because losses are permanent, an early failure costs a participant’s entire remaining life, and that failure is most likely in the first weeks, when the operation is least settled and the agent knows least about anybody. The rational response is to deliberately over serve at the start, at a cost per head well above steady state. It looks wasteful under a cost per meal lens and it is cheap under a lifetime one.
| Per head per day | Amount | Does it shrink when somebody leaves? |
|---|---|---|
| Received | £15.00 | Yes. It leaves with them, permanently. |
| Food | £6.00 | Yes, entirely. |
| Packaging, variable labour, distribution | £0.99 | Yes, mostly. |
| Retention and discovery | £0.75 | No, and cutting it is how the leaving starts. |
| Fixed: plant, technology, management, base labour | £2.14 | No. The assets cannot be sold and the routes still run, so this figure RISES per head as the base falls. |
| Total cost | £9.88 | |
| Margin | £5.12 | £1.9bn a year at a full base. |
Because the contract never renews and the base is replenished only against death, this is a perpetuity that can be damaged but not renewed. Discounting the margin at 8 per cent against an irreversible loss rate of 1.0 per cent a year:
In plain words: a stream of money that never ends is worth the yearly amount divided by the rate you discount it at. The yearly amount is the margin on everybody, and the loss rate is added to the discount rate, because an income that shrinks a little each year is worth less than one that does not. The second version is the same sum for one person, and it is the number that should decide how hard you work to keep them.
The whole book is worth about £20.8bn, and one participant is worth £20,758 against £3,607 to feed them for a year. That ratio is the entire operating philosophy: it is rational to spend several years of somebody’s cost of service to avoid losing them once, and no annual budget will ever produce that answer, because it weighs a permanent loss against a monthly line.
Death does two different things and they are easy to run together. The base is replenished, so revenue is untouched: 10,000 people a year are replaced and the perpetuity does not notice. But retention is an investment in a named person rather than a running cost, so whatever was spent on somebody is written off when they die, and their replacement starts from nothing. That is £2.5m a year rebuilt from zero, or £0.01 a head a day. Small here. Not small everywhere.
What decides whether it matters is how long the onboarding investment takes to pay back, which here is 49 days. At a mortality rate of 1.0 per cent a year, the chance of losing somebody before that investment has paid for itself is about 0.13 per cent. So it is worth making for very nearly anybody, and the mortality line is a rounding error rather than a constraint.
Push that ratio towards one, by making onboarding dearer, or the margin thinner, or the population older, and the arithmetic quietly starts telling the agent to invest less in whoever is likely to die sooner. Nobody would write that policy down. The spreadsheet arrives at it unaided, and it is parking wearing actuarial clothes.
Fixed cost does not fall with the base, so the operation breaks even at 294,991 participants, 29 per cent of the starting book. And the largest sum that can be paid for the concession while still surviving a fall to 70 per cent of the base is about £12.7bn. Anything above that buys an asset whose own price has removed its ability to keep the people it depends on.
derived: computed from the same inputs as the table above. The discount rate, the loss rate and the stress case are assumptions and are stated so they can be argued with rather than buried
Chapter 5 · The correction that makes the mechanism work
Adequate is discovered, not specified
The obvious safeguard is for the principal to specify what adequate means, and it is wrong. A specified standard becomes the thing the agent optimises, and it drifts from the thing the participant wanted. That is the funded measure problem, which is the subject of the rest of this study, and writing it into the contract as a protection would reinstate the very failure the arrangement was built to avoid.
Adequacy is person dependent. What keeps one participant will not keep another, so there is no single threshold for an agent to sit just above. There are a million of them, and the only way to stay above all of them is to actually serve each person.
Which is why pre ordering matters far beyond waste control. Every order is a statement of what that person considers adequate, collected continuously, at no cost, without a survey. Adequacy gets learned from revealed preference rather than declared in a schedule.
And the exit is not the only signal, it is the last one. Before somebody leaves they order less, they skip meals, they retreat to the same safe thing, they stop collecting. Declining consumption is the leading indicator of departure, measurable per person, daily. The agent watches consumption rather than satisfaction, which is a better instrument than any specification would have produced.
One residual risk remains and the framing sharpens it rather than removing it. With nothing specified, nothing obliges the agent to keep trying with the people whose adequacy is most expensive to discover. The protection therefore belongs on coverage rather than on the food: not what adequate means, but whose adequacy you are obliged to keep discovering.
Chapter 6 · Where the consequence actually lands
Leaving a provider, not leaving the scheme
A participant who is badly fed does not fall out of the system. There are controls, and a mirror of what has been discovered about them, so another provider takes them on without the usual constraints. Their record travels, so they do not have to teach somebody new what they eat, and there is no gap, no reassessment and no penalty.
One principle sits underneath that and it is worth stating on its own, because it is the opposite of how schemes like this are usually built. THE PARTICIPANT IS GOOD. They are never the instrument of discipline, never the party whose behaviour is being corrected, and never the one who pays for a failure. The entire consequence lands on the provider.
That changes the character of the exit completely. Leaving is now cheap for the participant, because they keep being fed, so they will do it sooner and on smaller provocation. The signal gets faster and more sensitive, which is harder for the provider and better for everybody the scheme exists to serve.
And it makes the loss zero sum rather than merely absolute. A departure no longer evaporates into a cash payment, it arrives at a competitor as scale. So the league table is not a ranking anybody has to construct: it is the net flow between providers, observable monthly, unambiguous, and impossible to present as anything other than what it is.
Two clauses have to hold or the whole mechanism inverts, and they are symmetric. The receiving provider must not be able to refuse. Give it discretion on intake and it will decline the expensive, and the worst served participants become unplaceable, which is the parking problem re entering through the door marked exit.
The other is harder and less obvious. If every participant carries the same fifteen pounds and any rival must accept them, then a provider can deliberately under serve its most expensive people until they leave, and offload its costly tail onto somebody obliged to take it. Free movement plus a flat rate is an arbitrage against the safeguard, and it is profitable.
It is also detectable, which is the useful part. Dumping shows up as the composition of the leavers rather than the number: a provider losing its expensive tail while retaining its cheap core is doing something quite different from one losing people evenly. The remedy is that the money following a participant should reflect what it costs to serve them rather than being flat, so that taking on a difficult person is a transfer of funding rather than a transfer of loss.
The same failure, in a system where the money does not follow the difficulty, is instruction 01.
Chapter 7 · And why competing it away breaks the design
The margin is the safeguard
The exit right is the cleverest feature of the arrangement. It makes quality and margin point the same direction by construction rather than by supervision: it reports itself, it needs no inspector, it arrives without a survey, and every departure removes a cover from the scale the agent’s economics depend on.
It only works while the agent has margin to protect. An agent operating on a thin margin cannot afford to discover anybody’s adequacy, cannot afford to keep trying with an expensive participant, and cannot afford the choice that makes discovery possible.
And because a departure now arrives at a competitor rather than evaporating, an agent without margin is not merely declining, it is feeding the provider that will replace it. So there are two ways to destroy it and they are the same move in different clothes. Compete the price per head to the floor, or auction the concession for a large capital sum. Either converts the quality margin into a payment, and a payment behaves exactly like fixed cost: it does not shrink when participants leave, so it rises per head precisely as the base erodes.
The tempting valuation at a low price or a high bid is therefore not conservative, it is arithmetically false. It discounts a perpetuity while assuming a retention rate that the price itself has made unfundable. You cannot put the quality spending in the denominator and the base stability in the numerator.
Which leaves the principal with the genuinely hard question, and this page exists to make it precise rather than to answer it. What is the lowest price at which the agent can still afford to care, and how much of the aggregation gain is the principal willing to leave in the food rather than take as a cheque?
Chapter 8 · The analogy, decoded
You have just designed a semantic model
None of this was about food.
A resource that is adequate in aggregate and useless when fragmented. A thousand individual preparations of the same thing, each one reasonable, together destroying most of the purchasing power. A constraint on how long any one person can occupy the resource, which turns out to forbid the obvious design. Users who will not wait and will not accept a narrow menu. And a quality signal that exists only as people quietly leaving, one at a time, permanently, without telling anybody.
That is a reporting model. It is the same problem with different nouns, and the table above is the translation.
The row that matters most is the one about people never coming back, because it is already documented elsewhere in this study from the other direction. At least one unofficial spreadsheet per region, maintained by somebody whose job is something else. That is not a governance failure or a discipline problem. It is a participant taking the cash, because what they were offered was not adequate for them, and they will not be back.
And here is the part that should be uncomfortable rather than reassuring. This is what a badly built model looks like from the inside, and a good one is not far removed. A good model is still an aggregation play with the same structure; the difference is unit economics, not kind. Which means its failure mode is identical and merely slower. The users drift off one at a time, permanently, quietly, and nothing in any dashboard records a departure as a departure.
That is the finding this study keeps arriving at from different directions. A model that was properly fixed stays fixed. A different one grows into the same condition unobserved, because nothing watches the curve and the losses do not present themselves as losses. The thing worth building may not be a faster model at all.
The model this describes is instruction 03. The organisation that has the answer and no route to a decision is instruction 04. They are the same problem: a resource adequate in aggregate, wasted by fragmentation, with nobody permitted to aggregate it. One wastes compute and the other wastes expertise, and both are the eighth waste.
| In the feeding problem | In a reporting model | What it costs when it goes wrong | |
|---|---|---|---|
| Fifteen pounds transferred to each person | Every report and every user fetching and preparing their own data | The same transformation performed again for each of them, on every refresh, forever | |
| Fifteen pounds buys nothing adequate when cooked for one | A query that computes from scratch what was computed an hour ago | The budget spent in full, the outcome partial, and no line item anywhere naming the loss | |
| Aggregation into central production | One properly modelled shared layer, computed once and read many times | Where the entire gain is, and it is available without spending anything more | |
| Ninety minutes of dwell | The resource held for the duration of a query | Concurrency demand that exceeds any capacity you could buy, which is why adding capacity does not fix it | |
| People will not travel far | Users will not accept latency | They leave rather than wait, and they do not announce it | |
| People want what they want | Everybody wants their own measure, their own cut, their own view | Answered with range it destroys the economics; answered with componentry it costs almost nothing | |
| Pre ordering | Knowing the query patterns, so the right things are pre computed | The difference between forecasting and guessing, and the mechanism that makes choice affordable | |
| A participant taking the cash | A user extracting it into their own spreadsheet | A worse answer for them, a lost cover for you, and it never appears as a failure | |
| They never come back | Nobody who has built their own version returns to yours | Permanent, one at a time, invisible, and it compounds against a cost base that does not shrink | |
| Adequate is discovered, not specified | You learn what a user needs from what they actually do | Specify it instead and you optimise a measure while the person quietly stops using it | |
| The exit is the quality measure | Usage telemetry is the only honest signal you will ever get | Ignore it and the only remaining feedback is the complaint of whoever is loudest | |
| The margin is the safeguard | Headroom is what lets you serve the awkward case | Squeeze it to nothing and every remedy becomes unaffordable exactly when it is needed |
summary: the analogy decoded. It is placed at the end rather than the beginning deliberately, because a reader who has just spent ten minutes designing the agent has designed a semantic model, and being told that at the start would have saved them a minute and cost them the argument.