Partner Revenue Share

Origin & evolution

Revenue sharing predates software by a long way, rooted in distribution and franchising, where a manufacturer gave a margin to whoever moved the product. Software adapted the model as channel sales matured, and the recurring nature of subscriptions🔂SubscriptionSales & RevenueA recurring subscriptionView reference → reshaped it. A one-time hardware margin became an ongoing share of monthly recurring revenue, which aligns a partner's incentive with retention rather than the initial sale alone.

Current practice has settled into recognisable bands. Industry benchmarks put referral partners around 15 to 30 percent of first-year value and resellers around 20 to 40 percent, with ongoing revenue share commonly 10 to 25 percent of MRR for managed-service partners who build a sustained practice on the product. Marketplace cuts run separately and steeper; the large app stores have long taken roughly 30 percent of gross. The share is the lever that decides which deals a partner brings you first.

Cusumano, Gawer, and Yoffie observe in *The Business of Platforms* that the cut a platform takes from complementors is one of the primary levers governing how much external developers and resellers invest in building on top of it: set the take-rate too high and partners redirect effort to competing platforms or build the capability💪CapabilityStrategyAn ability that enables value deliveryView reference → themselves; set it too low and the platform cannot sustain the infrastructure that makes partnering attractive in the first place. The roughly 30 percent rate that large app stores have held is not an industry equilibrium so much as a contested governance choice that partners weigh when deciding where to concentrate.

How it works in practice

A B2B analytics company runs a tiered programme. Bronze partners earn a 20 percent referral fee; Gold partners, defined by managed ARR above £100k, earn 30 percent plus co-marketing funds. A consultancy joins at Bronze, refers four accounts in two quarters, crosses the threshold, and moves to Gold. Its incentive to source the next deal rises with the split, and the company has spent nothing up front: every pound of share is paid against revenue that already landed. The tier structure does the work of turning a casual referrer into a committed channel.

Ramanujam and Tacke argue in *Monetizing Innovation* that how you charge is often more important than how much you charge: the structure of a monetisation model shapes behaviour throughout the customer relationship🫶Customer RelationshipBusiness ModelA type of customer relationshipView reference →. Applied to partner economics, a partner who earns a share of recurring revenue faces a different incentive surface than one who earns a one-time margin — the recurring model aligns partner effort with retention rather than with the initial close.

Partner revenue share vs. its neighbours

• Partner tier🥈Partner TierPartners & EcosystemA partner tier levelView reference → is the membership level a partner holds (Bronze, Gold, Platinum). The revenue share is the economic term attached to that level. The tier sorts partners; the share rewards them, and partner_revenue_share_governs_partner_tierPartner Revenue SharegovernsPartner Tiercross-domain ties the two.
• Partner program🎗️Partner ProgramPartners & EcosystemA partner programView reference → is the whole structure: rules, tiers, enablement, and the shares. The revenue share is one mechanism inside it, the part that moves money.
• Revenue stream💵Revenue StreamBusiness ModelA source of revenueView reference → is the company's own income line. The partner revenue share is a deduction against a stream, the cost of acquiring revenue through someone else's effort rather than direct sales.

In the graph

In the Unified Product Graph, a partner revenue share sits in the ecosystem region. A partner_program🎗️Partner ProgramPartners & EcosystemA partner programView reference → connects to it through partner_program_shares_revenue_via_partner_revenue_sharePartner Programshares revenue viaPartner Revenue Sharehierarchy, and the share in turn governs tiers via partner_revenue_share_governs_partner_tierPartner Revenue SharegovernsPartner Tiercross-domain. Modelling the split as its own node keeps the incentive economics legible: you can read, in one place, what each tier earns and which revenue streams those payouts draw against, which is exactly the view a channel team needs🫀NeedUserA user need, pain, desire, or constraintView reference → when it decides whether the programme is paying for itself.