Scenario Planning for Services Firms: Beyond the Best Case Spreadsheet

Every services firm's forecast is wrong. That is not a criticism, it is the structure of the business. Pipeline slips, deals expand or contract at signature, and one large client's renewal decision moves the whole quarter. A point-estimate forecast either underplans and scrambles or overplans and ends the quarter with a bench.

Scenario planning is not a way to be right more often. It is a way to be prepared for more of what happens. Done well, it takes about two hours a week and shapes almost every important staffing decision.

What is scenario planning at a services firm?

Scenario planning is running three parallel views of the next 12 weeks: a base case, an upside case, and a downside case. Each is a full staffing plan and a full revenue forecast, built from the same underlying capacity data, differing only in which pipeline assumptions and risk assumptions apply.

The three views answer three different questions:

• Base case. What does the quarter look like if signed pipeline closes as expected and no client churns unexpectedly?
• Upside case. What does the quarter look like if the top three weighted pipeline deals all land in the current quarter?
• Downside case. What does the quarter look like if the single largest at-risk account churns or delays?

The scenarios are not equally likely. They are meant to bracket the space of realistic outcomes.

How do you build the base case?

The base case is the starting point. Everything else is a perturbation of it.

1. Start from signed pipeline. Only revenue you have paper on. Do not include verbal commitments or letters of intent.
2. Add resource plan. Every allocation for every person for the next 12 weeks, using your standard weekly percentage cadence.
3. Apply target utilization. Any capacity above the role's target is over, below is bench. Do not smooth.
4. Multiply into forecast. Weekly allocations times bill rates gives weekly billable revenue.
5. Note the gaps. Any bench in the base case is bench that already exists, not a hypothetical.

The base case usually shows a modest gap under target somewhere between weeks 8 and 12, because that is where signed pipeline runs thin. That gap is the starting point for the other two scenarios.

What does the upside case actually look like?

Not "if everything goes well." That framing is useless. The upside case is specifically named.

• Pick the top three weighted opportunities. Highest expected value in the pipeline that could land inside the 12-week window.
• Assume they close on their earliest reasonable start date. Not the latest, not the average. The earliest.
• Layer their staffing needs onto the base case. Same weekly resolution, same bill rates, same skills requirements.

Now look at the resulting grid. Three questions to answer:

• Do we have the people? If not, which roles are short, and by how much.
• Are the people we have in the right places? Overlapping timelines, skill matches, geography.
• Can we accept all three? If two of them land the same week, is the delivery capacity actually there.

The upside case is where you find out whether "good news" is actually deliverable. Firms that skip this exercise end up either turning down deals they could have taken or accepting deals they cannot staff.

How do you construct a credible downside case?

The downside case is where most firms get soft, because it is uncomfortable. Force specificity.

• Pick the single largest at-risk revenue. Usually the largest account whose renewal is in the current or next quarter, or the largest engagement with a client showing distress signals.
• Assume it churns or delays by a full quarter. Not "reduces scope by 20%." Full loss for the modeling period.
• Remove the associated staffing. Every allocation to that engagement drops. That freed capacity is now bench.
• Model redeployment. Where can that capacity go, and how quickly. Anything unallocated after two weeks is measured bench in this scenario.

The downside case shows two things: the actual revenue exposure, and the redeployment friction. Both matter. Firms often discover their exposure is smaller than they feared but their redeployment friction is larger.

What questions do the three scenarios together answer?

The comparison is where the value is. Run it explicitly.

If your scenarios do not answer these questions cleanly, they are not specific enough. Add named inputs until they are.

How do you avoid scenario planning becoming wishful thinking?

Two disciplines keep it honest.

• Named inputs, not directional adjectives. The upside case is "if ACME and BigCo both close in September." Not "if sales has a strong quarter."
• Weekly reconciliation with reality. Each week, the assumed inputs either resolve or move. When they resolve, the scenario collapses toward or away from the base case. The moving pieces should be explicit in the review.

The point of scenarios is not to be right about the future. It is to make the assumptions visible so that when the future arrives you know which scenario matches, and you know what actions were already teed up for that outcome.

How does scenario planning connect to the hiring plan?

The hiring plan is the most important decision that scenarios inform. The rule is simple.

• Hire when the role is short in both the base and upside cases. This means demand is real without needing the upside to land.
• Hold when the role is short in the upside case only. This is the "hire on close" role, where the trigger is the deal landing.
• Do not hire when the role is short in the downside case only. That is bench-in-waiting.

Firms that hire only from the base case end up scrambling when the upside lands. Firms that hire from the upside case as their default end up over-hired if the upside does not land. The rule above splits the difference by requiring conviction across both cases.

What does a weekly scenario review look like?

Ninety minutes, biweekly for most firms, weekly during turbulent quarters.

• Attendees. Head of ops or FP&A lead, resource manager, head of delivery, sales lead.
• Agenda. Review of base case actuals against plan, upside case pipeline movement, downside case risk register.
• Output. Any changed staffing decisions, any hiring plan changes, any client conversations required. Each with a named owner and a deadline.

If the meeting runs longer than 90 minutes, the scenarios are too complex. Simplify by reducing the number of named inputs, not by cutting the meeting short.

What actually matters

Scenario planning at services firms is not about precision. It is about seeing the shape of the range and knowing which single decisions move the number most. Run three cases, anchor them to named inputs, review them biweekly, and let the hiring plan follow the intersections. The forecast will still be wrong. But the firm will be prepared for more of the ways it can be wrong, which is the entire point of the exercise.