# SaaS market forecasts: a reconciliation worksheet

> Forecast reconciliation explains why estimates differ before choosing which one supports a decision. Review definitions, sampling choices and common comparison errors.

Source: https://saas-marketing.net/research/saas-market-forecasts-reconciled/
Topic: SaaS Market and Industry Data
Type: research
Published: 2026-09-17
Last updated: 2026-09-17
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/research/saas-market-forecasts-reconciled/

## Short answer

Forecast reconciliation explains why estimates differ before choosing which one supports a decision.

## Key takeaways

- Place the definitions and dates beside each forecast, calculate comparable periods only where justified, and show unresolved differences openly.
- Averaging incompatible forecasts creates a new number without a defensible underlying market definition.
- Keep source dates, population definitions and limitations beside any numerical claim.
- This is a measurement and source-evaluation guide. It does not present an original customer survey or an industry-wide target.

---

Use this guide with the [saas market hub](/saas-market/). The goal is a defensible comparison: a result whose definition and limitations another person can understand.

## Define the comparison

Forecast reconciliation explains why estimates differ before choosing which one supports a decision.

| Dimension | What to record |
| --- | --- |
| Market boundary | State the exact scope for your data and for the external comparison. |
| Base year | State the exact scope for your data and for the external comparison. |
| Forecast horizon | State the exact scope for your data and for the external comparison. |
| Currency basis | State the exact scope for your data and for the external comparison. |
| Methodology | State the exact scope for your data and for the external comparison. |

A useful benchmark answers a specific management question. Write that question before collecting numbers. A figure can be accurate for its source population and still be inappropriate for your company's segment or decision.

## Measure it consistently

Place the definitions and dates beside each forecast, calculate comparable periods only where justified, and show unresolved differences openly.

Keep the underlying counts and dates, not only a final percentage or ratio. If a record is incomplete, distinguish unknown from zero. Record changes to definitions so a later trend does not silently combine incompatible periods.

## Avoid the main interpretation trap

Averaging incompatible forecasts creates a new number without a defensible underlying market definition.

Separate observation from explanation. The report may show that two things moved together; that does not identify which caused the other. List plausible alternative explanations and the additional evidence required to choose between them.

## Build an evidence register

| Field | Required entry |
| --- | --- |
| Decision | The action this evidence could change |
| Source | Original publisher and exact URL |
| Dates | Publication date and underlying collection window |
| Population | Who or what was included and excluded |
| Definition | Numerator, denominator, unit and treatment of edge cases |
| Method | Survey, product records, experiment, estimate or forecast |
| Limitation | The reason the comparison may not transfer |
| Owner | Person responsible for verification and the next review |

Use the [benchmark evaluation worksheet](/resources/) to keep these fields with the proposed claim. Do not replace a missing method or sample description with assumptions based on the publisher's reputation.

## Further reading

The following pages were discovered during the September 2026 source review and returned a successful response when checked. They are starting points for evaluation, not a combined dataset or an endorsement of every claim they contain.

- [TAM SAM SOM Calculator 2026 : Free Market Size Tool](https://ideaproof.io/calculators/market-size)
- [TAM SAM SOM Calculator : Free Market Size Estimator  Fonda](https://fonda.co/tools/tam-sam-som-calculator)
- [Market Sizing (TAM/SAM/SOM)  PM Toolkit Docs](https://pmtoolkit.ai/docs/market-size)
- [TAM, SAM, and SOM: fundamental market size metrics](https://www.trustedvaluecreator.com/wp-content/uploads/2023/09/TAM-SAM-SOM-from-Lean-Case.pdf)

## Turn the evidence into a decision

Compare your own consistent historical cohorts first, then use external evidence to identify questions worth investigating. If the external population differs materially, state the difference instead of forcing the number into a target. Record the proposed action, its uncertainty and the next review date.

- [Global SaaS Market Size](/guides/global-saas-market-size/)
- [SaaS Market Growth Rate](/guides/saas-market-growth-rate/)
- [SaaS Industry Growth](/guides/saas-industry-growth/)
- [B2B SaaS Market Size](/guides/b2b-saas-market-size/)
- [The B2B SaaS Industry](/guides/b2b-saas-industry-overview/)

The [metrics library](/saas-metrics/) explains related definitions, and the [calculators](/calculators/) can help check the arithmetic of a scenario.
{/* expanded-practice-2026-09 */}
## Apply saas market forecasts: a reconciliation worksheet in a working review

Build a source record before drawing a comparison. Capture the original publisher, collection period, sample, metric definition and relevant exclusions. Separate reported observations from forecasts and your own planning assumptions. If two sources use different populations or denominators, explain the difference instead of averaging them into a single number.

For this topic, involve the research owner and the person using the estimate for a decision and work from source method, market boundary and assumption table. The relevant unit is a clearly defined population, period and value measure. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

### Evidence to prepare

Read the original definition before combining figures. Publication date, collection period and forecast horizon answer different questions. A market estimate can be useful without being directly comparable to another publisher’s number.

| Review field | What to record |
| --- | --- |
| Topic | SaaS market forecasts: a reconciliation worksheet |
| Decision | The specific action this explanation should help you choose |
| Working evidence | source method, market boundary and assumption table |
| Unit and scope | a clearly defined population, period and value measure |
| Responsible people | research owner and the person using the estimate for a decision |
| Remaining uncertainty | The missing fact that could change the decision |

### Two situations that can change the interpretation

#### When a market estimate mixes unlike measures

A software-only estimate and a software-plus-services estimate can both be reasonable while answering different questions.

Use this check: Read each source's market boundary, unit, period and included products. Do not average conflicting definitions to create a falsely precise number.

The [focused diagnostic guide](/guides/market-size-estimate-mixes-revenue-and-spend/) provides the correction process and a working evidence sheet.

#### When a forecast is presented as measured growth

A category growth projection can provide context but does not establish the acquisition rate a new entrant will achieve.

Use this check: Check the source's methodology and identify which periods are observed and which are modeled. Do not convert a third-party forecast into a guaranteed outcome for an individual product.

The [focused diagnostic guide](/guides/market-growth-forecast-is-treated-as-observation/) provides the correction process and a working evidence sheet.

### Record the decision and the limit

A software-revenue estimate and a broader customer-spending estimate may both be credible within their own definitions. Averaging them does not create a better answer. Explain the boundary and choose the measure that matches the decision being made.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the [complete topic collection](/topics/saas-market/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied.

## Frequently asked questions

### Does this page report an original industry study?

No. It explains how to evaluate evidence and measure the topic. It does not claim a proprietary survey, a sampled customer panel or an industry-wide benchmark that has not been collected.

### What needs to match before comparing results?

Check market boundary, base year, forecast horizon, currency basis, methodology. Differences in these fields can change the interpretation even when the reported metric has the same name.

### What is the main comparison error?

Averaging incompatible forecasts creates a new number without a defensible underlying market definition.

### How should I record a source?

Save the original URL, publisher, publication and collection dates, population, metric definition and relevant table or passage. Label an estimate as an estimate and retain the source limitations.