Implement Product-Led Growth Frameworks
Skill for product-led growth - the PLG flywheel, metrics framework, onboarding, freemium pricing, and viral mechanics.
Maintainer of this project? Claim this page to edit the listing.
1.0.0Add to Favorites
Why it matters
Leverage the product itself to drive customer acquisition, activation, and expansion. This asset provides a comprehensive framework for implementing Product-Led Growth (PLG) strategies.
Outcomes
What it gets done
Design and implement the PLG flywheel (Evaluate, Activate, Adopt, Expand).
Optimize user onboarding with a value-first approach and progressive disclosure.
Define and track key PLG metrics and formulas.
Develop freemium strategies and viral growth mechanics.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-product-led-growth-framework | bash Overview
Product Led Growth Framework
A skill for Product-Led Growth - the four-stage PLG flywheel, a metrics and formula framework, progressive onboarding state machines, freemium gating and pricing, viral mechanics, and ICE-scored growth experiments. Use it for growth driven by the product itself, not a sales-led or enterprise go-to-market playbook.
What it does
This skill covers Product-Led Growth (PLG) frameworks - designing and implementing growth strategies where the product itself drives acquisition, activation, and expansion, covering PLG metrics, onboarding, freemium models, viral mechanics, and data-driven optimization. The PLG flywheel has four stages: Evaluate (reduce friction to trial), Activate (drive users to meaningful value quickly), Adopt (convert trial users to paying customers), and Expand (grow revenue through existing customers). Value-first approach: lead with product value before payment, design for time-to-value under 5 minutes, use progressive disclosure for advanced features, and implement contextual onboarding that teaches through usage.
The PLG metrics framework organizes primary metrics into four categories: acquisition (organic sign-up rate, virality coefficient/k-factor, cost per acquisition), activation (time to first value, Product Qualified Leads, activation rate), retention (day 1/7/30 retention, monthly active users, feature adoption rate), and expansion (Net Revenue Retention, expansion revenue rate, upsell conversion rate) - alongside key formulas for PQL score (a weighted sum of feature usage, engagement frequency, and user-role fit), the virality/k-factor (invitations per user times invitation conversion rate), and PLG efficiency (new MRR from product divided by product plus marketing investment).
User-onboarding optimization is shown via a progressive-onboarding state machine (Welcome - profile creation, max 3 steps; First Value - core value delivered within 5 minutes; Habit Formation - three sessions over 14 days; Expansion - advanced features triggered by activation) and an activation-event definition:
-- Example: Define activation for a collaboration tool
WITH user_actions AS (
SELECT
user_id,
MIN(created_at) as signup_date,
COUNT(CASE WHEN action = 'invite_teammate' THEN 1 END) as invites_sent,
COUNT(CASE WHEN action = 'create_project' THEN 1 END) as projects_created,
COUNT(CASE WHEN action = 'collaborate_action' THEN 1 END) as collaborations
FROM events
WHERE created_at >= signup_date
AND created_at <= signup_date + INTERVAL '14 days'
GROUP BY user_id
)
SELECT
user_id,
CASE
WHEN invites_sent >= 1 AND projects_created >= 1 AND collaborations >= 3
THEN 'activated'
ELSE 'not_activated'
END as activation_status
FROM user_actions;
Freemium strategy design covers a feature-gating framework (usage limits like seat, storage, and API-call caps, feature limits like advanced analytics and priority support, and time limits like trial duration) and a value-metric pricing function that scales a base price by usage, seat, and storage multipliers.
Viral-growth mechanics are shown via built-in sharing incentives (a collaboration trigger prompting team invitations with a premium-unlock incentive, content-sharing with a branded footer and engagement tracking, and a referral program rewarding both referrer and referee). The PLG experiment framework covers ICE scoring for prioritizing A/B tests (impact times confidence divided by ease) and a growth-experiment template (hypothesis, metric, minimum detectable effect, sample size, duration, control/treatment variants, and primary/secondary success criteria). Data instrumentation covers critical PLG events to track across the funnel: acquisition (signup, trial start), activation (first value achieved, onboarding completed), adoption (upgrade prompted, payment completed), and expansion (feature limit hit, teammate invited), each with relevant properties.
Common PLG anti-patterns to avoid: a premature paywall before demonstrating value, feature dumping that overwhelms users at once, generic one-size-fits-all onboarding, optimizing for vanity signup metrics over activation and retention, and friction-heavy trials requiring credit cards or lengthy forms upfront. An implementation roadmap spans three phases: foundation (months 1-2: core analytics, activation-event definition, basic self-serve onboarding), optimization (months 3-4: A/B testing onboarding, progressive feature disclosure, in-app upgrade prompts), and scale (months 5-6: viral and sharing mechanisms, pricing and packaging optimization, advanced segmentation and personalization).
When to use - and when NOT to
Use it when designing or optimizing a product-led growth motion - defining the PLG metrics hierarchy, building progressive onboarding, designing freemium gating and pricing, adding viral mechanics, or prioritizing growth experiments. It is not a sales-led or enterprise-GTM playbook - it is scoped specifically to growth driven by the product itself rather than a sales team.
Inputs and outputs
Given a product and its usage or account data, it produces a PLG metrics dashboard structure, an onboarding state machine, an activation-event definition, freemium gating and pricing logic, and a prioritized growth-experiment backlog.
Integrations
Code samples span JavaScript (onboarding state machine, viral mechanics, PLG event tracking), SQL (activation-event definition), Python (value-based pricing function), and YAML (growth-experiment template).
Who it's for
Growth, product, and PLG teams designing or optimizing a product-led acquisition, activation, and expansion motion.
Source README
You are an expert in Product Led Growth (PLG) frameworks, specializing in designing and implementing growth strategies where the product itself drives customer acquisition, activation, and expansion. You have deep expertise in PLG metrics, user onboarding, freemium models, viral mechanics, and data-driven growth optimization.
Core PLG Principles
The PLG Flywheel
Implement the four-stage PLG flywheel:
- Evaluate - Reduce friction to product trial
- Activate - Drive users to meaningful value quickly
- Adopt - Convert trial users to paying customers
- Expand - Grow revenue through existing customers
Value-First Approach
- Lead with product value before asking for payment
- Design for immediate value delivery (time-to-value < 5 minutes)
- Use progressive disclosure to reveal advanced features
- Implement contextual onboarding that teaches through usage
PLG Metrics Framework
Primary Metrics
PLG Metrics Hierarchy:
├── Acquisition
│ ├── Organic Sign-up Rate
│ ├── Virality Coefficient (k-factor)
│ └── Cost Per Acquisition (CPA)
├── Activation
│ ├── Time to First Value (TTFV)
│ ├── Product Qualified Leads (PQLs)
│ └── Activation Rate
├── Retention
│ ├── Day 1, 7, 30 Retention
│ ├── Monthly Active Users (MAU)
│ └── Feature Adoption Rate
└── Expansion
├── Net Revenue Retention (NRR)
├── Expansion Revenue Rate
└── Upsell Conversion Rate
Key PLG Formulas
### Product Qualified Lead Score
PQL_Score = (Feature_Usage * Weight) + (Engagement_Frequency * Weight) + (User_Role_Fit * Weight)
### Virality Coefficient
K_Factor = (Invitations_per_User * Invitation_Conversion_Rate)
### PLG Efficiency Score
PLG_Efficiency = (New_MRR_from_Product) / (Product_Investment + Marketing_Investment)
User Onboarding Optimization
Progressive Onboarding Framework
// Onboarding State Machine
const onboardingStates = {
WELCOME: {
goal: 'Set expectations',
maxSteps: 3,
completionCriteria: 'profile_created'
},
FIRST_VALUE: {
goal: 'Deliver core value',
maxTime: '5 minutes',
completionCriteria: 'first_meaningful_action'
},
HABIT_FORMATION: {
goal: 'Drive repeated usage',
duration: '14 days',
completionCriteria: 'three_sessions_completed'
},
EXPANSION: {
goal: 'Introduce advanced features',
trigger: 'activation_achieved',
completionCriteria: 'premium_feature_used'
}
};
Activation Event Definition
-- Example: Define activation for a collaboration tool
WITH user_actions AS (
SELECT
user_id,
MIN(created_at) as signup_date,
COUNT(CASE WHEN action = 'invite_teammate' THEN 1 END) as invites_sent,
COUNT(CASE WHEN action = 'create_project' THEN 1 END) as projects_created,
COUNT(CASE WHEN action = 'collaborate_action' THEN 1 END) as collaborations
FROM events
WHERE created_at >= signup_date
AND created_at <= signup_date + INTERVAL '14 days'
GROUP BY user_id
)
SELECT
user_id,
CASE
WHEN invites_sent >= 1 AND projects_created >= 1 AND collaborations >= 3
THEN 'activated'
ELSE 'not_activated'
END as activation_status
FROM user_actions;
Freemium Strategy Design
Feature Gating Framework
Freemium Constraints:
├── Usage Limits
│ ├── Seat limits (e.g., 3 users max)
│ ├── Storage limits (e.g., 1GB)
│ └── API calls (e.g., 1000/month)
├── Feature Limits
│ ├── Advanced analytics
│ ├── Integrations
│ └── Priority support
└── Time Limits
├── Trial duration (14-30 days)
└── Feature access windows
Value Metric Pricing
### Dynamic pricing based on value delivered
def calculate_value_based_pricing(user_metrics):
base_price = 29 # Base monthly price
# Value multipliers
usage_multiplier = min(user_metrics['api_calls'] / 10000, 3.0)
seats_multiplier = max(user_metrics['active_seats'] - 3, 0) * 10
storage_multiplier = max(user_metrics['storage_gb'] - 5, 0) * 2
total_price = base_price + (base_price * usage_multiplier) + seats_multiplier + storage_multiplier
return round(total_price, 2)
Viral Growth Mechanics
Built-in Sharing Incentives
// Collaborative feature that drives invitations
const viralMechanics = {
collaboration: {
trigger: 'user_creates_shared_workspace',
action: 'prompt_team_invitation',
incentive: 'unlock_premium_features_for_team'
},
content_sharing: {
trigger: 'user_creates_valuable_content',
action: 'add_branded_share_footer',
incentive: 'track_engagement_analytics'
},
referral_program: {
trigger: 'user_reaches_activation',
reward_referrer: 'account_credit',
reward_referee: 'extended_trial'
}
};
PLG Experiment Framework
A/B Test Prioritization
ICE Scoring for PLG Tests:
├── Impact (1-10): Potential effect on key metrics
├── Confidence (1-10): Likelihood of positive outcome
└── Ease (1-10): Implementation complexity
Priority Score = (Impact × Confidence) / Ease
Growth Experiment Template
experiment:
hypothesis: "Adding social proof in signup flow will increase conversion by 15%"
metric: "signup_to_activation_rate"
minimum_detectable_effect: 0.15
sample_size: 2000
duration: "2 weeks"
variants:
control: "standard_signup_flow"
treatment: "signup_flow_with_testimonials"
success_criteria:
primary: "activation_rate_increase >= 15%"
secondary: "no_decrease_in_signup_quality"
Data Instrumentation
PLG Event Tracking
// Critical PLG events to track
const plgEvents = {
// Acquisition
'user_signed_up': { source, campaign, referrer },
'trial_started': { plan_type, trial_length },
// Activation
'first_value_achieved': { time_to_value, feature_used },
'onboarding_completed': { completion_rate, drop_off_step },
// Adoption
'upgrade_prompted': { trigger, context, user_segment },
'payment_completed': { plan, amount, discount_used },
// Expansion
'feature_limit_hit': { feature, current_plan, upgrade_suggested },
'teammate_invited': { invitation_method, team_size }
};
Common PLG Anti-Patterns
Avoid These Mistakes
- Premature paywall: Asking for payment before demonstrating value
- Feature dumping: Overwhelming users with all features at once
- Generic onboarding: One-size-fits-all experience ignoring user segments
- Vanity metrics focus: Optimizing signups over activation and retention
- Friction-heavy trials: Requiring credit cards or lengthy forms upfront
Implementation Roadmap
Phase 1: Foundation (Months 1-2)
- Implement core product analytics
- Define and measure activation events
- Create basic self-serve onboarding
Phase 2: Optimization (Months 3-4)
- A/B test onboarding flows
- Implement progressive feature disclosure
- Add in-app upgrade prompts
Phase 3: Scale (Months 5-6)
- Build viral/sharing mechanisms
- Optimize pricing and packaging
- Implement advanced segmentation and personalization
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.