# Top-down vs bottom-up SaaS market sizing

> Compare top-down sizing and bottom-up sizing for SaaS: where each fits, the tradeoffs to test and a practical decision process.

Source: https://saas-marketing.net/comparisons/top-down-vs-bottom-up-market-sizing/
Topic: SaaS Market and Industry Data
Type: comparison
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/comparisons/top-down-vs-bottom-up-market-sizing/

## Short answer

Top-down analysis can establish broad context when the category boundaries and published estimates are relevant. Bottom-up analysis can connect a specific offer to eligible accounts and plausible spending assumptions.

## Key takeaways

- Top-down analysis can establish broad context when the category boundaries and published estimates are relevant.
- Bottom-up analysis can connect a specific offer to eligible accounts and plausible spending assumptions.
- A percentage of a huge market is not evidence of obtainable demand, and a detailed account model can still rely on weak inputs.
- Use the methods to challenge each other's boundaries and assumptions rather than averaging the answers automatically.

---

The decision belongs in your wider [saas market plan](/saas-market/). Start with the customer task and operating constraint, then compare the options against that context.

## Where each option fits

### Top-down sizing

Top-down analysis can establish broad context when the category boundaries and published estimates are relevant.

### Bottom-up sizing

Bottom-up analysis can connect a specific offer to eligible accounts and plausible spending assumptions.

## The comparison that matters

| Dimension | What changes the decision |
| --- | --- |
| Input | Published category total versus eligible accounts and spend. |
| Strength | Broad context versus explicit offer-level assumptions. |
| Limit | Category mismatch versus incomplete counts and pricing evidence. |

The table is a decision framework, not a claim that one option always wins. A useful choice accounts for the work your team can perform, the customer experience it must support and the evidence available today.

## Avoid this mistake

A percentage of a huge market is not evidence of obtainable demand, and a detailed account model can still rely on weak inputs.

Before comparing results, align the scope. Write down what is included, who does the work and which time period matters. If a comparison uses different definitions on either side, resolve that mismatch before interpreting the numbers.

## Run a practical evaluation

Use the methods to challenge each other's boundaries and assumptions rather than averaging the answers automatically.

1. Choose one representative workflow or customer situation. Avoid a demonstration that removes the difficult part of your actual case.
2. Define the required outcome and the conditions that would make an option unsuitable. Include operational and customer-experience constraints.
3. Collect evidence under the same scope for both options. Record implementation effort, dependencies and unresolved questions.
4. Review the result with the people who will operate the choice. A decision that requires unavailable skills or capacity needs a different plan.
5. Record the choice and a review trigger. New customer needs, product changes or a different scale can justify revisiting it.

## Document the decision

| Item | Your evidence |
| --- | --- |
| Customer task | What the choice must help someone accomplish |
| Required capability | The condition that cannot be compromised |
| Full cost | Money, internal effort and ongoing responsibility |
| Main risk | What could make the choice fail in your context |
| Validation | The observation or test supporting the decision |
| Review trigger | The change that would justify another evaluation |

## Continue the evaluation

- [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/)

Browse the [comparison library](/comparisons/) and [working resources](/resources/) for related decisions.
{/* expanded-practice-2026-09 */}
## Apply top-down vs bottom-up saas market sizing in a working review

Choose a representative customer task and compare both options under the same constraints. Keep required capabilities separate from preferences, and document the cost of moving as well as the cost of staying. An attractive feature does not resolve a missing requirement. Leave unknown evidence visible and identify the test that could change the choice.

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 | Top-down vs bottom-up SaaS market sizing |
| 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 competitor count is treated as demand

A crowded category may contain many small tools serving different jobs rather than one homogeneous market.

Use this check: Separate evidence of supply from evidence of customer problems, spending and switching behavior. Few competitors can indicate opportunity or lack of demand; the count alone does not decide.

The [focused diagnostic guide](/guides/competitor-count-is-used-as-market-demand/) provides the correction process and a working evidence sheet.

#### When market entry stops at a large TAM

An initial campaign can test whether a narrow audience recognizes the problem before the team assumes a broad market forecast applies to it.

Use this check: Define a specific buyer, offer, channel and bounded evaluation of demand. Do not treat a few positive interviews as proof of scalable acquisition economics.

The [focused diagnostic guide](/guides/market-entry-plan-has-no-obtainable-demand-test/) 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

### When does top-down sizing fit?

Top-down analysis can establish broad context when the category boundaries and published estimates are relevant.

### When does bottom-up sizing fit?

Bottom-up analysis can connect a specific offer to eligible accounts and plausible spending assumptions.

### What is the main comparison mistake?

A percentage of a huge market is not evidence of obtainable demand, and a detailed account model can still rely on weak inputs.

### How should I make the decision?

Use the methods to challenge each other's boundaries and assumptions rather than averaging the answers automatically. Record the evidence and remaining uncertainty before committing.