Market Size Versus Reachable and Eligible Accounts

Separate a market frame from serviceable, verified and action-eligible accounts, with a worked nested model that preserves unknowns.

10/24/20263 min read

Nested fictional account sets narrow from 120 to 18, preserving excluded and unresolved reasons

A market report counts thousands of businesses in a category. The sales plan treats that figure as the number of prospects the team can serve and contact. Several filters are missing: delivery coverage, service fit, reliable identity, an appropriate contact route and the rules governing its use.

Separate the broad market frame from the smaller sets relevant to a particular decision. A nested model can show how each condition changes the usable account population without pretending that market size equals reachable demand. Keep unknowns visible and avoid turning a research count into a revenue forecast.

Define every set before counting

State the geographic area, business category, entity unit and time period. A parent group, subsidiary and operating site may each appear in a source, but they are not interchangeable accounts. Decide which unit the proposed service actually addresses before adding the rows.

Then define serviceable, relevant, identity-verified and eligible for the particular next action. The last category is purpose and channel specific; it should not become a permanent safe-to-contact label. NIST's voluntary framework includes purpose mapping. It does not provide communication permission or settle applicable law.

A fictional nested-account model

The following counts are invented for a planning exercise. They do not describe a real market, a statistically representative study or actual contact eligibility.

Starting frame: 120 organization records in a defined source list after obvious duplicates are reviewed. This is the available frame, not necessarily the entire market.
Service coverage: ninety records fall within the provider's confirmed delivery boundary; thirty do not fit that boundary.
Defined task fit: sixty of those ninety match the specific service criteria. The remaining thirty are excluded or unresolved for that task and must retain their separate reason codes.
Identity verification: forty-two of the sixty have sufficient entity evidence for the next review. Eighteen require clarification; they are not assumed to be duplicates or unsuitable.
Next-action review: eighteen of the forty-two have an appropriate, currently confirmed route for the particular proposed action under the example's approved process. Twenty-four remain unreviewed, restricted or otherwise unresolved and are not placed in an active communication queue.

The model ends with eighteen accounts for that bounded next-action category, not eighteen interested buyers or guaranteed customers. It also preserves where the uncertainty sits, so the team can decide whether further review is worthwhile.

Avoid misleading subtraction

Nested sets require each later group to come from the prior group. If coverage and eligibility were assessed on different populations, do not subtract their totals as though they form one funnel. Reconcile the account identifiers and definitions first.

Keep excluded and unknown separate. A chart that combines them may imply the team has ruled out accounts it simply has not checked. Show the reason categories beside the summary, especially when the difference affects future research work.

W3C describes traceable information origins. Link each count to the source set, review rule and checked date. The custom model is a planning artifact, not a W3C method or proof that the underlying data is complete.

Match the model to the business decision

A service-capacity decision may need the serviceable set. A bounded research pilot may need the identity-verified set. An authorized communication task needs its own eligibility review. Use the count appropriate to the decision instead of selecting the largest number for a presentation.

Do not multiply a broad market count by an invented conversion rate and call the result expected revenue. The model describes scope and evidence limits. Demand, purchasing decisions and financial outcomes require different information.

Review the sets when service coverage, source quality or the intended action changes. A record eligible for one purpose may not be appropriate for another. The model is useful when it makes those boundaries explicit and gives each remaining gap a reason, rather than turning a large market headline into an oversized prospecting promise.

Sources and scope

The worked examples and decision tools are original editorial proposals, not reported customer results. References support the identified context, not endorsement or validation of these methods.