Should I pay SDRs on demos booked or only on demos held + qualified in 2027?

The Tuesday morning that exposes the plan

Picture a mid-market SaaS company with six SDRs, four AEs, and a comp plan that pays $75 per booked demo. It is Tuesday. The VP of Sales opens the pipeline dashboard and sees 41 demos booked last week — a record. She opens the AE calendar view and sees something else entirely: fourteen of those demos no-showed, six were rescheduled into the following month, and of the twenty-one that actually happened, the AEs disqualified nine on the call. That leaves twelve real conversations out of forty-one booked events. The company paid $3,075 in SDR commission for twelve meetings that mattered, which works out to $256 per meaningful conversation — but the accounting is the smaller problem.

The bigger problem is what happened in the room. The AEs burned roughly fifteen hours of calendar time on meetings that were never going to go anywhere. One AE spent forty minutes on a call with a nineteen-person company when the ICP floor is two hundred employees. Another sat through a "demo" that turned out to be a student doing research for a class project. A third took a meeting where the prospect thought they had agreed to a five-minute intro call and got a screen-share pitch instead — that person now has a bad impression of the brand, and no comp plan line item will ever capture that cost.

By Thursday, the AEs have started a private Slack channel where they screenshot the worst bookings. By the next quarter, they have stopped preparing for SDR-sourced meetings entirely, treating them as low-probability lottery tickets. When AEs stop preparing, even the genuinely good SDR meetings convert worse — and now the SDR team's real wins are being punished for the junk. The comp plan created a quality problem, the quality problem created a trust problem, and the trust problem is now suppressing the conversion rate of legitimate work. That is the full arc, and it starts with a single design choice: paying at the moment of booking.

Notice what nobody in this story is doing wrong. The SDRs are not cheating. They are responding rationally and efficiently to the scoreboard they were handed. If the fastest path to $75 is a calendar invite, the fastest path to $75 is a calendar invite — and a good SDR will find it faster than a mediocre one. The most common mistake leadership makes here is to treat this as a character problem and respond with more policing: booking-quality reviews, manager spot-checks, a "please only book good meetings" all-hands. None of it holds, because you are asking people to override a financial incentive with willpower. Move the money and the behavior moves with it, permanently, without a single lecture.

The same dynamic shows up in adjacent seats and is worth recognizing because the fix generalizes. Marketing teams paid on MQL volume produce MQLs that no one can call. Customer success teams bonused on ticket closure close tickets fast and reopen them fast. Partner managers paid on signed partner agreements sign partners who never source a deal. In every case the pattern is identical: the paid metric is the earliest, most controllable event in the chain, and the earliest event is precisely the one that carries the least information about value. RevOps exists in large part to notice this pattern and move payout triggers downstream to the first point where value is both real and observable.

How the mechanism actually works

The reason booked fails and held-plus-qualified works is not moral, it is informational. At each funnel stage you know more about whether the event was worth anything, and comp should attach at the earliest stage where that knowledge is both sufficient and auditable.

At the moment of booking, you know one fact: a person clicked accept on a calendar invite. You do not know whether they will show, whether their company fits your ICP, whether they have a problem you solve, whether they can buy, or whether they understood what the meeting was for. Five unknowns, all of which determine value, none of which are resolved.

At the moment the meeting is held, you have resolved exactly one unknown — attendance. That is real progress and it is why "held" is worth gating on, but a held meeting can still be completely worthless. The prospect showed, listened politely, has no budget, no authority, and no pain. Held is necessary and nowhere near sufficient.

At the Sales Accepted Opportunity — held, plus the AE formally accepts, plus it clears a written rubric — you have resolved all five. This is the first funnel stage that is simultaneously verifiable (there is a timestamp, an owner, and usually a call recording) and a genuine proxy for value (a qualified, accepted opportunity converts to revenue at a rate you can actually measure). That combination is the whole design principle: pay as close as possible to the moment value is both created and confirmable.

