skenetechnologies/plg-skills/expansion-revenue

Claude Code and agent skill by skenetechnologies/plg-skills

Trust tier 3
  • community
  • ext:[{"type":"plugin","description":"Custom plugin integration"}]
Source check pending

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-revenue

Semi-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 TypeMechanismExampleRevenue Impact
Seat expansionMore users added to the accountTeam grows from 5 to 15 seatsLinear: 3x seats = 3x revenue
Plan upgradeCustomer moves to a higher tierStarter → Pro or Pro → BusinessStep function: 2-5x per upgrade
Usage increaseCustomer consumes more of a metered resourceAPI calls grow from 10K to 100K/monthProportional to consumption
Add-on purchaseCustomer buys supplementary features or productsAdds premium support, advanced analytics moduleIncremental per add-on
Cross-sellCustomer adopts an adjacent productSlack customer adds Slack Connect or Slack AtlasMultiplied across product portfolio
Which Expansion Types to Prioritize
Is your pricing per-seat?
├── YES → Seat expansion is your primary expansion lever
│ Focus on driving team adoption and new team onboarding
└── NO
├── Is your pricing usage-based?
│ ├── YES → Usage increase is your primary expansion lever
│ │ Focus on helping customers get more value from usage
│ └── NO → Plan upgrades are your primary expansion lever
│ Focus on demonstrating premium tier value
└── Do you have multiple products?
├── YES → Cross-sell is an additional lever
└── NO → Consider add-ons as supplementary expansion

2. Net Revenue Retention (NRR) Framework

Formula
NRR = (Beginning MRR + Expansion MRR - Contraction MRR - Churned MRR) / Beginning MRR
Example:
Beginning MRR: $1,000,000
Expansion MRR: +$150,000 (upgrades, seats, usage)
Contraction MRR: -$30,000 (downgrades)
Churned MRR: -$50,000 (cancellations)
NRR = ($1,000,000 + $150,000 - $30,000 - $50,000) / $1,000,000 = 107%
NRR Benchmarks
NRR RangeQualityTypical Profile
<90%ConcerningHigh churn, minimal expansion
90-100%AcceptableExpansion barely offsets churn
100-110%GoodHealthy expansion motion
110-130%ExcellentStrong expansion, top-quartile PLG
>130%ExceptionalUsage-based models with high growth (Snowflake, Twilio)

3. Expansion Signals from Product Data

3.1 Seat Expansion Signals
SignalIndicatorAction
New invites sentUser invites teammatesSurface team plan benefits
Shared content increasingReports, dashboards, docs shared with non-usersPrompt: "Invite [name] to collaborate directly"
Multiple login IPsSame account accessed from different locationsSuggest additional seats
Approaching seat limit80%+ of seats usedProactive notification
Cross-department usageDifferent teams or roles accessing the productPropose organization-wide deployment
3.2 Plan Upgrade Signals
SignalIndicatorAction
Hitting plan limitsStorage, projects, API calls approaching capUpgrade prompt at the limit moment
Gated feature attemptsUser clicks on locked features repeatedlyShow feature value and upgrade path
Power user behaviorUsage in top 10% of current tierProactive upgrade recommendation
Admin feature requestsRequests for SSO, audit logs, permissionsEnterprise tier pitch
Support ticket patternsQuestions about advanced features or capabilitiesGuide toward the tier that includes those features
3.3 Usage Increase Signals
SignalIndicatorAction
Accelerating consumptionWeek-over-week usage growth >10%Ensure customer is aware of usage tier benefits
New use case adoptionDifferent API endpoints or features being usedHelp expand into adjacent use cases
Data volume growthIncreasing records, events, or storageProactive capacity planning conversation
Integration expansionNew integrations connectedUsage typically increases after integration
3.4 Cross-Sell Signals
SignalIndicatorAction
Adjacent feature explorationUsers browsing or requesting related product featuresIntroduce adjacent product
Workflow gapsUsers exporting data to use in other toolsPosition your product as the replacement
Team overlapDifferent teams using different tools for related workflowsPropose unified platform
Customer feedbackFeature requests that map to another productRoute to cross-sell conversation

4. Expansion Timing

Timing Framework
For self-serve expansion (< $1,000 ACV):
→ Primarily moment-of-need triggers
→ Supplemented by monthly usage summary emails
→ Automated upgrade flows
For mid-market expansion ($1,000 - $25,000 ACV):
→ Moment-of-need triggers + in-product prompts
→ Quarterly usage reviews (automated or CSM)
→ Annual renewal conversation
For enterprise expansion (> $25,000 ACV):
→ Product signals routed to CSM/AE
→ Quarterly business reviews with stakeholders
→ Annual strategic planning and renewal
→ Executive sponsorship for major expansion

5. In-Product Expansion Triggers

Trigger Specifications

Design each trigger with these components:

