Skills / Building the company / Sales comp and structure

How do I structure and pay a security sales team — openers, closers, quotas, ramp?

Pay for the sales motion you have, not the one in the plan you showed the board.

sales-comp-and-structure

SKILL.md · 919 words

Verified Sept 2026

Download the folder
What your agent reads.
name
sales-comp-and-structure
description
Structuring and paying a security sales team after the first hire: the opener and closer split, the price point that selects the motion, quotas set as ramp plans bounded by the buyer's evaluation cycle, commission paid on countersignature and cash rather than the verbal yes, the sales engineer paid on team attainment, when a player-coach team lead appears, the field overlay, discount authority, and matching the shape of the organization to the deals actually closed. Use when a founder is writing the first comp plan, setting a first quota, adding a second seller, hiring a sales engineer, or being told to build an enterprise-shaped team. Not for when to hire the first seller or their profile (first-sales-hire), equity tiers (security-talent-and-comp), or pricing (cyber-pricing).
title
Sales comp and structure
question
How do I structure and pay a security sales team — openers, closers, quotas, ramp?
subtitle
Pay for the sales motion you have, not the one in the plan you showed the board.
summary
You pay for the sales motion you actually have, not the one you hope to have, and you shape the team to the deals you closed this year. Split openers from closers, set the first quota as a ramp plan bounded by the buyer's evaluation cycle, pay commission on cash rather than on a verbal yes, and keep discount authority with the founder for the first year.
group
company
verified
2026-09-08
order
61

787 / 1024 characters

This is the top of the SKILL.md file, exactly as it downloads. Your agent reads the description field to decide when to load this skill. The rest of this page is for you.

You will design the sales organization from a template written for software that never passes through a third-party risk review, and it will cost you the ratios for years. In security the line that picks your motion is not a dollar figure. It is the point where the security review begins, and every deal above it is an enterprise sale whatever the price on it. The structures below are durable. The numbers inside them are yours to set, and they belong to your buyer's sales cycle, not to a benchmark.

Split openers from closers.

You divide early sales into an opener, who prospects, qualifies, and books the meeting, and a closer, who runs the evaluation, negotiates, and signs. They are different people with different experience, different pay, and different ramps, and the opener role is a training path into the closer role rather than a permanent tier. A single rep who does everything from prospecting to close exists, and it is the exception, only where the product sells itself quickly, which in security it does not.

The price point picks the motion.

You do not choose the sales motion. The price does. Below a threshold the sale is inside sales with no travel. Above it the sale is consultative, the rep is more experienced, the cycle is longer, and pay rises with the quota carried. In security the threshold sits where the security review begins, because a deal that passes through a third-party risk process is an enterprise sale whatever the price on it. Find that line in your own closed deals, and staff each side of it differently.

The first quota is a ramp plan.

You will model a new rep as productive from the start, and the ramp is real, budgetable, and different by role. Openers ramp faster than closers, and a single rep doing everything ramps slowest. In security the closer's ramp is set by the buyer's evaluation cycle, the proof of concept, the security review, and the change queue, and no learning curve shortens that. So the first seller's number is a ramp plan rather than a quota: what they should have at each stage by each month, given the cycle you measured on your own closed deals. A quota assumes a ramp the rep controls. Yours does not.

Pay on cash, at countersignature.

You pay commission when the contract is countersigned and the cash arrives, never on the verbal yes and never on a letter of intent. Security deals slip rather than lose, and a plan that pays on the forecast pays for slippage. Pay the opener on qualified meetings that reached the second stage, not on meetings booked. Pay the sales engineer on the team's results, because the technical evaluation is shared work and a sales engineer on an individual quota stops sharing. Long cycles argue for a heavier base salary than the software template, because a rep who cannot make a living for three quarters leaves in the third.

Keep discount authority with the founder.

You give the rep no authority to discount in the first year, because the first request from every new seller is a discount, and the number you sign becomes the reference price your next buyer hears about. A rep who needs a discount to close has either a demand problem or a qualification problem, and the discount hides which one.

Add a team lead at a span, not a headcount.

You add a player-coach over a small group at a specific span of control, before any non-selling manager is justified. A manager over two reps is management bought for a thing nobody has done twice. The field overlay, meaning travelling reps for large deals, partnerships, and event-sourced pipeline, is a separate role, usually paid on team results rather than an individual quota, and it comes after the first group, not before.

Shape the team to the deals you close.

The advice is to hire an enterprise-experienced team in order to move upmarket, and that is how you acquire an enterprise cost structure before you have enterprise deal sizes. An enterprise-shaped organization on a mid-market business looks busy and stays unprofitable: extra layers of management, longer ramps, specialist roles, and higher on-target earnings, all paid out of a deal size that cannot support them, and the ratios take years to surface. Shape the team to the deals you actually closed this year. Reshape it when the deals change, and not before.

Working the question.

  1. Find the price line in your own closed deals where the security review begins, and staff each side of it differently.
  2. Write the first seller's number as a ramp plan by stage and month, from the cycle you measured.
  3. Pay on countersignature and cash, pay openers on qualified second-stage meetings, and pay sales engineers on team results.
  4. Keep discount authority with the founder for the first year.
  5. Add the player-coach at the span, add the overlay after the first group, and never put a non-selling manager over two reps.
  6. Shape the organization to this year's closed deals, and reshape it when the deals change.

Working with an agent.

Give your agent every deal you closed this year, with its price and its length. Ask it at what deal size the security review starts appearing. That price is where your sales motion changes, and paying a seller as though it does not is how a first comp plan goes wrong.

Install the skill.

You are reading the skill itself — this page and the download are the same files. Unzip it into ~/.claude/skills/ (or a project’s .claude/skills/) and Claude Code loads it when the question comes up; so does any agent that reads Agent Skills.

mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -sLO https://techoperators.com/skills/sales-comp-and-structure.zip && unzip -oq sales-comp-and-structure.zip && rm sales-comp-and-structure.zip

sales-comp-and-structure/SKILL.md

No terminal? Download sales-comp-and-structure.zip and drop into your assistant’s project files.

Kevin Skapinetz

Tell us what you see.

Whether you’re thinking about starting a company, building one in stealth, or raising a round: send Kevin or Dan what you see on LinkedIn, in your words.