Chapter 16 & Closing

Chapter 16: Defending the Numbers - Financial Q&A, Assumptions, and Credibility Under Pressure

"You don't need to know every number. You need to know why your numbers make sense."

Learning Objectives

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

anticipate the financial questions judges are likely to ask
defend important assumptions without becoming defensive
explain financial calculations clearly and concisely
distinguish between facts, assumptions, estimates, and forecasts
respond when a judge challenges your numbers
acknowledge uncertainty without undermining your recommendation
use your financial model as a resource during Q&A
identify the assumptions that matter most
recover when you discover an error or weakness
maintain credibility when you don't know the answer

Why This Matters

A financial model can look impressive on a slide.

But the real test often comes during Q&A.

A judge may look at your projected revenue and ask:

"Why do you believe you can achieve that?"
"Your NPV seems very sensitive to the discount rate. Why did you use 12%?"
"What happens if adoption is only half of what you're projecting?"
"Where did that number come from?"

At that moment, the judge isn't necessarily testing your ability to perform another calculation. They are testing whether you understand the logic behind the number. This is an important distinction. A team can have an excellent spreadsheet and still lose credibility if they cannot explain it.

Discover Your Mad Skills Principle

Confidence in financial Q&A doesn't come from memorizing numbers. It comes from understanding the assumptions, relationships, and logic behind them.

The Four Types of Numbers

One of the most important distinctions a team can make is understanding what kind of number it is presenting. Not all numbers have the same level of certainty.

Fact: A number provided directly in the case or supported by reliable evidence. Example: Current annual revenue is $250M.
Historical Calculation: A number calculated from known information. Example:
Gross margin declined from 42% to 35%.
Estimate: A number developed using assumptions and reasonable benchmarks. Example: We estimate that 15% of customers would adopt the service.
Forecast: A projected future outcome based on a model. Example: We forecast $12M of incremental revenue in Year 3.

These distinctions matter enormously in Q&A. If a judge asks: "How do you know adoption will be 15%?" The answer should not be: "We know." You don't. You assumed it based on evidence and benchmarks. That is much more credible.

Never Pretend an Assumption Is a Fact

This is one of the fastest ways to lose credibility.

Weak: "Customers will adopt our product at 20%."
Stronger: "We assumed a 20% adoption rate based on the comparable programs we identified."
Even stronger: "Our base case assumes 20% adoption. We chose that assumption based on comparable programs, and our sensitivity analysis shows the recommendation remains value-creating down to approximately 14%."

The third answer does something important. It doesn't just defend the assumption. It demonstrates that the recommendation doesn't depend on one perfect assumption.

The Assumption Hierarchy

Not all assumptions deserve equal attention. Think about your model as a hierarchy.

High Impact

Assumptions that can materially change the recommendation. Examples:

adoption rate
selling price
market share
revenue growth
major capital investment
discount rate
operating margin

Medium Impact

Assumptions that influence the result but are less decisive. Examples:

administrative costs
staffing levels
maintenance costs

Low Impact

Small assumptions that have little effect on the conclusion. Examples:

minor overhead changes
small timing differences
immaterial rounding

Your Q&A preparation should focus heavily on the high-impact assumptions.

The Three Questions Behind Every Financial Number

When preparing for Q&A, ask:

Where did the number come from?
Why is the assumption reasonable?
What happens if we're wrong?

If your team can answer those three questions for every major financial assumption, you will be much more prepared.

The Financial Assumption Map

Before competition, build an assumption map.

Assumption	Value	Source	Impact	Downside
Adoption	20%	Comparable programs	High	Very high
Price	$100	Market benchmark	High	Medium
Variable cost	$35	Industry estimate	High	Medium
Growth	8%	Historical trend	Medium	Medium
Discount rate	12%	Risk assessment	High	High

This doesn't need to appear in your presentation. It is a team preparation tool. It helps identify where the judges are most likely to attack.

Coach's Lens

When I see a team prepare financial analysis, I don't just want to know: "What is your NPV?"

I want to know: "What three assumptions would make your NPV wrong?"

That question changes the team's preparation. They stop memorising outputs. They start understanding the model.

The Most Common Financial Q&A Questions

