Share of Wallet by Key Account

Goal of the analysis:

Estimate what portion of a key account’s total addressable spend in your category you currently capture, and quantify the “white space” remaining. Share of Wallet (SOW) by Key Account helps executives prioritize expansion targets, shape enterprise agreements and bundles, allocate seller/CSM capacity, and set realistic growth plans at the account level. A disciplined approach—using triangulated wallet estimates and confidence scoring—avoids wishful thinking and converts account plans into specific, sequenced cross-sell and upsell motions.

Data required:

• Internal revenue and CRM data:
  • Current ARR/MRR by account × product family/SKU; term, renewal date, co-term groups, discount %.
  • Installed footprint: seats/licenses provisioned vs. purchased; consumption (e.g., API calls, storage, messages).
  • Opportunity pipeline and closed-lost by product; contact roles and penetrated business units/regions.
• Account firmographics and structure:
  • Global/parent-child hierarchy, business units, regions/sites, employee counts by function, revenue, number of locations.
  • Technology stack and adjacent tools (from technographics vendors), key initiatives, M&A activity.
• External spend and market intelligence (where available):
  • Procurement/RFP data, public filings, analyst/benchmark ratios (category spend as % of revenue or per employee).
  • Third-party intent/usage signals, vendor presence (competitors) and estimated contract values where observable.
• Wallet model drivers (product-specific):
  • Seatable population (eligible users) by persona/function; device counts; transaction/volume drivers (e.g., monthly jobs, data volumes).
  • Adoption norms (penetration rates) and average price/volume multipliers by segment/industry.
• Normalization and governance:
  • Currency FX at contract dates, product taxonomy, segment/industry definitions, account naming standards.
  • Confidence scoring framework for wallet estimates and assumptions library.

Detailed step-by-step instruction on how to conduct the analysis:

1. Define scope and category.
   • Specify which spend you’re estimating (e.g., “Data Integration Platform” or “Sales Enablement Suite”).
   • Map your products to that category and note adjacent categories you may cross-sell.
2. Assemble the account master.
   • Consolidate parent/child entities; list business units, regions, and site counts; attach employee counts by function.
   • Pull your current ARR by product and installed footprint (licenses/usage) with renewal dates and discounts.
3. Build wallet estimation models (two-track).
   • Bottom-up (preferred): Wallet = Eligible users (by persona) × Target penetration % × Price/user (or) Volume driver × Price/unit.
   • Top-down (triangulation): Wallet = Benchmark spend ratio × Account size (e.g., $/employee × employee count, or % of revenue).
   • Document assumptions per product family and segment (e.g., penetration norms, price bands).
4. Triangulate with external intelligence.
   • Incorporate known competitor presence and any public contract values or RFP ranges.
   • Use technographics/intent to validate product adjacencies and likely adoption depth.
5. Calibrate and assign confidence.
   • Back-test the model on 5–10 reference accounts where wallet is well known; tune penetration and price assumptions.
   • Assign a confidence score (High/Med/Low) based on data completeness and external validation.
6. Compute SOW and white space.
   • SOW % (overall) = Your ARR in category ÷ Estimated Account Wallet.
   • White Space $ = Estimated Account Wallet − Your ARR.
   • Repeat by product family and by business unit/region to localize opportunity.
7. Identify penetration gaps and attach paths.
   • Compare seatable population vs. licensed seats; highlight under-penetrated personas or sites.
   • Map cross-sell adjacencies (anchor → module) with expected attach rates and prerequisites (integrations, adoption thresholds).
8. Time-bound the opportunity.
   • Overlay renewal dates (yours and known competitor terms where possible), budget cycles, and key initiatives to sequence pursuits.
   • Tag co-term opportunities to simplify estates and accelerate consolidation.
9. Prioritize and create account plays.
   • Rank white space by value × confidence × timing; select 2–3 focus plays per key account (e.g., “20% seat expansion in EMEA by Q3,” “Analytics add-on to NA BU”).
   • Define stakeholders, proof assets, pricing/packaging, and give–get guardrails per play.
