Author: Taylor Warfield, Former Bain Manager and interviewer

Last Updated: July 15, 2026

 

A revenue decline case interview asks you to find why a company's sales are falling and recommend how to fix it, which you do by breaking revenue into price and volume, segmenting to locate the drop, and tying it to a root cause. This guide walks you through the framework, a full worked example with the math, the most common causes, and the tips that separate strong candidates from the rest.

 

Before reading on:

 

Most candidates struggle to land interviews and even fewer turn them into offers. Watch my free training to learn how to triple your chances of landing interviews and increase your chances of receiving an offer by 8x.

 

👉 Watch for free

 

Key Takeaways

 

A revenue decline case is solved by diagnosing where revenue fell across price and volume before recommending any fix.

 

• Revenue equals price multiplied by volume, so every decline traces back to one of those two levers or a shift in product mix

 

• Confirm the size, timing, and scope of the drop before you build any structure

 

• Segment by product, customer, and geography to pinpoint exactly where revenue is leaking

 

• A volume drop and a revenue drop are not the same thing, since a price increase can hide falling units

 

• Tie your recommendation to the diagnosed driver, not to generic growth ideas

 

What Is a Revenue Decline Case Interview?

 

A revenue decline case interview is a case where a company's total sales have dropped over a set period and you are asked to find the cause and propose a fix. You diagnose it by splitting revenue into price and volume, segmenting to find where the decline sits, and connecting that driver to a real business reason such as churn or new competition.

 

The comparison is usually year over year or quarter over quarter, depending on how the prompt is framed. Revenue measures money coming in from customers, nothing more, which is what makes these cases narrower than they first appear.

 

In my years interviewing candidates at Bain, the ones who stalled almost always skipped the diagnosis and jumped straight to ideas for boosting sales. The whole point of the case is to prove you can isolate the cause first, then act.

 

How Is It Different From a Profitability Case?

 

A revenue decline case looks only at the sales side of the business, while a profitability case interview covers both revenue and costs. This distinction matters because a profit drop can come from falling revenue, rising costs, or both, and analyzing the wrong half wastes time you do not have.

 

The quickest way to fail is to hear "sales are down" and start digging into the cost structure. In a pure revenue case, costs are a distraction unless the interviewer explicitly opens that door.

 

Dimension	Revenue decline case	Profitability case
Core equation	Revenue = Price x Volume	Profit = Revenue - Costs
What you analyze	Price, volume, and product mix	Revenue drivers and cost drivers
Common trap	Drifting into costs	Ignoring which half is the bigger problem
Typical fix	Pricing, retention, or mix levers	Pricing, mix, or cost reduction levers

 

If the prompt mentions profit or margins, treat it as a profitability problem and confirm whether revenue or cost is the larger driver. If it mentions only sales or revenue, stay on the revenue side and resist the pull toward cost reduction case interview territory.

 

What Framework Should You Use?

 

The right structure for a revenue decline is a revenue driver tree built from one equation: Revenue equals Price multiplied by Volume. From there you ask whether average price fell, units sold dropped, or the mix of what customers bought shifted toward cheaper items.

 

Avoid pulling a memorized template off the shelf. The strongest answers tailor the tree to the client, which is the same instinct that strong case interview frameworks reward across every case type.

 

There are three drivers you break revenue into:

 

• Price: the average selling price per unit, which falls through discounting, competitive pressure, or lower perceived value

 

• Volume: the number of units or customers, which falls through churn, lost market share, or weaker demand

 

• Mix: the blend of products or segments sold, which drags revenue down when buyers shift toward lower-priced options

 

How you segment volume depends on the business model. A subscription company splits revenue into number of subscribers multiplied by average revenue per subscriber, while a transactional retailer splits it into number of transactions multiplied by average basket size.

 

How Do You Structure Your Approach Step by Step?

 

Approach a revenue decline case as a sequence that moves from the broad question to the specific cause without skipping rungs. Interviewers grade whether your logic is complete and whether you narrow methodically rather than guessing.

 

1. Confirm the decline: pin down how large the drop is, over what period, and across which parts of the business
   
   
2. Split price and volume: ask whether average price or units sold moved, since the fix differs entirely depending on the answer
   
   
3. Segment the decline: break the affected driver down by product, customer type, or geography to find where it concentrates
   
   
4. Find the root cause: explain why that specific driver changed by linking it to the market and the company's own actions
   
   
5. Recommend a fix: prioritize levers that target the diagnosed cause and estimate the impact where the numbers allow

 

The math in steps two and three is where many candidates lose points. If your case interview math is shaky, drilling the price-volume decomposition until it is automatic pays off more than memorizing another framework.

 

What Clarifying Questions Should You Ask First?

 

