Type a month of shifts for each host and the screen projects what that month produces — booked calls, new customers, wage and ad cost — and what those customers go on to be worth. This page shows where every number comes from.
Everything in the Monthly plan table is one month: the shifts you type, the calls they produce, the customers won, the wage and ad money spent. Only the last three columns look further out — they say what that month's new customers are worth over their first six months as customers.
One number per host: how many shifts they'll work in the month you're planning. Everything else recalculates as you type.
Booked calls, customers, wage, ads, total cost — all for that one month of shifts.
What those customers bring us over their first six months. The "6M" columns are the only ones that look past the month.
Type 18 shifts for Mkaya and the screen walks this chain — every step uses a measured rate, not a guess:
Add the two costs — £1,008 wage + £1,086 ads = £2,094 total, £67 per customer. Then the six-month columns: 31 customers × £127 = £3,964 net revenue, minus the £2,094 = £1,870 gross profit.
The Inputs table under the plan holds five rates per host. They're measured from the same booking, rota and advertising records as the Host analysis report, over the window of complete months you pick with the pills (last 1, 3, 6 or 12).
What the host was paid in the window, divided by the customers they won. Mkaya: £4,200 ÷ 130 customers, April–June.
The host's share of the Google Ads bill, divided by their customers. The all-calls / ad-traced toggle works exactly as it does on Host analysis.
The share of the host's booked calls that became paying customers. 130 of Mkaya's 293.
Straight from the rota system — the rate on the host's card today, and 4-hour shift blocks.
Hover any figure and it shows its working — the division and the months behind it. Type over any figure to override it: the cell turns amber, the projection runs on your number, and the ↺ puts the measured value back. A brand-new host with no history yet (no complete month worked) starts with blank cells for you to fill in.
The "6M net revenue / customer" figure is measured from real customers: everyone who became a LUFT customer in the last six finished cohorts, matched to what they actually spent in their first six months.
Two things to know about that number. It's our money only — the 25% platform share, never the therapist's 75%. And it agrees with the LTV reports: the Cohort payback machinery computes the same six-month figure its own way (by first order, all channels) and lands on £127 for the same months. One customer, one value, everywhere on the hub.
Both compare the six-month value against the one month of cost that bought it.
6M gross profit = net revenue minus the month's total cost. Mkaya: £3,964 − £2,094 = £1,870. Red means the customers won't cover what they cost.
Return on total cost = net revenue ÷ total cost. Mkaya: £3,964 ÷ £2,094 = 1.89 — every £1 spent on her shifts and ads comes back as £1.89 within six months. Note it divides by all cost, wage included, not just ad spend.
The Total line pools: it adds every host's £ and customers first, then divides once — it is not an average of the rows above it.
The same question with the per-host detail stripped away: if we land N customers in a month, what's the six-month profit at different all-in costs per customer?
Each row is one cost level. The break-even row is where cost equals value — profit £0. The ≈ your plan marker sits on the row closest to what your current plan actually pays per customer, so you can see at a glance how much headroom the plan has.
Given his inputs, the model prints his rows to the pound — Mkaya's 72h, £1,008, 59 calls, 26 customers, £2,585, 1.35. Automated tests run that comparison on every change to the code.
The planner reads the same records with the same rules — same wage ladder, same ad split, same conversion counts. Check any host's months on Host analysis and the pooled figure here agrees.
Two independent routes — LUFT customers by first call, and the payback report's cohorts by first order — land on the same six-month value per customer.
June really delivered 205 customers from 722 booked calls. Set the planner to June's actual staffing and it projects in line with what the month actually produced.
The current month never feeds the rates — its wage bill and customers are both still arriving. A host who started mid-month shows blank rates until their first complete month is in.
Same as Host analysis: until a host's invoice is agreed, their wage is what the rota says they're owed. Figures switch to real invoices automatically as they're checked off.
The rates are the host's recent average. A month with different call mix, holidays or a new campaign will land off the projection — treat the numbers as the centre of the range, not a guarantee.
Amber cells mean someone typed over the measured rate. The plan is only as honest as its amber cells — hover one to see what the measured value was.