Partner Tiers Explained
Turn this article into takeaways for your work.
Each assistant summarizes the article only for you and suggests best practices for your work.
Every vendor with more than a handful of partners eventually hits the same problem. Some partners sell constantly and some never close a deal, yet both hold the same agreement, the same logo on the website and the same access to the partner manager. Partner tiers are the usual fix. They sort partners into levels, attach different benefits to each level, and give partners a visible ladder to climb.
This article explains what a partner tier is, what programs actually measure to place partners, and how four well-documented programs (HubSpot, Google Cloud, Microsoft and Salesforce) structure theirs. It closes with a method for designing tiers of your own and the mistakes that make them collapse.
What a Partner Tier Is
A partner tier is a named level inside a partner program. A partner earns the level by meeting published criteria, and the level decides which benefits, support and recognition the partner receives. The tier is a property of the company, not of any one person at it.
That last point matters because tiers get confused with two neighbors:
| Concept | What it classifies | Example |
|---|---|---|
| Partner type | What the partner does | Reseller, referral partner, consulting partner, managed service provider |
| Partner tier | How much the partner has achieved | Select, Premier, Gold, Platinum |
| Certification or competency | What the partner can prove it knows | A product badge or an individual exam, covered in partner certification |
Type answers "what kind of partner is this?" Tier answers "how far along are they?" A tier ladder usually sits on top of a type, so a vendor with resellers and agencies may run one ladder per type or one shared ladder with type-specific requirements. If you need the definition of the partners themselves first, start with what is a channel partner.
Why Programs Use Tiers
Tiers solve four problems at once.
- Resource allocation. A vendor can't give every partner a dedicated manager, co-marketing budget and sales engineering time. Tiers decide who gets scarce attention.
- Motivation. A visible next level gives partners a reason to invest in training, headcount and pipeline.
- Buyer signal. A customer who has never heard of a partner can read its tier as a rough quality indicator.
- Risk control. The entry tier admits almost anyone cheaply, while higher tiers require evidence. That lets a program grow wide without lowering the bar at the top.
None of this works unless the tier is tied to something real. A tier with no benefit attached is a badge. The benefit side is covered in partner incentives and market development funds, and tiers are most often the switch that decides who qualifies for each.
What Programs Measure
Across programs, tier criteria fall into a few families. Most programs combine two or three of them.
- Revenue or sourced pipeline. The partner generates a threshold of sales, sourced customers or influenced deals.
- Customer retention or quality. Revenue is only counted if customers stay, or the program sets a minimum retention rate.
- Skills. A minimum number of certified people.
- Customer success evidence. Case studies, project counts, usage growth or satisfaction scores.
- Standing. The partner follows the program's rules and has no unresolved customer escalations.
The design question is which family leads. A revenue-led ladder rewards partners who sell. A skills-led ladder rewards partners who are ready to deliver. Mature programs usually mix them, because revenue alone invites low-quality deals and skills alone rewards partners who never sell.
How Real Programs Build Their Tiers
Each example below comes from the vendor's own pages. Programs rework their structures often, so details are described as the pages read, and you should check the current documentation before relying on them.
HubSpot: points, retention and monthly movement
HubSpot's Solutions Partner Program is a clear example of a revenue-led ladder. According to HubSpot's 2026 tiers and benefits page, the program has five tiers: Solutions Partner, Gold, Platinum, Diamond and Elite.
The thresholds on that page combine sourced points, total points and, at the top, customer retention:
| Tier | Sourced points | Total points | Average gross revenue retention |
|---|---|---|---|
| Gold | 115 | 345 | Not specified |
| Platinum | 425 | 1,275 | Not specified |
| Diamond | 1,250 | 3,750 | At least 75% |
| Elite | 2,750 | 11,000 | At least 80% |
HubSpot's tier points page explains where the points come from. Partners earn sourced points from closing deals with new customers, assisted points from helping close deals HubSpot sourced, and managed points from servicing existing customers. Points are awarded per $100 of monthly recurring revenue, and customers in growth markets receive a 2x multiplier.
Two mechanics are worth copying. First, movement is frequent in one direction and slow in the other: per the same page, partners can move up on the 15th of every month, while demotions happen twice a year, on January 15 and July 15. Second, a partner that falls below its tier gets time to recover. The page says a partner "will have at least six months to restore it."
The tiers page also sets a good-standing condition. To maintain or advance a tier, a partner must meet minimum conditions that include compliance with program policies, completed required training and certifications, and having no current or recent "at fault" escalations on record. It adds that good standing at the time of tiering is subject to HubSpot's "absolute discretion." That is a candid reminder that every ladder needs a judgment valve for cases the numbers miss.
Google Cloud: tiers for breadth, competencies for depth
Google Cloud splits what most programs bundle. Its partner program page uses three tiers to signal breadth and a separate competency framework to signal depth.
The three tiers are described this way:
- Select: partners who have "demonstrated a baseline of foundational knowledge and successful client engagements."
- Premier: partners with "a significant investment in certified technical resources and a consistent history of driving customer outcomes at scale."
- Diamond: described as the highest level of partnership, representing the deepest global commitment to Google technology and a portfolio of large-scale, complex customer deployments.
Competencies work differently. They cover product, solution and industry categories, and each can be reached at two levels, competency and advanced competency. The practical effect is that a small partner can be a Select-tier firm with a deep competency in one industry, and buyers can tell the two signals apart. A single ladder can't express that.
Microsoft: from metal tiers to a score
Microsoft is the useful example of a program that moved away from a conventional ladder. Its partner capability score documentation describes Solutions Partner designations in six solution areas. A partner qualifies in an area with a score of at least 70 points out of a possible 100, built from three categories: performance, skilling and customer success. Every metric in the area must also be above zero points.
The same page still refers to a "Legacy Gold/Silver" membership status when explaining how partners transitioned. That's the retired structure: the page refers to partners with legacy Gold or Silver membership, and the program now issues designations instead. Two design lessons stand out. Designations are per area rather than company-wide, so a partner is not one tier everywhere. And enrollment is time-limited: the page says the valid-till date is 13 months from the date of purchase, including a one-month renewal window.
Salesforce: fewer tiers, outcome-based competencies
Salesforce shows the opposite pressure, simplification. Its FY27 Consulting Partner Program brochure, a draft executive brochure, describes a move from four tiers to two, Select and Summit. It defines Summit as "top-tier partners aligned to strategic growth" and Select as "proven delivery partners meeting clear performance standards," and says fewer tiers "reduce ambiguity."
The same brochure replaces 170 Navigator distinctions with 28 outcome-based competencies, each measured by certifications, completed projects and customer satisfaction, with two recognition levels, Accredited and Expert. Salesforce's Consulting Partner Program page also names a Provisional Partner status for new partners, who are placed on an onboarding journey to reach the Registered tier. The brochure is a draft and structures differ by track, so treat it as evidence of a direction, not a final rulebook.
Comparison
| Design choice | HubSpot | Google Cloud | Microsoft | Salesforce (consulting, FY27 brochure) |
|---|---|---|---|---|
| Structure | Five tiers | Three tiers plus competencies | Designations per solution area | Two tiers plus competencies |
| Lead criterion | Points from revenue, with retention at the top | Certified resources and customer outcomes | Score across performance, skilling, customer success | Certifications, projects, CSAT |
| Handles decline | Demotion twice a year, six months to restore | Check current terms | Time-limited enrollment with renewal window | Check current terms |
| Retired structure | Not applicable | Not applicable | Gold and Silver | Four tiers, 170 Navigator distinctions |
Key Facts: Partner Tiers
- A partner tier is a published level, earned by meeting criteria, that decides which benefits and recognition a partner receives. It classifies achievement, not partner type.
- HubSpot's Solutions Partner Program has five tiers (Solutions Partner, Gold, Platinum, Diamond, Elite), and the Diamond and Elite tiers require average gross revenue retention of at least 75% and 80% respectively (HubSpot).
- HubSpot awards points per $100 of monthly recurring revenue, with a 2x multiplier for growth-market customers (HubSpot).
- Google Cloud separates three tiers (Select, Premier, Diamond) from competencies that are reached at two levels (Google Cloud).
- Microsoft qualifies partners per solution area with a capability score of at least 70 of 100 points, and enrollment runs 13 months (Microsoft Learn).
- Salesforce's FY27 consulting program brochure describes a move from four tiers to two (Salesforce).
How to Design Partner Tiers
Start with what the tiers must decide, then build the minimum structure that decides it.
- List the benefits first. Write down every benefit you can give a partner: lead routing, funding, support response, co-selling, directory placement. Rank them by cost to you. Tiers exist to ration the expensive ones.
- Choose how many tiers. Three or four is usual. The Salesforce brochure's argument that fewer tiers reduce ambiguity is worth weighing, because every extra tier needs its own benefits, criteria and administration. If you can't name a distinct benefit for a tier, remove it.
- Pick the lead criterion, then add a quality check. If revenue leads, add retention or customer satisfaction so partners can't climb on deals that churn. HubSpot's retention requirement at the top levels does this. If skills lead, add delivery evidence so certified people are backed by real projects.
- Make the entry tier easy and cheap. The bottom tier should admit any partner that signs the partner agreement and completes onboarding. Its job is to start the relationship, not to filter.
- Set review and recovery rules. Decide how often partners are reviewed, how fast they can move up and how long they have to recover after a dip. HubSpot's pattern of monthly promotions, twice-yearly demotions and a recovery window shows one workable balance between fairness and responsiveness.
- Count what you can measure. If you can't attribute a deal to a partner reliably, you can't place the partner fairly. Fix measurement before you publish thresholds.
- Publish the rules and show progress. Partners should see the criteria, their current standing and the gap to the next level. A partner scorecard built on agreed partner KPIs is the usual way to do this.
- Keep a judgment valve. Some partners will meet the numbers and still be a poor fit, or the reverse. A standing condition, as in HubSpot's good-standing rule, lets the program act on that without rewriting the thresholds.
- Review the whole ladder on a schedule. Check each year whether higher-tier partners really produce better results. A regular partner business review with top partners is where you learn that a threshold is too easy or a benefit no one wants.
Tiers also fit inside a larger arc. Where a partner sits on a ladder is one view of its journey from signing to scale, which the partner lifecycle article covers, and the wider strategy is in partner-led growth.
Common Mistakes
- Too many tiers. Five or six levels with thin differences leave partners unable to tell what moving up gets them.
- Thresholds set once and never revisited. Partner economics shift, and an old threshold either blocks good partners or admits weak ones. Programs do rework their structures, as the Microsoft and Salesforce examples above show.
- Revenue-only criteria. Partners optimize for whatever is counted. If churned customers still count, expect churned customers.
- Hidden rules. If partners can't see how placement is decided, every placement becomes a negotiation.
- No path down. A ladder that only goes up fills the top tier with inactive partners and devalues it. Pair promotion rules with a clear, fair demotion process.
- Benefits that don't match the tier. Giving top-tier support to everyone removes the reason to climb.
Related Reading

On this page
- What a Partner Tier Is
- Why Programs Use Tiers
- What Programs Measure
- How Real Programs Build Their Tiers
- HubSpot: points, retention and monthly movement
- Google Cloud: tiers for breadth, competencies for depth
- Microsoft: from metal tiers to a score
- Salesforce: fewer tiers, outcome-based competencies
- Comparison
- How to Design Partner Tiers
- Common Mistakes
- Related Reading