Monthly hours are only a screening limit. Several units can need service in the same short window, so the actual changeover calendar decides whether the promise fits. This page explains the specified case and decision, not average industry pricing or a promised outcome.
Two calendars can still collide
The case has two cleaners working independently. Each has 120 bookable monthly hours and a 150-minute reset slot including travel. That gives 96 monthly slots before booked demand and cancellations. The average does not say that two midday resets can be followed by a distant third unit before check-in.
Use the host’s actual departure and arrival calendar. On each peak day, place the whole reset, keys, travel and likely delays on each cleaner’s line. Do not convert unused Monday hours into capacity for simultaneous Friday jobs.
Inspect the worked case
| Measure | Scenario input or calculated value |
|---|---|
| Independent cleaner calendars | 2 |
| Bookable hours / cleaner / month | 120 |
| Whole reset slot / hours | 2.50 |
| Monthly maximum slots | 96.00 |
| Target completed resets / month | 73.38 |
| Collection delay / days | 14 |
| Peak-day promise | Not validated by the monthly model |
These values belong to this fictional operating format. Rounded visit counts are monthly planning averages; they are not a promise that the actual route or peak-day calendar fits.
Keep the promised service inside the slot
The host supplies clean linen and guest consumables. Off-site laundry, guest support, maintenance and property management are excluded. Adding any of them would alter time, staffing and cost; rental income belongs to the host, not this cleaning business.
The case allows 120 minutes at a unit and 30 minutes for travel and access. A late guest departure or damaged unit may require an exception process rather than another hurried booking. A backup worker has not been budgeted.
Read cash after the scheduling test
The model uses 78% requested slots, 2% cancellations and a $170 fee. Its monthly average is a forecast boundary, not proof of punctual resets. Customer receipts are delayed by 14 days, so an accepted service calendar still needs working cash.
Obtain paid reset timings and a real peak-day coverage plan before promising availability. The annual forecast results remain useful for screening the operation, provided the reader retains that unresolved calendar limit.
Read profit and cash together
| Measure | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Revenue | $130,987.60 | $152,694.12 | $155,748.00 |
| EBITDA | -$6,256.27 | $9,644.16 | $8,551.56 |
| Net income | -$12,768.46 | $3,089.54 | $2,226.39 |
| Closing cash | $21,143.20 | $29,849.65 | $37,690.60 |
The forecast cash low point is $14,716.48. Year 1 net income is -$12,768.46. Working-owner salary is included once; EBITDA excludes depreciation, interest and income tax, while net income includes the forecast depreciation and simplified tax provision. Funding is proposed, not secured. Project payback is not reached within 36 months and is not an investor payout.
Replace the assumption that changes the decision
Obtain actual proposed changeover calendars and replay peak days with travel. Complete paid resets and keep a backup agreement before offering a host a guaranteed window.
A monthly capacity average hides concentrated changeover windows. Late departures and a clustered calendar can make a nominally underused team miss promised arrival times.
Customer sales tax is outside the modeled service fees and cash schedule.
Texas lists home, office and window cleaning as taxable services. Review the actual billing treatment using the Texas Comptroller’s service guidance.
Review product-specific training and safety data with OSHA/NIOSH cleaning-chemical guidance. This page is a financial scenario, not a technical work instruction.
The complete Turnkey Reset example is in preparation for publication. Browse published examples ↗ Create your own plan ↗
Build from your own evidence.
Use a measured service scope, a coverage-based roster and actual payment terms. Save the revised model before interpreting the result.
Create my plan ↗