Judges frequently challenge financial analysis in predictable ways. "Where did that number come from?" Be prepared to identify:

case information
calculation
benchmark
research
assumption
estimate

"Why did you assume that?"

Explain the reasoning. Don't simply repeat the assumption. "What happens if that assumption changes?" Use your sensitivity or scenario analysis.

"Why is your market share realistic?" Connect it to:
- competitors
- capacity
- customer switching
- historical performance
- comparable organizations
- conversion rates
"Why is the investment this large?" Explain the underlying cost drivers.
"Why is the return attractive?" Put the return into context. Compare it to:
- investment size
- alternatives
- cost of capital
- organizational economics
- risk
"Why did you use NPV rather than ROI?" Explain the purpose of the metric. NPV focuses on value creation while incorporating the time value of money.
"Why is your discount rate appropriate?" Explain what risk considerations influenced the rate.
"What if growth is lower?" This is where sensitivity analysis becomes extremely valuable.
"What is your break-even point?" Know it.
"How long until we recover the investment?" Know it.

Don't Fight the Judge

One of the worst reactions to a challenge is defensiveness.

Judge: "I don't think 20% adoption is realistic."
Weak response: "But our research shows 20%." This turns the interaction into an argument.
Better: "That's fair. Twenty percent is our base-case assumption. We also tested 10% and 15%, and the initiative remains value-creating at 15%. Below that level, the economics become significantly less attractive." Now you're having a business conversation.

Acknowledge → Explain → Reframe

A useful Q&A structure is:

Acknowledge: "That's an important risk." --> Explain: "Our base case assumes 20% adoption based on comparable programs." --> Reframe: "However, the recommendation doesn't require 20% adoption to work. Our sensitivity analysis shows positive NPV down to approximately 15%."

This is much stronger than trying to prove that your original assumption is unquestionably correct.

Don't Overdefend Your Assumptions

Sometimes teams spend too much time defending an assumption that doesn't actually matter. Suppose the judge challenges a small cost assumption. Ask yourself: Does changing this assumption materially change the recommendation? If not, say so. For example: "That cost is an estimate, but it has limited impact on the overall result. The more important assumptions are adoption and pricing, which account for most of the sensitivity in our model." That demonstrates judgment.

Know Your Break-Even Points

Every important recommendation should have a point at which it stops working. Examples:

Adoption: "We need approximately 14% adoption to maintain a positive NPV."
Price: "The economics remain viable down to approximately $85 per customer."
Volume: "We need approximately 40,000 annual customers to break even."
Margin: "The initiative remains profitable until margin falls below 22%."

These numbers are extremely useful during Q&A. They convert: "We think this will work." into: "We know what has to be true for this to work."

Break-Even Is More Than a Calculation

Break-even analysis helps identify the critical assumption. Suppose your recommendation requires:

50,000 customers.
And the available market is: 5 million customers.

That may be very achievable.

But suppose it requires: 2 million customers.

Now the recommendation looks much more aggressive. Break-even creates context.

Sensitivity Analysis Is a Q&A Tool

Sensitivity analysis should not simply sit on a slide. Use it during Q&A.

Judge: "What happens if revenue is 20% lower?" You should be able to answer quickly. "At 20% lower revenue, NPV falls from $5.2M to $1.9M, but remains positive." That is powerful. You aren't improvising. You are using analysis you already performed.

Scenario Analysis

Your team should know at least three scenarios:

Downside: What if important assumptions disappoint?
Base Case: What do we reasonably expect?
Upside: What if the recommendation performs exceptionally well?

The goal isn't to make the upside look exciting. The goal is to understand the decision range.

What If the Downside Case Fails?

This is an important question.

Suppose: Base Case NPV = +$5M
but: Downside NPV = -$2M

You shouldn't hide this. Instead, ask: What decision rule would protect the organisation? Perhaps:

phased implementation
pilot first
investment gates
milestone-based funding
adoption targets
monthly monitoring

Financial analysis can therefore influence implementation design.

Financial Analysis Should Influence the Recommendation

