renewals through partners: who owns the customer in year two

On a subscription line, the renewal book becomes larger than new business within a few years. Through the channel, renewals are rarely lost to a better competitor. They are lost because the quote arrived after the customer had already started a new procurement. Name one renewal owner on the partner side and one on yours at the moment of the first sale, start the calendar six months before expiry, and protect the partner that keeps the customer happy.

the channel retains worse, for a fixable reason

SaaS Capital’s 2025 benchmarks put median gross revenue retention for private B2B SaaS companies at 91% and net revenue retention at 101%. An older SaaS Capital study found that companies whose revenue was dominated by channel partnerships retained about three percentage points less than direct-dominated companies.

That gap is mostly a management problem. In a direct model, a customer success manager owns the account. In a two-tier channel, the vendor assumes the partner will handle the renewal, the partner assumes the distributor will send a quote, and the customer’s procurement team assumes nobody minds if they open a tender.

Practitioner estimates of why channel-sold security subscriptions are lost, from the distribution playbook this guide draws on, put the late or missing quote first, at roughly a fifth to a third of losses, ahead of low adoption, price increases, platform consolidation and a sponsor leaving. Treat the shares as one practitioner’s estimate. The order is the useful part: the largest single cause is pure process.

decide who owns each renewal

Ownership means three things: who is accountable for the quote reaching the customer on time, who handles objections, and who is paid for the outcome.

Model	How it works	Fits
Partner-owned, supported	The partner of record owns it; you or your distributor send reminders and quote on request	Mature partners with account managers, mid-market and enterprise
Renewal desk	A desk prepares every quote and sends it to the partner of record with a deadline	Long-tail partners, many small renewals
Hybrid by segment	Partner-owned for top partners, desk for the long tail, with a takeover rule	Most channels above a handful of partners
Monthly or consumption	No discrete renewal; billing runs monthly	MSP and MSSP programmes, where churn is silent and seat counts drift

Three rules make the hybrid work. A partner with only a few renewals a year on your product gets every quote prepared for it, 90 days before expiry. A partner with an account manager and a strong retention record owns its renewals, and you only monitor. And if a renewal shows no partner activity 45 days before expiry, ownership moves to the desk, which contacts the partner first.

Never contact an end customer about a renewal without telling the partner of record first, unless the partner has gone silent past an agreed deadline and your agreement allows it. Write that into the partner agreement.

a renewal is a small sales cycle with a fixed deadline

1. T-180identified and assignedIn the CRM with customer, partner of record, value and expiry. Owners named on both sides.
2. T-150health checkUsage against licences, open critical tickets, whether the sponsor is still there.
3. T-120budget and procedure confirmedOrder, framework or tender. A public buyer running a procedure needs months, which is why this step sits here.
4. T-90quote issuedWith term options. Special pricing requests, if any, start now.
5. T-60 to T-30negotiation and approvalsDecision path and purchase order date agreed.
6. before T-0order and activationNo gap in the licence. Then log the lost reason or the expansion opportunity.

Some vendors tell partners to request the renewal quote 30 to 60 days before the date. That fits a private mid-market customer. For any customer that runs a tender, it is too late.

protect the incumbent partner

A partner keeps investing in a customer, with health checks, support and expansion, only if the renewal stays with it. Incumbency protection is the standard tool: a better buy price for the partner that sold and serves the customer, so another partner cannot take the renewal purely by discounting. Published vendor examples cluster around a 10% to 15% suggested advantage.

Write down when the protection ends: the partner left the programme, lost its authorisation, is in payment default, or the customer asks in writing for a different partner. In the EU, build the protection as a price advantage, never as a ban on the customer buying elsewhere.

watch health before the quote

A simple monthly health score tells you which renewals need work before they reach the quote stage.

Signal	Green	Red
Deployed against purchased volume	80% or more	below 50%
Open critical support tickets older than 14 days	none	two or more
Partner contact with the customer	in the last 90 days	none in 180 days
Sponsor still in role	confirmed	left
Price or budget objection	none	formal

Two rules keep it honest. A missing input is “unknown”, never green. And a sponsor who left is red on its own, whatever the weighted total says.

For a red account, choose one play: an adoption push with the partner’s engineers, a smaller renewal on the same term, a multi-year term at a lower annual price, a meeting between your regional lead, the partner and the customer’s security head, or, if the partner is the problem and the customer wants it, a partner change under the incumbency rules. A discount should not be the first play. Discounted renewals teach partners to bring every renewal as at risk.

pay for renewals separately

A single revenue target lets new customers hide churn. Pay partners, and your own channel team, separately for on-time renewal and for expansion. Partners that deliver services around your product tend to renew better, so push services attach as part of the renewal strategy as well as the first sale.

the question for your channel team

Of last year’s lost renewals, how many did you lose to a competitor, and how many to a calendar?