Account potential estimation

Account potential estimation sets a defensible ceiling for what an account could produce. Keep initial contract value, full account potential, expansion paths, and strategic value separate so a large theoretical account does not look like near-term pipeline. Account count hides workload and revenue potential. It treats a 40-person prospect and a 4,000-person prospect as equivalent units.¹ Estimate the value inside the account before deciding how much attention to give it. Treat every estimate as a working hypothesis whose assumptions you can inspect and revise.

Set the unit of value

Decide what the estimate should answer before doing the math. Keep the unit stable across accounts so the result can guide selection and tiering.

Use separate fields for initial contract value, full account potential, expansion value, and strategic value. Addressable ARR estimates how much an account would be worth in a complete sale.² A team used LinkedIn Sales Insights data to model addressable ARR by account.³

If an account spans related companies, roll up each child company's annual revenue when scoring its true value.⁴ This keeps the estimate tied to the whole buying group instead of a single legal entity.

Run the estimate

Work through the questions in this order. When an answer is missing, record the gap and the assumption you are using instead of hiding it inside the total.

Size the account

Start with the account's scale, then test how much revenue could sit inside it. Ask, "Like how big is this account that I'm going after?".⁵ Then ask, "What is the total amount of revenue that I think could be there?".⁶

Keep account size and revenue potential as separate answers. A large account can have limited reachable spend, while a smaller account can have a clearer path to an initial contract.

Set the initial contract value

Estimate the entry deal separately from the account ceiling. Confirm the most likely revenue size of the initial contract value of the opportunity.⁷ For pipeline work, average sales price can act as the proxy value for an opportunity.⁸ Keep the deal-size estimate tied to discovered needs in the opportunity record.⁹

For recurring businesses, calculate customers × average revenue per user, then annualize the result.¹⁰ If the account could buy several product lines, calculate revenue for each line separately and add the results for total revenue.¹¹

Map expansion

The initial contract is the entry point for the estimate. Analyze new business that could come from renewals, repeat business, or account growth.¹² Ask, "what percentage of growth does each account have?".¹³

Consider the value a customer brings across the entire customer relationship.¹⁴ Tie expansion to a concrete route, such as a renewal, repeat purchase, wider product use, or a broader buying group. If you cannot describe the route, keep the expansion amount as an assumption.

Test the wider route

Before giving a large account more attention, ask, "If I go do that, is there a run or a track to a larger deal somewhere else within that company? So one, is my time worth spending there?".¹⁵

Qualify what happens after the proof of concept ends.¹⁶ This shows whether the entry deal can lead to a larger commercial path or stops at the initial scope.

Capture strategic value

Revenue does not cover every reason to pursue an account. Sales should help customer success understand expansion potential, strategic importance, product footprint opportunity, and internal reference value.¹⁷

Use end-user team size as a signal of broader potential impact when deciding which accounts deserve attention.¹⁸ Record the strategic reason in plain language so another person can understand why the account matters even when the initial contract is modest.

Separate amount from confidence

An amount is useful when you can explain what supports it and what remains uncertain. Put a confidence note and a next proof point beside the estimate.

Deciding how large to make the ask involves quantitative analysis and judgment about the account.¹⁹ Predictions rely heavily on estimates and assumptions.²⁰ Inject real data into the projection wherever you can, because more real data improves the projection.²¹

Label the output as a transparent model with its assumptions.²² When you turn the estimate into pipeline action, use qualified opportunities as the input.²³

Proceed when the initial contract has a clear basis and the wider route has a credible owner or event. Investigate when account size is clear but reachable revenue or expansion is still vague. Deprioritize when the estimate depends on a large theoretical ceiling with no route to an initial purchase.

Once the estimates are comparable, outbound teams should identify the most profitable accounts and target them with outbound activity.²⁴ Use the estimate to decide where research and outreach time goes, and use the confidence note to show how much of that decision still needs proof.

What not to do

These mistakes make an estimate look precise while hiding what it includes. Keep the warnings beside the account record.

• Use addressable value per account in the territory plan. Revenue to date alone leaves that value unrecorded.²⁵
• Use expansion use cases to create a bigger revenue base inside the account.²⁶
• Evaluate each account's market value as part of the sales territory plan, then prioritize the accounts.²⁷