ASUME

Objectives

Partnerships

Objective
Partnerships
Primary use
Mutual fit
Applies to
Maintained understanding
Status
Planned
Capabilities
Partner Search · Joint Plays · Ecosystem Gap
Workflows
Partner identification · Ecosystem strategy

The Partnerships objective helps teams identify companies with evidence of mutual fit, define what they can credibly create or deliver together, and understand which capabilities or relationships are missing from their wider ecosystem.

Selecting Partnerships does not create a separate understanding of a company. It changes what ASUME evaluates and which outputs it produces from the maintained understanding.

What Partnerships evaluates

Complement
Looks for companies with the strongest potential to complement your capabilities, access, or relationships.
Joint value
Evaluates what the companies could credibly create, deliver, or distribute together.
Ecosystem gap
Considers which missing relationships prevent the wider ecosystem from meeting important market needs.

How ASUME applies Partnerships

Maintained understanding → Partnerships → Partnerships outputs

ASUME forms a structured understanding of your company and potential partners: what each company offers, which needs it addresses, which audiences it serves, what capabilities it lacks, and what it may gain from working with another organization.

It then evaluates the relationship from both directions. A partnership cannot succeed when its value exists for only one side.

Capabilities

CapabilityWhat it does
Partner SearchIdentifies companies with evidence of mutual fit.
Joint PlaysDefines what the companies could offer or pursue together.
Ecosystem GapReveals where missing capabilities or relationships limit the wider market.

Joint Plays

Finding a compatible company does not define what the partnership should do. A joint play describes the need being addressed, the contribution of each company, the audience that benefits, the way value will be delivered, and the intended outcome.

ASUME evaluates how the companies' capabilities fit together and where duplication, conflict, dependency, or weak incentives may exist. Joint plays should be designed around the specific relationship rather than copied across every company in the ecosystem.

Example: A cybersecurity platform and an incident-response consultancy identify a joint play for regulated companies. The platform provides continuous monitoring; the consultancy provides investigation and executive response.

Ecosystem Gap

Even when individual partnerships are valuable, the network may still contain important gaps. Ecosystem Gap examines the combined capabilities of your company and its partners.

The purpose is not to maximize the number of partners. It is to build the smallest useful network capable of addressing the intended market need with clear roles and limited unnecessary overlap.

Example: A company has partners for software implementation, cloud infrastructure, and customer support. Ecosystem Gap shows that the combined network cannot help customers demonstrate regulatory compliance, so the next search can be specific.

Workflows

WorkflowHow Partnerships is applied
Partner identificationFind companies with evidence of mutual fit before designing the relationship.
Ecosystem strategyTurn fit into a joint plan and see what the wider network still lacks.

Partner identification

Partner Search identifies companies with evidence of mutual fit. A newly identified ecosystem gap can initiate another search.

The result is not a guarantee that two companies will cooperate. It is a reasoned explanation of why a relationship deserves investigation.

Ecosystem strategy

Joint Plays transforms that fit into a specific plan for creating and distributing value. Ecosystem Gap shows how each relationship contributes to the wider network and what remains missing.

The addition of a new partner can alter the role or value of existing relationships.

Extending Partnerships

ASUME is expanding the Partnerships objective across additional workflows and developer interfaces. These extensions are planned.

InterfacePurpose
Partnerships APIAccess Partnerships capabilities programmatically.
Partnerships SDKBuild Partnerships-specific workflows into applications.
Partnerships MCPMake Partnerships capabilities available to supported agents.

What Partnerships does not claim

Not a guarantee of cooperation
A partnership output explains why a relationship deserves investigation. It does not guarantee that two companies will cooperate.
Value must exist for both sides
A relationship that is useful to only one party is not yet a strong partnership opportunity.
Human judgment still matters
ASUME supports partnership strategy but does not replace commercial, legal, or relationship judgment.
© 2026 ASUME B.V.