A strategic partnership
A partnership is a deliberate relationship with another organisation that supplies resources, activities, or reach a company chooses not to build alone. It is the key-partnerships block of the Business ModelBusiness ModelBusiness ModelThe business model canvas or definitionView reference → Canvas, the answer to a simple operating question: what do we depend on someone else for?
The key-partnerships block belongs to Alexander Osterwalder and Yves Pigneur's Business Model Generation (2010). They sort partnerships into four types: strategic alliances between non-competitorsCompetitorMarket IntelligenceA competing product or companyView reference →, coopetition between competitors, joint ventures to build new offerings, and buyer-supplier relationships that secure reliable inputs (OpenStax). The canvas frames three motives behind any of them: optimisation and economies of scale, reduction of riskRiskComplianceA risk to the product or businessView reference → and uncertainty, and acquisition of resources or activities a firm lacks (Strategyzer).
That three-motive framing was built for pipeline businesses, where one firm produces and another consumes. Geoffrey Parker, Marshall Van Alstyne, and Sangeet Paul Choudary's Platform Revolution (2016) argues that platform businesses use partnerships for a structurally different purpose: seeding and balancing the two sides of a network. A platform that cannot yet attract enough producers will partner with content owners or service providers not to outsource an activity but to make the platform attractive enough for consumers to join, which in turn draws more producers. By that reading, the partnership is not a cost-efficiency move but a network-effect accelerant, and its value decays as the network self-sustains.
Coopetition is the most counter-intuitive of the four, the case where direct rivals cooperate on a shared layer, often to reach the volume that makes an activity economic for either of them (OpenStax). The framework forces a firm to name its dependenciesDependencyTeam & OrganisationA cross-team or system dependencyView reference → explicitly. A model that quietly relies on one supplier or one channel partner looks sound on paper until that partner changes terms.
A fintech offers consumer lending. It cannot hold deposits, so it forms a strategic alliance with a chartered bank that originates the loans; the fintech handles the app and underwriting. That single partnership is the spine of the model. It governs the relationship with a contract specifying revenue share, compliance obligations, and a two-year term.
It also runs a buyer-supplier relationship with a credit-bureau data provider, and a partnership with a payments processor whose API it embeds for repayments. When the bank partner signals it may not renew, the risk the canvas was designed to expose becomes concrete: the lending model has no second originator. The fintech starts a parallel alliance with a second bank, accepting thinner margins for resilience.
In the Unified Product Graph, partnershipbusiness_model_partnered_via_partnershipcontract_governs_partnershippartnership_with_integration_partner
Worked example: Trellis
Trellis's distribution leans on the director-to-director sharing loop rather than a channel partner network: a working agent-built tool spreads from one director to the next, and each new director can become a source of further sharing. Any future partnership would sit alongside that loop, not replace it as the primary acquisition channelAcquisition ChannelGrowthA channel through which users are acquiredView reference →.
Mild inconvenience Notices but works around easily
Type-specific fields on BaseNode
partner_typeenumPartnership nature
value_exchangestringWhat each party gives and receives
partnership_tierenumCommercial significance. Drives attention and exec sponsorship.
risk_levelassessmentExposure if the partnership fails (concentration risk, IP risk, etc.)
ownerstringInternal owner. Promote to a `node_owned_by_person` edge if ownership must be queryable.
start_datestringDate the partnership became effective (ISO 8601)
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
5 phases, initial: planning · template: OPERATIONAL
7 edge types connected to this entity.
business_model_partnered_via_partnershipcontract_governs_partnershippartnership_with_integration_partneraccount_partners_via_partnershippartnership_performs_key_activitypartnership_provides_key_resourcepartnership_supports_value_proposition1 framework use this entity type.