10. Governance and refresh.
    • Refresh wallet models quarterly or upon material org changes; audit assumptions during QBRs.
    • Instrument feedback loops from wins/losses to improve penetration and price benchmarks.

Format of the output of analysis:

• Executive account table: current ARR, estimated wallet, SOW %, white space $, by product family and by BU/region; confidence score; key renewal dates.
• White-space matrix: rows = product families, columns = BUs/regions; cells show white space $ and penetration %.
• Waterfall/bridge: wallet → competitor/alt spend → your ARR → white space by driver (seats, modules, geos).
• Portfolio scatter: ARR vs. SOW % by key account (bubble = white space $) to prioritize expansion focus.
• Account plan slide: 2–3 plays with stakeholders, proof assets, pricing/terms strategy, and next best actions.

How to interpret results:

• High SOW (≥60–80%) with limited white space: Near-saturation in current category; focus on retention, price integrity, and cross-sell into adjacencies or new BUs.
• Moderate SOW (20–50%) in strategic accounts: Strong expansion potential; prioritize multi-threading, executive sponsorship, bundles, and co-term consolidation.
• Very low SOW (<20%) after long tenure: Competitive entrenchment or product fit gap; reassess positioning, proof, and potential for targeted land-and-expand in receptive BUs.
• SOW by product uneven: Anchor product saturated while adjacencies lag—codify attach plays and prerequisites (integrations, data migration).
• Confidence matters: Treat low-confidence large white space cautiously; validate with discovery and procurement intel before committing forecast.
• Trend view: Rising SOW quarter-over-quarter signals effective attach; flat SOW despite adoption growth may imply pricing or packaging constraints.

Steps a company can take to improve on this measure:

• Account strategy and coverage:
  • Map stakeholders across BUs/regions; set multi-threading minimums and executive sponsor assignments for top accounts.
  • Run executive business reviews (EBRs) tied to outcomes; align on a multi-year roadmap and co-termed estate.
• Offers, pricing, and terms:
  • Create enterprise agreements/bundles that monetize breadth (good/better/best suites) with usage floors and overage protection.
  • Introduce site/BU packs and phased rollouts; use give–get guardrails (term/volume for price) to preserve margin.
• Product and adoption plays:
  • Define adoption thresholds that trigger expansion (PQL/PQA) and surface them to AEs/CSMs.
  • Provide integration accelerators and migration tooling to remove cross-sell friction.
• Partner and ecosystem:
  • Leverage partners for footprint expansion in underpenetrated regions/BUs; align services for faster deployments.
  • Co-sell with adjacent vendors where joint value raises attach propensity.
• Data and governance:
  • Institutionalize wallet models with documented assumptions and confidence scoring; refresh quarterly.
  • Instrument account plans with SOW KPIs and white-space milestones; review in QBRs.
• Scenario guidance:
  • If SOW is low but adoption of the anchor is high, launch module attach plays with proof kits and outcome-based pricing.
  • If SOW is low and adoption is patchy, fix onboarding and integration before pushing expansion.
  • If SOW is high but margin thin, prioritize price harmonization and packaging migration over pure volume growth.

Benchmark comparisons:

General benchmarks (directional):

• For a landed “anchor” product in enterprise software, initial SOW often starts at 10–30% of the account wallet; leaders grow to 40–60%+ within 12–24 months through attach and regional rollout.
• Suite-level SOW (multiple families) above 60–70% in true strategic accounts is achievable with enterprise agreements and strong adoption.
• Penetration benchmarks: 50–70% of seatable population for core users; 20–40% for extended/adjacent personas pre-enterprise agreement.

Segment- or industry-specific benchmarks:

• SMB divisions within enterprises saturate faster on seats but have lower module attach; large regulated industries show slower seat penetration but higher multi-product attach when approved.
• Manufacturing/retail show site-by-site rollouts (slower but steady SOW growth); tech/services adopt faster with higher attach potential.
• Internal benchmarks: build 4–8 quarter SOW baselines for top 50–200 accounts by segment/industry; use top quartile SOW growth and attach rates as operating targets, with confidence bands. Where external wallet data is scarce, construct internal proxies (seats per employee, volume per site) and calibrate against known-reference accounts.