A partner channel rarely fails in one event. It goes quiet. Registrations fall a little each quarter, the same three partners carry most of the revenue, POCs wait three weeks for an engineer, and the partner count in your board deck stays flat because nobody removes anyone. Most of the causes are inside your control. Track a handful of leading indicators monthly, act when two turn amber at once, and when you change your programme, give partners two quarters of notice.
the failures you cause yourself
External shocks get the headlines: an acquisition, a programme reset by a new owner. The patterns below are more common in practice and entirely yours to fix. No public dataset measures how often each occurs. They come from practice.
| Anti-pattern | What you see | Early signal | Fix |
|---|---|---|---|
| Partner hoarding | Sixty signed partners, six selling | Active share below a quarter after two quarters | Count active partners only, prune once a year |
| Direct creep | Your sellers close deals, partners stop registering | Registrations fall while direct deals rise | A written direct-accounts list and a channel-neutral pay plan |
| Presales starvation | Pipeline stuck at POC | POC waiting time above three weeks | Hire or contract engineer capacity before more sellers |
| Paper certifications | Certified partners can’t run a demo | Partners ask for your engineer on every demo | A practical demo test as a tier condition |
| Margin leakage | Special pricing on most deals | Special pricing on more than 40% of deals | Publish the discount table, approve exceptions |
| Portal without data | Logins fall after month two | Weekly active users below a fifth of partners | Fix price lists and renewal data before the portal |
| Event treadmill | Many events, little pipeline | Pipeline per event below its cost | Named follow-ups per partner after every event |
| Renewal neglect | Renewals lost to another partner or to direct | Renewal quotes sent less than 60 days ahead | A renewal list per partner, 120 days out |
| Overbuilt programme | Five tiers for thirty partners | Partners can’t state their tier or margin | Two levels until you have 15 active partners |
Partner hoarding is usually the first. A recruitment target expressed in signatures produces signatures. The partners that never sell still receive newsletters, invitations and calls, and that time comes out of the partners that do.
Direct creep is the most expensive. A seller under quarter-end pressure closes a deal a partner had mentioned informally. The partner finds out at the next tender, stops registering, and tells other partners. One deal can cost a year of registrations.
an early-warning table to run monthly
amber
watch, discuss at the next channel review
- Active partners below 35% of signed
- Registrations down 10% to 25% on last year's quarter
- Top three partners above half of revenue
- POC waiting time 15 to 25 days
- Special pricing on 30% to 50% of deals
- Renewal rate 80% to 90%
red
act this month
- Active partners below 20% of signed
- Registrations down more than 25%
- Top three partners above 70% of revenue
- POC waiting time above 25 days
- Special pricing on more than half of deals
- Renewal rate below 80%
a line that stalls: diagnose in two weeks
When a product or a region has had no traction for two quarters, answer five questions with data before changing anything:
- How many partners have both a trained seller and a trained engineer? Fewer than four means the problem is enablement.
- Where are the qualified opportunities stuck? If at POC, it is presales capacity or product fit.
- Why were completed POCs lost? Losses clustered on price or one missing feature point at positioning or product.
- Do partners know about a deadline that creates demand, such as a NIS2 transposition date or an audit? If not, it is messaging.
- Are you delivering what the joint business plans promised?
Then spend 90 days on three to five partners with the best fit. Pick five target accounts with each, run one campaign together, and put your engineers on POCs only. If after 90 days there are still fewer than three closed deals and no real pipeline, the conversation is about the line itself.
changing your programme without a revolt
The best documented recent example of how not to do it is Broadcom’s handling of the VMware channel. ChannelE2E reported that VMware partners were told in mid-December 2023 that the existing programme was terminated, with an invitation-only replacement taking effect on 5 February 2024. ChannelWeb reported that around 2,000 strategic accounts were taken direct. Short notice, invitation-only access, a direct takeover of the largest accounts and a pricing change all landed at once. Any one of them can be absorbed. Together they removed partners’ ability to plan.
Compare two overhauls that went more quietly. Microsoft retired its Gold and Silver competencies on 30 September 2022 and kept selling legacy benefits until 21 January 2025. Cisco announced the Cisco 360 programme in November 2024 with 1 February 2026 as the start, a 15-month transition. Public sources do not measure partner reaction to either, so read them as practices without proof of effect.
- 1noticeAt least two quarters before anything that changes partner income or status takes effect.
- 2status protectionCurrent tier kept until the next scheduled review, whatever the new rules say.
- 3economic continuityPartners in good standing don't lose margin in the transition year.
- 4explanation and a feedback channelA written FAQ with what changes and why, dated steps, and a named person who answers.
If a change has already caused anger, acknowledge it in writing to every affected partner within a week, before defending it. In the first month, call your top 20 partners one by one, collect their specific objections, decide which to accommodate, and publish a revised version with at least a quarter of transition. Most revolts are driven by surprise and lost income. The content of the change matters less.
rebuilds that simplified
Fortinet replaced its partner tiers with the Engage programme in 2020, as ChannelLife reported, with engagement levels and named business models including MSSP. Neither it nor most other vendors publish before-and-after partner performance, so the lesson is structural: a clear statement of what changes and why, a simpler structure than before, economics that pay for partner work beyond resale, and a transition of at least two quarters.
the question for your channel team
Which of your partners stopped registering deals in the last year, and does anyone know why?
questions
Why do partner programmes fail?
Mostly for reasons inside the vendor's control: too many signed partners that never sell, direct sellers closing deals around partners, too few presales engineers, certifications that don't test skills, and programme changes announced without notice. External shocks such as acquisitions happen too, but they are rarer.
How much notice should partners get before a programme change?
At least two quarters for anything that changes partner income or status. Microsoft kept selling legacy partner benefits for more than two years after retiring Gold and Silver in 2022, and Cisco announced its Cisco 360 programme with a 15-month transition.
What share of signed partners should be active?
There is no reliable public benchmark. A practitioner rule of thumb: if fewer than a third of signed partners had a registered or closed deal in the last six months, treat it as a warning. Below a fifth, the programme is mostly paperwork.
sources
Security Revenue · every Tuesday
How security vendors build pipeline.
