The Churn That Wasn't
A customer renews. Same product, same seats, same contract. The only thing that changed is who is on the invoice: this year the renewal runs through a partner.
The customer is happy, and the relationship is stronger, with two teams now focused on supporting them. By every account, this sounds like a great outcome.
Sometimes the move is simply the customer's call. They already treat the partner as their trusted advisor and want to transact with that partner directly, or through a marketplace transaction with that partner involved. A preference worth honoring.
Sometimes a shift like this is tied to the bigger reason ecosystems get built in the first place. Done well, the AE isn't working one account at a time. They operate more like a sales manager, with partners functioning as their AEs. Partners also bring what the vendor can't build alone: vertical specializations and solutions expertise tied to customer initiatives, not just products.
The result is a more complete coverage model. The AE and presales teams spend their limited time on the handful of deals where direct or co-sell attention changes the outcome, and lean on partner capacity for the rest of the patch. That's not a workaround. That's the coverage model doing what it was built to do.
Not a shortcut
This isn't a renewal that landed on the AE's desk and got waved off to whoever was closest. It's the output of an earlier decision: bring in a partner to run this account day to day, so the AE can spend time on the strategic deals and the prospecting that need them. The renewal is just where that decision shows up on the books, months later.
Yes, there's a margin cost. Set against what it buys back, it's usually a small price: the AE's time for the deals only they can move, plus presales, customer success and the renewals team staying off an account that's already well run.
Where the rule breaks
So how can this be a problem? Because often Finance has a simple rule: if a customer was worth 100 last year, anything less than 100 this year counts as churn. Move that renewal to a partner who takes 8%, and the vendor's number is 92. The accounting sees a shortfall even though the customer is happy and better supported.
What that rule can't see is the true cost of managing the customer relationship, the full annual lifecycle. It sees the margin at the point of renewal only, not what the margin bought.
Who actually pays for it
The real problem sits in how the AE is paid. Most comp plans start from the same net number finance uses, so the renewal that nets 92 against a baseline of 100 shows up as a miss on the AE's target. They have no reason to route a renewal through a partner, even when the partner is the reason the AE has bandwidth for the rest of the patch.
And when an AE wants to use a partner anyway, the workaround is to ask the partner to shave their own margin, just to make the number look closer to whole.
That is the partner subsidizing the vendor's measurement. They may accept it once, while the pipeline keeps flowing. They won't accept it as policy.
The actual cost
Neither rule was wrong on its own terms. Finance set a churn definition to protect against real revenue loss. Sales comp inherited that definition without checking whether it still meant the same thing once the customer hadn't left, just moved to a partner's book.
What was missing was anyone whose job it was to ask what the rule would do once a partner was in the picture. A coverage model built on trusting partners with parts of the book can't survive a comp plan that punishes the AE every time that trust gets used.
That's not a partner problem. It's a measurement problem wearing a partner's face.
The whole point of a partner ecosystem is that a well run one doesn't just cover accounts. It amplifies what one AE could reach alone. Build a measurement that punishes the exact motion that creates that amplification, and the coverage model you built ends up quietly working against itself.