Most companies spend significant time refining strategy.

Market positioning is debated. Pricing is adjusted. ICP definitions are updated. Growth ambitions are recalibrated.

But behaviour inside the organisation rarely shifts because of strategy documents.

It shifts because of incentives.

What Counts as an Incentive in a Revenue System

Compensation structures, quota mechanics, approval thresholds and reporting definitions quietly determine how people act under pressure. They define what feels safe, what feels rewarded and what feels risky.

Strategy expresses intent.

Incentives shape behaviour.

If strategy emphasises long-term positioning but compensation rewards short-term volume, behaviour will follow the compensation plan. If leadership communicates margin discipline but approvals accelerate under quarter-end pressure, discounting behaviour adjusts accordingly.

No memo overrides a misaligned incentive.

When I review a revenue system, I treat as an incentive anything that affects a person’s earnings, their decision rights or the way their performance is assessed. The compensation plan is only one part of that. A fuller inventory usually includes:

  • Pay mechanics: commission rates, accelerators, SPIFs, multi-year kickers, crediting and split rules, and clawbacks.
  • Quota mechanics: how targets are set and allocated, how ramp is treated and whether quotas move during the year.
  • Approval thresholds: who can sign off a discount, a non-standard term or a customer outside the ICP, and how long that takes.
  • Reporting definitions: what counts as pipeline, what qualifies a deal for commit and which numbers get discussed in leadership meetings.
  • Recognition and progression: who gets promoted and who is given the strongest accounts.

Each item sends a signal about what the organisation values. Where those signals conflict with the strategy, people tend to follow the one that affects them most directly, which is usually pay or the approval process.

Where the Effects of Incentive Design Show Up First

The effects are often subtle.

Deal structure changes first. Then pipeline composition shifts. Forecast probabilities drift. Customer selection becomes narrower or broader depending on what is rewarded.

Each of these shifts is hard to see from the leadership table because, deal by deal, it looks like a reasonable commercial decision. A larger discount closes a deal that matters this quarter, and a prospect slightly outside the ICP looks worth pursuing when pipeline is thin. The pattern only shows up in aggregate, across several quarters of deal data, which is why I look for it in the CRM before asking anyone about it.

Over time, the revenue system begins to optimise for the logic embedded in incentives rather than the logic articulated in strategy.

This is not cynicism.

It is rational behaviour.

Why Every Function Optimises for a Different Number

Sales leaders optimise for quota attainment. Customer success leaders optimise for retention and expansion metrics. Marketing optimises for pipeline generation targets. Finance optimises for predictability and margin protection.

If those optimisation logics are not structurally aligned, misalignment is inevitable.

In my experience, the conflict surfaces at the decisions these teams share:

  • a discount request late in the quarter, between a sales leader who needs the deal and a finance leader accountable for margin;
  • an expansion opportunity, where an account executive and a customer success manager may both expect the credit;
  • the handoff from Sales to Customer Success, between a team paid at signature and a team measured on adoption and renewal;
  • lead acceptance, where Marketing is measured on volume and Sales on the quality of what it receives.

At each of these points, one team’s metric has to give way to another’s. If leadership has not decided in advance which one, it gets decided deal by deal, and the outcome depends on who is under the most pressure that week.

Incentive design is therefore not an administrative exercise.

It is architectural.

In practice, that changes who should be involved in designing it. Finance usually owns the cost model for a compensation plan, and sales leadership knows how the field will read it. What tends to be missing is a behavioural model: which deals the plan makes more attractive, and where it pays for something the strategy is trying to discourage. RevOps holds the deal history needed to build that model, so it belongs in the room when the plan is designed.

How to Tell If Your Incentives Are Working Against Your Strategy

The diagnostic I use starts with the strategy and works backwards to the incentives. It needs a few working sessions and the last four quarters of won and lost deals.

  1. List the behaviours the strategy depends on. Examples include selling within the ICP, holding price, multi-threading larger deals and handing accounts over cleanly. Keep the list short and specific enough to observe in data.
  2. Trace each behaviour to the incentives that touch it. Ask what the compensation plan, approval rules and reporting definitions do when that behaviour costs an individual time or money. If a rep loses commission by walking away from a poor-fit deal, the plan is working against the ICP.
  3. Check the deal data. Look at discount depth by week of the quarter, close dates around quota resets and accelerator thresholds, win rates and deal sizes inside and outside the ICP, and how often forecast categories change in the final month.
  4. Ask the people closest to the pressure. The answers to a question such as “what do you do when you are behind with three weeks left?” usually describe the working incentive system more accurately than the plan document does.

Where the incentive trace and the deal data both point away from the strategy, that incentive is the place to start. A revenue architecture audit applies the same logic across the wider operating model.

How to Test an Incentive Structure Before It Goes Live

Before adjusting targets or refining messaging, leadership should ask:

What behaviour will this structure reward under pressure? Where will individuals optimise if performance gaps appear? What trade-offs are we embedding implicitly? Who has authority to enforce discipline when incentives conflict?

These questions are uncomfortable because they expose tension between ambition and discipline.

But they are essential.

They are easier to answer against specific scenarios. I usually test four: a rep just short of quota with two weeks left, a rep already past quota with a large deal ready to close, a sizeable deal outside the ICP, and a renewal where the customer wants a discount in exchange for expanding. Walk each one through the proposed compensation plan, approval rules and forecast definitions, and write down what the structure rewards.

The last question needs an answer that names a role and a threshold before the quarter starts. If the honest answer is that it would be discussed at the time, then nobody holds that authority yet, and it will be settled during a live deal.

How to Realign Incentives With Strategy

When the diagnostic shows a conflict, I sequence the changes in this order:

  1. Decision rights and approval thresholds. These can be changed mid-year without reopening signed compensation plans, and they quickly limit costly behaviour such as quarter-end discounting.
  2. Reporting definitions. Stage criteria, commit rules and forecast categories should reward accurate calls. A forecast process that praises large commits and questions small ones will push reps towards over-committing.
  3. Compensation and quota design. Change these at the next plan cycle, model the new plan against last year’s deals before launch, and check how it interacts with quota setting and territory allocation.
  4. A quarterly review. Compare deal structure, discount depth and pipeline mix with what the strategy asked for, and adjust whichever mechanism is drifting.

When incentives and strategy agree, the signs are measurable. Discount depth looks similar in week two and week twelve. Exceptions are rare enough to review individually. Reps can explain how their plan rewards the behaviours the strategy asks for, and forecast changes come with a reason that traces back to a deal.

Revenue architecture improves when incentive logic, authority structure and strategic intent reinforce each other.

It erodes when they compete.

Strategy may define direction.

Incentives determine movement.