5.1 Limit-Approaching Notification
Trigger: User reaches 80% of plan limit
Location: In-product banner or notification
Copy: "You have used [X] of [Y] [resource]. Upgrade to [Plan] for
[higher limit or unlimited]."
CTA: "Upgrade Now" (primary) | "Remind Me Later" (secondary)
Frequency: Show once per session, max 3 times total
Suppress: If user dismissed 3 times, stop showing for 30 days
5.2 Feature Discovery Prompt
Trigger: User navigates near a gated feature or searches for it
Location: Contextual tooltip or inline prompt near the feature
Copy: "[Feature name] helps you [specific benefit]. Available on [Plan]."
CTA: "Learn More" → feature explainer with upgrade option
Frequency: Show once per feature per user
Suppress: After user has seen 3 feature prompts in one session
5.3 Team Growth Prompt
Trigger: Account has new active users approaching seat limit, or
user attempts to invite beyond seat limit
Location: Invite flow or team settings
Copy: "Your team is growing! Add more seats to bring everyone onto
[Product]."
CTA: "Add Seats" → seat purchase flow
Frequency: At the moment of need
Suppress: Not applicable (this is a hard block if at seat limit)
5.4 Usage Milestone Celebration
Trigger: User reaches a meaningful usage milestone
Location: In-product celebration modal or notification
Copy: "Congratulations! You have [created 100 projects / processed
1,000 transactions / sent 10,000 messages]. Unlock [benefit]
with [Plan]."
CTA: "See What's Next" → plan comparison with upgrade option
Frequency: At each milestone (define 3-5 meaningful milestones)
Suppress: Not after milestone; this is a positive moment
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
ApproachDescriptionBest For
Per-seat pricingEach additional seat costs the sameSimple, predictable, transparent
Tiered seat pricingPrice per seat decreases at volume (e.g., 1-10: $20, 11-50: $15, 51+: $10)Encouraging bulk purchase, enterprise
Seat bundlesBuy in packs (5, 10, 25 seats)Reducing purchase frequency, encouraging growth
Usage-Based Overages
ApproachDescriptionBest For
Hard stopUsage stops at limit, must upgradeClear boundaries, no surprise bills
Automatic upgradeAutomatically moves to next tierSeamless experience, higher revenue
Overage billingCharged per unit above limitMaximum flexibility, but surprise bill risk
Grace periodAllow overages temporarily, then require upgradeBalance of flexibility and conversion
Prorated Upgrades

Always prorate when a customer upgrades mid-billing cycle:

Days remaining in cycle: 15 of 30
Current plan cost: $50/month
New plan cost: $100/month
Prorated charge: ($100 - $50) x (15/30) = $25
Next full cycle: $100/month

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

FactorSelf-ServeSales-Assisted
Deal size<$1,000 ACV expansion>$1,000 ACV expansion
ComplexityAdding seats, simple upgradeMulti-product, custom pricing, enterprise
Customer preferenceFast, autonomousConsultative, negotiated
ScalabilityHigh (automated)Lower (requires human)
Conversion rateLower per opportunityHigher per opportunity
Cost to serveVery lowHigher (sales/CS time)
Hybrid Model

Most PLG companies use a hybrid approach:

  1. Self-serve for small expansions: Adding seats, upgrading from Starter to Pro, purchasing add-ons
  2. Sales-assisted for large expansions: Enterprise upgrades, multi-year deals, cross-sell, volume discounts
  3. 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
markdown
# QBR: [Customer Name] -- [Quarter/Year]
## Account Summary
-Current plan: [Plan name]
-Seats: [X active / Y purchased]
-MRR: [$X]
-Account age: [N months]
-Health score: [X/100]
## Usage Review
-Key metrics this quarter:
-[Metric 1]: [Value] (trend: up/down/flat vs last quarter)
-[Metric 2]: [Value] (trend)
-[Metric 3]: [Value] (trend)
-Feature adoption:
-Using: [features actively used]
-Not using: [features available but unused]
-Approaching limits: [features near plan ceiling]
## Value Delivered
-[Quantified outcome 1]: "You saved X hours this quarter using [feature]"
-[Quantified outcome 2]: "Your team processed X more [things] than last quarter"
-[ROI calculation]: "Based on your usage, [Product] is delivering
[$X] in value against your [$Y] investment"
## Growth Opportunities
1.[Opportunity 1]: [Description, business case, recommended plan/add-on]
2.[Opportunity 2]: [Description, business case]
3.[Opportunity 3]: [Description, business case]
## Recommended Next Steps
-[ ] [Action 1] -- [Owner] -- [Due date]
-[ ] [Action 2] -- [Owner] -- [Due date]
## Questions for the Customer
1.What are your priorities for next quarter?
2.Are there new teams or use cases where [Product] could help?
3.Are there any challenges or gaps in the current product?
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

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
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/skenetechnologies/plg-skills/expansion-revenue/badge)](https://verified-skill.com/skills/skenetechnologies/plg-skills/expansion-revenue)

Something wrong with this skill or its page? Tell us.