When to use
Use for a portfolio or named-account review when the requester wants possible upsell, cross-sell,
or seat-expansion opportunities grounded in account evidence and a customer-expressed need.
Confirm the account scope and review as-of date before scanning.
Do not use this skill to edit CRM records, create pipeline commitments, contact a customer, quote
pricing, promise an expansion, or decide commercial strategy. Not for renewal negotiation or a
health-score decision; use renewal-prep or health-score for those jobs.
Inputs and source discipline
- Establish account identity, scope, and
as-of date. Record each source, source date, date
checked, unit/currency, and account identifier. Prefer current customer statements and signed
entitlements, then CRM/account facts, product telemetry, support records, and dated internal
notes. Do not merge conflicting accounts by name alone.
- Keep four evidence lanes separate:
- account evidence: observed product, seat, usage, contract, or organizational facts;
- expressed need: a dated customer request, pain point, or desired outcome, quoted or cited;
- product fit: a source-backed mapping from that need to an available product capability;
- speculation: an untested hypothesis, never presented as customer intent.
- Show potential value only when price, quantity, currency, and calculation basis are sourced
and comparable. Otherwise write
unknown and explain the missing input; never invent potential
value, likelihood, budget, percentage, owner, or urgency.
Method
- Work read-only and deduplicate account records before ranking. Preserve account-level source
references and label whether each statement is observed, expressed, fit-checked, or speculative.
- For each candidate, test product fit against a dated, authoritative capability or entitlement
source. A usage gap can be evidence for investigation but is not an expressed need. If the
capability or eligibility is not verified, mark fit unknown.
- Classify the candidate as upsell, cross-sell, or seat expansion only when the account evidence
supports that category. Rank by evidence completeness and sourced timing signals, not by an
invented probability. Treat any suggested next step as a recommendation for human review.
- Calculate an aggregate only when all included values share a documented unit, currency,
period, and basis. If any value is unknown or incomparable, report the aggregate as unavailable
rather than filling the gap.
Truth and uncertainty rules
Use observed for account evidence directly supported by a source, inferred for a fit
interpretation, unknown for missing or unverified need/fit/value, stale for evidence outside
the relevant freshness or as-of period, and contradictory when sources disagree. Keep
speculation visibly separate from evidence, state confidence, and never infer intent from silence
or usage alone. Never invent dates, metrics, owners, intent, money, percentages, causes, status,
or evidence. Recommendations are not human decisions.
Output contract
Return a review containing:
- account scope,
as-of date, source register, source dates, and account identifiers;
- one row per candidate with separate account evidence, expressed need, product fit, and
speculation fields;
- sourced potential value and calculation basis, or explicit
unknown/unavailable value;
- category, evidence completeness, confidence, stale inputs, unknowns, and contradictions;
- human-review questions and non-binding recommendations, with no invented pipeline total; and
- a clear statement of what was not checked or cannot be concluded.
Safety and write boundaries
Remain read-only by default. Do not change CRM, account pages, opportunities, pricing, forecasts,
or customer records. If a CRM change, outreach, quote, pricing action, or other commercial action
is requested, preview the exact target, fields/content, audience, and side effects; redact secrets
or unapproved personal/confidential content; wait for explicit confirm from the authorized
human owner; then perform only that approved action. A recommendation never authorizes a human
or commercial decision.
Verification and recovery
Read back account identifiers, evidence citations, product-fit references, and any value formula.
Reconcile duplicate accounts, category counts, units, currency, period, and aggregate totals;
fail closed on mismatches. If a source or CRM read fails, preserve the review, mark the affected
candidate unknown or blocked, record the failure, and rerun after refresh. Never silently merge
accounts or turn speculation into a CRM fact.
1---2name: expansion-opportunities3description: Use when reviewing customer accounts for evidence-backed expansion hypotheses based on current usage, product fit, and expressed needs. Not for renewal strategy or negotiation; use renewal-prep.4---56<!-- Generated from `.claude/skills/_available/customer-success/expansion-opportunities/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. -->78## When to use910Use for a portfolio or named-account review when the requester wants possible upsell, cross-sell,11or seat-expansion opportunities grounded in account evidence and a customer-expressed need.12Confirm the account scope and review `as-of` date before scanning.1314Do not use this skill to edit CRM records, create pipeline commitments, contact a customer, quote15pricing, promise an expansion, or decide commercial strategy. Not for renewal negotiation or a16health-score decision; use renewal-prep or health-score for those jobs.1718## Inputs and source discipline19201. Establish account identity, scope, and `as-of` date. Record each source, source date, date21 checked, unit/currency, and account identifier. Prefer current customer statements and signed22 entitlements, then CRM/account facts, product telemetry, support records, and dated internal23 notes. Do not merge conflicting accounts by name alone.242. Keep four evidence lanes separate:25 - **account evidence:** observed product, seat, usage, contract, or organizational facts;26 - **expressed need:** a dated customer request, pain point, or desired outcome, quoted or cited;27 - **product fit:** a source-backed mapping from that need to an available product capability;28 - **speculation:** an untested hypothesis, never presented as customer intent.293. Show potential value only when price, quantity, currency, and calculation basis are sourced30 and comparable. Otherwise write `unknown` and explain the missing input; never invent potential31 value, likelihood, budget, percentage, owner, or urgency.3233## Method34351. Work read-only and deduplicate account records before ranking. Preserve account-level source36 references and label whether each statement is observed, expressed, fit-checked, or speculative.372. For each candidate, test product fit against a dated, authoritative capability or entitlement38 source. A usage gap can be evidence for investigation but is not an expressed need. If the39 capability or eligibility is not verified, mark fit unknown.403. Classify the candidate as upsell, cross-sell, or seat expansion only when the account evidence41 supports that category. Rank by evidence completeness and sourced timing signals, not by an42 invented probability. Treat any suggested next step as a recommendation for human review.434. Calculate an aggregate only when all included values share a documented unit, currency,44 period, and basis. If any value is unknown or incomparable, report the aggregate as unavailable45 rather than filling the gap.4647## Truth and uncertainty rules4849Use `observed` for account evidence directly supported by a source, `inferred` for a fit50interpretation, `unknown` for missing or unverified need/fit/value, `stale` for evidence outside51the relevant freshness or `as-of` period, and `contradictory` when sources disagree. Keep52speculation visibly separate from evidence, state confidence, and never infer intent from silence53or usage alone. Never invent dates, metrics, owners, intent, money, percentages, causes, status,54or evidence. Recommendations are not human decisions.5556## Output contract5758Return a review containing:5960- account scope, `as-of` date, source register, source dates, and account identifiers;61- one row per candidate with separate account evidence, expressed need, product fit, and62 speculation fields;63- sourced potential value and calculation basis, or explicit `unknown`/unavailable value;64- category, evidence completeness, confidence, stale inputs, unknowns, and contradictions;65- human-review questions and non-binding recommendations, with no invented pipeline total; and66- a clear statement of what was not checked or cannot be concluded.6768## Safety and write boundaries6970Remain read-only by default. Do not change CRM, account pages, opportunities, pricing, forecasts,71or customer records. If a CRM change, outreach, quote, pricing action, or other commercial action72is requested, preview the exact target, fields/content, audience, and side effects; redact secrets73or unapproved personal/confidential content; wait for explicit `confirm` from the authorized74human owner; then perform only that approved action. A recommendation never authorizes a human75or commercial decision.7677## Verification and recovery7879Read back account identifiers, evidence citations, product-fit references, and any value formula.80Reconcile duplicate accounts, category counts, units, currency, period, and aggregate totals;81fail closed on mismatches. If a source or CRM read fails, preserve the review, mark the affected82candidate unknown or blocked, record the failure, and rerun after refresh. Never silently merge83accounts or turn speculation into a CRM fact.