Expansion Opportunity Detector
Expansion signal spotter

Monitor existing customer accounts for upsell and cross-sell signals: team growth on LinkedIn, new job postings, product usage patterns, funding announcements, and public company news. Produces a weekly expansion opportunity list with…
--- name: expansion-signal-spotter description: > Monitor existing customer accounts for upsell and cross-sell signals: team growth on LinkedIn, new job postings, product usage patterns, funding announcements, and public company news. Produces a weekly expansion opportunity list with context and talk tracks. Chains web search, LinkedIn profile monitoring, and job posting detection. tags: [lead-generation] --- # Expansion Signal Spotter Find expansion revenue hiding in your existing customer base. Monitors accounts for signals that indicate they're ready to buy more — before they ask or before a competitor gets there first. **Built for:** CS teams and founders at early-stage companies where expansion revenue is the fastest path to growth. You already have the relationship — this skill finds the timing. ## When to Use
Overview
Find expansion revenue hiding in your existing customer base. Monitors accounts for signals that indicate they're ready to buy more — before they ask or before a competitor gets there first.
Manual install (npx, ZIP)
npx skills add gooseworks-ai/goose-skills --skill expansion-signal-spotter -g -a claude-codemkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/gooseworks-ai/goose-skills/tar.gz/615c685f34f8 \
| tar -xz -C ~/.claude/skills --strip-components=4 goose-skills-615c685f34f8/skills/sales/composites/expansion-signal-spotterNew-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/1c9d3472fdc967657776/expansion-signal-spotter.zip" -OutFile "$env:TEMP\expansion-signal-spotter.zip"; Expand-Archive "$env:TEMP\expansion-signal-spotter.zip" -DestinationPath "$HOME\.claude\skills" -ForceConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md9.1 KBskill.meta.json366 B
Read the files here
gooseworks-ai/
Show the full text273 lines
Expansion Signal Spotter
Find expansion revenue hiding in your existing customer base. Monitors accounts for signals that indicate they're ready to buy more — before they ask or before a competitor gets there first.
Built for: CS teams and founders at early-stage companies where expansion revenue is the fastest path to growth. You already have the relationship — this skill finds the timing.
When to Use
- "Which customers are ready to expand?"
- "Find upsell opportunities in our accounts"
- "Run the weekly expansion signal scan"
- "Who should I pitch [new feature/tier] to?"
- "Monitor customer accounts for growth signals"
Phase 0: Intake
Account Data
- Customer list — CSV or sheet with: company name, domain, primary contact LinkedIn URL, current plan/tier, MRR/ARR, seats/usage
- Product tiers — What plans exist? What triggers an upgrade? (e.g., "Pro → Enterprise at 50+ seats")
- Cross-sell products — Any add-ons or adjacent products you can sell?
Signal Configuration
- Expansion triggers — What signals mean "ready to buy more" for your product?
- Team growth (new hires in relevant roles)
- Funding announcement
- Usage hitting plan limits
- New department/use case interest
- Champion promoted (more budget authority)
- Key contacts to monitor — LinkedIn URLs of champions, decision-makers per account (if available beyond primary)
Filters
- Minimum account value — Only scan accounts above $X MRR? (Focus effort)
- Accounts to exclude — Any accounts in active churn risk, paused, or in dispute
Phase 1: Signal Detection
1A: Team Growth Signals
For each customer, search for hiring activity:
Search: "[company name]" hiring OR "we're hiring" OR "join our team"
Search: site:linkedin.com/jobs "[company name]" [relevant role keywords]
Search: "[company name]" "head of" OR "director of" OR "VP" [your product's domain]
Signals to detect:
| Signal | What It Means | Expansion Play |
|---|---|---|
| Hiring in your product's domain | Growing the team that uses you | More seats / higher tier |
| New leadership hire | Budget holder arrived, will evaluate stack | Executive alignment meeting |
| Hiring in adjacent team | New department could use your product | Cross-sell / new use case |
| Rapid headcount growth | Scaling fast, needs to scale tools too | Volume upgrade |
1B: Funding & Financial Signals
Search: "[company name]" funding OR raised OR "series" OR investment 2026
Search: "[company name]" revenue OR growth OR expansion
| Signal | What It Means | Expansion Play |
|---|---|---|
| New funding round | Cash in bank, expanding everything | Premium tier / annual contract |
| Revenue milestone | Business doing well, likely investing in tools | ROI-focused expansion pitch |
| Acquisition | New parent company = new budget | Enterprise plan / multi-team |
1C: Product Usage Signals (if usage data available)
From internal data, flag:
| Signal | Threshold | Expansion Play |
|---|---|---|
| Approaching plan limit | >80% of seats/usage quota | Proactive upgrade offer |
| New feature adoption | Started using a feature in higher tier (via trial/beta) | Convert trial to paid |
| Power user emergence | 1+ users with 3x average usage | Champion for internal expansion |
| Multi-team usage | Users from 2+ departments | Department-level deal |
| API usage growth | API calls trending up month-over-month | Usage-based tier upgrade |
1D: Public Signal Monitoring
Search: "[company name]" launch OR "new product" OR partnership OR expansion
Search: "[company name]" "[your product category]" OR "[related use case]"
| Signal | What It Means | Expansion Play |
|---|---|---|
| New product launch | May need your product for the new line | New use case pitch |
| Geographic expansion | Growing into new markets | Multi-region / additional seats |
| Partnership announced | Business growing, more complexity | Higher tier for scale |
| Competitor of yours mentioned | Evaluating alternatives | Retention + upgrade pre-empt |
1E: Champion & Stakeholder Signals
If monitoring champion LinkedIn profiles:
Search: "[champion name]" promoted OR "new role" OR "excited to announce"
| Signal | What It Means | Expansion Play |
|---|---|---|
| Champion promoted | More authority, bigger budget | Propose expansion aligned to new scope |
| Champion left | Risk + opportunity (new person = fresh pitch) | Onboard new contact, re-pitch value |
| New exec joined | Potential new sponsor | Executive briefing |
Phase 2: Opportunity Scoring
Score each expansion opportunity:
Expansion Score = Signal Strength × Account Value × Timing
Signal Strength (1-5):
5 = Approaching plan limit + funding + team growth (multiple signals)
4 = Strong usage signal + one external signal
3 = One strong external signal (funding, hiring)
2 = Usage trending up, no external confirmation
1 = Weak or single minor signal
Account Value (multiplier):
2.0x = Top 20% accounts by MRR
1.5x = Mid-tier accounts
1.0x = Smaller accounts
Timing (multiplier):
2.0x = Signal detected this week (fresh)
1.5x = Signal detected this month
1.0x = Signal older than 30 days
Opportunity Tiers
| Tier | Score | Action |
|---|---|---|
| Hot | 15+ | Schedule expansion call this week |
| Warm | 8-14 | Send value-add touchpoint, plant expansion seed |
| Watch | 3-7 | Add to next QBR agenda, monitor |
Phase 3: Talk Track Generation
For each Hot and Warm opportunity, generate:
ACCOUNT: [Company Name]
CURRENT PLAN: [Plan] — $[MRR]/mo
EXPANSION TYPE: [Upsell / Cross-sell / Volume increase]
ESTIMATED EXPANSION: $[additional MRR]/mo
SIGNALS:
- [Signal 1] — [Source + date]
- [Signal 2] — [Source + date]
EXPANSION OPPORTUNITY:
[2-3 sentences: What should they buy and why now?]
TALK TRACK:
"[Opening line — connects the signal to their business goals, not your quota]"
"[Value bridge — how the expansion directly helps with what they're already trying to do]"
"[Soft ask — suggest next step without pressure]"
TIMING: [Why now is the right time — tied to signal]
RISK: [What could block this — budget freeze, champion change, etc.]
Phase 4: Output Format
# Expansion Signal Report — Week of [DATE]
Accounts scanned: [N]
Total expansion pipeline identified: $[X] additional MRR
---
## Summary
| Tier | Opportunities | Potential MRR |
|------|--------------|---------------|
| 🔥 Hot | [N] | $[X]/mo |
| 🟡 Warm | [N] | $[X]/mo |
| 👀 Watch | [N] | $[X]/mo |
---
## 🔥 Hot Opportunities
### [Company 1] — Current: $[X]/mo → Target: $[Y]/mo (+$[Z])
**Signals:** [list]
**Expansion type:** [Upsell to Enterprise / Add 20 seats / Cross-sell analytics]
**Talk track:** "[scripted opener]"
**Next step:** [Specific action + date]
### [Company 2] — ...
---
## 🟡 Warm Opportunities
### [Company] — Current: $[X]/mo | Signal: [brief]
**Recommended touchpoint:** [What to do — e.g., "Send case study of similar customer who expanded"]
---
## 👀 Watch List
| Account | Signal | Next Check |
|---------|--------|------------|
| [Name] | [Signal] | [Date] |
---
## Trends
- [N] accounts showing team growth signals (potential seat expansion)
- [N] accounts approaching usage limits
- [N] accounts with new funding (potential tier upgrade)
## Expansion Playbook Priority
This week, focus on:
1. **[Account]** — [Why: highest value + strongest signal]
2. **[Account]** — [Why]
3. **[Account]** — [Why]
Save to the current working directory or wherever the user prefers (e.g., expansion/expansion-signals-[YYYY-MM-DD].md).
Scheduling
Run weekly:
0 8 * * 2 python3 run_skill.py expansion-signal-spotter
Cost
| Component | Cost |
|---|---|
| Web search (hiring, funding, news) | Free |
| LinkedIn monitoring (if using linkedin-profile-post-scraper) | ~$0.50-1.00 |
| Job posting detection (if using job-posting-intent) | ~$0.50 |
| All analysis and talk tracks | Free (LLM reasoning) |
| Total | Free — $1.50 |
Tools Required
- web_search — for funding, news, hiring signals
- fetch_webpage — for career pages and announcements
- Optional:
linkedin-profile-post-scraperfor champion monitoring - Optional:
job-posting-intentfor structured hiring signal detection
Trigger Phrases
- "Find expansion opportunities in our accounts"
- "Which customers are ready for an upgrade?"
- "Run the expansion signal scan"
- "Weekly expansion opportunity report"
| 1 | |
| 2 | name expansion-signal-spotter |
| 3 | description > |
| 4 | Monitor existing customer accounts for upsell and cross-sell signals: team growth |
| 5 | on LinkedIn, new job postings, product usage patterns, funding announcements, and |
| 6 | public company news. Produces a weekly expansion opportunity list with context and |
| 7 | talk tracks. Chains web search, LinkedIn profile monitoring, and job posting detection. |
| 8 | tags [lead-generation] |
| 9 | |
| 10 | |
| 11 | # Expansion Signal Spotter |
| 12 | |
| 13 | Find expansion revenue hiding in your existing customer base. Monitors accounts for signals that indicate they're ready to buy more — before they ask or before a competitor gets there first. |
| 14 | |
| 15 | **Built for:** CS teams and founders at early-stage companies where expansion revenue is the fastest path to growth. You already have the relationship — this skill finds the timing. |
| 16 | |
| 17 | ## When to Use |
| 18 | |
| 19 | "Which customers are ready to expand?" |
| 20 | "Find upsell opportunities in our accounts" |
| 21 | "Run the weekly expansion signal scan" |
| 22 | "Who should I pitch [new feature/tier] to?" |
| 23 | "Monitor customer accounts for growth signals" |
| 24 | |
| 25 | ## Phase 0: Intake |
| 26 | |
| 27 | ### Account Data |
| 28 | **Customer list** — CSV or sheet with: company name, domain, primary contact LinkedIn URL, current plan/tier, MRR/ARR, seats/usage |
| 29 | **Product tiers** — What plans exist? What triggers an upgrade? (e.g., "Pro → Enterprise at 50+ seats") |
| 30 | **Cross-sell products** — Any add-ons or adjacent products you can sell? |
| 31 | |
| 32 | ### Signal Configuration |
| 33 | **Expansion triggers** — What signals mean "ready to buy more" for your product? |
| 34 | Team growth (new hires in relevant roles) |
| 35 | Funding announcement |
| 36 | Usage hitting plan limits |
| 37 | New department/use case interest |
| 38 | Champion promoted (more budget authority) |
| 39 | **Key contacts to monitor** — LinkedIn URLs of champions, decision-makers per account (if available beyond primary) |
| 40 | |
| 41 | ### Filters |
| 42 | **Minimum account value** — Only scan accounts above $X MRR? (Focus effort) |
| 43 | **Accounts to exclude** — Any accounts in active churn risk, paused, or in dispute |
| 44 | |
| 45 | ## Phase 1: Signal Detection |
| 46 | |
| 47 | ### 1A: Team Growth Signals |
| 48 | |
| 49 | For each customer, search for hiring activity: |
| 50 | |
| 51 | |
| 52 | Search: "[company name]" hiring OR "we're hiring" OR "join our team" |
| 53 | Search: site:linkedin.com/jobs "[company name]" [relevant role keywords] |
| 54 | Search: "[company name]" "head of" OR "director of" OR "VP" [your product's domain] |
| 55 | |
| 56 | |
| 57 | Signals to detect: |
| 58 | | Signal | What It Means | Expansion Play | |
| 59 | |--------|---------------|----------------| |
| 60 | | **Hiring in your product's domain** | Growing the team that uses you | More seats / higher tier | |
| 61 | | **New leadership hire** | Budget holder arrived, will evaluate stack | Executive alignment meeting | |
| 62 | | **Hiring in adjacent team** | New department could use your product | Cross-sell / new use case | |
| 63 | | **Rapid headcount growth** | Scaling fast, needs to scale tools too | Volume upgrade | |
| 64 | |
| 65 | ### 1B: Funding & Financial Signals |
| 66 | |
| 67 | |
| 68 | Search: "[company name]" funding OR raised OR "series" OR investment 2026 |
| 69 | Search: "[company name]" revenue OR growth OR expansion |
| 70 | |
| 71 | |
| 72 | | Signal | What It Means | Expansion Play | |
| 73 | |--------|---------------|----------------| |
| 74 | | **New funding round** | Cash in bank, expanding everything | Premium tier / annual contract | |
| 75 | | **Revenue milestone** | Business doing well, likely investing in tools | ROI-focused expansion pitch | |
| 76 | | **Acquisition** | New parent company = new budget | Enterprise plan / multi-team | |
| 77 | |
| 78 | ### 1C: Product Usage Signals (if usage data available) |
| 79 | |
| 80 | From internal data, flag: |
| 81 | |
| 82 | | Signal | Threshold | Expansion Play | |
| 83 | |--------|-----------|----------------| |
| 84 | | **Approaching plan limit** | >80% of seats/usage quota | Proactive upgrade offer | |
| 85 | | **New feature adoption** | Started using a feature in higher tier (via trial/beta) | Convert trial to paid | |
| 86 | | **Power user emergence** | 1+ users with 3x average usage | Champion for internal expansion | |
| 87 | | **Multi-team usage** | Users from 2+ departments | Department-level deal | |
| 88 | | **API usage growth** | API calls trending up month-over-month | Usage-based tier upgrade | |
| 89 | |
| 90 | ### 1D: Public Signal Monitoring |
| 91 | |
| 92 | |
| 93 | Search: "[company name]" launch OR "new product" OR partnership OR expansion |
| 94 | Search: "[company name]" "[your product category]" OR "[related use case]" |
| 95 | |
| 96 | |
| 97 | | Signal | What It Means | Expansion Play | |
| 98 | |--------|---------------|----------------| |
| 99 | | **New product launch** | May need your product for the new line | New use case pitch | |
| 100 | | **Geographic expansion** | Growing into new markets | Multi-region / additional seats | |
| 101 | | **Partnership announced** | Business growing, more complexity | Higher tier for scale | |
| 102 | | **Competitor of yours mentioned** | Evaluating alternatives | Retention + upgrade pre-empt | |
| 103 | |
| 104 | ### 1E: Champion & Stakeholder Signals |
| 105 | |
| 106 | If monitoring champion LinkedIn profiles: |
| 107 | |
| 108 | |
| 109 | Search: "[champion name]" promoted OR "new role" OR "excited to announce" |
| 110 | |
| 111 | |
| 112 | | Signal | What It Means | Expansion Play | |
| 113 | |--------|---------------|----------------| |
| 114 | | **Champion promoted** | More authority, bigger budget | Propose expansion aligned to new scope | |
| 115 | | **Champion left** | Risk + opportunity (new person = fresh pitch) | Onboard new contact, re-pitch value | |
| 116 | | **New exec joined** | Potential new sponsor | Executive briefing | |
| 117 | |
| 118 | ## Phase 2: Opportunity Scoring |
| 119 | |
| 120 | Score each expansion opportunity: |
| 121 | |
| 122 | |
| 123 | Expansion Score = Signal Strength × Account Value × Timing |
| 124 | |
| 125 | Signal Strength (1-5): |
| 126 | 5 = Approaching plan limit + funding + team growth (multiple signals) |
| 127 | 4 = Strong usage signal + one external signal |
| 128 | 3 = One strong external signal (funding, hiring) |
| 129 | 2 = Usage trending up, no external confirmation |
| 130 | 1 = Weak or single minor signal |
| 131 | |
| 132 | Account Value (multiplier): |
| 133 | 2.0x = Top 20% accounts by MRR |
| 134 | 1.5x = Mid-tier accounts |
| 135 | 1.0x = Smaller accounts |
| 136 | |
| 137 | Timing (multiplier): |
| 138 | 2.0x = Signal detected this week (fresh) |
| 139 | 1.5x = Signal detected this month |
| 140 | 1.0x = Signal older than 30 days |
| 141 | |
| 142 | |
| 143 | ### Opportunity Tiers |
| 144 | |
| 145 | | Tier | Score | Action | |
| 146 | |------|-------|--------| |
| 147 | | **Hot** | 15+ | Schedule expansion call this week | |
| 148 | | **Warm** | 8-14 | Send value-add touchpoint, plant expansion seed | |
| 149 | | **Watch** | 3-7 | Add to next QBR agenda, monitor | |
| 150 | |
| 151 | ## Phase 3: Talk Track Generation |
| 152 | |
| 153 | For each Hot and Warm opportunity, generate: |
| 154 | |
| 155 | |
| 156 | ACCOUNT: [Company Name] |
| 157 | CURRENT PLAN: [Plan] — $[MRR]/mo |
| 158 | EXPANSION TYPE: [Upsell / Cross-sell / Volume increase] |
| 159 | ESTIMATED EXPANSION: $[additional MRR]/mo |
| 160 | |
| 161 | SIGNALS: |
| 162 | - [Signal 1] — [Source + date] |
| 163 | - [Signal 2] — [Source + date] |
| 164 | |
| 165 | EXPANSION OPPORTUNITY: |
| 166 | [2-3 sentences: What should they buy and why now?] |
| 167 | |
| 168 | TALK TRACK: |
| 169 | "[Opening line — connects the signal to their business goals, not your quota]" |
| 170 | |
| 171 | "[Value bridge — how the expansion directly helps with what they're already trying to do]" |
| 172 | |
| 173 | "[Soft ask — suggest next step without pressure]" |
| 174 | |
| 175 | TIMING: [Why now is the right time — tied to signal] |
| 176 | |
| 177 | RISK: [What could block this — budget freeze, champion change, etc.] |
| 178 | |
| 179 | |
| 180 | ## Phase 4: Output Format |
| 181 | |
| 182 | |
| 183 | # Expansion Signal Report — Week of [DATE] |
| 184 | Accounts scanned: [N] |
| 185 | Total expansion pipeline identified: $[X] additional MRR |
| 186 | |
| 187 | |
| 188 | |
| 189 | ## Summary |
| 190 | |
| 191 | | Tier | Opportunities | Potential MRR | |
| 192 | |------|--------------|---------------| |
| 193 | | 🔥 Hot | [N] | $[X]/mo | |
| 194 | | 🟡 Warm | [N] | $[X]/mo | |
| 195 | | 👀 Watch | [N] | $[X]/mo | |
| 196 | |
| 197 | |
| 198 | |
| 199 | ## 🔥 Hot Opportunities |
| 200 | |
| 201 | ### [Company 1] — Current: $[X]/mo → Target: $[Y]/mo (+$[Z]) |
| 202 | **Signals:** [list] |
| 203 | **Expansion type:** [Upsell to Enterprise / Add 20 seats / Cross-sell analytics] |
| 204 | **Talk track:** "[scripted opener]" |
| 205 | **Next step:** [Specific action + date] |
| 206 | |
| 207 | ### [Company 2] — ... |
| 208 | |
| 209 | |
| 210 | |
| 211 | ## 🟡 Warm Opportunities |
| 212 | |
| 213 | ### [Company] — Current: $[X]/mo | Signal: [brief] |
| 214 | **Recommended touchpoint:** [What to do — e.g., "Send case study of similar customer who expanded"] |
| 215 | |
| 216 | |
| 217 | |
| 218 | ## 👀 Watch List |
| 219 | |
| 220 | | Account | Signal | Next Check | |
| 221 | |---------|--------|------------| |
| 222 | | [Name] | [Signal] | [Date] | |
| 223 | |
| 224 | |
| 225 | |
| 226 | ## Trends |
| 227 | |
| 228 | - [N] accounts showing team growth signals (potential seat expansion) |
| 229 | - [N] accounts approaching usage limits |
| 230 | - [N] accounts with new funding (potential tier upgrade) |
| 231 | |
| 232 | ## Expansion Playbook Priority |
| 233 | |
| 234 | This week, focus on: |
| 235 | 1. **[Account]** — [Why: highest value + strongest signal] |
| 236 | 2. **[Account]** — [Why] |
| 237 | 3. **[Account]** — [Why] |
| 238 | |
| 239 | |
| 240 | Save to the current working directory or wherever the user prefers (e.g., `expansion/expansion-signals-[YYYY-MM-DD].md`). |
| 241 | |
| 242 | ## Scheduling |
| 243 | |
| 244 | Run weekly: |
| 245 | |
| 246 | |
| 247 | 0 8 * * 2 python3 run_skill.py expansion-signal-spotter |
| 248 | |
| 249 | |
| 250 | ## Cost |
| 251 | |
| 252 | | Component | Cost | |
| 253 | |-----------|------| |
| 254 | | Web search (hiring, funding, news) | Free | |
| 255 | | LinkedIn monitoring (if using linkedin-profile-post-scraper) | ~$0.50-1.00 | |
| 256 | | Job posting detection (if using job-posting-intent) | ~$0.50 | |
| 257 | | All analysis and talk tracks | Free (LLM reasoning) | |
| 258 | | **Total** | **Free — $1.50** | |
| 259 | |
| 260 | ## Tools Required |
| 261 | |
| 262 | **web_search** — for funding, news, hiring signals |
| 263 | **fetch_webpage** — for career pages and announcements |
| 264 | **Optional:** `linkedin-profile-post-scraper` for champion monitoring |
| 265 | **Optional:** `job-posting-intent` for structured hiring signal detection |
| 266 | |
| 267 | ## Trigger Phrases |
| 268 | |
| 269 | "Find expansion opportunities in our accounts" |
| 270 | "Which customers are ready for an upgrade?" |
| 271 | "Run the expansion signal scan" |
| 272 | "Weekly expansion opportunity report" |
| 273 |
Details
- Updated
- Sep 21, 2026
- License
- MIT
- Stars on the repo
- ★ 1,220
- Checked
- Source
- gooseworks-ai/goose-skills ↗
- Creator
- gooseworks-ai · 205 listings
Similar skills
See all →
SkillChampion Job Change Tracker
SkillSeries A-C Signal Tracker
SkillFunded Company Outreach
SkillJob Posting Intent Detection
SkillBuying Signal Detector
SkillBuying Signal ScannerMore from gooseworks-ai
SkillAd Angle Miner
SkillAd Campaign Analyzer
SkillLead Quality Analyzer
SkillMessage Match Auditor
SkillAI Search Visibility
SkillAmazon Product Search