Skip to content

A Revenue Decline Has Several Causes. What Should the Pitch Explain?

Business

A Revenue Decline Has Several Causes. What Should the Pitch Explain?

Two decks can describe the same quarter and name different culprits. One says pricing broke: average selling price fell, and that was the story. The other says volume broke: units dropped, and pricing was a footnote. Both bridges add up. Both totals tie to the ledger. Neither deck has told you why the business changed.

Neither is lying, which is the uncomfortable part. Explaining how a total moved is arithmetic plus a convention. Explaining why the business moved is a claim about the world, and it needs evidence the arithmetic cannot supply. A deck has to do both, in that order, with the seam between them visible.

The sequence that survives scrutiny is short. Confirm the two periods measure the same revenue. Reconcile the contributions the records can actually support. Then explain drivers only as far as the evidence reaches, and label the rest as what it is. Price, volume, mix and timing can move together without resolving into any single convenient story. A bridge can make the numbers foot while leaving the reason customers behaved differently entirely unresolved — and that gap is what a skeptical reader is standing in.

Confirm the two periods measure the same revenue

Attribution is a second-order problem. Comparability is first.

Before anyone argues about drivers, establish four things with whoever owns the revenue number: the definition, the two observation periods, which activities are inside that definition, and which source records the deck will cite. If the deck's revenue line excludes freight and the weekly operations report does not, the two trends you are comparing are not the same trend. If a business line was reclassified mid-year, the "decline" may be partly an accounting boundary moving rather than customers moving. If the comparison periods differ in length — a 53-week year against a 52-week one — part of the change is calendar, and calling it a driver mislabels a measurement artifact as a business event.

Recognition rules deserve the same care. Revenue can arrive in a different period than the activity that produced it: work delivered late in one quarter and billed in the next, a contract signed in December and recognized in January. Whether that matters depends on what the deck is trying to explain. For a trend, a shift across a period boundary changes the shape of both periods. For a total-year comparison, it may wash out.

This is not stage-setting to be rushed. If the definitions are incompatible, you cannot build a compelling explanation on top of them; you can only build a persuasive one, which is worse. Fix the prerequisite first, in writing, with a name attached to it.

Reconcile the change, then say which convention you used

Once the periods are comparable, identify the components the records can support and make their movements reconcile to the total.

Here is a deliberately simple invented case to work with — one product, two periods, abstract revenue units. The numbers are an arithmetic illustration, not company data:

  • Prior period: 100 units at 10 each → 1,000
  • Current period: 80 units at 9 each → 720
  • Total change: −280, a 28% decline

Two things moved: quantity and price. There is no single way to split their contributions, because each one is measured while holding the other fixed — and you have to decide which one gets held.

Convention Volume effect Price effect Total
Volume first (volume at prior price, price at current volume) (80 − 100) × 10 = −200 (9 − 10) × 80 = −80 −280
Price first (price at prior volume, volume at current price) (80 − 100) × 9 = −180 (9 − 10) × 100 = −100 −280
Midpoint (each effect on the average of the two) (80 − 100) × 9.5 = −190 (9 − 10) × 90 = −90 −280

All three foot to the same −280. The price row is −80, −100 or −90 depending on nothing but the convention. A decomposition is a decision about where to put the seam, not a discovery about where the seam is.

Two consequences follow.

First, state the convention on the slide, in plain words — "volume effect measured at prior-period price" is enough. Without it, the reader cannot reproduce your arithmetic, and a reader who cannot reproduce it has to take the split on faith. The convention is not a trick and not a confession; it is a modeling choice, and naming it costs one footnote.

Second, do not treat your convention's output as observed fact. If an investor's own analysis splits the same quarter differently, you are not looking at a factual disagreement. You are looking at two seams. The argument worth having is about which convention fits the claim being made — volume first is often the more natural choice when the question is "did we sell fewer things?" — not about whose bridge is true.

