Chapter 6: Financial Estimation

Chapter 6: Financial Estimation - Making Smart Assumptions Under Pressure

Video: Estimation in Case Finances: Quick Market Sizing, Budgeting & Sanity Checks

Learning Objectives

By the end of this chapter, you should be able to:

• understand the role of estimation in case-solving

• develop reasonable assumptions when data is limited

• estimate markets, revenues, costs, and operational capacity

• use estimation to test the feasibility of recommendations

• communicate assumptions with confidence

• recognise the difference between precision and credibility

Why This Matters

Business cases are intentionally incomplete. You are rarely given every number you need.

• Judges know this.
• Executives know this.
• Consultants know this.

One of the defining characteristics of effective decision-makers is the ability to make informed estimates when perfect information is unavailable. Case competitors face the same challenge. Should the company open twenty stores?

• How much will implementation cost?
• How many customers will adopt the new product?
• How much additional revenue could be generated?

Very few cases provide these answers directly. Instead, they provide clues. Your job is to develop reasonable assumptions, perform logical calculations, and communicate your thinking clearly. Remember:

An estimate supported by sound reasoning is far more valuable than a precise number built on unrealistic assumptions.

Estimation Is Executive Thinking

Executives make decisions every day with incomplete information. Consultants rarely begin with detailed spreadsheets. They begin with rough calculations. They ask: "Does this recommendation even make sense?" Before spending an hour building financial models, successful teams perform quick "back-of-the-envelope" estimates. These early calculations often prevent major mistakes later.

The Estimation Process

Good estimation follows a simple process.

Start with the question. → Identify the key drivers.→ Make reasonable assumptions. → Calculate using simple numbers. → Test whether the answer is realistic. → Refine if necessary.

Notice that estimation is iterative. The first estimate is rarely the final estimate.

Step One - Define the Question

Every estimate begins with a clear objective. Examples include:

• How many customers exist?

• What is the market size?

• How much will implementation cost?

• How many employees are required?

• How much inventory is needed?

• What revenue could realistically be generated?

A poorly defined question almost always produces a poor estimate.

Step Two - Break Large Problems into Smaller Pieces

Large numbers are intimidating. Smaller numbers are manageable. Suppose you want to estimate daily railway ticket sales in China. Rather than guessing four million tickets per day, break the problem into logical steps. Ask:

• What is the population?

• How many people regularly travel?

• How often do they travel?

• How many tickets does each trip require?

Multiply the assumptions together. Large estimates become surprisingly manageable when divided into smaller questions.

Example: Estimating Railway Ticket Sales

Suppose:

• Population = 1.4 billion
• Approximately 40% travel regularly by rail
• Average traveller makes two return trips per year
• Each return trip requires two tickets.

The calculation becomes:

1.4 billion × 40% × 4 tickets annually = 2.24 billion tickets annually Divide by 365. Approximately 6.1 million tickets per day.

Will this number be exact? No. Is it logical? Yes. That is the objective.

Step Three - State Your Assumptions Clearly

Judges are remarkably forgiving when assumptions are transparent. Instead of saying, "Our revenue will increase by 18%." Explain: "We estimate 18% growth based on historical industry growth of approximately 12%, combined with projected customer acquisition from our new distribution strategy."

Assumptions should always answer the question: Why do we believe this number?

Step Four - Use Round Numbers

Precision often creates the illusion of accuracy. Early estimates should be simple.

• Instead of: $4,987,342
• Estimate: $5 million.
• Instead of: 8.37%
• Estimate: 8%.

Simple numbers are easier to explain and much easier to adjust later.

Estimating Revenue

Revenue estimation usually follows the same structure.

• Revenue = Customers × Purchase Frequency × Average Selling Price
• For example: 10,000 customers × 3 purchases annually × $120 average sale = $3.6 million annual revenue

This simple framework works for almost every industry.

Estimating Costs

Cost estimation follows a similar approach. Separate costs into categories.

One-time costs

• equipment

• software

• implementation

• consulting

Ongoing costs

• salaries

• maintenance

• marketing

• administration

Breaking costs apart improves credibility. It also prepares the team for budgeting in the next chapter.

Diagnosing Problems Through Estimation

Estimation is not only used for forecasting. It can also identify underlying business problems. Imagine a hardware retailer whose profits suddenly decline. Rather than assuming costs increased, estimate the components of profit.

• Profit = Revenue − Costs
• Revenue = Price × Quantity
• Costs = Fixed Costs + Variable Costs

Now ask: What changed?

• Price?
• Sales volume?
• Product mix?
• Operating costs?

This structured thinking quickly narrows the possible explanations. Often, the issue is not declining sales but a shift toward lower-margin products. Estimation helps uncover that insight.

Reality Checks

Every estimate deserves a reality check. Ask:

• Does this recommendation fit the organisation's size?
• Would operations support this level of growth?
• Does this estimate exceed industry norms?
• Would an investor believe these assumptions?

If the answer is "probably not," revisit the assumptions.

Discover Your MAD Skills Principle

Great estimators are not trying to be exactly right. They are trying to avoid being obviously wrong.

Business decisions rarely require perfect numbers. They require reasonable confidence.

Coach's Lens

One of the biggest mistakes I see is teams hiding their assumptions. They present the final number. Experienced judges immediately ask: "Where did that come from?" Instead, explain your assumptions before presenting the calculation. Transparency builds credibility.

Deciphering Cases

Cases are designed to reward logical reasoning. Missing information is rarely an obstacle. It is an invitation to think. Successful competitors learn to separate facts from assumptions. 

• Facts come from the case.
• Assumptions fill the gaps.

Strong recommendations clearly distinguish between the two.

Common Mistakes

Avoid these common errors:

• guessing without explaining assumptions

• using unrealistic growth rates

• confusing precision with accuracy

• ignoring operational capacity

• forgetting to test the estimate

• presenting unsupported numbers

• assuming judges will accept unexplained calculations

MAD Skills Drill

Choose a local business. Estimate:

• annual customers

• annual revenue

• staffing requirements

• operating costs

Write down every assumption. Now ask yourself: Which assumptions have the greatest impact on the result? Those assumptions deserve the greatest attention during your presentation.

Chapter Summary

Financial estimation is one of the most valuable skills in business case competitions. It allows competitors to evaluate opportunities, test recommendations, and build credible financial arguments even when information is incomplete. Successful estimators are not rewarded because their numbers are perfect. They are rewarded because their reasoning is sound.

Key Takeaways

✓ Estimation is a structured thinking process, not educated guessing.

✓ Break large problems into smaller, manageable components.

✓ Clearly communicate assumptions.

✓ Use round numbers during early analysis.

✓ Test every estimate against operational reality.

✓ Logical reasoning is more valuable than false precision.

Looking Ahead

Estimating the opportunity tells us what could happen. The next step is determining what it will cost. In the next chapter, we will build realistic implementation budgets that connect strategic recommendations to financial feasibility, ensuring every recommendation is supported by a credible investment plan.