The Host Took 30%: What Is Left on 259 Units at a scenic area visitor centre

The Short Version First

This note looks at tech for 259 units over 41 months at a scenic area visitor centre, written from the buyer's side of the table. The figures are modelled rather than measured: cup volumes, price per cup and cost lines follow stated assumptions, and the arithmetic is left visible so a reader can substitute their own numbers.

The Assumptions Behind the Numbers

Cup volume is stated per unit per day. Revenue is cups x 30 days x units x price per cup, taken at 14.7. Cost is consumables, the site share, power and parts. Payback is equipment spend divided by steady monthly net. No figure here is a quotation.

The model keeps the ramp separate from the steady state: the early months carry a lower cup count, and the steady figure is the plateau the site settles into once regulars appear. A reader who expects a different ramp can replace it without disturbing anything else on the page.

Month by Month, Line by Line

The columns are shown separately because the argument is rarely about the total. It is about which line moves fastest when a site underperforms, and which lines were fixed before the first cup was sold.

What Moves First in These Rows

The best month in this model nets about 1078220, the weakest about 601771. The gap is the site's own variability rather than a change in cost, and that gap is what a trial period exists to measure.

At the modelled plateau, payback lands at 4.8 months. Read it as a reading of these assumptions, not a forecast: halve the cup volume and the same placement reads very differently.

Consumables scale with sales, so they rarely surprise anyone. The site share and the route hours are the two lines that do surprise operators, because both are agreed before the first cup and neither moves when the site underperforms.

Reading the Rows for service

Telemetry has changed what unattended means. Stock, faults and sales report themselves, which moves the operator's job from finding problems to deciding which problems matter this week.

What telemetry does not report is the last metre: a drip tray gone sticky, cups stacked out of reach, a machine unplugged to charge a floor polisher.

Whatever the dashboard does not show becomes somebody's walk. The omitted fields are where the route time hides.

The Follow-Up Worth Answering

Time disappears in this business in fifteen-minute pieces: a wiped tray, a restock note, a call from a host about a screen. None of it shows on an invoice and all of it decides how many sites one person can carry.

A route that runs on memory works until the memory takes a holiday. A route with a written cadence survives a new hire, a flu season and a public holiday in the same month.

The Check List

1. Check what the dashboard reports and what it omits
2. Record the first three faults with date, part and cause
3. Decide the escalation path before the first failure, not after
4. Write the weekly cadence down and time one full cycle
5. Count the minutes per visit, not the minutes per machine
6. Confirm the trial period and the move-out term before delivery
7. Write the modelled cup volume into the plan and review it after month one

The Method, Applied to Your Numbers

The method, stripped to five moves, runs like this:

1. Take a full week of cup counts, including the two dead hours nobody likes to record
2. Price one cup from the invoice, including the capsule, the cup and the lid
3. Put the host share, power and spares on three separate lines, never one
4. Divide total equipment and installation spend by steady monthly net, then round the answer into a range
5. Halve the cup volume and see whether the site still earns - if it does not, say so before signing

The Venue Changes the Curve

Venue shapes the curve more than the machine does. Four patterns recur in operator accounts, and each one moves a different line in the table.

A venue can change category within a year - a new tenant, a shift pattern, a bus route. The pattern is a snapshot, and the walkthrough is what confirms it.

The Takeaway, Stripped Down

The first thing to keep is the habit of arguing with numbers rather than with adjectives. Every payback claim decomposes into five inputs, and four of them are checkable before signing.

The trial period does the work that due diligence pretends to do. Thirty days of real cups beats three months of projections.

Finally, put the planned cup volume in writing. Most placements fail on volume, not margin, and a written number turns that failure into a month-two conversation instead of a year-ten post-mortem.

The Conditions Behind the Result

Three assumptions carry most of the weight - daily cups, the host's percentage, and access hours. Change any one of them by a fifth and the payback moves by more than the others combined.

Compare models, not headlines. Two payback figures built on different cup volumes are not a comparison; they are two advertisements.

Common questions

What should a dashboard actually report?

Stock depth per line, faults with timestamps, sales by hour and the machine's online state. Anything beyond that is useful only if someone reads it weekly.

Does remote monitoring reduce service visits?

It changes them rather than removing them: fewer emergency visits, more planned ones, and a better guess at which part to carry.

What do the modelled numbers actually mean?

They are the arithmetic of stated assumptions, not measurements. Every input is listed in the assumptions section so a buyer can replace it with their own.

Why show six months instead of a full year?

Because the first six months contain the decision: the ramp, the plateau, and the first sign of which cost line moves when the site underperforms.

Related reading

• $7,564 in a Good Month, $2,458 in a Bad One: Plan for Both
• Month One Is Not the Business: 13 Cups, Then 32
• 16 Months In, Payback Is Still 22 Months Away
• The Host Took 22%: What Is Left on 32 Units at a motorway service area