sales-compensation▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Design sales compensation plans aligned with business goals and customer retention.
- ›Starts with the standard 50/50 base-to-variable split, then adjusts based on sales cycle length, customer churn patterns, and business model to avoid misaligned incentives
- ›Emphasizes tying compensation to customer outcomes and net dollar retention, not just closed bookings, to reward sticky deals over churny ones
- ›Guides ramp structures for new hires (3–6 months for SMB, 6–12 months for enterprise) wit
Sales Compensation
Help the user design effective sales compensation plans using frameworks from 2 product leaders.
How to Help
When the user asks for help with sales compensation:
- Understand the business model - Ask about their sales cycle, ACV, and customer retention patterns
- Identify current problems - Determine if there are misaligned incentives or retention issues
- Design aligned incentives - Help them create comp plans that drive the right behaviors
- Consider ramp and quotas - Guide them on structuring pay for new hires
Core Principles
The standard 50/50 split is a starting point
Jason M Lemkin: "It's usually 50/50, right? 50% base, 50% bonus for a sales rep." The standard OTE structure is 50% base salary and 50% variable commission. This is a common baseline for quota-carrying roles.
Traditional comp plans are misaligned
Sahil Mansuri: "Sales comp plans are stuck in the stone ages... What we haven't done is built a modern technical sales compensation plan that actually aligns the needs and incentives of the business, the customer and the rep." Consider designing comp that rewards long-term retention and net dollar retention, not just closed deals.
Align incentives with customer success
If your business depends on customer retention, comp plans should include components tied to customer outcomes, not just initial bookings. Reps who close churny deals should earn less than those who close sticky customers.
Ramp periods matter
New sales hires need ramp periods with guaranteed draws or reduced quotas while they learn the product and market. Typical ramps are 3-6 months for SMB and 6-12 months for enterprise.
Simplicity drives behavior
Complex comp plans with many variables lead to confusion and gaming. Simple plans where reps understand exactly what actions increase their pay are more effective.
Questions to Help Users
- "What percentage of new deals churn within the first year? Does your comp plan account for this?"
- "Is your comp plan so complex that reps don't know how to maximize their earnings?"
- "What behaviors are you trying to incentivize? Does your comp plan actually reward those behaviors?"
- "How long is your sales cycle, and how does that affect cash flow for reps?"
- "What's your ramp structure for new hires? Is it working?"
Common Mistakes to Flag
- Incentivizing only bookings - Paying for closed deals without considering customer quality or retention
- Over-complicated plans - Too many variables that confuse reps and enable gaming
- No ramp protection - Expecting new hires to hit full quota immediately
- Misaligned accelerators - Bonuses that kick in at the wrong thresholds
- Ignoring churn - Comp plans that don't account for customers who don't renew
Deep Dive
For all 2 insights from 2 guests, see references/guest-insights.md
Related Skills
- sales-qualification
- product-led-sales
- pricing-strategy
How to use sales-compensation on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add sales-compensation
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches sales-compensation from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate sales-compensation. Access the skill through slash commands (e.g., /sales-compensation) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★43 reviews- ★★★★★Lucas Ndlovu· Dec 24, 2024
We added sales-compensation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Michael Farah· Dec 24, 2024
Keeps context tight: sales-compensation is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Piyush G· Dec 12, 2024
Useful defaults in sales-compensation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ava Verma· Dec 12, 2024
sales-compensation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Pratham Ware· Nov 27, 2024
Registry listing for sales-compensation matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Hiroshi Nasser· Nov 15, 2024
Keeps context tight: sales-compensation is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Shikha Mishra· Nov 3, 2024
sales-compensation has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Camila Wang· Nov 3, 2024
sales-compensation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yash Thakker· Oct 22, 2024
Solid pick for teams standardizing on skills: sales-compensation is focused, and the summary matches what you get after install.
- ★★★★★Lucas Lopez· Oct 22, 2024
We added sales-compensation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 43