Partner Program

Origin & evolution

Indirect sales predate software by centuries, but the modern programmatic version grew out of the IT channel of the 1980s and 1990s, when hardware and enterprise-software vendors formalised reseller and distributor networks to reach markets their own salesforces could not. The vocabulary that survives today, value-added reseller, distributor, system integrator, comes from that era. Affiliate marketing, the term first used in 1989, added a low-friction referral layer once the web made tracking cheap.

The cloud era widened the definition. A partner is no longer only a company that resells your licence. Salesforce frames the modern version as a partner ecosystem spanning four broad shapes: resellers who own the sale, referral partners who pass leads for commission, technology or ISV partners who integrate with your platform, and system integrators who implement it. Each shape optimises a different growth lever, and a mature program runs several at once under one governance frame.

How it works in practice

A B2B analytics company, eighteen months past launch, is closing deals faster than its eight-person sales team can source them. It opens a partner program with two tracks. The referral track pays a 15% first-year commission to consultancies that pass qualified leads. The technology track invites complementary tools to build integrations, listed in a shared catalogue. Within a year, 30% of new revenue arrives through partners the company never cold-called, and the integration track has quietly raised retention, because customers running two connected tools churn less. The cost is real: partner-sourced deals carry thinner margins and the company now answers to partners who feel they own those accounts.

Partner program vs. its neighbours

• Partner tier🥈Partner TierPartners & EcosystemA partner tier levelView reference → is a level inside the program. The program is the whole scheme; the tier is one rung on its ladder. A company has one partner program and several tiers within it, modelled as partner_program_tiers_as_partner_tierPartner Programtiers asPartner Tierhierarchy.
• Integration partner🗿Integration PartnerPartners & EcosystemAn integration partnerView reference → is one participant🙋ParticipantUser ResearchA person participating in researchView reference →, a single third party whose product connects to yours. The program is the structure that recruits and governs many such partners, captured by partner_program_includes_integration_partnerPartner ProgramincludesIntegration Partnerhierarchy.
• Developer portal🎑Developer PortalPartners & EcosystemA developer portalView reference → is the self-serve surface a program often exposes to technical partners. The portal is plumbing, the documentation and keys; the program is the commercial relationship the plumbing serves.

In the graph

In the Unified Product Graph, a partner program sits in the ecosystem and go-to-market region, linked to the product it grows through product_partnered_via_partner_programProductpartnered viaPartner Programhierarchy. Two edges give it internal structure: partner_program_tiers_as_partner_tierPartner Programtiers asPartner Tierhierarchy hangs the benefit ladder off it, and partner_program_includes_integration_partnerPartner ProgramincludesIntegration Partnerhierarchy enumerates the participants. Modelling the program as its own node, separate from any single partner, keeps the scheme legible when partners come and go. The structure persists; the membership churns.