skenetechnologies/plg-skills/expansion-revenue
Claude Code and agent skill by skenetechnologies/plg-skills
- community
- ext:[{"type":"plugin","description":"Custom plugin integration"}]
Checking that the SKILL.md file is still in the repository.
When the user wants to grow revenue from existing customers -- including seat expansion, plan upgrades, usage upsells, or cross-sell strategies. Also use when the user says "NRR," "net revenue retention," "upsell," "expansion MRR," or "how to increase revenue from existing customers." For pricing, see pricing-strategy. For upgrade screens, see paywall-upgrade-cro.
Install
npx vskill@latest install skenetechnologies/plg-skills/expansion-revenueSemi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard
SKILL.md
Expansion Revenue
You are an expansion revenue strategist. A framework for systematically growing revenue from existing customers through seat expansion, plan upgrades, usage increases, add-on purchases, and cross-sell. In mature PLG companies, expansion revenue is the primary growth engine -- often contributing more new ARR than new customer acquisition.
1. Expansion Types
| Expansion Type | Mechanism | Example | Revenue Impact | |
|---|---|---|---|---|
| Seat expansion | More users added to the account | Team grows from 5 to 15 seats | Linear: 3x seats = 3x revenue | |
| Plan upgrade | Customer moves to a higher tier | Starter → Pro or Pro → Business | Step function: 2-5x per upgrade | |
| Usage increase | Customer consumes more of a metered resource | API calls grow from 10K to 100K/month | Proportional to consumption | |
| Add-on purchase | Customer buys supplementary features or products | Adds premium support, advanced analytics module | Incremental per add-on | |
| Cross-sell | Customer adopts an adjacent product | Slack customer adds Slack Connect or Slack Atlas | Multiplied across product portfolio |
Which Expansion Types to Prioritize
2. Net Revenue Retention (NRR) Framework
Formula
NRR Benchmarks
| NRR Range | Quality | Typical Profile | |
|---|---|---|---|
| <90% | Concerning | High churn, minimal expansion | |
| 90-100% | Acceptable | Expansion barely offsets churn | |
| 100-110% | Good | Healthy expansion motion | |
| 110-130% | Excellent | Strong expansion, top-quartile PLG | |
| >130% | Exceptional | Usage-based models with high growth (Snowflake, Twilio) |
3. Expansion Signals from Product Data
3.1 Seat Expansion Signals
| Signal | Indicator | Action | |
|---|---|---|---|
| New invites sent | User invites teammates | Surface team plan benefits | |
| Shared content increasing | Reports, dashboards, docs shared with non-users | Prompt: "Invite [name] to collaborate directly" | |
| Multiple login IPs | Same account accessed from different locations | Suggest additional seats | |
| Approaching seat limit | 80%+ of seats used | Proactive notification | |
| Cross-department usage | Different teams or roles accessing the product | Propose organization-wide deployment |
3.2 Plan Upgrade Signals
| Signal | Indicator | Action | |
|---|---|---|---|
| Hitting plan limits | Storage, projects, API calls approaching cap | Upgrade prompt at the limit moment | |
| Gated feature attempts | User clicks on locked features repeatedly | Show feature value and upgrade path | |
| Power user behavior | Usage in top 10% of current tier | Proactive upgrade recommendation | |
| Admin feature requests | Requests for SSO, audit logs, permissions | Enterprise tier pitch | |
| Support ticket patterns | Questions about advanced features or capabilities | Guide toward the tier that includes those features |
3.3 Usage Increase Signals
| Signal | Indicator | Action | |
|---|---|---|---|
| Accelerating consumption | Week-over-week usage growth >10% | Ensure customer is aware of usage tier benefits | |
| New use case adoption | Different API endpoints or features being used | Help expand into adjacent use cases | |
| Data volume growth | Increasing records, events, or storage | Proactive capacity planning conversation | |
| Integration expansion | New integrations connected | Usage typically increases after integration |
3.4 Cross-Sell Signals
| Signal | Indicator | Action | |
|---|---|---|---|
| Adjacent feature exploration | Users browsing or requesting related product features | Introduce adjacent product | |
| Workflow gaps | Users exporting data to use in other tools | Position your product as the replacement | |
| Team overlap | Different teams using different tools for related workflows | Propose unified platform | |
| Customer feedback | Feature requests that map to another product | Route to cross-sell conversation |
4. Expansion Timing
Timing Framework
5. In-Product Expansion Triggers
Trigger Specifications
Design each trigger with these components:
5.1 Limit-Approaching Notification
5.2 Feature Discovery Prompt
5.3 Team Growth Prompt
5.4 Usage Milestone Celebration
Anti-Patterns for In-Product Triggers
- Too frequent: More than 2-3 expansion prompts per session feels aggressive
- Irrelevant: Showing upgrade prompts for features the user has no interest in
- Blocking: Interrupting the user's workflow with a modal they must dismiss
- No value context: "Upgrade now!" without explaining what they gain
- One-size-fits-all: Same prompt for a solo user and a team admin
6. Expansion Pricing
Seat-Based Uplift
| Approach | Description | Best For | |
|---|---|---|---|
| Per-seat pricing | Each additional seat costs the same | Simple, predictable, transparent | |
| Tiered seat pricing | Price per seat decreases at volume (e.g., 1-10: $20, 11-50: $15, 51+: $10) | Encouraging bulk purchase, enterprise | |
| Seat bundles | Buy in packs (5, 10, 25 seats) | Reducing purchase frequency, encouraging growth |
Usage-Based Overages
| Approach | Description | Best For | |
|---|---|---|---|
| Hard stop | Usage stops at limit, must upgrade | Clear boundaries, no surprise bills | |
| Automatic upgrade | Automatically moves to next tier | Seamless experience, higher revenue | |
| Overage billing | Charged per unit above limit | Maximum flexibility, but surprise bill risk | |
| Grace period | Allow overages temporarily, then require upgrade | Balance of flexibility and conversion |
Prorated Upgrades
Always prorate when a customer upgrades mid-billing cycle:
Communicate this clearly in the upgrade flow: "You will be charged $25 now for the remainder of this billing period, then $100/month starting [date]."
7. Self-Serve vs Sales-Assisted Expansion
| Factor | Self-Serve | Sales-Assisted | |
|---|---|---|---|
| Deal size | <$1,000 ACV expansion | >$1,000 ACV expansion | |
| Complexity | Adding seats, simple upgrade | Multi-product, custom pricing, enterprise | |
| Customer preference | Fast, autonomous | Consultative, negotiated | |
| Scalability | High (automated) | Lower (requires human) | |
| Conversion rate | Lower per opportunity | Higher per opportunity | |
| Cost to serve | Very low | Higher (sales/CS time) |
Hybrid Model
Most PLG companies use a hybrid approach:
- Self-serve for small expansions: Adding seats, upgrading from Starter to Pro, purchasing add-ons
- Sales-assisted for large expansions: Enterprise upgrades, multi-year deals, cross-sell, volume discounts
- Product-qualified leads (PQLs): Product signals trigger sales outreach for high-potential accounts
PQL Criteria for Expansion
An account becomes an expansion PQL when:
- Usage has grown >50% in the last 30 days
- User hit a plan limit 3+ times in the last 14 days
- Account has 5+ active users on a plan designed for smaller teams
- Account uses features that indicate readiness for the next tier
- Account health score is high AND approaching plan limits
8. Expansion Playbook for Customer Success
Quarterly Business Review (QBR) Template
Usage Review Framework
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/expansion-revenue/SKILL.md
Popularity
- Repository stars
- 14
- Repository forks
- 1
- 7-day trend score
- 14
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 12 Apr 2026, 6 months ago.
Extension points
pluginCustom plugin integration
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/skenetechnologies/plg-skills/expansion-revenue)