Sales Compensation logo

Sales Compensation

Community
cnfeat
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.

Overview

Publishercnfeat
Repositorytop-pm-skills
Skill namesales-compensation
Stars
55
Forks
6
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by cnfeat on GitHub. Read the source before you install it.

Installation

Install the Sales Compensation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/cnfeat/top-pm-skills/tree/main/参考skill/lenny-skills-main%20(2)/lenny-skills-main/skills/sales-compensation
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Use it in TypingMind

Enable Sales Compensation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Sales Compensation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Sales Compensation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Sales Compensation AI skill do?

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.

Why use Sales Compensation on TypingMind?

Because you install it once and use it with any model. Sales Compensation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Sales Compensation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cnfeat/top-pm-skills/tree/main/参考skill/lenny-skills-main%20(2)/lenny-skills-main/skills/sales-compensation. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Sales Compensation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Sales Compensation?

As many as you like. As long as a model supports skills, you can use Sales Compensation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Sales Compensation AI skill free?

Yes. It is published on GitHub by cnfeat under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