The rubric is what turns "qualified" from a feeling into a mechanism. Use four dimensions — call them Fit, Problem, Authority, and Intent. Fit means the account is inside ICP on industry, size, and technical environment, verified against firmographic data on the account record, not vibes. Problem means the prospect articulated a specific pain your product addresses, verifiable in AE call notes or the recording. Authority means the attendee is a decision-maker or a named, credible champion with an actual described path to one — "they'll probably loop in their boss" does not pass, "Marcus in Finance owns the budget and she's introducing me next week" does. Intent means the prospect knowingly agreed to an evaluation conversation, not "a quick chat."

Make each dimension binary wherever possible. "Is the attendee inside ICP — yes or no" is dramatically harder to argue about at payday than "rate fit 1 to 5." Set an explicit pass bar in writing: most teams require all four to pass, some allow three of four with a documented reason. Either is defensible; leaving it unstated is not. Require the AE to complete the rubric within twenty-four hours of the meeting, while the call is fresh, and enforce that SLA visibly — the "I'll get to it" black hole is the single most common cause of delayed SDR pay and the resentment that follows.

There is a structural point hiding in that diagram worth stating outright: the SDR cannot be the sole owner of any payable stage. Booked is entirely SDR-controlled, which is exactly the reason it must not be payable. SAO requires an action by a second party with opposing interests — the AE, who pays the price for junk meetings — and that opposition is the control. Any payout trigger a single person can flip unilaterally will eventually be flipped for reasons other than the ones you intended.

Before any of this is implementable, five funnel stages need to be defined in writing, instrumented as single auditable CRM fields with owners and timestamps, and signed off by both Sales and Marketing: booked, held, SAO, pipeline or SQO, and closed-won. If "accepted" lives in three places — a checkbox, a stage, and a Slack message — you cannot pay reliably and you certainly cannot audit fairly. And Marketing and Sales must share one SAO definition. Two definitions produce a turf war over credit that consumes more leadership time than the comp plan itself ever will.

Real numbers, ranges, and benchmarks

Work backward from On-Target Earnings, because the per-unit number falls out of the OTE math rather than being picked in isolation.

Variable comp for an SDR generally lands at 35-45% of OTE. A 60/40 base-to-variable split is a common default; aggressive high-velocity teams push to 50/50, more conservative or enterprise-leaning teams sit at 70/30. Take a worked mid-market example: OTE of $80,000 on a 65/35 split gives base $52,000 and variable $28,000. Put 70% of that variable on SAO and you get $19,600 per year in the SAO bucket, with $8,400 in the downstream kicker bucket.

Now set the SAO quota from actual conversion data, never from the old booked number. If the quota is 14 SAOs per month, that is 168 per year, and $19,600 divided by 168 is roughly $117 per SAO at 100% attainment. If instead you carelessly carried over a 30-per-month booked quota into an SAO plan, you would set every SDR up to miss by half and detonate the team within a quarter.

Typical per-SAO ranges by segment, as a sanity band: SMB and velocity motions with ACV under $15,000 run $50-90 per SAO on a quota of 16-22 per month. Mid-market at $15,000-60,000 ACV runs $90-150 per SAO on 10-15 per month. Enterprise above $60,000 ACV runs $150-250 per SAO on 6-10 per month. The logic is proportional: higher-ACV segments produce fewer, harder, more valuable meetings, so each unit is worth more and the volume expectation drops.

The downstream kicker gets sized against sourced pipeline. If a mid-market SDR at quota sources roughly $1.4M in pipeline annually, an $8,400 kicker is about 0.6% of sourced pipeline. What the kicker pays on should vary by cycle length, and this is the detail most teams get wrong. Velocity motions can pay the kicker on closed-won, because a January booking can close in February and the SDR feels the connection. Mid-market should generally pay on pipeline created — an opportunity reaching a real stage with an amount and a close date — because closed-won is one to three months out and the motivational link is weak. Enterprise should pay on pipeline or SQO and essentially never on closed-won, because a nine-month cycle means paying an SDR in Q4 for Q1 work, quite possibly after they have been promoted into an AE seat, which creates a genuinely awkward payroll situation.

