Blog · Wallet share and penetration · SaaS

Whitespace as a number, reconciled to ARR: product fit for SaaS accounts

How a SaaS company turns the hand-coloured whitespace spreadsheet into a computed, valued list per account: fit from what similar customers own, the gap at list price, untouched accounts from CRM activity, AE capacity, and the reconciliation to ARR.

By CoviragePublished 16 September 20263 min read

The short answerWhitespace for a SaaS account is the products the account does not own that customers of the same size and segment usually own, valued at list price or at what the account already pays per product. Compute it from billing joined to the CRM, define fit from your own customer base, add untouched accounts from activity history and AE capacity from account counts, and assert that account ARR sums to the reported ARR before the list goes out.

Every SaaS revenue team has a whitespace map. Almost every one is a spreadsheet with cells coloured by hand in the week before the QBR, and it is wrong by the time the meeting starts. The information to compute it is in billing and the CRM. This guide shows how to turn it into a number per account that reconciles to ARR.

The three measures

Whitespace, per account:

Whitespace = products in the account's fit set − products owned, valued

Untouched, per account:

Untouched = no logged activity in the last N days

Capacity, per AE or CSM:

Load = accounts owned ÷ the accounts one person can work

The third is what makes the first two actionable. A whitespace list that exceeds the AE's capacity is a list that will not be worked, and the ranking within capacity is what matters.

The rows you need

Billing: ARR by account and product. From Stripe, the billing system, or a finance export.
CRM: accounts with segment, size, owner, and activity history with dates. Salesforce or HubSpot exports.
Product list: the products and their list prices.

Account identifiers throughout.

Defining fit from your own base

Band accounts by size and segment.
For each band, the share of accounts owning each product.
The fit set is every product owned by more than half the band, or a threshold product marketing sets.

A new product with low adoption never enters any fit set by this rule. Product marketing can declare it in the set for a band, and the report shows that override as a labelled assumption.

The roll-up

Account by product: owned, ARR.
Account: products owned, fit set, whitespace, valued; last activity, untouched flag.
AE or CSM: accounts, ARR, whitespace total, untouched count, load against capacity. Assert that account ARR sums to the owner's book.
Segment, region, company: assert up to the reported ARR.

reported ARR = Σ segments = Σ owners = Σ accounts = Σ products

A product renamed in billing, or an account that changed owner mid-quarter without a date, each break one equality.

A worked example

Mid-market band, fit set of Core, Analytics and Automation. One account.

Product	Owned	ARR	In fit set	Gap at list	Gap at account rate
Core	Yes	$48,000	Yes
Analytics	No		Yes	$30,000	$24,000
Automation	No		Yes	$36,000	$28,800
Enterprise SSO	No		No

Whitespace: two products, $66,000 at list, $52,800 at the account's rate per product. Last logged activity: 104 days. The account is on the AE's untouched list and near the top of their whitespace list at once, which is the account to open Monday with.

Where it goes wrong

Fit measured against the whole catalogue. Every small account shows whitespace it could never buy, and the AE stops reading. Fit per band, always.

Billing and CRM identifiers differ. The account in billing is the paying entity; the account in the CRM is the logo. Keep a mapping table and count the accounts that do not join; they are the ones no list can reach.

Owner changes without dates. An account that moved between AEs mid-quarter appears in both books. The owner assertion fails. The fix is the transfer date in the CRM.

Usage-driven churn ignored. An account with full product ownership and falling usage is not whitespace; it is risk. Load usage as another file and let it flag accounts before the renewal.

Every Monday, reconciled to ARR

Mapped once, billing and the CRM export produce the same three lists per owner every week, reconciled to ARR, with capacity applied. Covirage builds this from the exports as they are. The SaaS page describes the setup, and you can upload a sample billing export and see the roll-up on your own rows.

Questions people ask

How is fit defined?

From your own base. Band customers by size and segment, and a product is in the band's fit set if more than half the band owns it. An account below its band's fit set has whitespace; one above it is a reference customer for the band. Product marketing can override the rule per product.

Should the gap be valued at list or at the account's current spend?

Both are defensible; say which. List price gives the upper bound. The account's current spend per product gives what a similar deal has actually closed for. The second is usually the one sales leadership believes.

Do we need usage data?

No. Billing and the CRM give whitespace and untouched accounts. Usage adds a risk signal and a fit signal, and can be loaded later as another file.

Related reading

Forecast and pipeline · SaaS

Expansion pipeline against whitespace: are the reps working the gaps the data found?

How a SaaS revenue team checks whether its expansion pipeline covers the whitespace the account data shows: expansion opportunities per account against the account's valued whitespace, the accounts with large gaps and no open opportunity, the opportunities on accounts with no gap, the share of whitespace value under active pursuit per rep, and the identity that ties expansion pipeline to the whitespace grid.

16 Sept 20262 min read Board and management reporting · SaaS

Net revenue retention by cohort, reconciled to ARR

How a SaaS finance or revenue team computes net revenue retention per signing cohort from the subscription ledger, the four movements that make it up, expansion, contraction, churn and reactivation, the identity that ties every cohort's movements back to the ARR bridge, and why a single company NRR figure hides the cohort that is quietly failing.

16 Sept 20262 min read Forecast and pipeline · SaaS

Seat utilisation before renewal: active seats against contracted seats in SaaS

How a SaaS revenue team turns product usage and the contract register into a renewal risk and expansion list: active seats against contracted seats per account, the utilisation trend over the last two quarters, the accounts under a threshold with a renewal inside 120 days, the accounts at or above their seat cap, and the identity that ties the seat table to ARR.

16 Sept 20262 min read Forecast and pipeline · SaaS

Ten questions a SaaS CRO asks about the base, and the table that answers each

The ten questions a SaaS chief revenue officer puts to the sales and success teams about existing customers, what is net revenue retention by cohort and which cohort broke, which accounts renew inside 120 days under their seats, is the expansion pipeline on the accounts with whitespace, which onboardings are behind the milestone that predicts renewal, what is whitespace reconciled to ARR, which accounts are over their cap, which accounts have gone untouched, what do bookings, billings and revenue each say, which deals slipped three times, and what changed, each with the table from the subscription ledger, the usage export and the CRM, and the answer to send back.

16 Sept 20262 min read