When self-serve users hit the 15K ceiling, /product-led-sales defines PQA triggers and designs the handoff to close the enterprise contract. — Claude Skill
A Claude Skill for Claude Code by Refound — run /product-led-sales in Claude·Updated
Convert self-serve usage into enterprise contracts with PQA triggers.
- PQA (Product Qualified Account) definition: usage patterns that predict enterprise conversion
- Sales handoff design: Hila Qu's 'I saw you were checking it out, how can I help' trigger model
- Self-serve ceiling analysis: Elena Verna's 10-15K credit-card threshold as the PLS trigger
- Pilot AE structure: run product-led sales outside the main quota engine while you learn the motion
- Account consolidation: 'magic number' of users per company account (often 7+) as the enterprise signal
Who this is for
Turn self-serve signups into qualified enterprise conversations without strangling the PLG funnel
See skills for this roleAlign PLG and sales-led motions without cannibalizing either pipeline
See skills for this roleBuild PQL scoring models and handoff rules between self-serve and sales-assisted
See skills for this roleWhat it does
A few accounts are at 14K/year on self-serve and asking for invoices. /product-led-sales applies Elena Verna's escalator: find the buyer outside the product, tell the organizational-value story, and convert to a 60-100K enterprise contract.
You have 3,000 active accounts and one SDR. /product-led-sales defines PQA criteria based on usage depth, seat count, and feature adoption, then ranks the top 50 accounts for this week's outreach.
You're moving from pure PLG to a hybrid model. /product-led-sales applies Elena Verna's pilot-AE rule (run it outside the main sales engine, no top-down quota pressure) and designs the exact handoff trigger, SLA, and messaging.
Your first PLS touches converted at 2% and users complained. /product-led-sales rewrites outreach using Hila Qu's help-first model ('I noticed you were exploring our API, how can I help?') instead of traditional demo pitches.
How it works
You share your current PLG motion: active accounts, self-serve pricing, usage data sources, and current sales setup
The skill applies Elena Verna's PLG-to-enterprise escalator framework and identifies the revenue ceiling where PLS unlocks contract value
Define PQA criteria: which usage signals (seat count, feature depth, API calls, team growth) predict enterprise conversion
Design the handoff: Hila Qu's help-first trigger, SLA for AE response time, and the exact messaging for first touch
Get a 30-day pilot plan: 1 pilot AE, top 50 PQAs, success metrics, and the exit criteria for scaling the motion
Example
Product: API-first data platform Self-serve price: 99-299/month Active accounts: 4000 Top 5% accounts: 1-3K/month, growing 20% MoM Sales team: 0 AEs, founder answers 'talk to sales' emails Data available: seat count, API calls, feature adoption, domain
Elena Verna rule: self-serve caps around 10-15K annually because buyers stop putting that on a credit card. Your top 5% are already at 12-36K/year, which means they are actively hitting the ceiling. PLS is the right motion now.
An account is PQA if it matches 3+ of: - 7+ active seats from the same company domain (Verna's magic number) - API calls above the p95 threshold for 2 consecutive weeks - 3+ feature categories adopted - Domain matches a target enterprise list (F5000, ARR > 50M) - Any user explicitly searches for 'enterprise', 'SSO', 'SOC 2', or 'invoice'
Trigger: account hits PQA threshold. SLA: pilot AE reaches out within 24h. First touch (Hila Qu model): 'I saw your team is running 40K API calls/day across 9 seats. I work with companies at that scale, anything I can unblock?' Not: 'I'd like to schedule a demo of our enterprise plan'.
Hire 1 pilot AE (not under main sales quota per Elena Verna). Top 50 PQAs uploaded from your data warehouse. Success metrics: 20% response rate, 5 opportunities created, 1 closed-won over 60K. If the pilot works, expand to 2 AEs and automate the PQA query in your data pipeline.
Metrics this improves
Works with
Product-Led Sales
Help the user implement product-led sales motions using frameworks from 2 product leaders.
How to Help
When the user asks for help with product-led sales:
- Understand the current state - Ask about their existing PLG motion and sales infrastructure
- Define the trigger criteria - Help them identify what signals indicate a user is ready for sales outreach
- Design the handoff - Create smooth transitions from self-serve to sales-assisted
- Align incentives - Ensure product and sales teams are working toward the same goals
Core Principles
PLS converts usage into sales opportunities
Elena Verna: "Product-led sales converts the usage that you've generated via self-serve into a sales opportunity and it attaches a salesperson to close a much larger contract." PLS is a distinct motion that sits between PLG and traditional sales, using product usage data to identify and prioritize sales opportunities.
Use data signals for outreach
Hila Qu: "How the product led funnel work for us is... our sales team get that data signal, they may send an email and reach out and say, 'Hey, I saw you were checking it out. How can I help?'" Product usage signals should trigger personalized sales outreach, not generic sequences.
Define Product Qualified Accounts (PQAs)
Product-led sales requires new metrics like PQAs and PQLs (Product Qualified Leads) that measure product engagement rather than marketing engagement. These signals are more predictive of conversion than traditional MQLs.
Sales should help, not sell
The initial sales outreach in a PLS motion should offer assistance based on observed behavior, not push for an immediate sale. The user has already experienced the product - sales adds value by solving specific expansion needs.
Know when to transition
There's a natural ceiling for self-serve revenue (typically $10K-$15K). Product-led sales helps capture the value of users who need contracts larger than what credit cards support.
Questions to Help Users
- "What user behaviors in your product correlate most strongly with eventual conversion to paid?"
- "At what usage level do users typically need capabilities beyond your self-serve tier?"
- "How will your sales team know which users to prioritize for outreach?"
- "What does your sales team say that adds value beyond what users can do self-serve?"
- "How do you prevent sales outreach from feeling intrusive to users who prefer self-serve?"
Common Mistakes to Flag
- Treating PLS like traditional sales - Using high-pressure tactics with users who already have product experience
- No clear trigger criteria - Reaching out to all active users instead of those showing expansion signals
- Sales and product misalignment - Sales team incentivized on behaviors that conflict with product growth
- Generic outreach - Not personalizing based on actual product usage data
- Ignoring the self-serve path - Forcing users into sales when they'd convert faster on their own
Deep Dive
For all 2 insights from 2 guests, see references/guest-insights.md
Related Skills
- pricing-strategy
- retention-engagement
- sales-qualification
Reference documents
Product-Led Sales Strategy - All Guest Insights
2 guests, 2 mentions
Elena Verna
Elena Verna 2.0
"Product-led sales converts the usage that you've generated via self-serve into a sales opportunity and it attaches a salesperson to close a much larger contract."
Insight: The guest provides a comprehensive framework for a specific go-to-market motion that sits between PLG and traditional sales, involving unique metrics (PQAs), organizational accountability (Product own
Hila Qu
Hila Qu
"How the product led funnel work for us is... our sales team get that data signal, they may send an email and reach out and say, 'Hey, I saw you were checking it out. How can I help?'"
Insight: The guest discusses the specific transition and mechanics of moving from pure PLG to a hybrid model involving Product Qualified Leads (PQLs) and sales handoffs.