Scenario Planning for Multi-Location Services: Price, Lease, and Headcount Levers

A scenario plan is supposed to answer a simple question: if reality turns out materially different from the base case, how bad — or good — could it get, and what would we do about it?

Most scenario plans fail to answer that question because they perturb the wrong variables. They wiggle revenue up and down by 10% and see what happens to EBITDA. The result is mathematically correct and operationally useless. The question is not “what happens if revenue drops 10%.” The question is which levers will you actually pull, in what order, under which conditions, and with what lead time.

This is the scenario-planning framework we use with multi-location service operators. It is organized around three levers — price, lease, and headcount — because those are the three levers operators can actually pull in the 4-to-12-week horizon that matters.

Start with three scenarios, not seven

More scenarios do not produce more insight. They produce more spreadsheet. Three is the right number:

• Base. Your current best estimate. This is your rolling forecast — not your budget. For why these are different, see rolling forecasts vs. annual budgets.
• Upside. Base, with your two most optimistic-plausible driver moves applied.
• Downside. Base, with a specific demand shock and a defensive lever response.

The trick is that the scenarios are not parametric — they are narrative. Each scenario has a one-paragraph story. “Local competitor closes, we absorb 15% of their volume.” “Medicaid reimbursement rates fall 7%, we need to preserve DSCR.” The narrative is what forces the levers to be specific and believable.

Lever 1: Price

Price is the highest-ROI lever in most multi-location service businesses and, correspondingly, the lever most operators underuse. A 3% price increase that holds customer volume flat drops essentially 100% to EBITDA. The entire increase is incremental margin.

Model price as three tiers:

1. Tier 1 (price taker). Markets where you are at or near the median. Hold.
2. Tier 2 (pricing headroom). Markets where your lease coverage is above 12× and your utilization is above 72%. You have room. Model a 3% to 5% increase phased over two quarters.
3. Tier 3 (introduce premium SKU). Markets where demand is structurally constrained by capacity. Model a premium tier at 20% to 40% above base, captured by 15% to 25% of volume.

The enterprise-value math is severe. A 3% price increase across a $4M-revenue group at 14% EBITDA margin adds $120k of annual EBITDA, which is $660k of enterprise value at 5.5×. That is a single lever, one quarter of work, and a number that almost always exceeds the tool stack budget for the next decade.

Modeling price elasticity honestly

Elasticity is real. Every price increase costs some volume. The question is how much. Most multi-location service businesses see 0.1× to 0.3× volume sensitivity on modest (under 5%) price moves — meaning a 3% price increase loses 0.3% to 0.9% of volume. That leaves the vast majority of the gain intact. Aggressive moves (above 8%) see elasticity rise quickly, which is why small, staged increases almost always beat single large ones.

Lever 2: Lease

Lease is the most structural lever and, because renewals cluster, the lever most operators miss entirely.

For each location, track four things in your scenario model: current rent, remaining lease term, TI allowance status, and market comp rent. The scenario moves come from three patterns:

• Renewal negotiation. When a lease is within 18 months of renewal, the landlord is highly motivated. Model a 10% to 20% rent reduction with a 5-year extension in Tier 2 and Tier 3 markets.
• TI allowance capture. Unused TI allowances expire silently. Audit every lease for unclaimed TI and model the capital reinvestment (equipment upgrades, build-out improvements) that converts TI into revenue.
• Exit of marginal locations. In the downside scenario, identify the two worst branches on lease coverage (revenue ÷ rent < 6×) and model an exit on lease expiry. This is not pleasant, but the scenario framework exists precisely to examine unpleasant options before they become urgent.

Lever 3: Headcount

Labor is the largest cost line in most service businesses and the most operationally fraught lever to adjust. Model it with precision or not at all.

The single most important distinction: labor is step cost, not variable cost. (We covered this in the driver-based budgeting framework.) Modeling labor as a flat % of revenue produces the single largest scenario-analysis error I see in the field.

For the downside scenario, model headcount in three layers:

1. Overtime suppression. Cap OT at 2% of base across the group. Immediate, no severance cost, no service quality impact in most businesses. Typical saving: 1 to 2 points of labor cost.
2. Shift consolidation. Collapse underutilized shifts identified by the branch leaderboard. Two-week notice. Typical saving: 2 to 4 additional points of labor cost.
3. Manager layer reduction. If a multi-branch operator has a regional manager per branch, consolidate to one regional per 3 to 5 branches. Severance cost is real; the saving pays back in roughly 8 to 12 months.

Do not model all three at once in a single scenario. Stage them. The scenario model is most useful when each layer can be activated conditionally on a trigger (revenue drop threshold, DSCR floor, specific covenant breach).

Putting it together: the three-scenario output

The final scenario artifact is a single-page view with three columns — upside, base, downside — and six rows:

• Revenue (with driver decomposition)
• Prime cost % and absolute
• EBITDA and margin
• Operating cash flow
• Debt service coverage
• Enterprise value at exit multiple

Under each column, a one-paragraph narrative describing the levers activated. The page fits on one sheet of paper. That is the scenario plan. Anything longer is not read.

When to update the scenarios

Quarterly, minimum. Monthly during periods of meaningful volatility (new location opening, acquisition integration, material demand shift). The base scenario updates with the rolling forecast, so its mechanical inputs refresh on a regular cadence. The upside and downside narratives should be re-examined quarterly — not the numbers, but the story. Scenarios age out as the environment shifts, and a scenario with a stale narrative is worse than no scenario at all.

How Aziell runs scenarios

Scenarios in Aziell are forks of the base plan. You clone the plan, change exactly the drivers that correspond to the narrative, and the system computes the full P&L, cash flow, and DSCR impact — plus the enterprise-value delta at the multiple you have calibrated. The three scenarios live side by side in one comparison view. Driver-level deltas are explainable down to the line.

The scenario layer is most useful once the driver model is already in place. If you are earlier in the stack, the driver-based budgeting framework is the right starting point, followed by the 30-minute setup path.