Accelerators matter more than most plans admit. Pay 1.2x to 1.5x per SAO above quota, scaling the multiple with segment — 1.2x for velocity, 1.5x for enterprise where each unit is scarcer. An SDR consistently exceeding quota with genuinely qualified meetings is the highest-ROI headcount in the revenue organization, and overpaying them is deliberate, correct, and cheaper than replacing them. Skip the decelerator below quota. On an entry-level role, decelerators mostly accelerate attrition; handle underperformance with coaching and performance management, not a comp death spiral. During ramp, months one through three, a modest monthly guarantee prevents new hires from being punished for the unavoidable pipeline-build lag.

Make the numbers concrete with three SDRs on the same mid-market plan. Priya books 34 meetings a month, well above team average, and was the top earner under the old booked plan. Under SAO comp: 34 booked, 21 held (62% — she books a lot of soft "let's just chat" meetings), 9 clearing the rubric (43% of held, mostly failing Fit and Intent). Nine SAOs against a 14 quota is 64% attainment, about $12,636 in the SAO bucket, and a thin kicker near $4,000 because her borderline SAOs do not progress. Total variable roughly $16,600 against a $28,000 target.

Marcus books 22 a month, far fewer, but qualifies hard on the phone before offering a slot. He holds 18 of 22 (82%) and lands 14 SAOs (78% of held), hitting exactly 100% attainment for $19,600, and his SAOs progress cleanly for a full $8,400 kicker — $28,000 variable, full OTE. He books twelve fewer meetings a month than Priya and earns over $11,000 more. Put those two rows next to each other on a dashboard and you have the most powerful SDR coaching artifact your managers will ever have.

Dana averages 16 SAOs a month, 192 against a 168 quota. The first 168 at $117 is $19,656; the 24 above quota at a 1.3x accelerator ($152) adds $3,648, for roughly $23,300 in SAO pay, plus a stronger kicker near $10,200 on about $1.7M sourced. Total variable around $33,500, or 120% of OTE. That overpayment is not a leak — it is the cheapest pipeline in the company, and Dana has the best résumé on the team and the most inbound recruiter traffic. The accelerator is a retention tool wearing a comp-line costume.

Trade-offs, alternatives, and the honest counter-case

Three forces pull against each other in every incentive design, and no funnel stage wins all three. Proximity to value pulls toward closed-won — pay where revenue actually appears. Controllability pulls toward booked and held — pay on what the rep owns end to end. Verifiability pulls toward objective, timestamped, single-owner events. Booked wins controllability and loses proximity badly. Closed-won wins proximity and loses controllability. SAO is the equilibrium: close enough to value to be meaningful, controllable enough to be fair, verifiable if you build the rubric and turn on recording.

The 70/30 split is itself a compromise on that triangle, and both extremes are worth understanding. Putting 100% on SAO makes the SDR structurally indifferent to everything after handoff — they will tolerate borderline-passing qualification and move on, because nothing downstream touches their paycheck. Pushing to 50/50 or heavier on closed-won puts too much pay on an outcome the SDR does not control: they do not run the deal, set price, handle procurement, or close. Tie half their income to closed-won and a strong SDR routed to a weak AE gets punished for someone else's performance. There is a real fairness ceiling here, somewhere around 35% downstream weight, past which the plan reads as a lottery rather than a meritocracy — and the SDRs with the most options leave first.

On the held bonus: default to folding "held" into the SAO definition and paying nothing separately, since SAO already requires the meeting to have occurred. The exception is a structurally high no-show environment — long booking lead times, hard-to-reach personas, field or event-sourced meetings — where a small held bonus of roughly $15-30 usefully funds the chase work of confirmation calls, reminder sequences, and reschedule hustle. Carve it out of the 70% bucket rather than adding it on top, and keep it small enough that nobody can farm it.

Now the honest counter-case, because there are narrow situations where booked-weighting is temporarily defensible. A brand-new SDR team with zero funnel history cannot set an SAO quota that is not a guess; running booked-weighted for one quarter purely to collect booked-to-SAO conversion data is legitimate, provided everyone knows it is a calibration phase with a written sunset date. A pure appointment-setting function genuinely decoupled from qualification — where a separate inside team does all the qualifying — has a case, though even there paying setters on held and the qualifying team on SAO beats pure booked. Severe AE capacity constraints can distort accepts so badly that SDRs get under-paid for reasons outside their control, but the correct fix is hiring AEs and fixing routing, not retreating to booked. And in an extremely high-velocity motion where instant-booked demos almost always hold, the booked-to-held gap is genuinely small — but you still want a qualification gate, so the answer is "held plus light qualification," not booked.