Ask a tight set of clarifying questions that frame the decline before you structure anything. The goal is to size the problem and rule out the obvious, not to interrogate the interviewer.

 

Good opening questions sound like a consultant, not a checklist. Strong clarifying questions at the start of a case do more to shape your path than any framework you draw later.

 

• How large is the decline, and over what time frame did it happen

 

• Is the drop across the whole business or concentrated in certain products, segments, or regions

 

• Is this a one-time fall or part of a longer trend

 

• What does the client sell, and how does the company make money

 

• What is the objective, since stabilizing revenue and returning to growth call for different plans

 

Worked Example: A Coffee Chain With Falling Revenue

 

Here's an example that shows the full diagnosis with the math attached. The numbers are illustrative and rounded so you can follow the logic, not real figures for any company.

 

Case prompt: A regional coffee chain has seen annual revenue fall from $50 million to $44 million over the past year, a 12% drop. The CEO wants to know why and what to do about it.

 

Start by splitting revenue into price and volume. Let's say last year the chain served 20 million cups at an average price of $2.50, which gives the original $50 million.

 

Interviewer: This year, average price held steady at $2.50. What does that tell you?

 

You: If price is flat at $2.50 and revenue is now $44 million, then volume must have fallen. Dividing $44 million by $2.50 gives 17.6 million cups, down from 20 million, a volume drop of 2.4 million cups or 12%. The entire decline is a volume problem, not a pricing problem.

 

Now segment that volume drop. Suppose the chain has 100 stores split between city-center locations and suburban locations, and the data shows suburban stores held steady while city-center stores lost most of the traffic.

 

You: The decline is concentrated in city-center stores, so I want to understand what changed there. Possible causes include a new competitor nearby, fewer office workers commuting in, or a drop in foot traffic from construction or transit changes.

 

Generating those causes cleanly is its own skill. Practicing brainstorming in case interviews trains you to produce structured, distinct hypotheses instead of a random scatter of guesses.

 

Say the interviewer reveals that a hybrid-work shift cut weekday morning commuters in the city. The root cause is a demand shift, so the fix should target winning back or replacing that lost traffic rather than touching price.

 

You: My recommendation is to recover the lost city-center volume by adding afternoon and weekend promotions to attract non-commuter visits, testing a mobile pre-order channel for the remaining commuters, and reviewing whether two or three of the weakest stores should be relocated. I would size the promotion test first, since it is the cheapest lever to try.

 

That answer works because it traces a clean line from a 12% revenue drop to a volume decline, to a single concentrated location, to a named cause, to a fix that matches the cause. If you want more cases like this to practice on, my case interview course includes full-length cases with worked solutions you can run through in as little as 7 days.

 

What Are the Most Common Causes of a Revenue Decline?

 

The most common causes split into internal causes the company controls and external causes coming from the market. Sorting them this way keeps your hypotheses organized and shows the interviewer you can think in clean buckets.

 

Internal causes	External causes
Price cuts or heavier discounting	A new competitor entering the market
A mix shift toward cheaper products	A rival cutting prices or launching a better product
Product quality or service problems	Falling overall market demand
Stockouts or distribution gaps	Regulation, seasonality, or an economic downturn
Weaker marketing or sales execution	A shift in customer preferences or channel

 

One of the biggest mistakes candidates make is reciting this whole list once they reach the cause stage. The interviewer wants you to pick the two or three causes the data actually supports and test those, not to prove you can name every possibility.

 

What Recovery Solutions Should You Recommend?

 

Your recommendation should attack the diagnosed driver directly and nothing else. If price caused the decline you fix pricing, and if volume caused it you fix retention, acquisition, or distribution.

 

Match the lever to the cause using the pairings below:

 

• Price-driven decline: tighten discount policy, introduce segment-specific pricing, or reposition the product to justify the price, the same logic tested in a pricing case interview

 

• Volume-driven decline from churn: launch retention programs, improve the product, or fix the service gap pushing customers away

 

• Volume-driven decline from acquisition: increase marketing, open new channels, or expand into new geographies

 

• Mix-driven decline: steer customers toward higher-value products through bundling, merchandising, or sales incentives

 

Always prioritize. State which lever to try first, why it beats the alternatives, and what tradeoff it carries, such as implementation cost or time to take effect.

 

Why a Volume Drop Is Not Always a Revenue Drop

 

The single most useful lesson in these cases is that price and volume can move in opposite directions, so you must never assume a customer loss equals a revenue loss. A real example makes this concrete.

 

In the first quarter of 2022, Netflix lost paid memberships in the United States and Canada for the first time in years, with the region shedding roughly 636,000 paid subscribers according to the company's SEC filing. Many people assumed the region's revenue must have fallen with it.

 

