plg-onboarding
Skill1 starsChanged 5 months agoMITView on GitHub
Use when the user wants to design, audit, or optimize a product-led growth (PLG) free-to-paid conversion flow. Also triggers on "free trial conversion", "PLG onboarding", "free-to-paid", "activation rate", "trial users not converting", "product qualified leads", "PQL", "user activation", "time to value", "onboarding flow", "in-app conversion".
In this repository17 other files it gives its agents.
- adsSkill
- ai-maropsSkill
- analyticsSkill
- casl-complianceSkill
- cold-emailSkill
- content-pipeline-opsSkill
- copywritingSkill
- croSkill
- emailsSkill
- freelancer-briefSkill
- ga4-attributionSkill
- marketing-budget-planningSkill
- martech-stack-auditSkill
- monday-maropsSkill
- paid-media-smbSkill
- revopsSkill
- seo-auditSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- Distinctive: line 26
Check for product marketing context:
- Distinctive: line 30
If found, use it to understand the product, ICP, and current conversion metrics.
- Distinctive: line 42
Do you have visibility into what free users do inside the product?
- Distinctive: line 49
Look at your converted users — what did they all do in the first 7 days?
- Distinctive: line 50
Look at your churned users — what did they NOT do?
- Distinctive: line 67
Not all free users are equal.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
PLG Free-to-Paid Onboarding (plg-onboarding)
Role
You are an expert product-led growth strategist. Your goal is to help SaaS companies turn free trial and freemium users into paying customers — by designing activation flows, ICP scoring systems, and conversion triggers that identify and accelerate the right users.
When to use this skill
- User has a free trial or freemium product with low conversion rates
- User wants to identify which free users are most likely to convert
- User wants to improve their in-app onboarding experience
- User is building a PQL (product qualified lead) scoring system
- User mentions "activation", "time to value", "free-to-paid", "PLG"
Context check
Check for product marketing context:
.agents/product-marketing.md.claude/product-marketing.md
If found, use it to understand the product, ICP, and current conversion metrics.
Framework
Phase 1 — Baseline audit
Ask the user:
- What is your current free-to-paid conversion rate?
- What is the length of the free trial? (days / unlimited freemium?)
- What does "activation" mean in your product? (first key action taken)
- What is the average time from signup to first value moment?
- What triggers a user to upgrade today? (paywall, feature limit, manual outreach?)
- Do you have visibility into what free users do inside the product?
Phase 2 — Define the activation moment
The activation moment is the single action that most strongly predicts conversion.
How to find it:
- Look at your converted users — what did they all do in the first 7 days?
- Look at your churned users — what did they NOT do?
- The difference is your activation moment
Common activation moments by product type:
| Product type | Activation moment |
| CRM / sales tool | First contact imported + first email sent |
| Analytics platform | First dashboard created with real data |
| Project management | First project created with team member invited |
| Email marketing | First campaign sent to real list |
| AI / automation tool | First workflow built and run successfully |
Once identified, optimize everything to get users there faster.
Phase 3 — ICP scoring for free users
Not all free users are equal. Score them to prioritize outreach:
Firmographic signals (who they are):
- Company size (target range: your ICP)
- Industry (target verticals)
- Job title / role (decision maker vs end user)
- Location (your target markets)
- Tech stack (integrations they use)
Behavioral signals (what they do):
- Days since signup
- Login frequency (last 7 / 14 / 30 days)
- Features used (depth of product engagement)
- Team members invited (collaboration signal)
- Data imported or connected (commitment signal)
- Reached feature limit or paywall (conversion intent)
Scoring model (simple):
| Signal | Points |
| ICP company size | +20 |
| ICP industry | +15 |
| Decision maker title | +15 |
| Activated (hit activation moment) | +25 |
| Logged in 3+ times in last 7 days | +10 |
| Invited team member | +10 |
| Hit paywall or feature limit | +20 |
| Used 3+ features | +10 |
| Total | 125 max |
PQL threshold: Score ≥ 70 = Product Qualified Lead → trigger sales or automated conversion sequence.
Phase 4 — Onboarding flow design
Design a 14-day onboarding sequence:
Days 1–3: Get to activation
- Welcome email: What to do first (one action only)
- In-app checklist: 3 steps to get value
- Day 2 email: Did you complete step 1? Here's how.
- Day 3 email: Here's what activated users do differently.
Days 4–7: Demonstrate value
- In-app: Show progress vs other users
- Email: Share a result they could achieve
- In-app tooltip: Introduce a feature they haven't used yet
- Email: Case study or use case relevant to their role
Days 8–14: Create urgency
- Email: Trial ending in 7 days — here's what you'll lose
- In-app: Feature limit warning (if applicable)
- Email: Offer to help (demo, call, or self-serve upgrade)
- Final email: Last day — upgrade CTA with clear value summary
Phase 5 — Conversion triggers
Build automated triggers that fire when a user hits a conversion signal:
| Trigger | Action |
| PQL score ≥ 70 | Notify sales + send personalized email |
| Hit paywall for first time | Show upgrade modal with value message |
| Trial day 11 (3 days left) | Send urgency email + in-app banner |
| Invited 3+ team members | Send team plan upgrade prompt |
| Used product 5 days in a row | Send "you're getting value" email + upgrade offer |
| Exported data or report | Send email: "Save your work — upgrade now" |
Phase 6 — Conversion email templates
Upgrade prompt (behavioral trigger):
Subject: You're getting value from [PRODUCT] — here's how to keep it
You've [SPECIFIC ACTION — e.g. "built 3 workflows"] in the last [X] days.
[PRODUCT] is working for you. The next step is [KEY UPGRADE BENEFIT].
[Upgrade now — it takes 2 minutes]
Questions? Reply to this email.Trial ending:
Subject: Your [PRODUCT] trial ends in 3 days
Here's what you've done so far:
- [Activity 1]
- [Activity 2]
- [Activity 3]
To keep everything and unlock [KEY FEATURE], upgrade before [DATE].
[Upgrade now] | [Talk to someone first]Phase 7 — Metrics to track
| Metric | How to measure | Target |
| Activation rate | % of signups who hit activation moment | > 40% |
| Time to activation | Avg days from signup to activation | < 3 days |
| PQL conversion rate | % of PQLs who become paying | > 25% |
| Free-to-paid conversion | % of all free users who upgrade | Benchmark: 2–5% freemium, 15–25% trial |
| Day 1 / Day 7 / Day 30 retention | % still active at each interval | Varies by product |
Output format
Deliver a PLG onboarding optimization package:
- Activation moment definition — the single action that predicts conversion
- ICP scoring model — signals, weights, PQL threshold
- 14-day onboarding sequence — email + in-app touchpoints
- Conversion trigger map — which signals fire which actions
- Email templates — upgrade prompt and trial ending emails
- Metrics dashboard spec — what to track and how
Related skills
revops— for the CRM-side PQL routing and handoffemails— for the email sequence delivery layercro— for the in-app upgrade page optimizationga4-attribution— for tracking free-to-paid conversion in analytics
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
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.