A small booked component, say 10% of variable, can also work as a deliberate activity floor during the first two quarters of a new team so raw outbound volume does not collapse while people learn to qualify. Treat it as training wheels with a removal date in the plan document. The danger is never the 10% — it is that 10% quietly becomes 30% because a sales manager finds it the easiest lever to pull when monthly meeting counts dip, and eighteen months later the junk-meeting problem is fully back under a different name. Any booked component needs an explicit sunset, a quarterly review, and someone willing to defend it by name.

One alternative deserves explicit rejection: paying on booked and adding clawbacks for no-shows and disqualifications. This is a booked plan wearing an SAO costume and it inherits the worst of both. It pays before quality is known, then yanks money back later — maximizing loss aversion and destroying trust while delivering none of the behavioral benefit. Behavioral research going back to prospect theory shows people feel a loss roughly twice as intensely as an equivalent gain. An SDR who watches $117 appear and vanish two pay periods later experiences a punishment, not a correction, no matter how correct the accounting. If you need clawbacks — and you do — make them same-period only. A correction inside the same paycheck reads as "the number was still settling." A reversal three months later reads as "they took my money."

Pitfalls, controls, and the migration path

Every comp plan is a system under adversarial pressure from smart, motivated people. Design the controls before launch, not after the first scandal.

The AE-accept is the primary control, and it needs controls of its own, because it can be corrupted in both directions. Collusion looks like an AE who is friendly with an SDR, or desperate for pipeline coverage, rubber-stamping marginal meetings; the SAO count rises while SAO-to-pipeline conversion collapses, which means you are now paying booked-quality meetings under an SAO label. Counter it three ways: the rubric forces specific written criteria so "accept" is not a mood, a slice of AE variable comp ties to opportunity progression and win rate so junk accepts cost the AE something, and a monthly audit pulls ten to fifteen random SAOs and checks them against the recordings. Publish that the audit happens — the deterrent effect is most of the value.

Over-rejection is the mirror failure: an AE who dislikes an SDR, or simply wants to protect their calendar, rejects legitimate meetings. Track reject rate per AE. An AE rejecting 40% when the team averages 15% is the anomaly, not the SDR who keeps landing in front of them. Give disputes a fast, neutral arbitration path — RevOps or a sales manager who reviews the recording and rules within 48 hours — and never let a single AE be both the rejecter and the final word. Arbitration doubles as a data source: a pattern of overturned rejections from one AE is a management conversation, and so is a pattern of overturned accepts.

Beyond the accept, a handful of specific exploit-killers earn their keep. Cap SAOs per SDR-AE pair per week — something like three — so no single friendly pairing can become a collusion machine. Cap same-account SAOs so one logo cannot generate five payouts a quarter through creative relabeling of internal stakeholders. De-duplicate accounts with a written tiebreak rule, usually first-touch or account ownership, so two SDRs working the same logo produce one SAO and no argument. Recycle rather than punish no-shows: allow a rebook inside a 30-90 day window to still earn credit when it eventually holds, which removes the incentive to over-book as insurance. And watch the ratios per SDR, because they localize problems precisely — a 95% booked rate with a 40% held rate means junk bookings, while a high held rate with a 30% SAO rate means the meetings happen but do not qualify. Those are two entirely different coaching conversations.

Decide the messy edge cases in advance so they are policy rather than improvisation. An inbound lead where the SDR only confirmed a time is not full SAO credit — pay a reduced rate or none, and write the rule down. An SAO that a different AE eventually closes should keep the SDR's credit attached to the opportunity, not the AE seat, with a documented snapshot taken at SAO time. A prospect who re-engages and qualifies months later gets credit inside the recycle window and counts as a fresh meeting beyond it. A partner-sourced meeting the SDR coordinated usually earns reduced credit, since real work happened but the demand was not SDR-sourced. And a held meeting where the recording shows the prospect expected something other than an evaluation is an Intent failure — disqualify it and coach, because that is exactly the behavior a booked plan rewards and an SAO plan exists to catch.

