Expansion Opportunity

Expansion opportunities exist only in the heads of account managers. No one documents which customers might buy more, what products they'd need, or what signals suggest readiness. 'I think Acme might want the analytics module, but I haven't written that down anywhere.' When an AM leaves, every pipeline expansion opportunity vanishes with them.

None — AI cannot identify, score, or prioritize expansion opportunities because no expansion opportunity records exist in any system.

Some expansion opportunities are logged in the CRM as informal notes or free-text opportunity descriptions. One AM writes 'might want enterprise tier' in the account notes. Another creates an opportunity record but leaves most fields blank. There's no standard definition of what constitutes an expansion opportunity versus a renewal versus a new deal. 'Everyone logs opportunities differently — or not at all.'

AI can surface expansion opportunity mentions from CRM notes through text search, but cannot reliably score, prioritize, or compare opportunities because the records lack consistent structure, required fields, and standardized definitions.

Expansion opportunities have a structured record format in the CRM with standard fields — account, product, estimated value, stage, next steps, and close date. Stage definitions are documented so 'qualified' means the same thing to every AM. But the expansion opportunity record is self-contained with no links to the account's usage patterns, health score, or contract terms. Context about why this customer is ripe for expansion lives in the AM's head.

AI can generate pipeline reports, forecast expansion revenue, and flag stale opportunities. Cannot assess expansion readiness or recommend which opportunities to prioritize because the connection between opportunity records and account context (usage, health, contract) isn't formalized.

Expansion opportunity records are connected knowledge assets. Each opportunity links to the account's product usage metrics, health score components, contract terms, and engagement history. An AM can query 'show me all expansion opportunities where the customer's feature usage exceeds their current tier limits and their health score is above 80' and get a contextualized, reliable answer.

AI can score expansion opportunities against account context, recommend optimal timing based on usage patterns and contract cycles, and predict close probability by correlating opportunity characteristics with historical outcomes. Cannot dynamically discover new expansion signals that aren't in the defined relationship model.

The expansion opportunity is a formal entity in a typed business model. Opportunity records have validated relationships to account profiles, product catalogs, usage metric definitions, and revenue models. An AI agent can reason: 'This account's API call volume exceeds their current plan by 40%, they've activated 3 features only available at the next tier, and their contract renews in 90 days — this is a high-confidence expansion opportunity for the enterprise tier upgrade.'

AI can autonomously identify expansion opportunities from account signals, generate opportunity records with supporting evidence, recommend pricing strategies, and predict close timelines with high accuracy. Human judgment needed for strategic account negotiations and non-standard deal structures.

Expansion opportunity records are self-defining entities that evolve in real-time. The system continuously identifies new expansion signals from account behavior, auto-generates opportunity records when threshold conditions are met, and dynamically adjusts opportunity scoring models based on closed-deal outcomes. The expansion pipeline writes and prioritizes itself from live account signals.

Can autonomously discover, define, score, and prioritize expansion opportunities across the entire customer base with real-time signal processing. Opportunity models evolve themselves from outcomes, requiring no manual pipeline management.

Ceiling of the CMC framework for this dimension.