Choosing Funding Sources

Strategic intent: Decide, for every Category-2 platform being asked to build something its roadmap didn't include, who bears the investment risk and who captures the upside — then deliberately distribute funding across mechanisms to optimize alignment, risk-sharing, and decision speed.

#Overview

This technique resolves the most consequential decisions in the Launching Initiatives in a Distributed Organization pipeline. It applies only to Category-2 dependencies (enabling platforms doing tweaks) identified in Categorizing Launch Contributors. Three funding mechanisms exist; each carries a different distribution of risk, ownership, and upside.

#When to use it

• After categorization, for every Category-2 platform tweak the launch requires
• When a platform team is asked to build something off-roadmap and the question "who pays, who owns it" is open
• When designing the risk/upside distribution of the launch

#Composition

1. #1. Initiator-funded (Purchase)

   The initiative pays the platform team up-front for the modification, as commissioned development. The platform takes no risk; the initiative bears the full cost.

   Use when: the tweak is narrowly useful to the initiative, the platform has limited confidence in the initiative, or speed matters more than aligned incentives. Trade-off: the initiative carries all financial risk; if the launch underperforms, the investment is sunk.

2. #2. Contributor-funded with revenue share

   The platform funds the modification itself, for a defined share of the revenue the initiative generates. The platform takes the risk and participates in the upside.

   Use when: the platform believes in the initiative, the initiative is cash-light up-front, or the platform's quality of contribution is critical (revenue-share creates ongoing skin in the game). Trade-off: negotiating the share — base, trigger, duration, cap — is cognitively expensive; done poorly it produces post-launch disputes.

3. #3. Holding-funded with equity (strategic investment)

   The Holding funds the modification as a strategic investment, recognizing value beyond the specific initiative. The Holding (or contributing teams) may receive equity-style participation when the initiative becomes a unit.

   Use when: the capability is strategic across the organization (multiple potential consumers), the modification is substantial, or the initiative is being incubated as a future unit. Trade-off: slowest to negotiate, requires governance involvement; most powerful when activated correctly.

4. #4. Design the mix

   Complex launches use mixed funding — some Category-2 dependencies initiator-funded, some revenue-share, some Holding-funded. The mix is itself a design output. Decide each against three variables:

   1. How strategic is the capability beyond this launch?
   2. How much does the contributor believe in the initiative's success?
   3. What are each party's cash constraints?

#Inputs

• Required: the Category-2 list from Categorizing Launch Contributors
• Required: a view of each contributor's belief in the initiative and cash position
• Recommended: the intended post-build governance scenario (equity needs a JV/spin-off)

#Outputs

• Funding decision per Category-2 dependency — initiator / revenue-share / Holding-equity
• Documented rationale — the three decision variables applied to each
• Funding mix — the deliberate distribution across mechanisms

#Process heuristics

• The three sources are exhaustive — new capability is paid for by the requester, the builder, or a third party (the Holding); every arrangement reduces to one or a combination
• Belief enables revenue-share — without contributor belief, revenue-share collapses into bargaining
• Equity needs the right destination — equity participation only works if post-build governance is JV/spin-off, not "absorbed"

#Validation criteria

• Every Category-2 dependency has a funding decision
• Each decision is justified against the three decision variables
• The mix is deliberate, not accidental
• Equity-based choices are consistent with the intended post-build scenario

#Common mistakes

• One-size funding — forcing every tweak through purchase loses alignment; through revenue-share loses speed
• Promising equity without a JV — value-sharing the post-build structure cannot honor
• Under-specifying revenue-share terms — base/trigger/duration/cap left vague becomes a dispute

#Used in pipelines

• Launching Initiatives in a Distributed Organization — as the funding-design technique

#Connections

• Requires: Categorizing Launch Contributors — supplies the Category-2 list
• Feeds: Designing the Multi-Party Launch Contract — funding choices become per-contributor value-sharing terms
• Depends on: Reaching Financial Autonomy — revenue-share/equity require contributors with real financial autonomy

#Related reading

• Boundaryless field methodology "The Ecosystem Formation Pattern" — the three funding sources, decision variables, the mixed case
• Legacy 3EO Toolkit — the investment and revenue-share contracts