How to structure partner tiers for a B2B channel programme

A partner tier should tell a partner what it needs to achieve, what support it can expect and when its status will be reviewed. Start with the behaviours your programme needs, choose evidence that demonstrates them, and connect each level to benefits you can deliver.

Tier names can wait. The useful work is deciding whether an additional level changes the relationship in a meaningful way.

This guide is for technology vendors that have a partner model and want to make qualification, progression and investment more consistent. If the wider operating model is still taking shape, start with Mesh's guide to building a channel partner programme.

Decide what the tiers should change

Write down the decision you want a tier to support. You might need to allocate specialist sales support, recognise delivery capability or offer additional planning resources to partners making a larger commitment.

Then describe the corresponding partner action. If the benefit is access to technical presales support, the requirement might include a qualified opportunity and a prepared discovery brief. If the benefit is a joint marketing planning session, the requirement might include a named marketing owner and an agreed target audience.

Avoid promising a benefit just because it looks attractive in the programme guide. A dedicated manager, campaign budget or technical resource creates a capacity commitment. Estimate how many partners could qualify and whether the team could support them all.

If two proposed levels have nearly identical requirements and benefits, combine them. A small programme may need only membership plus a separate capability designation until there is a clear reason for more levels.

Separate membership, capability and performance

These three questions deserve separate answers:

Membership: Has the organisation completed the requirements to participate in the programme?

Capability: Can its people perform the work expected of their partner role?

Performance: Is the relationship producing the outcomes the programme is designed to create?

Combining them into a single unexplained score makes the result hard to interpret. A partner could have strong sales and a gap in technical coverage. Another could have capable delivery staff but little relevant commercial activity.

Microsoft provides a useful example of considering multiple dimensions. Its Partner Capability Score assesses performance, skilling and customer success. That is Microsoft's programme design, with its own qualification rules. For your programme, select dimensions that reflect the work your partners actually do.

Treat essential capabilities as requirements in their own right when a shortfall would change what a partner should be allowed to deliver. Additional sales points should not silently compensate for a missing required qualification.

Choose criteria a partner can understand and verify

For each criterion, specify the measure, the evidence source, the measurement period and who resolves an error.

Use a small number of criteria that influence a real decision. A count of portal visits can help identify whether someone needs assistance, but it is a weak substitute for demonstrated ability or commercial progress.

Distinguish activity from its purpose. Requiring a partner to run three webinars rewards completion of an activity. Requiring an agreed campaign plan and a review of its outcomes creates a different expectation. Choose the requirement that matches what you are trying to improve.

Design appropriate routes for different partner types

A reseller, distributor and managed service provider may contribute in different ways. A single resale target can obscure those differences.

Keep common membership requirements where they make sense, then define qualification routes that reflect the partner's role. A reseller route might emphasise qualified opportunities and sales capability. A services route might emphasise delivery competence and customer outcomes. A distributor route might include support for its reseller network.

You can retain a common set of tier names while using different criteria, provided the distinction is visible. Make it clear what the designation certifies. A high commercial tier should not imply that every partner has the same technical specialism.

Avoid inventing a new route for every exception. Create a separate route when the underlying business model requires different evidence, and keep individual commercial exceptions recorded outside the general qualification rules.

Sketch the progression before setting thresholds

The following is an illustrative design, not a Mesh programme or an industry benchmark.

Keep the basic means of participating available to eligible partners at the entry level. If a partner needs training to progress, explain how it can access that training. If deal registration is part of the programme, make the entry requirements and process clear.

Set thresholds only after reviewing the distribution of actual partner activity, your economics and the capacity behind the benefits. A revenue threshold borrowed from a much larger vendor gives little guidance about whether it fits your programme.

Test what happens when a partner almost qualifies

An illustrative reseller programme might require two currently qualified sales employees, one qualified technical employee and two eligible won opportunities in the previous 12 months for its Growth level. These are sample rules, not recommended targets.

One partner meets the sales and opportunity requirements, but its only qualified technical employee has left. Another meets the capability requirements but has won only one eligible opportunity.

The first has a capability gap. The second has a performance gap. They need different next actions, and the partner guide should make both understandable.

Decide whether a temporary capability gap allows a defined remediation period, what support or permissions apply during that period, and who can approve any exception. For the performance gap, show the missing requirement and the next review date. Do not change the calculation to accommodate a favoured partner.

Use the same exercise for a new partner, a partner entering a new region and a partner with an unusually large transaction. Check that the result recognises the contribution you intended to reward.

Publish the review and progression rules

Partners should be able to find the measurement window, review cadence, effective date of a change and route for correcting inaccurate data.

Separate the date of a review from the date a status change takes effect. Explain how a partner can move up, what maintaining a tier requires and what happens if a requirement is no longer met. Apply changes in line with the programme terms and communicate them clearly.

Make data corrections part of the process. A missing qualification record is different from an expired qualification. A transaction omitted from the report is different from one that does not meet the eligibility rule. Give the partner a way to supply evidence and see the outcome.

Keep an exception record with the reason, scope, decision owner and expiry or review date. This makes it possible to distinguish an intentional exception from an unexplained discrepancy.

Show partners the next useful action

Give each partner a concise view of its current tier, the applicable criteria, recorded progress, remaining gaps and next review date. Link the gaps to the action that resolves them, such as completing training or correcting an opportunity record.

Mesh's partner portal guide explains the wider partner experience. For tier progression, the practical requirement is that people can understand their status and act on it. A badge alone provides little guidance.

Introduce the rules during partner onboarding, then use the same definitions in subsequent reviews. Before launch, ask a small group of partners to explain how they would reach the next level and what they would receive. Any uncertainty is a useful signal to simplify the guide.

Once the structure is running, review both progression and delivery. Are partners developing the intended capability? Are the benefits being used? Can the team fulfil the commitments it made? Those answers should determine whether the tiers need adjustment.