Suppose your financial model tells you: The recommendation works only if adoption reaches 15%. That should affect implementation. Your recommendation may become: Launch a six-month pilot and scale only if adoption exceeds 15%. Now the financial analysis isn't just supporting the recommendation. It is shaping the recommendation.

The "What Would Change Your Mind?" Question

Prepare for this question: "What would cause you not to pursue this recommendation?" A strong answer demonstrates decision discipline. For example: "If pilot adoption remains below 15% after six months, we would not proceed to full rollout." This is much more credible than: "We believe strongly in the recommendation."

What If the Judge Finds an Error?

This is one of the most stressful situations. Suppose a judge says: "I think your NPV calculation is wrong."

Don't panic.
Don't immediately argue.

First understand the question. "Can you clarify which assumption or calculation you're referring to?" If you identify an error: "You're right. We used the wrong timing assumption in that calculation. That would reduce the NPV. The recommendation would still be viable, but our slide should have reflected the corrected figure." That response demonstrates integrity.

Never Manufacture an Answer

One of the worst things you can do in Q&A is invent a number. If you don't know:

"I don't have that figure in front of me, but the relationship we would expect is..."
"We didn't model that specific scenario. What we did test was..."
"That's outside the assumptions we used, so I wouldn't want to give you a number that we haven't validated."

This is far better than guessing.

The Three Levels of Financial Confidence

Think of financial answers in three levels.

Level 1: Know the Number: "Our NPV is $5.2M."
- Necessary. But insufficient.
Level 2: Know the Logic: "The NPV is $5.2M because we generate approximately $1.5M in annual incremental cash flow against a $3M initial investment."
- Better.
Level 3: Know the Boundary: "The NPV is $5.2M in our base case, but it remains positive down to approximately 15% adoption."
- This demonstrates true financial understanding.

Level 3 is the goal.

Build a Financial Q&A Sheet

Before competition, create a one-page financial Q&A sheet. Include:

Core Numbers

investment
revenue
costs
profit impact
ROI
NPV
IRR
payback
break-even

Major Assumptions

price
volume
adoption
growth
margin
discount rate

Sources

case data
industry benchmark
research
team estimate

Critical Sensitivities

biggest upside driver
biggest downside driver
break-even point

Potential Questions

Write the five hardest questions you expect judges to ask.
Then answer them.

The 30-Second Financial Defence

Your team should be able to explain the entire financial case in approximately 30 seconds.

For example: "The initiative requires a $3M initial investment and generates approximately $1.5M in annual incremental cash flow. That produces a $5.2M NPV and 28% IRR in our base case. Our key assumption is 20% adoption, but the recommendation remains value-creating down to approximately 15%. That's why we recommend a phased rollout with adoption milestones before full investment." That's a financial story. Not a spreadsheet.

The 10-Second Version

You should also be able to summarise it in one sentence: "A $3M investment creates $5.2M of NPV, and remains viable under reasonable downside assumptions." If you can communicate the economics that simply, you understand them.

Mad Skills Drill

Attack the Model

Choose the five assumptions that matter most. Have one team member act as the judge. The judge should challenge each assumption:

"Why?"
"What evidence?"
"What if you're wrong?"
"What happens at half that value?"
"Why should management accept that risk?"

The presenter cannot look at the model. Afterwards, compare the answers against the actual model. Repeat until the answers become natural.

The Financial Hot Seat

One team member sits in the "hot seat." The coach or another team member asks rapid-fire questions:

What's your investment?
What's your NPV?
What's your IRR?
What's your ROI?
What's your payback?
What's your break-even?
What's your biggest assumption?
What's your biggest risk?
What happens if revenue falls 20%?
What happens if costs rise 20%?
What assumption matters most?
Why is your discount rate reasonable?
Why is this better than the alternative?

The goal isn't speed alone. The goal is calm, accurate, concise answers.

Coach's Lens

Watch for three behaviours.

The Calculator: The student starts calculating everything during Q&A.
The Defender: The student argues with every challenge.
The Storyteller: The student explains the logic, acknowledges uncertainty, and connects the answer back to the recommendation.

You want the third.

Common Mistakes

