Bottom-Up Market Sizing: Units, Price, and Scope

Bottom-up market sizing estimates value by building from identifiable units such as customers, sites, devices, procedures or transactions. It works when each multiplication has a clear definition. If the units, eligibility rate or price are vague, the model merely gives a spreadsheet a confident appearance.

Market Survey Analysis view: This guide is built for the decision of whether a target population can support a commercial opportunity under realistic reach, usage and price assumptions. Start with the boundary, then test the evidence chain. For related market intelligence and research workflows, keep the definition, source and decision in one review record.

How to read the result

Read the result in four layers: the observed measure, the definition that limits it, the interpretation that connects it to the decision and the condition that would change the conclusion. The observed measure may be a count, ratio, price, flow or stock. The definition tells the reader whose activity, which object, which geography and which period are represented. The interpretation explains why the measure matters for whether a target population can support a commercial opportunity under realistic reach, usage and price assumptions. The condition keeps the recommendation honest when the market, source or operating context changes.

Do not let the headline travel without its method note. If a finding is copied into a forecast, sales plan or investment case, carry its unit, source date, scope and limitation with it. This prevents a market signal from becoming an unsupported promise after it leaves the original research file. It also gives the next analyst a clean starting point instead of an attractive mystery.

Apply the framework in practice

Begin with a one-page decision brief. Write the object being measured, the population or market boundary, the economic event, the evidence sources and the decision date. Then list the assumptions that could reverse the recommendation. This makes the research useful before a large dataset or elaborate dashboard exists, and it gives reviewers a common language for challenging the work.

Use the first pass to find the most consequential gap, not to create the appearance of completeness. A missing denominator, untested eligibility rule, stale source or unclear buyer can matter more than another page of background. Assign that gap to an owner, choose a practical check and record the result beside the original claim. Good market intelligence becomes stronger through visible review.

Define the unit of opportunity

Choose the smallest unit that maps to the commercial event. A hospital network, facility, bed, clinician, patient, device or treatment can each be valid in a different model. Do not count every entity that could be interested if only some can buy. The unit must have an observable eligibility rule and a plausible path to revenue or use.

Decision check: Ask what would change the call if this definition, measure or assumption moved. Record that condition beside the result instead of hiding it in an appendix.

Build the population from named records

A bottom-up model gains credibility when its population can be reconciled to a register, survey frame, public dataset, company list or operational record. Record the source date, geography, exclusions and duplicate treatment. If the list is incomplete, the gap is a model risk, not a reason to quietly inflate the total.

Decision check: Ask what would change the call if this definition, measure or assumption moved. Record that condition beside the result instead of hiding it in an appendix.

Apply eligibility before adoption

Eligibility answers whether the unit could use the offer. Adoption answers whether it will. Budget, infrastructure, regulation, workflow, procurement and technical requirements can remove units before preference is measured. Applying adoption to the whole population before eligibility usually produces a market that exists only in the model.

Decision check: Ask what would change the call if this definition, measure or assumption moved. Record that condition beside the result instead of hiding it in an appendix.

Treat price as a distribution

A single price can conceal plan mix, contract length, discounts, geography, channel margin and usage tiers. Use a stated price basis and test a reasonable range. Where the market has different segments, model them separately before adding them. The result should show whether the opportunity depends on a premium price that few buyers can actually pay.

Decision check: Ask what would change the call if this definition, measure or assumption moved. Record that condition beside the result instead of hiding it in an appendix.

Model repeat use and replacement

Recurring revenue, repeat purchases and replacement demand have different timing. A user count multiplied by an annual price is not automatically annual revenue if the user can cancel, pause, share or buy through a distributor. State the renewal, replacement or utilisation assumption and identify the evidence that supports it.

Decision check: Ask what would change the call if this definition, measure or assumption moved. Record that condition beside the result instead of hiding it in an appendix.

Use sensitivity to find the decision variable

Run the model with alternative values for reach, conversion, price, frequency and eligible units. The purpose is not to decorate a chart with three scenarios. It is to show which input can change the decision. If a small change in one assumption reverses the conclusion, that assumption deserves field research.

Decision check: Ask what would change the call if this definition, measure or assumption moved. Record that condition beside the result instead of hiding it in an appendix.

Reconcile against an external total

A bottom-up result should be compared with an independent top-down measure where one exists. The comparison is a diagnostic, not a demand to force agreement. A gap can reflect a different category boundary, domestic activity, distributor revenue, double counting or a missing segment. Investigate the bridge before choosing a preferred number.

Decision check: Ask what would change the call if this definition, measure or assumption moved. Record that condition beside the result instead of hiding it in an appendix.

Keep the model updateable

Give each input an owner, source, access date and review trigger. A model that cannot be refreshed becomes a presentation asset rather than market intelligence. Keep definitions beside the formula and record changes to scope, price or population so a later analyst can explain why the estimate moved.

Decision check: Ask what would change the call if this definition, measure or assumption moved. Record that condition beside the result instead of hiding it in an appendix.

A practical evidence table

The table is a control, not a substitute for judgement. Keep the source title, date, unit and limitation beside every material input. When two rows use different definitions, do not combine them until the bridge is written and reviewed.

What this analysis does not prove

A market estimate, share, indicator or forecast is not proof of revenue, ranking, adoption, profitability or future performance unless the evidence directly measures that claim. It may be a useful signal or planning input. State the limit near the conclusion so the number is not reused outside its original boundary.

Source quality has more than one dimension. Authority does not guarantee current coverage. Detail does not guarantee comparability. A transparent method should show what is known, what is derived, what is missing and what the next review will test.

Review checklist before publication

• Write the market, industry or evidence object in one sentence.
• Name the population, buyer, user, provider or economic unit.
• Align the geography, period, currency and measurement basis.
• Mark every estimate, proxy, transformation and excluded group.
• Test the internal links and source links over HTTPS.
• Give the decision owner one condition that would change the recommendation.

Frequently asked questions

When is bottom-up sizing useful?

It is useful when the target units can be identified and the economic event can be modelled with explicit, reviewable inputs.

What is the biggest bottom-up sizing error?

Applying a broad population, optimistic adoption and a high price without proving eligibility, reach or payment behaviour.

How many scenarios should a model include?

Enough to show the decision boundary. A base case plus carefully explained alternatives is better than a long list of labels with no changed assumptions.

Can a company list prove the market size?

It can help define the population, but a list may contain duplicates, inactive entities, ineligible buyers or no information about need and budget.

What should be documented beside a model?

Definitions, sources, dates, exclusions, formulas, assumptions, sensitivity results and the trigger for the next review.

Sources and method notes

The links below are the primary or institutional references used for the method. They provide definitions and context. They do not turn an unsupported market claim into a verified statistic.

• U.S. Census Bureau: Annual Business Survey. Business population, ownership and activity data with stated survey definitions. Checked on 2026-09-15.
• Office for National Statistics Methodology. Official-statistics production, quality, concepts and methodological practice. Checked on 2026-09-15.
• ICC/ESOMAR International Code 2025. Ethics, transparency, accountability, privacy and human oversight in research and analytics. Checked on 2026-09-15.

Next step

Use this framework to define a focused brief, test the evidence and identify the next decision. If the boundary or source base needs work, request a custom research discussion rather than forcing a weak number into a plan.