Comp Plans That Reward Collaboration, Not Silos

You can redraw the org chart, merge the reporting lines, and give the "one team" speech at the all-hands. If the comp plan still pays people to hoard, they will hoard. Comp is the most honest document in a revenue org. It says what you actually value, whatever the strategy deck claims. And in most companies we've seen, the comp plan quietly tells every function to optimize its own number at the expense of everyone else, which is the exact behavior an orchestrated org is trying to get rid of.

That makes comp design one of the highest-leverage things a revenue leader controls. Get it wrong and no structural change sticks. Get it right and collaboration becomes the path of least resistance, because the coordinated thing and the paid thing are the same thing.

How standard plans manufacture silos

The default comp architecture produces silos without anyone intending it.

Take the classic setup. The AE is paid on new bookings, full stop. The CSM is paid on retention and gross renewal. Marketing's bonus is tied to pipeline generated. Each of those is reasonable on its own. Together they guarantee friction. The AE closes a poor-fit deal because it books this quarter, then hands the wreckage to a CSM who is paid to keep it alive. The CSM spots an obvious expansion but has no reason to loop in the AE, so it either goes unworked or turns into a fight over credit. Marketing chases pipeline volume over quality, because volume is what it's paid on.

Nobody here is behaving badly. They're behaving exactly as compensated. The silos look like a culture problem, but they're a comp problem wearing a culture costume. It's also why the hiring and org-structure work only pays off once the incentives underneath it line up.

Design principles that hold up

The fix is not paying everyone on one giant blended number. That just removes accountability. You want to keep individual accountability and add shared stakes at the specific moments where collaboration creates value.

Four principles do most of the work.

Pay for the shared outcome as well as the local one. Keep a core individual metric, but attach a real component to the joint result. An AE whose comp includes a retention or expansion factor suddenly cares whether the deal they closed actually works out.

Reward the handoff. If a CSM is paid partly on how well accounts are set up at handoff, and an AE on how well they equip that handoff, the seam between them stops leaking.

Make expansion a shared prize. Expansion revenue should pay both the person who spotted it and the person who closed it. Once expansion is a shared win instead of a contested one, it surfaces instead of dying in a credit dispute. This is the core mechanic for taking down the wall between sales and customer success.

Keep it legible. A plan so complicated that reps can't predict their own paycheck will be ignored or gamed. If the collaboration incentive can't be explained in a sentence, it won't change anyone's Tuesday.

Attribution is the hard part

Most companies avoid collaborative comp because of attribution. The moment two people can be paid on the same deal, someone has to decide who contributed what. That's genuinely hard, and hardest in co-sell and partner motions where the value is created across company lines. Double-crediting can push up cost of sale. Under-crediting kills the exact behavior you were trying to buy.

There's no perfect formula. A few practices help.

Accept some double-counting on purpose. Paying two people for one collaborative win is usually cheaper than the revenue you lose when neither of them collaborates. Think of overlapping credit as the price of the behavior.

Instrument the contribution. You can only reward collaboration you can see. Capturing who touched an account, what signal they raised, and how the deal actually moved requires shared data, which is the same problem the co-sell attribution problem digs into.

Review and adjust. Collaborative comp isn't set-and-forget. Watch for gaming and tune the plan as behavior shows you what it's really incentivizing.

One example of how little it can take: a company adds a modest expansion pool, split between the CSM who identifies an upsell and the AE who closes it. Before the change, CSMs sat on expansion signals because working them was unpaid effort with a turf fight attached. After, expansion opportunities surfaced far more often, because both people had a stake and neither felt robbed. The plan wasn't elaborate. It just made the collaborative act the paid act.

Comp has to match the operating model

Finance can't design this in a vacuum. The plan has to reflect the motion the org actually runs, so RevOps and revenue leadership need to own it together. It should encode the handoffs, the shared plays, and the moments where revenue is created or lost. That's the same map that drives how you structure a revenue team for the orchestration era.

In practical terms, whoever designs the plan needs to see how deals actually move across functions. Without shared data on contribution, collaborative comp collapses into arguments. With it, you can pay for exactly the behavior the strategy needs.

Key takeaways

• Comp is the clearest statement of what an org values. A misaligned plan will manufacture silos that no reorg can undo.
• Paying each function on its own local metric reliably produces cross-functional conflict, even when everyone is acting in good faith.
• Keep individual accountability, then add shared stakes at the handoffs and expansion moments where collaboration actually creates value.
• Attribution is the hard part. Accept some deliberate double-counting and get the contribution data instrumented.
• Whoever designs the plan needs visibility into how deals really move, or the plan will get argued to death.

This is where org design stops being aspirational. If you're redesigning comp for an orchestrated motion, you'll need a system that captures cross-functional contribution, because fair collaborative pay depends on seeing who did what. That is part of what a platform like Revnewo is for.