Memorising Outputs. Students memorise NPV but don't understand the assumptions.
Treating Estimates as Facts. This creates credibility problems.
Getting Defensive. A challenge isn't necessarily an attack.
Guessing. An incorrect confident answer is worse than an honest limitation.
Ignoring Sensitivity. If your recommendation is highly sensitive, you need to understand why.
Knowing the Model but Not the Story. The numbers need to connect to the decision.
Overexplaining. Answer the question first.

Then provide supporting detail if necessary.

The Answer-First Principle

When a judge asks a financial question: Answer first, then explain. For example: "Yes. The project remains profitable at that adoption rate. At 15% adoption, NPV is approximately $800,000. The reason is that our fixed costs remain largely unchanged while the variable costs scale with volume." Don't make the judge wait through 60 seconds of explanation before hearing the answer.

The "Because" Test

A powerful way to improve financial answers is to finish every answer with: "...because..."

Judge: "Why is your revenue forecast realistic?"
Answer: "Because our forecast is based on 20% adoption of the serviceable market, which is consistent with the comparable programs we identified."
Judge: "Why is the investment worthwhile?"
Answer: "Because it produces a positive NPV and remains value-creating under our downside scenario."

The "because" forces you to connect the answer to evidence.

Chapter Summary

Financial Q&A is not about defending every decimal place in your model. It is about demonstrating that you understand:

what you know
what you assumed
why you assumed it
what matters most
what happens if you're wrong
why the decision still makes sense

The strongest teams don't pretend uncertainty doesn't exist.

They understand it.
They quantify it.
They manage it.
And they explain it confidently.

Key Takeaways

✓ Know the story behind every major financial number.

✓ Distinguish facts from estimates and forecasts.

✓ Identify your highest-impact assumptions.

✓ Prepare for "Where did that number come from?"

✓ Know your break-even points.

✓ Use sensitivity analysis as a Q&A resource.

✓ Don't become defensive when challenged.

✓ Acknowledge uncertainty rather than hiding it.

✓ Never invent a number you don't know.

✓ Answer the question first, then explain.

✓ Connect financial answers back to the decision.

✓ Know what would cause you to change your recommendation.

✓ Prepare a financial Q&A sheet before competition.

✓ Practice defending assumptions, not just memorising outputs.

The goal of financial Q&A isn't to prove that your forecast is perfect. It's to prove that your decision is thoughtful, informed, and resilient.

Part V Closing

The financial work in a case should ultimately answer one question:

Does this decision create enough value to justify taking the risk?

You began this section by understanding the organisation's financial position.

You learned how to:

analyse financial statements
compare performance
estimate markets
build budgets
estimate financial impacts
evaluate investments
calculate ROI
calculate NPV
calculate IRR
compare alternatives
test sensitivity
build scenarios
translate financial analysis into presentations
defend your assumptions

But financial analysis is not the recommendation. It is evidence. The strongest case teams use finance to strengthen the strategic story rather than allowing finance to become a separate technical exercise. The progression is:

Understand --> Estimate --> Model --> Evaluate --> Stress-Test --> Communicate --> Defend --> Decide

That is financial thinking in a case competition. And that is the real skill.

Don't just calculate the answer. Understand what the numbers are telling you—and use them to make a better decision.

Financial Analysis & Excel Mastery Checklist

Situational Financial Analysis

Comparative Analysis

Market Sizing - If market sizing is relevant:

Estimation

Have we estimated important numbers before building a detailed model?
Have we clearly stated our assumptions?
Have we used reasonable round numbers where appropriate?
Have we sanity-checked our calculations?
Do our estimates make sense relative to the size of the organisation?
Have we used estimation to identify potential problems early?
Can we explain the logic behind our estimate?

Budget

Financial Impact

Have we modelled the financial impact of the recommendation?
Have we identified the major revenue drivers?
Have we identified the major cost drivers?
Have we distinguished fixed and variable costs where relevant?
Have we considered incremental versus existing revenue and costs?
Have we calculated the resulting profit impact?
Have we considered cash flow where appropriate?
Does the financial impact appear material to the decision-maker?
Can we explain the financial story without requiring the judges to read the spreadsheet?

ROI - If ROI is relevant:

