agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/expansion-opportunity-finder/SKILL.md

expansion-opportunity-finder

Skill13 starsChanged 25 days agoMITView on GitHub

Use this skill when you want to grow revenue from existing customers: \"find upsell and cross-sell opportunities\", \"which customers are ready to expand\", \"net revenue retention plan\", \"expansion playbook\". Scores customer accounts on usage, health, growth signals and whitespace (teams, products and seats not yet bought), finds the strongest expansion opportunities with the evidence behind each, and writes the value-review outreach that opens the conversation without sounding like an upsell.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Use this quarterly or before renewals.

    line 16
  2. Distinctive:

    Every opportunity has evidence: usage numbers, a growth signal, an interested team.

    line 53
  3. Distinctive:

    MUST check health before recommending expansion.

    line 59
  4. Distinctive:

    MUST base opportunities on actual usage and signals.

    line 60
  5. Distinctive:

    NEVER pressure customers with artificial limits or surprise price increases.

    line 61

≈ “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

Use this quarterly or before renewals. Expansion is usually the cheapest revenue a company can win, but only from customers who are getting value; pushing more onto unhappy customers accelerates churn.

Inputs

  • Customers: plan, seats or units, contract value, renewal date.
  • Usage: active users vs paid seats, feature adoption, trends.
  • Health: support tickets, satisfaction scores, champion status, payment issues.
  • Products and pricing: what else could they buy.

The play

1. Check health first

Exclude or flag accounts with falling usage, unresolved escalations, a departed champion or payment problems. They need a save plan, not an upsell.

2. Score expansion signals

SignalExampleWeight
Usage near limits90%+ of seats or volume usedHigh
Growth at the companyHiring, funding, new locationsHigh
New team showing interestUsers from another department signing up or askingHigh
Strong adoption of core featuresReady for an advanced tierMedium
Successful outcomes documentedA result they can repeat elsewhereMedium
Renewal in 60-120 daysNatural moment to resizeTiming

3. Map the whitespace

Per account: which teams, regions, sites or products could use it and do not yet. Sister companies and subsidiaries count.

4. Open with a value review

The best expansion conversation starts with what the customer got: results so far, usage, what peers do next. The expansion idea follows from their goals, not from your quota.

Hi Priya, it's been a year since rollout, so I put together a short review: close time down from 9 days to 4, and your team is now running reconciliation for all three entities. Two other finance teams in your group asked about it last month. Would a 30-minute review with you be useful before planning season?

5. Route and track

Account managers or customer success own the conversation; sales joins for new buyers. Track expansion pipeline and net revenue retention by segment.

What good looks like

  • Every opportunity has evidence: usage numbers, a growth signal, an interested team.
  • Unhealthy accounts get a save plan before any expansion pitch.
  • The common mistake is a blanket "upgrade now" campaign to all customers, which annoys the ones not getting value.

Rules

  • MUST check health before recommending expansion.
  • MUST base opportunities on actual usage and signals.
  • NEVER pressure customers with artificial limits or surprise price increases.

Example prompts

  • "Here's our customer export with usage. Who's ready to expand and why?"
  • "Map whitespace across our top 30 accounts."
  • "Write value-review emails for customers renewing next quarter."

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.