skills/product-led-sales/SKILL.md
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.
npx skillsauth add cvillamarp-lgtm/skillspodcast product-led-salesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user implement product-led sales motions using frameworks from 2 product leaders.
When the user asks for help with product-led sales:
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.
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.
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.
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.
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.
For all 2 insights from 2 guests, see references/guest-insights.md
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.