The Partnership Playbook: How We Structure Venture Collaborations

The first partnership I entered without a proper structure cost six months of operational time and produced nothing. It was a distribution agreement with a regional e-commerce platform — handshake terms, informal milestones, no exit clause. When the partner's priorities changed (and they did, three months in), there was no mechanism to either hold them accountable or wind down cleanly. We just stopped. No documentation of what was owed, no agreement on what to do with the leads that had been generated, no clear statement of who owned the channel relationship we'd jointly built.

That experience produced the partnership playbook we use at HW88 today. The core insight: partnerships fail because founders treat them as relationship agreements instead of operational contracts. The relationship part is built through execution. The contract part must be built before execution begins.

The Three Partnership Types We Enter

Not all partnerships are the same, and treating them as if they were — using one template, one set of terms, one operating cadence — is how you create conflicts that were preventable.

Equity Partnership. An equity partnership is one where HW88 takes a structured ownership stake in a venture or provides significant intellectual and operational infrastructure in exchange for equity. These are the highest-commitment, highest-upside partnerships we enter. The distinguishing feature: the governance structure. In an equity partnership, HW88 has board or advisory representation, access to financial reporting, and veto rights on specific categories of decisions (new debt, acquisition, or change of control). Terms: equity percentage negotiated case-by-case, typically 10-25% for operational support and infrastructure, with vesting tied to performance milestones over 24-36 months. The primary risk in equity partnerships is valuation — establishing fair equity value at early stage requires explicit agreement on a valuation methodology before the conversation gets emotional.

Revenue Partnership. A revenue partnership is one where HW88 and a partner share revenue generated through a jointly operated channel, initiative, or customer relationship. No equity changes hands. The distinguishing feature: a clear revenue attribution mechanism agreed in advance. Who generated the customer? At what percentage does HW88 participate? On which revenue events (first purchase, recurring, lifetime)? Revenue partnerships are easier to enter and exit than equity partnerships, which makes them the correct default for exploratory collaborations where the long-term fit is uncertain. Our Bayanihan Harvest co-distribution arrangements with regional cooperatives are revenue partnerships — we provide operational infrastructure and platform, the cooperative provides distribution reach, and we share margin on completed transactions.

Service Partnership. A service partnership is one where HW88 provides defined services to a partner entity in exchange for retainer or project fees. The service partnership differs from a client relationship in scope and integration — a service partner is typically embedded in our operations or vice versa, not just receiving deliverables. Our NDA-bound client engagement is a service partnership of this type. Service partnerships require the clearest scope definition because the failure mode is scope expansion without corresponding compensation — a phenomenon I have seen referred to as "relationship scope creep" that is functionally a silent renegotiation of the original terms.

The 5 Deal-Breaker Conditions

Before any partnership conversation advances to term sheet, we assess five conditions. If any of them is present, we do not proceed.

Misaligned time horizons. If a potential partner is optimizing for a 6-month outcome and we are building a 36-month relationship, the operational decisions will conflict continuously. Time horizon alignment must be explicit. We ask directly: "What does success look like in 12 months? In 3 years?" If the answers are incompatible, the partnership will surface that incompatibility at a cost.

Unclear decision authority. Partnerships fail when neither side knows who can make a binding decision on the partner's behalf. We will not enter a partnership where the point of contact cannot commit resources without escalating every decision to an undisclosed approval chain. If a conversation ends with "I'll need to check with the team," we ask to meet whoever has decision authority before proceeding to terms. This is not about ego — it is about operational velocity.

Prior partnership termination without documentation. If a potential partner has exited a previous partnership without a formal termination record — no settlement memo, no transition documentation — that is a signal about how they handle exits. Exits happen in every partnership. Partners who have not developed exit discipline will not develop it when they are exiting with us.

Technology or infrastructure dependency without fallback. In ventures where the partnership involves technical integration, a partner that requires HW88 to build infrastructure that only benefits the partner — and for which HW88 has no fallback if the partnership ends — creates a structural hostage dynamic. We build integration architecture that can be undeployed cleanly. If a potential partner's model requires us to create irreversible technical dependency, we treat it as a deal-breaker.

Unresolved IP ownership. Any partnership that involves the creation of new intellectual property — code, content, data models, brand assets — requires explicit IP ownership documentation before the first line of code is written or the first piece of content is produced. The conversation that should be five minutes at the start becomes a six-month legal dispute at the end if it is skipped.

The Term Sheet Structure

We have five non-negotiable terms in every partnership agreement, regardless of partnership type.

1. Defined revenue attribution mechanism. How is revenue attributed to the partnership? What is the calculation methodology? Who provides the data that determines the attribution? Ambiguity here is the source of the most painful partnership disputes. The mechanism must be specific enough that both parties could independently calculate the same number from the same data.

2. Operating cadence commitment. What does each party commit to doing, and at what frequency? Monthly review meeting, quarterly reporting, defined escalation path. A partnership without an operating cadence is not a partnership — it is an intention that will become irrelevant the moment each party's other priorities compete for attention.

3. Exit terms with trigger conditions. Under what conditions can either party exit? What is the notice period? What happens to jointly created assets, customer relationships, and data on exit? We require this language even in partnerships we expect to be long-term. The value of exit terms is not that you expect to use them — it is that their existence prevents the negotiation from happening under adversarial conditions.

