Account potential estimation

Estimate an account's potential before assigning coverage. Use a current revenue baseline, what the account could support across its structure, and expansion paths you can name. Keep the theoretical ceiling separate from the path to reach it. An account may have a large theoretical value while its reachable value stays small until more than one business unit gets value. This keeps size alone from deciding where you spend attention and makes the next outbound action visible.

The estimation sequence

Use this sequence to keep a large theoretical number tied to the facts you have about the account.

Stage	What you are trying to learn	Example question
Set the ceiling	What the account could support across its structure	What could this account spend if fit and coverage were complete?
Establish the baseline	What revenue exists today and which part can continue	Which revenue is current, and which part is recurring?
Map expansion	Where another team, entity, or use case could create spend	Where could this account buy more?
Test reachability	Whether a path exists from the current foothold to larger value	What would have to happen for this account to become larger?
Make the coverage call	Whether the upside justifies the work required to pursue it	Is the upside reachable enough for the effort?

Set the account ceiling

Start with the largest defensible account value, then work down to the part you can reach. The ceiling lets you compare accounts with different structures and buying surfaces.

Use addressable ARR for the ceiling of a complete sale. It estimates how much an account would be worth in a complete sale.¹ When the account contains subsidiaries, roll up each child company's annual revenue so the account's value reflects the wider structure.²

Ask, "What is the total amount of revenue that I think could be there?"³ Write the answer as an account-level estimate and note what must happen before that value becomes reachable. A parent-level figure without the underlying entities can make a good account look smaller than it is.

Establish the current baseline

The baseline shows what the account already produces and gives the expansion estimate a starting point. Keep it clean before adding future use cases or wider deployment.

MRR measures monthly subscription or recurring revenue that is highly likely to continue.⁴ Track recurring and non-recurring revenue separately when calculating MRR.⁵ To calculate it, assign each current customer a monthly subscription value, divide multi-month contract values by the number of subscription months, and add the resulting subscription values.⁶ The data for this calculation should be in your accounting software.⁷

For existing accounts, include new business from renewals, repeat business, or growth.⁸ Keep each path as a separate assumption, so a renewal does not look like fresh expansion and a speculative use case does not look contracted.

Map expansion

Find routes beyond the current baseline. Each route needs an identifiable buyer, business unit, entity, or use case that could receive value.

When two business units receive value from the product, the team can make the case for a deal across the account.⁹ Expansion use cases can create a bigger revenue base inside the account.¹⁰ Map where the current foothold can lead and record the condition that opens each route.

Sales should help customer success understand an account's expansion potential, strategic importance, product footprint opportunity, and internal reference value.¹¹ Include these fields in the account estimate even when the immediate deal is small. They show whether the account has room for a broader commercial outcome.

Ask, "What percentage of growth does each account have?"¹² Use the answer to separate accounts with a large ceiling and little movement from accounts where growth already has a visible path.

Test reachability and effort

A ceiling supports prioritization when you can describe the route from the current foothold to the larger deal. Test that route before assigning heavy coverage.

Ask, "If I go do that, is there a run or a track to a larger deal somewhere else within that company?"¹³ Look for a specific next conversation, internal sponsor, or business use that would open the route. If you cannot name what comes after the first win, keep the account's reachable value below its theoretical ceiling.

Compare the expected route with the work required to pursue it. Use the estimate to decide whether the account gets active attention, a lighter touch, or a place in a later review.

Calculate the estimate

Account model

Current baseline

Reachable expansion amount

Ceiling for wider adoption

Parts of account model:

• Current baseline
• Reachable expansion amount
• Ceiling for wider adoption

Start with a simple calculation, then add complexity only when it changes the decision. The model should show which assumption produces the result.

Start with "Revenue = Price × Quantity sold".¹⁴ For an account with several products, calculate revenue for each product line separately and add the results.¹⁵ For recurring sales, calculate customers multiplied by average revenue per user, then annualize the result.¹⁶

An account model can hold a current baseline, a reachable expansion amount, and a ceiling for wider adoption. Keep quantities, prices, product lines, and expansion assumptions visible. When you turn account potential into a pipeline scenario, calculate monthly revenue from monthly opportunities, current win rate, and average deal value.¹⁷

Use sensitivity views for win rate, target requirements, and price protection.¹⁸ Keep opportunity volume and deal value visible so you can see which assumption changes the result.¹⁹ If a small change in one assumption moves the estimate sharply, validate that assumption first.

Make the coverage call

The finished estimate should change what you do with the account. Compare the ceiling with the current baseline, the expansion route, and the effort required to reach it.

Direct budgets and sales resources toward prospects with the greatest need for the offering.²⁰ For outbound, the account with the highest ceiling will not automatically win. The better target is the account where the reachable value and the route to it are both clear.

Record the next validation action beside the estimate. It might be confirming the account structure, testing a second use case, or finding whether another business unit has a reason to buy. Recalculate when that action changes the baseline or opens a new route.

What not to do

Check these errors when you turn account information into a revenue estimate.

• Do not use account count as a measure of potential. It treats a 40-person prospect and a 4,000-person prospect as equivalent units.²¹
• Do not add implementation fees, professional service fees, hardware, or discounts to MRR.²²
• Use qualified opportunities as the basis for the estimate, and leave raw leads out.²³
• Compare the assumptions without treating a sensitivity scenario as a forecast.¹⁸
• Do not claim net revenue changes when future commodity prices and trade projections are unavailable to the analysis.²⁴