Migration is where good plans die. Do not flip the switch overnight; a mid-quarter change that cuts take-home pay is the most reliable attrition trigger in sales management. Announce a full quarter ahead and lead with the why — quality, AE trust, the credibility of SDR-sourced pipeline in the forecast — not just the what. Run a shadow quarter where you keep paying the old plan while calculating the new one in parallel, then show every SDR both numbers side by side; this converts abstract fear into data and surfaces design bugs before they cost real money. Build the rubric, the CRM fields, the 24-hour AE SLA, and call recording before launching, because a plan you cannot audit is a plan you cannot defend. Hold OTE flat or raise it: the migration changes what SDRs are paid for, not how much a good SDR earns, and if your top performers would earn less at identical performance, the per-SAO value is mis-sized. Re-baseline quotas from real booked-to-SAO conversion. Grandfather in-flight meetings under the old plan with a clean cutover date. And over-communicate the first two paydays — have managers walk each SDR through their statement line by line, because that first paycheck is where the plan earns trust or loses it permanently.

Instrumentation makes all of this routine rather than heroic. You need five timestamped fields (booked, held, SAO, pipeline, closed-won), the four rubric dimensions as structured pass/fail fields rather than free text, an accept owner and timestamp with a visible SLA clock, validation rules that refuse to flip the SAO flag until the rubric is complete, and field history tracking on every payable field so a clawback is defensible rather than a "trust me." Layer on conversion dashboards sliced by SDR, by AE, and by source, plus a live self-serve comp tracker each SDR can check — surprise-free paydays are a measurable retention lever. The tooling landscape supports all of it: Salesforce or HubSpot as system of record, Gong or Salesloft or Clari for conversation intelligence and recording, dedicated incentive compensation tools like CaptivateIQ, QuotaPath, Spiff, Everstage or Xactly so payout math is never a hand-edited spreadsheet with one person as the single point of failure, and outbound platforms like Outreach, Salesloft, or Apollo writing activity and booking data back so booked-to-held is measured rather than guessed. Before launch, run one true end-to-end test: a real meeting booked, held, rubric-completed, SAO flag flipped, commission computed, statement visible — with nobody touching a spreadsheet. If that loop works for one meeting it works for ten thousand.

Finally, review plan health quarterly against a short list of signals. Booked-to-SAO conversion should trend up as SDRs stop booking junk; flat or falling means the rubric is being gamed. No-show rate should trend down. SAO-to-pipeline should hold or rise — if SAO count climbs while pipeline does not, your pass bar has gone soft. The attainment distribution should cluster most SDRs between 80% and 120% with a real right tail; if everyone is above 130% the quota is too low, if everyone is below 70% you have a retention bomb ticking. Watch accept and reject rates by AE for outliers, comp as a percentage of SDR-sourced revenue as the efficiency number finance cares about, dispute volume at arbitration (a spike means an ambiguous rubric dimension), ramp-time-to-first-SAO by hire cohort as a leading indicator of onboarding clarity, and the near-miss rate — meetings that held and failed exactly one dimension. Near-misses clustering on one dimension, Authority especially, is a team-wide coaching theme and possibly a sign that dimension's bar is mis-calibrated.

Related questions

Should I pay a partial commission for demos that no-show?

No — pay nothing at no-show, but allow the SDR to earn full SAO credit if the meeting is rebooked and held within a 30-90 day recycle window. That removes the incentive to over-book as no-show insurance without punishing SDRs for prospect behavior they cannot control.

Who should own the "qualified" decision — the AE or a manager?

The AE, because they bear the cost of junk meetings, with a manager or RevOps as the arbitration backstop. Requiring manager approval on every meeting creates a bottleneck that delays SDR pay; requiring nobody creates a self-serve payout. AE accept plus 48-hour arbitration balances both.

How does this change for a product-led motion where prospects self-book?

Self-booked demos need a fit-and-intent gate more than an attendance gate, since they almost always hold. Pay SDRs only on self-booked meetings they meaningfully influenced or qualified, and route pure self-serve bookings outside the SDR quota entirely so nobody earns commission on a form fill.

Should SDR comp include a component for pipeline the AE never works?

