Sales Compensation, Quota Capacity & Commission PlansPlaybook3 min readUpdated September 2026

Commission Math When a Deal Carries Heavy Hosting Costs

A deal on your standard shared infrastructure and a deal that requires a dedicated, single-tenant environment can carry the same contract value on paper while costing the company very different amounts to actually deliver. Paying commission purely on contract value treats these as identical, which quietly rewards reps for selling the less profitable version of your product.

Here's how to think through adjusting the calculation without punishing reps for selling what the customer actually needed.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Why Contract Value Alone Is the Wrong Base

Commission on raw contract value assumes gross margin is roughly consistent across deals of similar size. That assumption breaks down when a customer requires a dedicated hosting environment for compliance or performance reasons, since the cost to deliver that environment can be substantially higher per dollar of revenue than your standard shared-infrastructure offering. A rep chasing the largest possible commission check has no reason to know or care about this difference unless the comp plan accounts for it.

Moving to a Margin-Aware Commission Base

The more accurate approach pays commission on a margin-adjusted number rather than raw contract value, factoring in the estimated cost of delivery for that specific deal type. This doesn't need to be a precise, deal-by-deal cost accounting exercise; a simpler version applies a lower commission rate specifically to the private or dedicated hosting tier, reflecting its known lower average margin, while standard shared-infrastructure deals keep the normal rate.

Being Transparent About Why the Rate Differs

Reps will notice a lower rate on certain deals and will ask why. Explain the reasoning directly: dedicated hosting costs the company more to deliver, so the commission reflects that difference, not a judgment that the deal itself was less valuable or less hard to close. A rep who understands the margin logic is far less likely to feel like they're being penalized for meeting a real customer requirement, especially if leadership can show the actual cost gap rather than just asserting one exists.

For example, a rep who learns about the lower dedicated rate only when a payout statement arrives will likely assume an error. Instead, share the reasoning at plan rollout: show the cost gap between hosting tiers in plain terms, explain that the rate reflects delivery cost rather than selling effort, and give managers the same one-page explanation so answers stay consistent. When a rep later pushes back on a specific deal, you can point to a rule everyone saw in advance instead of defending a decision after the fact. Revisit the rate when finance's estimate of the margin gap changes, so the adjustment keeps matching reality and never goes stale.

Avoiding the Opposite Problem

Don't overcorrect into a structure so punitive on dedicated hosting deals that reps start steering customers away from an option that might genuinely be the right fit for their compliance or performance needs. The goal is aligning incentive with actual margin, not discouraging reps from selling what the customer legitimately requires. If a customer needs dedicated infrastructure and a rep talks them out of it to protect their own commission, that's a worse outcome than the original problem.

A reasonable guardrail is to keep the rate difference between tiers modest enough that a rep's total commission on a dedicated deal still meaningfully exceeds what they'd earn walking away from the sale entirely. The adjustment should shave the edges off an unfair incentive, not flip it into the opposite unfairness.

A Worked Comparison

Say two deals close in the same month at a similar contract value, one on shared infrastructure and one requiring a dedicated environment. Under a flat commission rate, both checks look identical. Under a margin-aware rate, the dedicated deal's check is somewhat smaller, reflecting its higher delivery cost, while the shared-infrastructure deal earns the full standard rate. Walking a rep through this comparison directly, ideally before they're negotiating a deal that might land in the dedicated tier, helps the logic land as fair rather than as a surprise discovered on a payout statement.

Tracking Which Tier Applies

This kind of tiered commission only works if the deal record clearly states which hosting tier applies at the time of close, so the calculation isn't a manual judgment call each payout cycle. Tag deals by hosting tier in Pipedrive at the point the customer's requirement is confirmed, and let that tag drive which commission rate applies once the deal reaches Rippling for payout, rather than relying on someone remembering which deals were which by the time commission runs.

When setting a margin-aware rate, check these points:

  • Finance and sales leadership set the rate together, starting from the estimated margin gap between hosting tiers.
  • The lower rate applies only to the dedicated tier, while shared-infrastructure deals keep the standard rate.
  • The rate gap stays modest, so a rep still earns meaningfully more on a dedicated deal than by walking away from it.
  • The deal record states the hosting tier at close, so the rate is not a manual judgment call each payout cycle.
  • Reps hear the margin reasoning, ideally with a worked comparison, before they negotiate a dedicated deal.
Executive Capability Standard

What Good Looks Like

A margin-aware commission structure applies a different rate to deal types with meaningfully different delivery costs, communicates the reasoning openly to reps, and ties the applicable rate to a deal record field rather than a manual judgment call at payout time.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Ask finance for the actual average margin difference between your standard and dedicated hosting tiers before assuming a rate adjustment is even needed.
2. Do Manually:Model what commission checks would look like under a margin-adjusted rate for last quarter's dedicated hosting deals before rolling it out.
3. Delegate:Have RevOps own tagging deal hosting tier correctly at close and resolving edge cases like mid-contract upgrades.
4. Automate:Tag hosting tier in Pipedrive at the point it's confirmed and let that tag drive the applicable rate through to Rippling for payout.
5. Buy:Bring in a finance or compensation consultant if margin data by deal type isn't reliable enough yet to set a defensible rate.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Frequently Asked Questions

How do we set the lower commission rate for dedicated hosting deals?

Start from finance's estimate of the average margin difference between the two delivery tiers, then set a rate that still rewards the rep meaningfully while reflecting the lower profitability. This is a finance and sales leadership decision together, not something sales operations should set alone without margin input.

What if a deal starts as standard hosting and later upgrades to dedicated?

Define this upgrade case in the plan rather than leaving it ambiguous. Typically the rate at the time of the upgrade applies to the incremental value, while the original deal keeps the rate that applied when it first closed.

Should this same logic apply to other cost-heavy deal types, like extensive custom integration work?

Yes, the same margin-aware logic applies anywhere a deal type reliably carries a different cost to deliver. The hosting tier example is common, but any deal category with a known, consistent margin difference is a candidate for the same treatment.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides