# How to Build Base, Low-Sales and High-Cost Business Scenarios

Build business scenarios by changing a small set of related assumptions and recalculating the full operating and cash forecast. Keep a base case representing the current expected path, a low-sales case reflecting credible demand weakness and a high-cost case reflecting plausible input pressure. Add a combined case where those events could occur together.

Scenarios are conditional stories, not predictions with automatic probabilities. Their purpose is to reveal consequences and prepare actions. A useful case explains why its assumptions move together and what management can do before the adverse outcome becomes unavoidable.

## Define one consistent starting model

Consider an illustrative Vadodara industrial-cleaning-products maker planning one month. The base case assumes 1,000 units at ₹1,500 each, variable cost of ₹900 per unit and ₹4,00,000 fixed operating costs. Contribution is ₹6,00,000 and operating profit ₹2,00,000.

The model keeps quantities, selling price, cost rates, capacity and payment timing in separate input cells. That makes each scenario easier to understand than entering different total revenue and expense amounts without explaining the drivers.

ICAI's budgeting and marginal-costing materials connect activity, costs and operating results. The cases below are original management illustrations using those relationships. Their particular percentages are assumptions chosen for this business example, not industry standards.

## Create distinct cases with an explanation

The low-sales case assumes demand falls 20% to 800 units while price and unit variable cost remain unchanged. Fixed commitments continue for the month. This tests the effect of losing volume without pretending that every expense falls proportionately.

The high-cost case retains 1,000 units but raises variable cost to ₹1,050 and fixed costs to ₹4,40,000. The reasons might be supplier revisions and a confirmed premises or support increase. The actual forecast should attach evidence to those changes.

The combined case uses 800 units with the higher cost assumptions. It is useful if demand weakness and input pressure could occur together. Do not assume separate adverse cases are mutually exclusive without a business reason.

## Compare the operating results

| Illustrative monthly measure | Base | Low sales | High cost | Combined |
|---|---:|---:|---:|---:|
| Units | 1,000 | 800 | 1,000 | 800 |
| Net price | ₹1,500 | ₹1,500 | ₹1,500 | ₹1,500 |
| Variable cost per unit | ₹900 | ₹900 | ₹1,050 | ₹1,050 |
| Total contribution | ₹6,00,000 | ₹4,80,000 | ₹4,50,000 | ₹3,60,000 |
| Fixed costs | ₹4,00,000 | ₹4,00,000 | ₹4,40,000 | ₹4,40,000 |
| Operating result | ₹2,00,000 | ₹80,000 | ₹10,000 | ₹80,000 loss |

The high-cost case is close to break-even despite unchanged revenue. The combined case shows a loss. These outcomes direct attention to contribution and committed costs, rather than a headline sales target alone.

Keep the output boundary clear. Interest, tax or other excluded items need separate modelling before describing the result as final profit. Use transaction-appropriate inputs rather than adding an assumed universal rate.

## Carry each case into cash

Translate sales into receipts and purchases into payments using each case's assumptions. Lower demand may leave existing stock and committed purchase orders in place. Cash payments therefore may not decline as quickly as the operating cost of goods sold.

A further ₹1,00,000 collection delay reduces cash available during the period by ₹1,00,000, even if the underlying sale and operating profit remain unchanged on the chosen accounting basis. Show the delayed receipt later instead of deleting it permanently unless noncollection is the scenario being tested.

Include equipment, financing and owner-related cash commitments that sit outside the operating calculation. Compare the lowest balance with the operating minimum in each case, not merely month-end profit.

## Make the cases internally coherent

A price increase may reduce volume; an input shortage may both raise cost and delay dispatch. Where those relationships are material, model them explicitly. Do not combine the lowest purchase price, highest sales price and maximum volume merely to create an attractive base case.

Separate immediate effects from changes that require time. A monthly lease payment may remain fixed in the short term, while a longer-term scenario can include relocation or resizing. Use the horizon management is actually deciding about.

Avoid adding a general contingency on top of every adverse driver without explaining the overlap. The purpose is a traceable alternative, not an accumulation of hidden cushions.

## Attach practical triggers and actions

The maker could review pricing when confirmed unit cost rises above a specified level and pause discretionary hiring if accepted orders fall below a defined volume. The exact trigger should reflect response time, customer commitments and the cost of waiting.

Model the action separately. A proposed price change is not a confirmed saving, and reduced purchasing must remain compatible with expected demand and valid supplier commitments. Name the person responsible for obtaining the evidence and implementing the response.

## Keep action timing inside the case

A planned cost reduction should begin only when it can realistically take effect. If an agreement needs notice or a process change needs training, the first month may retain most of the original cost. Model the implementation date and any transition expenditure before relying on the later saving.

## Revisit the scenarios as evidence changes

Compare actual orders, supplier quotes and collections with the trigger assumptions during the month. Update the expected case without erasing the original scenario versions. Review whether the prepared actions remain feasible.

The value of scenario planning lies in readiness. A compact set of coherent cases can show when margin becomes fragile, how much cash is needed and which decisions should happen first. Finish with actions tied to observable evidence, so the forecast helps management respond before the most difficult case arrives.

## Sources and references

- [ICAI: Budgets and Budgetary Control](https://resource.cdn.icai.org/74758bos60489-cp15.pdf)
- [ICAI: Marginal Costing](https://resource.cdn.icai.org/74757bos60489-cp14.pdf)
- [ICAI: Treasury and Cash Management](https://resource.cdn.icai.org/74782bos60495-cp9u2.pdf)