SDR compensation plans in 2026: ranges, structures, and pitfalls

The best SDR comp plan is the one your reps understand in 60 seconds and can forecast to the dollar. The worst ones stack five modifiers on top of a base and ship in Q1 to explain the paycheck all year. Here are the 2026 SDR compensation ranges, the plan structures that hold up, and the ones we would refuse to run.

2026 US market ranges

For US-based SDRs at Series A to Series B B2B SaaS companies in 2026, expect the following fully loaded ranges:

• Base salary: $55K to $75K depending on region and experience.
• OTE (on-target earnings): $80K to $115K.
• Variable portion: 25 to 40 percent of OTE.
• Fully loaded (with benefits, tools, ramp): $135K to $180K per rep per year.

Enterprise SDR roles at $60K+ ACV motions run higher, typically $95K to $130K OTE. Remote roles from lower-cost US regions run 10 to 20 percent below coastal numbers. LATAM-based SDR pods run $2,000 to $5,000 per month all-in, which is why cost-efficient teams increasingly blend regions.

The three plan structures that work

1. Meeting-held variable. Reps earn a flat bounty per meeting held (not booked). Common range: $150 to $300 per held meeting. Simple, clear, easy to forecast, and aligns the rep with quality because no-shows do not pay.

2. SQL-tiered variable. Reps earn a smaller bounty per meeting held and a larger bounty per meeting that converts to SQL (a stage the AE controls). Aligns the SDR with real pipeline creation but requires clean SQL definitions and AE discipline.

3. Pipeline-created variable. Reps earn a percentage of ARR entered into pipeline from their sourced meetings. Best for enterprise motions where ACVs are large enough to move the number. Not appropriate for SMB where the calculation gets noisy.

Plans we would refuse to run

Plans with more than three variable components are a red flag. Any plan that requires a Slack thread to calculate a paycheck destroys morale. Plans that pay on activity (dials, emails sent) create incentives to sandbag quality. Plans that clawback commissions when a deal churns 12 months later shift risk to the wrong party and drive attrition.

Quotas that hold up

A working SDR quota for a mid-market B2B SaaS motion in 2026 is 10 to 14 meetings held per month, of which 60 to 75 percent convert to SQL. Below that, either the ICP is too small, the sequences are broken, or the reps are undermanaged. Above 16 meetings held per rep per month sustained for a quarter, you are usually seeing quality degradation the AEs will surface within 60 days.

Ramp is a comp problem

Most plans do not handle ramp cleanly. A new SDR typically needs 4 to 6 months to hit quota. Guaranteeing 100 percent of variable in month 1, 75 percent in month 2, 50 percent in month 3 gives the rep runway without letting the guarantee become a habit. See our fractional vs in-house SDR breakdown for the total ramp cost math.

Accelerators and decelerators

Above 110 percent of quota, accelerate the variable rate by 1.25x to 1.5x. Below 60 percent for two consecutive months, deceleration or a performance plan is the honest move, not lowering quota. Accelerators are what separate high performers who stay from high performers who leave.

Quality guardrails

Any meeting-based plan needs a quality guardrail or you will pay for garbage. Common guardrails: 80 percent minimum show rate, meeting must be with an ICP-fit account, meeting cannot be with an existing customer or open opportunity, AE must accept the meeting within 24 hours or the SDR resubmits. Without these, the plan pays for activity theater.

Team spiffs that actually motivate

• First-meeting-of-the-week spiff (small, weekly, resets Monday).
• Top-of-funnel president's club: quarterly, top 20 percent, real budget.
• Team-level unlock for hitting monthly SQL target (dinner, half-day off, real perk).
• Individual spiff for booking a target-named account (list of 20 to 50, refreshed monthly).

What compensation cannot fix

Broken data, broken deliverability, and broken management cannot be compensated around. Reps under those conditions will churn regardless of OTE. The fastest way to overpay is to raise OTE to compensate for a broken motion. See our cost per meeting benchmarks to sanity-check whether the motion is the problem, not the comp.

The AE handoff clause

Your comp plan should specify what happens when an AE rejects a meeting. The healthy pattern: AE has 24 hours to reject with a written reason, SDR is not penalized, and the reason feeds a monthly quality review. Without this, AEs quietly reject meetings and SDRs stop trusting the pipeline data.

Common mistakes

1. Setting quota based on last quarter's outlier rep.
2. Stacking a base, meeting bounty, SQL bounty, pipeline percentage, and MBO in one plan.
3. Not capping accelerators (rare, but produces windfalls that break the P&L).
4. Paying on meetings booked instead of held.
5. Rolling out mid-quarter comp changes without honoring the prior plan for existing meetings.

When to consider a managed pod instead

If you cannot yet justify a manager, a comp analyst, and 3+ SDRs, the total cost of running a small in-house team usually exceeds the cost of a managed pod that produces the same pipeline. See our managed outbound overview or the SDR as a service page for how a pod replaces the in-house math.

The closing take

A great SDR comp plan is boring, forecastable, and quality-anchored. Complexity is not sophistication; it is a failure mode. If you would rather skip the plan design and buy a working motion with reps who are already comp'd and managed, book a 20-minute pipeline review.