It did not. Per the same Netflix quarterly filing, United States and Canada streaming revenue actually rose from about $3.17 billion to roughly $3.35 billion year over year, because price increases more than offset the lost subscribers.

 

That is the whole reason you decompose revenue before drawing conclusions. A case prompt that says "we lost customers" is not the same as "revenue fell," and a candidate who proves they understand the difference stands out immediately.

 

Tips to Ace a Revenue Decline Case Interview

 

Tip #1: Confirm the decline before you structure anything

 

Spend the first minute pinning down the size, period, and scope of the drop. Building a structure before you know whether revenue fell 3% or 30% wastes your best thinking on the wrong scale of problem.

 

Tip #2: Separate price from volume immediately

 

The first analytical move in every revenue case is splitting the decline into price and volume. This single step tells you which half of the business to investigate and saves you from analyzing the wrong driver for ten minutes.

 

Tip #3: Segment until the decline has one address

 

Keep cutting the data by product, customer, and region until the decline points to a specific place. A drop that lives in one segment is far easier to explain and fix than a vague companywide average.

 

Tip #4: Tailor the tree to the business model

 

A subscription business, a retailer, and a B2B manufacturer each break volume down differently. Renaming your buckets to fit the client signals real business sense rather than a memorized template.

 

Tip #5: Connect the data to a real-world cause

 

Finding that volume fell is only half the job, since the interviewer wants to know why. Link the number to a believable mechanism such as a new competitor, a price war, or a demand shift, and back it with the evidence in front of you.

 

Tip #6: Make your recommendation specific and prioritized

 

Close with a clear recommendation, two or three supporting reasons, and a first action to take. Vague advice to "grow sales" signals you never really diagnosed the problem.

 

Tip #7: Practice cases out loud, not just on paper

 

Reading solutions is not the same as performing under pressure. Running live reps with a partner or coach is how the price-volume split becomes automatic, which is the difference I saw most often between candidates who passed and those who did not.

 

A revenue decline case interview comes down to one discipline: diagnose where revenue fell across price and volume before you recommend a single fix. Master that sequence, practice it out loud until it is second nature, and you will handle any sales-decline prompt a firm throws at you.

 

Frequently Asked Questions

 

How do you solve a revenue decline case interview?

 

Solve a revenue decline case interview by first confirming the size and scope of the drop, then breaking revenue into price and volume, segmenting by product, customer, or geography to find where the decline is concentrated, identifying the root cause behind that driver, and recommending targeted fixes. Diagnose before you prescribe.

 

What is the difference between a revenue decline case and a profitability case?

 

A revenue decline case focuses only on the sales side, meaning price, volume, and mix, while a profitability case covers both revenue and costs. A profit drop can come from falling revenue, rising costs, or both, so a profitability case is broader. Confirm which one you are solving before you build your structure.

 

What framework should you use for a revenue decline case?

 

Use a revenue driver tree built from the equation Revenue equals Price multiplied by Volume. Break the decline into whether average price fell or units sold dropped, then segment by product, customer, or region to isolate the source. Avoid memorized templates and tailor the tree to the client's business model.

 

What are the most common causes of a revenue decline?

 

Common causes include customer churn, new competitors taking share, price cuts or heavier discounting, a shift toward lower-priced products, weaker demand, distribution or stockout problems, and external shocks such as regulation or a downturn. Strong candidates tie a specific cause to the data rather than listing every possibility.

 

How long is a revenue decline case interview?

 

A revenue decline case usually runs 30 to 45 minutes as part of a full interview round. You spend the first few minutes clarifying and structuring, the bulk of the time diagnosing the driver with the data provided, and the final minutes delivering a recommendation. Pacing matters as much as the analysis.

 

Can revenue fall even if a company sells more units?

 

Yes. Revenue can fall while unit volume rises if average price drops, usually through discounting or a mix shift toward cheaper products. The reverse is also true, since revenue can rise while volume falls if price increases offset the lost units. This is exactly why you separate price from volume before drawing conclusions.

 

Everything You Need to Land a Consulting Offer

 

Need help passing your interviews?

• Case Interview Course: Become a top 10% case interview candidate in 7 days while saving yourself 100+ hours
  
  
• Fit Interview Course: Master 98% of consulting fit interview questions in a few hours
  
  
• Interview Coaching: Accelerate your prep with 1-on-1 coaching with Taylor Warfield, former Bain interviewer and best-selling author

 

Need help landing interviews?

• Resume Review & Editing: Craft the perfect resume with unlimited revisions and 24-hour turnaround

 

Need help with everything?

• Consulting Offer Program: Go from zero to offer-ready with a complete system

 

Not sure where to start?

• Free 40-Minute Training: Triple your chances of landing consulting interviews and 8x your chances of passing them