partner tiers that change what partners do

A partner tier is worth something only if it changes what a partner does: trains an engineer, registers deals early, attaches services, commits to a plan. Partners care far more about rebates and deal protection than about the name of the level they are in. So spend your design effort on the money mechanics and the requirements, keep the number of tiers small, and set the thresholds from your own partners in each country. A global price book won’t fit them.

what partners actually value

In a Canalys survey of 130 partners, reported by CRN UK, back-end rebates and deal registration ranked as the most valued programme elements, ahead of lead generation, account management and front-end discounts. Tier names and branding ranked lowest. 26% named back-end rebates as the single most important benefit.

where programmes spend effort

visible, easy to launch

• Tier names and metal colours
• Badges and logos for websites
• Five or six levels
• Thresholds copied from the global guide

what moves partner behaviour

harder to design, worth it

• Rebates paid on growth and new customers
• Deal registration that holds
• Requirements tied to a benefit the partner uses
• Thresholds a partner in this country can reach

three tiers are enough

Large vendors run four or five tiers because they manage thousands of partners. A vendor building a channel in a European country with tens or a few hundred partners does not need that. Three levels cover it.

Level	Purpose	Typical requirements
Registered	Entry after signing and onboarding, transactional access	Signed agreement, onboarding done, one person through sales training
Certified	Partners with trained people that register deals regularly	One sales and one technical certification on your product, a minimum number of registered deals per year, a revenue threshold
Strategic	Partners that commit to a joint plan	Certified requirements, a signed joint business plan, a quarterly forecast, one joint campaign per half-year, a higher revenue threshold

A fourth, invitation-only level can make sense for one or two partners that carry a quarter of your business in a country. Keep it out of the published guide and run it through the joint business plan.

capability, commitment and performance

The market is moving away from tiers bought with revenue alone. Microsoft’s partner capability score is the clearest public example: up to 100 points per solution area, built from performance, skilling and customer success, with qualification at 70 points and every metric above zero. Revenue alone cannot buy the designation.

The same idea works for a security vendor with three families of requirements.

• Capability: people with sales accreditation and technical certification on your product, a completed specialisation.
• Commitment: a signed joint plan, a submitted forecast, named sales and technical contacts, a joint campaign.
• Performance: revenue, registered deals, new end customers, renewal rate.

One rule keeps the list honest. If you cannot measure a requirement from data you already hold, in your CRM, partner portal or training system, without asking the partner, do not make it a requirement.

set thresholds per country, from your own data

Global tier thresholds are written for the largest markets. Vendor guides that publish thresholds by country show how much country size matters: one large security vendor’s public guide sets its top-tier threshold for “other countries” at about a tenth of the US figure. A mid-sized European integrator will never reach a threshold written for the US, and a tier nobody can reach motivates nobody.

Calibrate instead:

1. Rank your partners in the country by trailing 12-month revenue.
2. Find the level that separates the top 5% to 15% (strategic) and the next 20% to 40% (certified).
3. Round to a number partners can remember.
4. Check that the benefits at each tier cost less than the margin those partners bring.

Say whether renewals count towards thresholds. They should, at a reduced weight, because in subscription security renewals are most of the revenue by year three.

tie every requirement to a benefit

A requirement without a benefit is a tax. A benefit without a requirement is a gift. Link them.

Requirement	Evidence	Benefit that follows
Certified engineers	Certification records	Access to projects that need those skills, lab access, specialist support
Qualified opportunities	Deal registrations that turn into opportunities	Account mapping, joint campaigns
Confirmed implementations	Customer acceptance	Referral of implementation work, a listing in your partner locator
A managed service that runs	Operational runbook and tests	A managed service offer, consumption pricing
Current data, timely renewals	No critical arrears, renewals on time	Simpler ordering, faster approvals

Avoid rewards that invite gaming: points for empty deal registrations, training sign-ups or contact lists. They raise reported activity and nothing else.

Keep the axes separate where it matters. A small partner can be excellent at industrial deployments and sell little. A large reseller can run procurement well and be unable to operate a security service. A specialisation badge for verified skill, separate from the commercial level, lets you reward the first without promoting it to strategic, and stops the second from claiming skills it lacks.

rebates that reward the right things

Rebates steer behaviour over a quarter or a year, so pay them for what you want more of.

• Pay on growth, a share of revenue above a baseline such as last year or the plan, with an accelerator above target. Flat volume rebates mostly reward partners who would have bought anyway.
• Add a new-customer component, a fixed amount per net-new end customer above a minimum deal size.
• Publish the calculation and send a statement every quarter, even when the result is zero.
• Cap the pool in your budget, so rebates do not quietly eat the margin that pays for presales and support.

A useful variant credits part of a partner’s earned rebate to a development budget it can spend only on certifications, joint marketing or demo licences. That keeps rebates from becoming a hidden price discount.

govern it like a contract

Separate the partner agreement, which is legal and stable, from the programme guide, which is commercial and changes. Change the guide once a year, with at least 90 days’ notice. Review tiers once or twice a year, with a grace period of one review before a downgrade, and say what happens to open registered deals when a partner moves down.

And keep resale prices out of it. Under Regulation (EU) 2022/720 a vendor may recommend a resale price or set a maximum, but a fixed or minimum resale price is a hardcore restriction. A tier benefit that depends on a partner not discounting below a level is the same restriction in a different form.

the question for your channel team

Which partner behaviour changed last year because of your tier structure, and how do you know?