sales-compensation-design
Design sales compensation plans aligned with quotas, incentives, and long-term business outcomes.
What this skill does
# Sales Compensation Design **Category:** Sales & GTM **Source:** https://refoundai.com/lenny-skills/s/sales-compensation --- Sales Compensation Design | Refound AI Lenny Skills Database SKILLS PLAYBOOKS GUESTS ABOUT SKILLS PLAYBOOKS GUESTS ABOUT Sales & GTM 2 guests | 2 insights Sales Compensation Design Sales compensation design is the strategic structuring of pay plans to align rep incentives with business objectives. The traditional 50/50 base-bonus split has remained unchanged for decades, but modern approaches consider long-term retention, net dollar retention, and customer success - not just closed deals. Download Claude Skill Read Guide The Guide 3 key steps synthesized from 2 experts. 1 Understand the standard 50/50 structure The traditional model is 50% base salary, 50% bonus tied to quota attainment. This is the industry baseline that most reps expect. Before innovating, understand why this structure exists and what it optimizes for (new business acquisition above all else). Featured guest perspectives "It's usually 50/50, right? 50% base, 50% bonus for a sales rep." — Jason M Lemkin 2 Align comp with business outcomes beyond closed deals Modern comp plans should align rep incentives with what actually matters to the business: customer success, retention, and net dollar retention - not just initial close. The old model was built for a different era. Consider how to incent behavior that leads to long-term value, not just short-term wins. Featured guest perspectives "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." — Sahil Mansuri 3 Design ramping strategies for new hires New sales hires need time to ramp up before they can hit full quota. Your comp plan should account for this with ramping structures that provide financial stability during the learning period while still incentivizing performance improvement. Featured guest perspectives "It's usually 50/50, right? 50% base, 50% bonus for a sales rep." — Jason M Lemkin ✗ Common Mistakes Using the same comp structure as every other company without considering your specific modelOnly incentivizing new business while ignoring retention and expansionCreating overly complex plans that reps can't understand or predictNot ramping new hires appropriately, leading to early departures ✓ Signs You're Doing It Well Rep behavior aligns with what's actually good for customers and the businessTop performers are highly compensated and unlikely to leaveReps can accurately predict their compensation based on their activitiesCustomer retention metrics are strong, not just new business metrics All Guest Perspectives Deep dive into what all 2 guests shared about sales compensation design. Jason M Lemkin 1 quote Listen to episode → "It's usually 50/50, right? 50% base, 50% bonus for a sales rep." View all skills from Jason M Lemkin → Sahil Mansuri 1 quote Listen to episode → "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." View all skills from Sahil Mansuri → Install This Skill Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills. 1 Download the skill Download SKILL.md 2 Add to your project Create a folder in your project root and add the skill file: .claude/skills/sales-compensation/SKILL.md 3 Start using it Claude will automatically detect and use the skill when relevant. You can also invoke it directly: Help me with sales compensation design Related Skills Other Sales & GTM skills you might find useful. 16 guests Founder Sales The primary competitor in B2B sales is often customer indecision and the fear of making a high-stake... View Skill → → 9 guests Enterprise Sales Enterprise sales require a high-level narrative to align diverse stakeholders within a buying commit... View Skill → → 14 guests Building Sales Team Early sales hires in a PLG company should match the current inbound motion and the specific target b... View Skill → → 9 guests Partnership & BD Securing strategic partnerships with major platforms (like Facebook or Google) requires demonstratin... View Skill → → AI Transformation Partner Start Your Journey SERVICES AI Audit AI Automation AI Training COMPANY About Case Studies Book a Call © 2026 Refound. All rights reserved.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.