agentleFS
stephenroganstephenrogan/csm-skills/skills/expansion-opportunity-scorer/SKILL.md

expansion-opportunity-scorer

Skill0 starsChanged 8 months agoMITView on GitHub

Scores expansion readiness for a customer account by assessing adoption depth, value realisation, stakeholder alignment, commercial signals, and timing. Produces a readiness classification with the recommended expansion approach and the specific signal that triggered the assessment. Use when asked to assess expansion potential, evaluate upsell readiness, score an account for growth, determine whether a customer is ready for a commercial conversation about expansion, or when a CSM detects expansion signals and needs to decide whether and how to pursue them. Also triggers for questions about expansion timing, upsell assessment, growth readiness, when to start an expansion conversation, or evaluating whether a customer is ready to buy more.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When readiness score is 3.1+:

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Expansion Opportunity Scorer

Scores whether a customer account is ready for an expansion conversation and what type of expansion is most likely. The critical distinction: expansion readiness is not the same as expansion interest. A customer who mentions growth is interested. A customer with deep adoption, proven value, executive engagement, and budget availability is ready.

How to Use

Provide:

  • Account name, current ARR, product tier, tenure
  • The expansion signal (what triggered this assessment -- seat limit, feature request, new team interest, customer-initiated conversation)
  • Adoption depth (feature breadth, usage intensity, active users vs. licensed seats)
  • Value evidence (ROI confirmed, outcomes measured, customer-confirmed value)
  • Stakeholder alignment (is the expansion champion the same as the economic buyer? Is the decision-maker engaged?)
  • Health status (strong, healthy, at risk)
  • Commercial context (budget cycle timing, pricing history, contract terms)
  • Any blockers (open issues, unresolved concerns, competitive evaluation)

Expansion Types

TypeSignalTypical ValueComplexity
Seat expansionLicence utilisation >85%, new team forming, credential sharing10-30% ARR increaseLow -- straightforward addition
Tier upgradeUsing features at the ceiling of current tier, requesting capabilities in higher tier20-50% ARR increaseMedium -- requires value justification for the price delta
Cross-sell (new product)Customer using one product and expressing needs addressed by another30-100% ARR increaseHigh -- requires new discovery, demo, and business case
Usage expansionVolume-based pricing and usage growing beyond current band10-25% ARR increaseLow-Medium -- data-driven conversation

Readiness Scoring

Score each dimension 1-5:

Dimension1 (Not Ready)3 (Developing)5 (Ready)Weight
Adoption depthShallow usage, low feature breadth, many unused capabilitiesModerate usage, growing adoptionDeep usage, high breadth, users dependent on the product25%
Value evidenceNo ROI measured, value unprovenData-derived value, not confirmed by customerCustomer-confirmed ROI, quantifiable outcomes25%
Signal strengthNo signal -- CSM-initiated assessmentIndirect signals (usage growth, feature requests)Direct signal (customer asked about expansion, new team expressed interest)20%
Stakeholder readinessDecision-maker not engaged, no commercial relationshipChampion supportive, decision-maker aware but not engagedChampion actively sponsoring, decision-maker engaged and budget-aware20%
HealthAt risk or decliningHealthy and stableStrong and improving10%

Composite readiness score = weighted sum (1.0-5.0)

ScoreClassificationMeaningAction
1.0-2.0Not readyFocus on adoption and value realisation before commercial conversationsDeepen adoption. Build value evidence. Revisit in 60-90 days
2.1-3.0DevelopingSignals exist but foundation is not strong enough for a commercial conversationStrengthen the weakest dimension. Prepare the ground over the next 30-60 days
3.1-4.0ReadyFoundation is strong. Time to initiate the expansion conversationBuild the commercial case. Engage the decision-maker. Propose the expansion
4.1-5.0High confidenceCustomer is essentially asking for expansion. Execution risk onlyAct this week. The conversation is warm. Delaying risks losing momentum or timing