Three further rules keep the reconciliation honest:

Do not count a movement twice. If two rows describe the same underlying activity — units and orders, say, when each order contains exactly one unit — the duplication has to go somewhere. Either a residual swings negative to compensate, or someone quietly shrinks the residual so the clean rows stay clean. Both are worth checking, and a residual pointing the wrong direction is a clue rather than proof.

Do not use a residual as a plug. A row defined as "whatever is left" will always make the bridge foot, because it is defined to. That is not a driver; it is the part you have not explained. Label it that way, and if it is large, say so. A bridge that balances with a third of the movement parked in "other" is a reconciled total with an unreconciled explanation.

Do not add an effect that is already inside a named component. If pricing includes a promotional discount, then "promotions" is not a separate row.

A contribution is not a cause

This is the distinction that carries the whole answer, so it is worth being pedantic about it.

A volume contribution of −200 is a statement about the arithmetic under a stated convention. It is not a statement about why customers bought less. The same −200 is consistent with a stockout, a lost account, a competitor's launch, a shift of orders across the period boundary, or an unusually strong comparable period a year earlier. The decomposition cannot choose among those. It has already done its job.

So it helps to keep an explicit ladder of what the deck is entitled to say:

  1. Measured. Units fell from 100 to 80. In the invented illustration above, those unit counts are assumed inputs; in a real deck, this rung comes from a record.
  2. Reconciled contribution. Volume accounts for −200 under the volume-first convention. This is arithmetic on that record plus a stated convention.
  3. Supported cause. A claim tied to evidence outside the revenue total — order-level history, inventory and availability records, pricing and discount logs, customer-level retention.
  4. Hypothesis. A plausible mechanism that current evidence does not establish, such as competitive loss supported mainly by the fact that revenue fell and competitors exist.
  5. Story. A convenient explanation with no evidence attached, usually the one that makes the quarter sound recoverable.

The work is deciding which rung each sentence in the deck stands on, and then writing it so the reader can tell.

The SEC staff's Financial Reporting Manual, Topic 9, makes a related move in its results-of-operations discussion: reporting a numerical change is treated as distinct from explaining the underlying drivers, price and volume among them (sections 9220.1 and 9220.5; page dated December 11, 2017, reviewed here as HTML text on September 18, 2025, at sec.gov's Financial Reporting Manual, Topic 9). That guidance is written for public filings, and it is dated staff material rather than a legal opinion. It places no obligation on a private pitch deck, and it says nothing about what any particular investor wants to see. Its use here is narrower and still useful: the drafters of filing guidance found the two things worth naming separately, which suggests a deck benefits from the same discipline.

One more distinction belongs on this ladder, because it is where otherwise careful decks slip. A movement in average selling price is a movement in a ratio, and a ratio moves for more than one reason. A list-price cut, a discount increase, and a mix shift toward cheaper products all lower average selling price, and all three sit inside the same price row — which is why a discount does not get its own row above. They are three different explanations with three different implications, and only the list-price cut is a pure list-price movement; a discount increase changes the realized price instead. If the deck has more than one product or more than one customer tier, the price row in such a table is concealing a mix question that needs its own evidence before anyone labels it.

The headline that survives contact

A single-driver headline is not inherently dishonest. Under both the volume-first and price-first conventions above, volume is the larger effect: about seven-tenths of the decline in one split, about two-thirds in the other. "Revenue declined 28%, driven mainly by lower volume" is defensible in this example, and a deck that buries that in six equally weighted rows has hidden its own finding.

Note what changed and what did not. The ranking held; the magnitude did not. Which means the safer headline names the driver, and the specific number attached to it carries the convention. "Volume drove the decline" survives both seams. "Volume drove 71% of the decline" survives only one, and needs the footnote that says which.

