Scenarios
Year 1 always ramps to the Year-1 exit targets on the Assumptions tab (default: the 30 July plan). Loading a scenario only rewrites Months 13–36. Any cell you then edit locks to your number and stops following the scenario.
Decision warnings
Year 1 reconciled against the 30 July plan
Where this model and the 30 July plan disagree, the difference is in cost lines the earlier plan did not carry: customer acquisition cost, per-subscriber variable cost, tiered NOC staffing and support. Revenue should track closely — if it does not, your Year-1 exit targets have been changed.
Year summary
Revenue, OPEX and cash profit
Cumulative cash position
Customer trajectory
Bandwidth usage vs provisioned capacity
Month 36 operating summary
Year 1 · Months 1–12
This is the Kumar plan window. Retail, LCO and LL cells are editable — type a number and press Enter to lock it. Locked cells turn orange and hold their value while everything else recalculates. Double-click a locked cell to release it back to the scenario.
Follows the scenarioLocked to your number
Years 2–3 · Months 13–36
Customer counts interpolate from the Year-1 exit to the Month-36 target of the loaded scenario. Edit any cell to lock it; the months after it continue to interpolate toward the Month-36 target.
Follows the scenarioLocked to your number
36-month OPEX schedule
Every OPEX line is editable for every month. An edited cell turns orange and stays fixed while customers, pricing and capacity change around it. Double-click a locked cell, use the row Reset, or use Reset OPEX in the toolbar.
Formula valueLocked to your number
Assumptions
Editing any assumption locks it, so Load scenario and Reset will not overwrite it. Cohort pricing is used throughout: your existing base keeps its legacy ARPU and decays with churn, while every new customer is priced at the acquisition ARPU.
Activity Log
Every edit made by anyone signed in, most recent first.