The Expansion Conversation Sequence

When readiness score is 3.1+:

Step 1: Confirm the Need (Consultative, Not Sales)

"I have noticed your team is approaching the seat limit / using features at the ceiling of your tier / expressing interest in [capability]. Can you tell me more about what is driving that?"

Why consultative: The CSM who listens to the need first and proposes second builds trust. The CSM who jumps to the upsell proposal loses the advisory position.

Step 2: Build the Case

Connect the expansion to the customer's stated goals, not to your revenue target.

FrameFor the ChampionFor the CFO
Seat expansion"Your team has outgrown the current licence. 15 people sharing 10 seats means queuing and workarounds""At current usage, the cost per active user drops with additional seats. The productivity gain per seat exceeds the incremental cost"
Tier upgrade"The advanced features you have been requesting are available in the next tier and would address [specific workflow gap]""The tier upgrade adds [specific capabilities] at a [X]% price increase. Based on current usage, the ROI on the upgrade is [X]x"

Step 3: Propose and Close

Specific, tied to their timeline, with a clear next step.

"Based on what you have shared, I recommend [specific expansion]. The annual cost would be EUR [X], bringing your total to EUR [Y]. Given your Q2 team growth, I would suggest we aim to have this in place by [date]. Can I put together a formal proposal?"

Blockers That Kill Expansion

BlockerImpactResolution Before Proposing
Unresolved support issueCustomer will not buy more from a vendor that has not fixed what they already boughtResolve the issue first. Expansion after resolution feels earned
Low adoption on current purchase"Why would we buy more when we do not fully use what we have?"Drive adoption first. Show them the value of what they already own
No value evidenceThe CFO will ask "what did we get from the last purchase?" and you cannot answerBuild the value case before the commercial case
Decision-maker not engagedThe champion is ready but the person who approves the budget has never heard from youEngage the decision-maker with value evidence before proposing expansion
Competitive evaluation underwayThe customer is evaluating whether to stay, not whether to growResolve the competitive situation first. Expansion during evaluation is tone-deaf

Output Format

## Expansion Assessment: [Account Name]
**Current ARR:** EUR [amount] | **Expansion type:** [type] | **Estimated value:** EUR [amount]

### Readiness Scores
| Dimension | Score | Evidence |
|-----------|-------|---------|
| Adoption depth | [1-5] | [data] |
| Value evidence | [1-5] | [data] |
| Signal strength | [1-5] | [data] |
| Stakeholder readiness | [1-5] | [data] |
| Health | [1-5] | [data] |

### Composite: [X.X] -- [Classification]

### Blockers
[Any blockers and resolution plan, or "None identified"]

### Recommended Approach
[Specific next action based on readiness level]

Quality Gates

  • Is the signal real? A CSM projecting expansion hope onto a neutral account wastes commercial effort and risks the relationship. Verify the signal: did the customer indicate interest or are you interpreting usage data optimistically?
  • Are blockers identified and addressed? Proposing expansion with an unresolved P1 ticket is self-sabotage
  • Is the decision-maker identified and at least aware? An expansion proposal that reaches the champion but never reaches the budget holder stalls indefinitely
  • Is the value case built? The expansion conversation is dramatically easier when you can say "your team saved X hours this quarter and the expansion would multiply that"

Principles

  • Expansion is earned, not sold. A customer who sees deep value, has broad adoption, and trusts the CSM will expand naturally. A customer who is pushed to expand before value is proven will resist and resent
  • Timing matters as much as readiness. A customer who is ready but in the middle of budget freeze will say no regardless of the score. Align with their budget cycle, not your quarter-end
  • The CSM is not a salesperson. The CSM identifies the opportunity, builds the case, and initiates the conversation. If the expansion requires commercial negotiation, involve your sales counterpart at the right moment
  • A customer who says "not now" is not saying "never." Document the signal, note the timing constraint, and revisit. The groundwork you laid makes the next conversation easier

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.