What makes a headline materially incomplete is usually not the omission of a small effect. It is one of three things:

  • A second effect large enough to change the impression. If the two rows are close, a headline naming one is editorializing.
  • Two effects moving in opposite directions that net out. A flat average selling price can sit on top of prices rising and mix shifting toward cheaper products. Reporting "pricing was flat" as a single fact erases two real movements that point in different directions.
  • A resolved sound where the evidence is unresolved. Presenting an inference in the declarative mood, with no trace of the question behind it.

There is also a specific trap worth naming because it is the one decks fall into most often. A driver that sounds temporary implies a rebound. If orders moved a few weeks across a period boundary, the revenue may return. If a customer stopped buying, that revenue is gone until someone wins it back, and the timing label was the wrong frame from the start. Do not let a word like "timing" carry a recovery promise the evidence has not earned. The deck can say the movement is concentrated in a period boundary. It cannot say the next quarter fixes itself unless the order records say the orders arrived.

Draw it only after it reconciles

A bridge chart or table is the last step, not the first, and it should carry three things: the starting figure with its period, the ending figure with its period, and units stated for every row. If an allocation is estimated rather than measured, mark it. If the residual is a plug, describe it as unexplained rather than dressing it up as "other movements."

Then get two separate reviews.

Ask the finance owner to verify the arithmetic, the definitions behind each row, and the convention. That is a real review and it covers the numbers.

Ask whoever owns the evidence behind each causal sentence — operations for availability, sales for account losses, marketing for promotion timing — to verify the wording of their sentence. These are different reviews with different failure modes, and one does not substitute for the other. A finance owner who confirmed the bridge has not thereby confirmed that a stockout caused anything. A polished chart is not an independent review, and a chart that foots can still be standing on a sentence nobody checked.

What the slide ends up saying

The finished account has three parts, and they should be visibly three parts.

The reconciled change: the total moved by this much, decomposed this way, under this convention, with this much unexplained.

The supported drivers: the components whose behavior the records can speak to, each traced back to evidence that lives outside the revenue total.

The open questions: what the deck cannot yet say, and what evidence would settle it. Fewer accounts, lower units per order, a competitor's entry — name which one is a finding and which one is still a question.

The distinction to protect all the way to the last sentence is the one this article started with. "This component accounts for the difference" is a statement about arithmetic, and the deck can make it with confidence once the seams are named. "This evidence explains why it happened" is a statement about the world, and it is only as strong as the evidence under it. Deck writers who blur those two sentences do not usually do it from dishonesty. They do it because the first one is available, the second one is hard, and the slide has to say something.

Frequently asked questions

What must be confirmed before explaining why revenue declined?

Comparability first: the revenue definition, the two observation periods, which activities are inside the definition, and which source records the deck will cite. Reclassification, 53-week versus 52-week periods, or recognition timing can make part of a 'decline' an accounting or calendar boundary rather than a business event.

Why can two correct decompositions split the same decline differently?

A decomposition depends on a convention that holds one factor fixed while measuring the other. Volume-first, price-first and midpoint conventions all foot to the same total but assign different amounts to volume and price. The split is a decision about where to put the seam, not a discovery about where the seam is.

When does a volume contribution become a cause?

A volume contribution is arithmetic under a stated convention; it does not explain why customers bought less. A supported cause needs evidence outside the revenue total, such as order-level history, inventory records, pricing logs or retention data. The ladder separates measured, reconciled contribution, supported cause, hypothesis and story.

Why can 'pricing was flat' be misleading?

Average selling price is a ratio, so it can move for different reasons: a list-price cut, a discount increase, or a mix shift toward cheaper products. Opposite movements can net out. The article says reporting 'pricing was flat' as one fact can erase two real movements that point in different directions.

What should a bridge chart include, and who should review it?

The starting and ending figures with their periods, units for every row, a mark for estimated allocations, and a residual described as unexplained if it is a plug. Finance should review the arithmetic, definitions and convention; the owners of evidence behind each causal sentence should review the wording of their sentence.

More in Business Browse all articles