Forecasting Company Revenues

Updated for the 2026-2027 CFA® Level I curriculum.

Revenue forecasting is the starting point for almost every company analysis task on the CFA Level I exam. Get the revenue forecast wrong and every downstream number, from operating income to free cash flow, is wrong too. This note covers the main approaches analysts use to forecast revenue, how revenue drivers turn into specific assumptions, and how to check whether a forecast makes sense.

Key Takeaways About Forecasting Company Revenues

• Top-down forecasting starts with macroeconomic or industry growth and allocates a market share to the company.

• Bottom-up forecasting starts with company-specific drivers, such as volume and price, and sums results up to total revenue.

• Common revenue drivers include units sold, average selling price, same-store sales growth, store or unit count, and segment-level growth rates.

• Driver-based forecasting expresses revenue as volume multiplied by price, applied at the segment or product line level when useful.

• A reasonable forecast is checked against historical growth, industry growth, and the consistency of related assumptions, not accepted at face value.

• Changing one assumption in isolation, without adjusting related assumptions, is a common source of forecast error.

• Revenue forecasts are estimates built on assumptions. They are not guaranteed outcomes, and Level I questions often test whether a candidate treats them that way.

What You Need to Know for CFA Level I

• Identify the main approaches to forecasting company revenue: top-down, bottom-up, and driver-based methods.

• Explain how a specific revenue driver, such as price or volume, becomes a forecast assumption.

• Distinguish top-down reasoning from bottom-up reasoning and know when each is more appropriate.

• Apply a basic reasonableness test to a stated revenue forecast.

• Recognize when a forecast assumption is inconsistent with other assumptions in the same forecast.

Approaches to Forecasting Revenues

Analysts generally use one of three broad approaches, often in combination.

Growth relative to a macro or industry variable (top-down)

The analyst starts with an economic forecast, such as nominal GDP growth, or an industry growth forecast. The company's revenue is then estimated as a share of that larger number, using an assumed or trended market share.

Driver-based forecasting (bottom-up)

The analyst forecasts revenue directly from operating drivers: units sold, average selling price, subscriber counts, same-store sales growth, or new unit or store openings. This method works segment by segment or product line by product line, then sums to a company total.

Trend or time-series extrapolation

The analyst projects revenue forward using the company's own historical growth rate, adjusted for any known changes. This is the simplest method and works best for stable, mature businesses with few structural changes ahead.

Most real forecasts blend these approaches. An analyst might use a top-down industry growth estimate to set a ceiling on plausible growth, then build the actual forecast from bottom-up, driver-based assumptions.

How Revenue Drivers Translate Into Forecast Assumptions

A revenue driver is an operating measure that directly explains revenue. Turning a driver into a forecast assumption means assigning it a specific expected value or growth rate for the forecast period.

The basic driver-based relationship is:

For a company with multiple segments, total revenue is the sum of each segment's volume-times-price calculation, or the segment's own growth assumption applied to its current revenue base.

Defining drivers this way keeps the forecast transparent. A reviewer can trace every dollar of forecast revenue back to a specific volume or price assumption.

How Top-Down and Bottom-Up Reasoning May Differ

Top-down and bottom-up approaches start from opposite ends of the same problem.

Neither approach is automatically correct. A top-down forecast anchored to GDP growth can miss company-specific factors, such as a new product launch. A bottom-up forecast built purely from internal drivers can miss a shrinking end market. Analysts often calculate both and investigate any large gap between them.

How to Test the Reasonableness of a Revenue Forecast

A forecast needs a reasonableness check before it feeds into the rest of a company analysis. Useful checks include:

• Comparing the forecast growth rate to the company's own historical growth rate.

• Comparing the forecast growth rate to industry or peer group growth rates.

• Checking that the forecast is not persistently above nominal GDP growth for a mature, broad-economy company, since that pattern is difficult to sustain over the long run.

• Confirming that related assumptions move together. A higher volume assumption often implies added capacity, which affects other line items.

• Running the forecast under alternative scenarios to see how sensitive the result is to a single assumption.

If a forecast survives these checks without requiring an unusual or unexplained assumption, it is reasonable to use as a base case.

Worked Example

Northfield Coffee Co. has two segments: Retail Stores and Wholesale.

Current year figures:

• Retail Stores: 500 stores, average revenue per store of $600,000

• Wholesale: current segment revenue of $80 million

Analyst assumptions for next year:

• Retail store count grows 4%

• Average revenue per store (same-store sales) grows 3%

• Wholesale segment revenue grows 5%

Step 1: Forecast retail store count

Step 2: Forecast average revenue per store

Step 3: Forecast retail segment revenue

Step 4: Forecast wholesale segment revenue

Step 5: Sum segments for total forecast revenue.

This is a bottom-up, driver-based forecast. Retail revenue combines two separate drivers, store count and same-store sales, rather than a single blended growth rate. Wholesale revenue uses a single segment-level growth assumption.

Because the drivers are explicit, an analyst can test each one separately if new information changes the outlook for either segment.

Common Exam Traps

Changing one assumption without updating related line items

Raising a volume assumption without also reviewing price or segment mix produces an internally inconsistent forecast. Level I questions sometimes present a "revised" forecast that only adjusts one input.

Treating a forecast as a certainty

A revenue forecast is a point estimate built on assumptions. Exam questions may test whether a candidate understands that changing an input changes the output, rather than treating the forecast number as fixed.

Using inconsistent growth, margin, or financing assumptions

A revenue growth assumption that is not consistent with the margin or capacity assumptions used elsewhere in the same analysis produces an unreliable forecast, even if each individual number looks reasonable in isolation.

Confusing a single sensitivity change with a full scenario

Moving one input, such as price, while holding volume fixed, is a sensitivity test on that one variable. A full scenario, such as a recession case, usually requires moving several related assumptions together.

Practice Question

An analyst uses a top-down approach to forecast revenue for a consumer electronics company. She forecasts nominal GDP growth of 4% next year and expects the company's industry to grow at 1.5 times the GDP growth rate. She assumes the company maintains its current 20% market share. Current industry revenue is $50 billion.

What is the company's forecasted revenue for next year?

1. $10.0 billion

2. $10.6 billion

3. $10.4 billion

FAQs About Forecasting Company Revenues