Agile Capital Allocation

Why Capital Allocation Kills Scale-Ups

Approximately 29% of scale-ups that have achieved product-market fit fail because of financial mismanagement. The product works. The market exists. The money runs out or is deployed in the wrong places at the wrong time.

Pattern 1: Gut-feel funding. The founder believes in a project. Capital flows based on conviction, not evidence. Six months later, the project shows no measurable traction. Killing it feels like admitting a mistake, so it gets more funding. Sunk cost bias turns a bad bet fatal.

Pattern 2: Gate creep. A project starts with clear KPIs. Three months in, the team misses them. Instead of killing the project, leadership redefines the KPIs. Goalposts move. Capital keeps flowing. The original thesis is abandoned but spending continues.

Pattern 3: No connection between operational performance and funding. The sales team misses quota two quarters running. Capital allocation stays unchanged. A new product initiative gets the same funding as when revenue grew 40% YoY. The annual budget never adjusts to operating reality.

Module 8 addresses all three patterns through evidence-based funding tiers (not gut feel), locked gate KPIs (not movable goalposts), and weekly KPI feeds from Modules 3 and 6 (not annual budgets).

Four Funding Tiers

Structure

Every project in the company maps to one of four funding tiers based on its stage of development and evidence of traction.

Tier 1: Exploration (up to 4 weeks). Rapid discovery. The only KPIs at this tier are validated pain and customer acquisition cost (CAC) tracked from baseline and below $100. The bar is intentionally low. Exploration should be cheap and fast. Kill decisions at this tier cost almost nothing.

Tier 2: MVP. Build small. KPIs tighten: pilot users, NPS at or above 30, and baseline gross margin. The project must demonstrate that a small audience values the output. Module 5's client health data can provide NPS and usage signals for projects with customer-facing components.

Tier 3: Scaling. Expand team and marketing. KPIs become financial: lifetime value to customer acquisition cost (LTV:CAC) at 3 or higher, and churn at or below 5%. Module 6's PV2 metric enters the picture here as a revenue-side gate KPI. If sales velocity is red, the project cannot advance regardless of other metrics.

Tier 4: Expansion. Geographic or vertical rollout. KPIs are company-level: payback under 12 months and cash runway at or above 12 months. Module 3's full KPI dashboard feeds this tier review.

Tier cap transparency

Tier caps are published in the finance portal. This prevents spend creep where project leads incrementally increase budgets without formal tier advancement. Everyone in the organization can see the boundaries.

KPI-Driven Gate Criteria

Gate logic

Capital releases when all gate KPIs hit green for two consecutive checkpoints. Not one. Two. This prevents single-period anomalies from triggering premature advancement. If KPIs are not met after two checkpoints, the project presents a mitigation plan at the Monthly Capital Governance Forum.

Locked KPIs

Gate KPIs are locked at project kickoff. Any changes require board-level approval. This is Module 8's answer to gate creep. The team that launched the project agreed to specific success criteria. Those criteria cannot be revised downward to accommodate disappointing results.

Connection to Module 1

Module 1's Leadership DNA Radar adds behavioral governance. Red on financial discipline requires board-level sign-off for any gate KPI exception. This prevents founders from overriding controls through personality rather than evidence.

Module 1's Vision Canvas adds a strategic layer. The assumptions named in the Risks and Assumptions Block become gate criteria. "We assume CAC holds at current levels" becomes a funding gate. If CAC exceeds the stated threshold, the project gate KPI automatically turns amber. If it exceeds the threshold for two consecutive checkpoints, the gate turns red and funding freezes until two consecutive green checkpoints, and the Forum may kill the project.

The Live Capital Tracker

What it does

The Capital Tracker is a weekly-fed dashboard that shows every project's funding status. Columns include project name, tier, tranche amount, burn percentage, KPI status (traffic-light), and next gate date.

Automation

Finance tools push actual spend data weekly. The KPI system (Module 3) sends status updates weekly. The tracker is not a quarterly review document. It is a living dashboard that updates continuously.

Early warning system

If a KPI flips to amber, the system auto-fires an email: "At-risk: prepare mitigation plan." This forces project leads to develop solutions before the gate review, not during it. Arriving at the Monthly Forum with a red KPI and no mitigation plan is a signal that the project should be killed.

Scenario modeling

The tracker includes scenario modeling capability. Toggle variables (growth rate, CAC, gross margin) to instantly visualize the cash runway impact. This connects to Module 7's AI governance: the scenario modeling engine is itself an AI deployment, registered in Module 7's AI Register with appropriate oversight.

Variance alert bots

Automated monitoring flags when actual spend runs more than 10% over plan, the Module 3 red edge (starting value). Two consecutive variance alerts automatically trigger a finance team SOP mandating a revised quarterly financial outlook. This prevents the common failure of plans that diverge from reality for months before anyone formally acknowledges the gap.

Monthly Capital Governance Forum

Structure

Attendees: CFO, COO, and relevant project leads. Duration: 60 minutes, strictly enforced.

Agenda:

Ten minutes: Tracker heat-map overview (quick scan of all projects). Fifteen minutes: Deep dive on red items or projects exceeding tier gates only. Twenty minutes: Decisions (confirm evidence-based advances, hold, or kill). Ten minutes: Assign action owners. Five minutes: Update tracker live and circulate minutes.

Decision rules

Advancement follows the evidence: two consecutive green checkpoints release the tranche, and the Forum may hold or kill with a recorded reason. "Kill" is an explicit agenda option at every meeting. Normalizing the kill decision is critical. Sunk cost bias is the most common capital allocation failure, and the only way to combat it is to make killing a project a routine, expected, psychologically safe option.

All meeting notes are auto-archived for audit trail. This connects to Module 9 (Exit and Acquisition Layer), where a complete capital governance history demonstrates fiscal discipline to acquirers and investors.

What makes this different from standard capital allocation

Standard capital allocation frameworks (Swiss Re's gated funding model from 2016, Bain's strategic resource allocation, venture-style staged investment) provide excellent methodology for managing capital deployment.

Module 8 adds four capabilities that standalone frameworks do not include.

First, gate criteria are seeded by diagnostic scores. Module 1's heat-map does not just inform the conversation. It proposes the parameters, and leadership confirms them. Red on financial discipline moves gate exceptions to the board. A revenue-dependent project advances to Tier 3 only with PV2 green (via Module 6).

Second, KPI data flows weekly from Module 3, not from quarterly reports. The Capital Tracker shows today's reality, not last quarter's numbers.

Third, the kill decision connects to the full operating system. Killing a project in Module 8 may trigger Module 10 (Change Enablement Sprint) to manage the communication of the wind-down. It may affect Module 7's AI Register if the killed project included an AI deployment. It may shift Module 4's integration roadmap if the project required new system connections.

Fourth, the governance history is always audit-ready for Module 9. A company running Module 8 can produce a complete record of every capital decision, every gate review, and every kill rationale within minutes. This is the kind of operational transparency that commands premium valuations.

Who This Module Is For

Module 8 was designed for mid-market companies that have capital to deploy but lack a systematic method for tying that deployment to evidence.

These companies fund projects. Some succeed. Some fail. The difference between the two is often invisible until it is too late because there is no structured gate review, no locked KPIs, and no real-time visibility into burn versus plan. Module 8 creates the financial discipline that prevents the 29% failure rate from applying to them.