4. Dispute resolution pathway. Philippine legal process for commercial disputes is slow. We require all partnerships to include a specific dispute resolution pathway: first, written notice; second, senior leadership meeting within 15 business days; third, mediation through a named mediator; fourth, arbitration. Litigation as a first resort is prohibited in our template. The pathway is not about distrust — it is about preserving the relationship through manageable friction.

5. Information rights. What financial and operational information does each party have the right to request? At what frequency? Within what timeframe must requests be fulfilled? This is non-negotiable for equity partnerships and important for revenue partnerships. A partner who will not agree to transparency about shared-revenue reporting is communicating something worth hearing before the partnership begins.

The Operating Cadence for an Active Partnership

A partnership agreement without an operating cadence produces drift. Every active partnership at HW88 runs on the following structure:

Monthly: A working session between the operational leads on both sides. Agenda: current period metrics against agreed targets, blockers, and decisions required. Duration: 60 minutes maximum. Required output: a brief memo (one page) documenting the decisions made and the blockers identified. The memo is shared within 48 hours. Skipping the monthly review is grounds for a formal partnership health check — not as punishment, but because a partner who consistently cannot allocate 60 minutes per month to the relationship is communicating something about prioritization.

Quarterly: A senior leadership review. Agenda: trailing 90-day performance against the partnership plan, budget review for the following quarter, and any amendments to the partnership terms warranted by material changes in either party's situation. The quarterly review is also the moment to formally document any agreed departures from the original term sheet — nothing changes the terms without a written amendment signed by both parties.

Annually (for equity partnerships): A full partnership review. Performance against the 12-month milestones embedded in the equity agreement, assessment of the vesting timeline, and a formal discussion of whether the partnership's strategic rationale still holds. Annual reviews have produced both term extensions and structured exits — both are valid outcomes.

The Partnership That Failed and What the Failure Mode Was

In 2024, HW88 entered a revenue partnership with a content distribution platform that was building audience in the Philippine digital finance space. The partnership was structured around a revenue share on workshop enrollments generated through the platform's email list. The term sheet was adequate — attribution mechanism defined, exit terms present, monthly cadence agreed.

The failure was in execution, specifically in information rights. The partner controlled the email list, the send data, and the click-to-enrollment tracking. The attribution mechanism assumed they would provide accurate send data monthly. They provided data that was inconsistent — different reporting formats in different months, delays in delivering the numbers, and one quarter where the data was simply not provided.

The dispute was not about intent to deceive. It was about the gap between agreeing to an information rights clause and actually having the operational systems to fulfill it. The partner's reporting infrastructure could not produce the data the agreement required.

We could have discovered this before signing by asking a simple due diligence question: "Can you show me an example of the monthly report you would generate for this partnership?" We did not ask. We assumed that agreeing to provide data was the same as having the infrastructure to provide it.

The exit was clean — the exit terms were well-documented — but the three quarters of disputed attribution before exit cost operational attention that should have gone elsewhere.

The lesson: due diligence on operational infrastructure matters as much as due diligence on strategic fit. A partner who cannot produce the data a partnership requires is not a bad partner. They are an incompatible one.

Partnerships Are Operational Commitments

The temptation in the early stage is to sign partnerships quickly because they feel like growth without capital. They are not free. Every partnership requires operating cadence time, governance attention, and conflict resolution energy. A bad partnership costs more than no partnership.

The playbook exists because we have paid the tuition. Use the deal-breaker conditions to filter early. Use the term sheet structure to establish clarity before trust is required. Use the operating cadence to catch drift before it becomes conflict. And document exits as carefully as you document entries.

Partnerships that run well compound. They produce introductions, shared distribution, and operational infrastructure that benefits the next partnership you enter. That compounding is real, but it only starts when the structure is correct.

The Pre-Partnership Due Diligence Checklist

Before we enter any partnership term sheet, we complete a checklist that has evolved through every partnership we have run. These are not hypothetical — each item exists because a gap in that area caused a real problem.

Operational capacity verification. Can the partner actually execute the commitments they are making? This requires looking past the sales presentation. We ask to see examples of reports they currently produce for other relationships, documentation of their current workflows, and references from at least one prior partnership. A partner who cannot show you how they execute is a partner who has not executed yet.

Stakeholder map. Who at the partner organization makes decisions about resources, about budget, about personnel assigned to the partnership? We draw this explicitly. If the champion is at one level and resource authority is at a different level, there is a structural risk that the champion's enthusiasm does not translate into the delivery that requires resources.

Exit scenario walkthrough. Before signing, we walk through the exit clause out loud with the partner. Not as a threat — as a collaborative exercise. "If this partnership needed to wind down in six months, here is what we have agreed happens to the customer list, the joint assets, the pending deliverables. Does this match your understanding?" Partners who are uncomfortable with this conversation are communicating that they have not thought through the exit. Partners who engage with it straightforwardly are easier to work with and easier to exit cleanly if necessary.

Data ownership and portability. Any data generated through the partnership — customer data, transaction records, usage analytics — must have an ownership and portability agreement before the first data point is created. The question is not just "who owns it" but "in what format can it be exported, and by when, if the partnership ends." The partner who controls the data controls the exit terms in practice, regardless of what the agreement says.

This checklist does not guarantee good outcomes. What it does is eliminate the class of failures that come from things you knew but did not formalize. The failures that remain are genuine surprises — which are significantly fewer and significantly more instructive.