Have we clearly defined the investment?
Have we identified the expected return?
Have we calculated ROI correctly?
Have we distinguished annual ROI from cumulative ROI where appropriate?
Have we compared ROI across alternatives when useful?
Have we recognised that ROI does not account for the time value of money?
Are we using ROI because it answers the decision question—not simply because it is easy to calculate?

NPV - If NPV is relevant:

Have we identified the initial investment?
Is the initial investment represented as a negative cash flow?
Have we identified the appropriate discount rate?
Are future cash flows clearly identified?
Have we considered the timing of cash flows?
Have we calculated NPV correctly?
Do we understand whether the result creates or destroys value?
Have we avoided confusing present value of future cash flows with NPV?
If using Excel, have we used the appropriate NPV/XNPV function for the cash-flow structure?

IRR - If IRR is relevant:

Have we included the initial investment as a negative cash flow?
Are the cash flows in the correct sequence?
Have we calculated IRR correctly?
Does the IRR make economic sense?
Have we considered whether the timing of cash flows makes standard IRR appropriate?
If actual dates matter, have we considered XIRR?
Have we avoided relying on IRR alone when comparing mutually exclusive investments?
If IRR and NPV conflict, have we given appropriate weight to NPV?

Comparing Investment Alternatives

Valuation - If valuation is relevant:

Sensitivity Analysis

Risk and Robustness

Excel Model Quality

Excel Presentation Quality

Financial Storytelling

Does every major financial number answer a business question?
Have we moved beyond "what happened?" to "why does it matter?"
Can we explain the financial impact in plain language?
Does the financial analysis support the strategic recommendation?
Have we connected financial results to the organisation's objectives?
Can we explain the most important number in one sentence?
Can we explain the biggest assumption in one sentence?
Can we explain the biggest risk in one sentence?

Recommendation Test - Before finalising the recommendation, ask:

Can we state the recommendation in one sentence?
Can we explain the investment clearly?
Can we quantify the expected impact?
Do we have evidence it will work?
Have we identified our critical assumptions?
Have we tested the downside?
Have we compared all the alternatives?
Have we justified the timing?

The CFO Test - Can you answer:

Final Financial Readiness Check

Numbers don't win cases. Numbers that strengthen a decision do.

Looking Ahead

With the financial foundation complete, your challenge is to bring the entire case together.

The strategy.
The analysis.
The alternatives.
The recommendation.
The financial case.
The implementation.
And ultimately, the story you tell the judges.

Because winning a case is not about having the most analysis. It is about turning analysis into a decision that people believe in.

Discover Your Mad Skills

Don't show me your spreadsheet.

Show me what you discovered.

Show me why it matters.

Show me what you recommend.

And show me why the numbers give us confidence to act.

That is how you turn numbers into insights.

Chapter 16 & Closing

Chapter 16: Defending the Numbers - Financial Q&A, Assumptions, and Credibility Under Pressure

Learning Objectives

Why This Matters

Discover Your Mad Skills Principle

The Four Types of Numbers

Never Pretend an Assumption Is a Fact

The Assumption Hierarchy

High Impact

Medium Impact

Low Impact

The Three Questions Behind Every Financial Number

The Financial Assumption Map

Coach's Lens

The Most Common Financial Q&A Questions

"Why did you assume that?"

Don't Fight the Judge

Acknowledge → Explain → Reframe

Don't Overdefend Your Assumptions

Know Your Break-Even Points

Break-Even Is More Than a Calculation

Sensitivity Analysis Is a Q&A Tool

Scenario Analysis

What If the Downside Case Fails?

Financial Analysis Should Influence the Recommendation

The "What Would Change Your Mind?" Question

What If the Judge Finds an Error?

Never Manufacture an Answer

The Three Levels of Financial Confidence

Build a Financial Q&A Sheet

The 30-Second Financial Defence

The 10-Second Version

Mad Skills Drill

Attack the Model

The Financial Hot Seat

Coach's Lens

Common Mistakes

The Answer-First Principle

The "Because" Test

Chapter Summary

Key Takeaways

Part V Closing

Financial Analysis & Excel Mastery Checklist

Looking Ahead

Discover Your Mad Skills

DISCOVER YOUR MAD SKILLS

One Case at a Time. One Skill at a Time. One Podium at a Time.