product-led-sales
Skill9 starsChanged 6 months agoMITView on GitHub
Help users implement product-led sales motions. Use when someone is transitioning from pure PLG to sales-assisted, defining PQLs, building sales handoff processes, or trying to expand self-serve users into enterprise contracts.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Layneformalized225/ai-cofounderedited, first seen Mar 22, 2026
- SkeneTechnologies/plg-skillstheir own version, first seen Jan 26, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Layneformalized225/ai-cofounder★ 198% same
Wrote their own version · 1
- SkeneTechnologies/plg-skills★ 19same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository78 other files it gives its agents.
- anti-pattern-auditSkill
- brand-storytellingSkill
- business-investigationSkill
- ceo-weekly-reviewSkill
- cold-emailSkill
- community-buildingSkill
- company-intelSkill
- competitive-analysisSkill
- competitor-researchSkill
- composio-cliSkill
- conducting-user-interviewsSkill
- content-strategySkill
- copywritingSkill
- daily-recapSkill
- decision-playbookSkill
- designing-growth-loopsSkill
- discovery-debriefSkill
- email-sequenceSkill
- enterprise-salesSkill
- evening-recapSkill
- exa-code-searchSkill
- exa-company-researchSkill
- exa-lead-genSkill
- exa-people-researchSkill
- exa-personal-siteSkill
- exa-x-searchSkill
- feedback-trackerSkill
- find-email-by-nameSkill
- focus-keeperSkill
- founder-salesSkill
- fpf-problem-solvingSkill
- github-stars-monitorSkill
- google-calendarSkill
- grafana-monitoringSkill
- humanizerSkill
- hypothesis-trackerSkill
- idea-generatorSkill
- install-openclaw-to-digitaloceanSkill
- install-openclaw-to-hetznerSkill
- install-openclaw-to-ycSkill
- launch-marketingSkill
- lead-enrichmentSkill
- measuring-product-market-fitSkill
- meeting-prepSkill
- metrics-briefingSkill
- morning-briefSkill
- openclaw-guideSkill
- openclaw-user-onboardingSkill
- orthogonalSkill
- outreach-senderSkill
- person-lookupSkill
- ph-launch-timelineSkill
- pipeline-managerSkill
- positioning-messagingSkill
- positioning-workshopSkill
- posthog-analyticsSkill
- prepare-yc-workshopSkill
- pricing-strategySkill
- problem-definitionSkill
- product-hunt-launchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
- Distinctive: line 9
Follow output preferences from USER.md (language, format, platform constraints).
- Distinctive: line 19
When the user asks for help with product-led sales:
- Distinctive: line 21
Understand the current state: - Ask about their existing PLG motion and sales infrastructure
- Distinctive: line 23
Design the handoff: - Create smooth transitions from self-serve to sales-assisted
- Distinctive: line 24
Align incentives: - Ensure product and sales teams are working toward the same goals
- Distinctive: line 56
Generic outreach: - Not personalizing based on actual product usage data
≈ “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
[YOUR_PRODUCT] Context
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
Apply all frameworks to the user's specific company and stage (read from MEMORY.md).
Follow output preferences from USER.md (language, format, platform constraints).
For chat platforms: max 15 lines, no markdown tables, be concrete and actionable.
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
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.

