# Pressure-test the estimate and present its limits > Find which assumptions drive the market result and explain the range without false precision. Complete the exercise, produce a working artifact and review it against a practical rubric. Source: https://saas-marketing.net/courses/saas-market-sizing/03-pressure-test-and-present/ Topic: SaaS Market and Industry Data Type: course-lesson 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/courses/saas-market-sizing/03-pressure-test-and-present/ ## Short answer Find which assumptions drive the market result and explain the range without false precision. This lesson turns that decision into a working document: a short market memo with the range, sensitivity drivers and evidence gaps. Use the steps, example and review questions below to complete the exercise with your own product or an explicitly labelled practice case. ## Key takeaways - Find which assumptions drive the market result and explain the range without false precision. - A short market memo with the range, sensitivity drivers and evidence gaps. - Keep assumptions separate from observed evidence. - Finish with a decision and a named next action, not only a completed document. --- This lesson is part of the [saas market sizing course](/courses/saas-market-sizing/). Find which assumptions drive the market result and explain the range without false precision. ## Prepare your working case Choose one product and one customer segment. Gather the relevant product information, customer evidence and operating records before writing the answer. If you are learning without access to a business, use a clearly labelled practice case and state the assumptions you make. Keep the scope small enough that you can explain the decision to another person. The purpose is to learn how to reason through the work, not to produce a longer document than the situation needs. ## Work through the exercise ### Step 1 Vary account eligibility and annual spend separately. Record your answer, the evidence behind it and any unresolved dependency before moving to the next step. ### Step 2 Compare the result with independently defined market evidence. Record your answer, the evidence behind it and any unresolved dependency before moving to the next step. ### Step 3 Investigate differences in category scope rather than averaging incompatible totals. Record your answer, the evidence behind it and any unresolved dependency before moving to the next step. ### Step 4 Present the key assumptions, limitations and next research step. Record your answer, the evidence behind it and any unresolved dependency before moving to the next step. ## Worked situation Two forecasts can disagree because one counts infrastructure and the other counts only application subscriptions. The difference is definitional before it is numerical. Treat this as an illustration of the decision, not a measured result or a claim that the same approach fits every company. In your own case, identify which condition would make the conclusion different. That condition belongs beside the recommendation. ## Produce the deliverable A short market memo with the range, sensitivity drivers and evidence gaps. Use the [working template](/templates/saas-market-sizing-model/) to organize the result, then run the [review checklist](/checklists/market-data-quality-audit/). Add the project name, date, owner and a link to supporting evidence. If a key input is unknown, describe how you would learn it rather than filling the gap with a confident guess. A useful deliverable can be read without a live presentation. Another person should be able to identify the problem, understand the recommended choice and see what happens next. Remove any section that does not help them make or execute that decision. ## Review your work | Review question | Evidence in your work | Revision needed | | --- | --- | --- | | Is the main conclusion supported under plausible assumptions? | | | | Are forecasts labelled separately from observations? | | | | Can the audience see what would change the estimate? | | | Ask a colleague to challenge the weakest assumption. Write down the strongest alternative explanation and the evidence that would distinguish it from your current view. This makes the result easier to revise when new information arrives. ## Continue the course Return to the [course outline](/courses/saas-market-sizing/) or use the lesson navigation below. For the wider topic, visit [saas market](/saas-market/). The [resource library](/resources/) and [calculators](/calculators/) provide additional working tools. {/* expanded-practice-2026-09 */} ## Apply pressure-test the estimate and present its limits in a working review Use the lesson to produce a small working artifact. State the starting problem, apply the method to one case and ask another person to inspect the result. Compare their interpretation with the explanation you intended. Revise the artifact before repeating the exercise at a larger scope; reading the material alone does not establish that the method can be applied. 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 | Pressure-test the estimate and present its limits | | 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 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. ### 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 ### What should I have completed by the end? A short market memo with the range, sensitivity drivers and evidence gaps. ### Can I take the lesson without company data? Yes. Use an explicitly labelled fictional practice case. Do not present its assumptions or outcomes as customer evidence, and note what you would need to verify in a real project. ### How do I know if my work is ready? Is the main conclusion supported under plausible assumptions? Are forecasts labelled separately from observations? Can the audience see what would change the estimate? Use the rubric to identify what is supported and what needs another check. ### Do I need to sign up for the course? No. The published lessons are free to read. Download forms are optional, and the course can be completed at your own pace.