sales-compensation
Help users design sales compensation plans. Use when someone is hiring their first sales rep, restructuring sales comp, trying to align sales incentives with business goals, or dealing with comp plan issues like sandbagging or churn.
What this skill does
# 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: 1. **Understand the business model** - Ask about their sales cycle, ACV, and customer retention patterns 2. **Identify current problems** - Determine if there are misaligned incentives or retention issues 3. **Design aligned incentives** - Help them create comp plans that drive the right behaviors 4. **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
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.