Partner Tier

Origin & evolution

Tiering grew up inside the enterprise IT channel as a way to allocate scarce vendor resources to the partners most likely to return them. The metal-name convention, Silver/Gold/Platinum, became a de facto standard across vendors, alongside Authorised/Premier/Elite and numbered variants🆎VariantGrowthA variant in an A/B testView reference →. Oracle, Microsoft, Cisco, and Salesforce each codified multi-level structures; Salesforce's partner levels run up to a top "Summit" tier reached through validated revenue and customer-success metrics🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference →.

Current practice has settled on three to four levels. Channel-program guidance treats three tiers as right for smaller programs and four for most enterprise ones, with an entry-level Registered or Authorised rung below the committed tiers so new partners can join cheaply and see a clear path up. Requirements typically combine a revenue threshold, a count of certified staff, and training completions; benefits scale from basic discounts to dedicated channel managers, market development funds, deal-registration priority, and co-selling rights. The live debate concerns what the ladder measures. Revenue-weighted tiers reward volume and can promote a partner who sells a lot but serves customers poorly, which is why competence and customer-outcome🏆OutcomeStrategyA desired business or user outcomeView reference → metrics increasingly sit alongside the dollar threshold.

How it works in practice

A security vendor runs four tiers. A partner at Silver clears a £100k annual threshold and two certifications🏵️CertificationCustomer EducationA certification programView reference →, earning a 10-point margin uplift and short-window deal registration. To reach Gold the partner doubles revenue, certifies four engineers, and gains a named channel manager plus market development funds. One partner games the boundary: it registers deals it has barely touched to defend exclusivity and pad its number. The vendor responds by adding a customer-satisfaction gate to the Gold requirements, so the tier rewards delivery rather than registration volume alone.

Partner tier vs. its neighbours

• Partner program is the whole scheme; the tier is one level inside it. There is one program and several tiers, related by partner_program_tiers_as_partner_tierPartner Programtiers asPartner Tierhierarchy.
• Integration partner🗿Integration PartnerPartners & EcosystemAn integration partnerView reference → is a participant🙋ParticipantUser ResearchA person participating in researchView reference → that a tier can qualify or gate. A partner earns or loses a tier; the tier itself is the rung, modelled through partner_tier_qualifies_integration_partnerPartner TierqualifiesIntegration Partnercross-domain.
• Revenue share is the commercial term a tier often governs: the higher the tier, the richer the split, captured by partner_revenue_share_governs_partner_tierPartner Revenue SharegovernsPartner Tiercross-domain.

In the graph

In the Unified Product Graph, a partner tier sits in the ecosystem and go-to-market region as a child of its program via partner_program_tiers_as_partner_tierPartner Programtiers asPartner Tierhierarchy. Two further edges express what the tier does: partner_tier_qualifies_integration_partnerPartner TierqualifiesIntegration Partnercross-domain connects it to the partners that hold it, and partner_revenue_share_governs_partner_tierPartner Revenue SharegovernsPartner Tiercross-domain ties the benefit economics to the rung. Separating tier from program lets a graph model the ladder explicitly, so a query can ask which partners sit where and what each level actually costs to maintain.