No, but track it. If accepted opportunities repeatedly sit unworked, that is an AE capacity or routing failure, and penalizing the SDR for it will drive out good people. Fix routing, then hold the SDR kicker on pipeline stage progression rather than AE activity.

What if we only have two SDRs and no formal CRM stages?

Start with the definitions, not the tooling. Two SDRs still need a written rubric, a single "accepted" field with a timestamp, and a rule about recycles. You can run this in a spreadsheet honestly for a quarter; you cannot run it on verbal agreements at any headcount.

FAQ

My SDRs say the SAO plan makes their pay depend on AEs they cannot control. Are they right?

Partly, which is exactly why downstream weight is capped near 30% and the primary 70% rides on SAO — something the SDR substantially controls through which accounts they source and how well they qualify before offering a slot. The AE accept is a gate, not a lottery: a genuinely qualified meeting passes for any honest AE. If SDRs experience accepts as arbitrary, your rubric is too subjective or one specific AE is a statistical outlier. Fix the rubric or the AE; do not retreat to paying on booked.

Should marketing-sourced meetings count toward an SDR's SAO quota?

Only when the SDR did real qualification work. A pure calendar-confirm on a marketing lead is not a full SAO and paying it as one both inflates attainment and creates a race to camp on inbound rather than prospect. Either exclude inbound from the SDR quota entirely or pay a clearly reduced rate — and write the rule into the plan document so it is not re-litigated every month by whoever had the slowest week.

How long should it take an SDR to get paid under a held-and-qualified plan?

Typically days to two weeks from booking: the meeting has to occur, then the AE completes the rubric within a 24-hour SLA. That short delay is the entire cost of the model, and you are buying something valuable with it — paying once, on a verified event, with no clawback in the normal case. Booked plans pay faster but run a permanent pay-early-correct-later cycle that generates administrative overhead and erodes trust.

Do we still need a booked-demo metric at all if we do not pay on it?

Absolutely. Booked stays a tracked activity metric and one of your best coaching inputs — it is the numerator in the booked-to-held and booked-to-SAO ratios that localize exactly where an individual SDR is struggling. The rule is narrow and specific: measure booked, coach on booked, never pay on booked. A metric stops being a good measure the moment cash is attached to it.

What per-SAO dollar value should we start with if we have no historical data?

Do not start with a per-SAO number — start with OTE. Decide the OTE, split it 60/40 or 65/35 base to variable, put 70% of the variable in the SAO bucket, then divide by a quota estimated from whatever booked-to-qualified conversion you can observe over even a few weeks. Sanity-check the result against the segment bands: roughly $50-90 for SMB, $90-150 for mid-market, $150-250 for enterprise.

How do we stop AEs from rubber-stamping meetings to keep SDRs happy?

Give the accept a consequence. Tie a meaningful slice of AE variable comp to opportunity progression and win rate on SDR-sourced deals, so an AE who accepts junk watches their own conversion metrics sag. Add a monthly random audit of ten to fifteen SAOs against call recordings, cap SAOs per SDR-AE pair per week to break up friendly pairings, and publish that both controls exist. Most of the deterrent value comes from people knowing the audit happens.

Sources

• https://blog.hubspot.com/sales/sales-compensation
• https://www.saastr.com/how-to-comp-your-sdrs/
• https://www.gartner.com/en/sales/topics/sales-compensation
• https://hbr.org/2015/04/motivating-salespeople-what-really-works
• https://www.salesforce.com/resources/articles/sales-compensation-plans/
• https://www.forrester.com/blogs/category/demand-management/
• https://openviewpartners.com/blog/sales-development-compensation/
• https://www.gong.io/resources/
• https://www.pavilion.com/blog

Related on PULSE

• How should I structure SDR commission to discourage gaming MQL counts?
• What's a fair OTE for an enterprise AE selling $100k+ ACV deals?
• What accelerator multiples are typical past 100% of quota for SaaS AEs?
• What's the right SPIFF cadence to drive end-of-quarter pipeline pull-ins?
• How do I define SQL vs SAO vs SQO so Sales and Marketing stop fighting?
• What should an SDR-to-AE promotion scorecard actually measure?