This capital allocation method funds projects by tier and releases capital once all gate KPIs show green for two consecutive checkpoints. The Agile Capital Allocation diagnostic scores 5 dimensions on a 0 to 5 scale against written anchors. Red scores propose remediation playbooks for tier mapping, gate locking, evidence wiring, and forum discipline.
What the Lowest Anchors Describe
The VWCG OS Agile Capital Allocation diagnostic defines failure through its lowest written anchors. At a score of 1, the business funds projects ad hoc, with no tiers and caps unknown to the organization. Goalposts move when results disappoint, and funding status lives in quarterly documents, and surprises arrive at review time.
The forum anchor completes the picture of the failure pattern. At a score of 1, no forum exists, funding decisions happen in hallways, and kills never happen. At a score of 3, a forum meets, but the agenda or decision rules slip. Kills at that level are rare and dramatic rather than routine.
A theory of constraints lens suggests finding the one missing rule that limits every later decision. In this diagnostic, every cap and every gate KPI attaches to a tier.
Evidence Coupling adds a further failure mode at its lowest anchor. At a score of 1, budgets are annual, and operating reality never adjusts them. At a score of 5, all upstream feeds are live, and a red PV2 visibly blocks advancement.
Capital Allocation Rules and Partial Adoption
Four published rules carry the page thresholds for the whole module. Tier caps set the size of each funding step, and capital releases only when all gate KPIs show green for two consecutive checkpoints. Two consecutive variance alerts trigger the finance SOP for a revised quarterly outlook. The Forum, chaired by the CFO with the COO, may hold or kill with a recorded reason.
The middle anchors show what partial adoption of those rules looks like. At a score of 3, the tracker exists, but feeds lag or run manually. Alerts exist without routing, and the exception process for gate KPIs stays informal.
Gate KPI Integrity sets the rule for any change after kickoff. Gate KPIs lock at kickoff, and changes need board-level approval. A red financial-discipline signal from the Intelligent Foundations module upgrades any exception to board sign-off. At a score of 5, nobody bypasses the two-checkpoint rule.
Suppose a firm discovers projects funded without tiers during a routine review. That condition is itself a trigger for the Tier Mapping and Tracker Standup playbook. A red Shadow IT Containment score in the Integrated Tech Stack module also routes here. Net-new platform spend must then fit an Agile Capital Allocation funding tier.
The Agile Capital Allocation Diagnostic
The diagnostic scores 5 dimensions on a 0 to 5 scale against written anchors. The composite score is a weighted sum with equal weights of 0.20 per dimension.
Tier Structure Adoption asks whether every project maps to a tier with the page caps and gate KPIs. Gate KPI Integrity asks whether KPIs stay locked and whether Vision Canvas assumptions serve as gate criteria. Capital Tracker Reality asks whether the tracker shows tier, tranche, burn percentage, KPI traffic-light, and next gate date.
Governance Forum Discipline asks whether the monthly Forum runs at 60 minutes with the 10/15/20/10/5 agenda. It also checks that the Forum uses kill as a routine option and that minutes archive automatically for the Exit and Acquisition Layer module. Evidence Coupling asks whether KPI Precision Grid variance alerts update project KPI status, Sales Velocity Engine PV2 gates revenue-dependent advancement, and the AI Deployment Canvas module governs scenario modeling. It also checks kill consequence routing.
A balanced scorecard lens can help leaders read the five scores side by side rather than one at a time.
Capital Allocation Tiers, Caps and Gate Rules
Tier caps run T1 up to $25K for 4 weeks, T2 above $25K to $100K, T3 above $100K to $500K, and T4 above $500K. The finance portal publishes all four caps. Each tier then carries its own published gate KPIs.
T1 requires validated pain and customer acquisition cost below $100. T2 requires pilot users with a net promoter score at or above 30, plus baseline gross margin. A jobs to be done lens can help a sponsor state which customer need the T1 validated pain refers to.
T3 requires LTV to CAC at or above 3, churn at or below 5%, and PV2 green. T4 requires payback under 12 months and runway at or above 12 months. At a score of 5, every project carries a tier, caps sit in public view, and the transparency rule blocks spend creep. The tier rule covers every project, and the diagnostic names no separate rule for inventory build-ups.
Capital releases when all gate KPIs show green for two consecutive checkpoints. A gate unmet after two checkpoints requires a mitigation plan at the Forum. The Forum may hold or kill any project with a recorded reason.
Reading the Score Bands and Routing Red Dimensions
The composite score falls into three bands with no gaps and no overlaps. Red runs from 0.0 up to but not including 2.0 on the scale. Amber runs from 2.0 to 3.5 inclusive, and green runs above 3.5 up to and including 5.0.
A red score proposes the owning remediation playbook, and safety routes act on the first reading. Every amber dimension routes to the Capital Monitoring and Amber Path playbook with 30-day pulse checks. Green dimensions hold, and the CFO monitors them quarterly through the Core Execution module and monthly for the gate status signal.
A color changes only when a score clears the band edge by a margin, or holds for two consecutive scorings. The method publishes that margin for each scale. A route that fires from a scored dimension stays a proposal until leadership confirms it. Confirmation happens at the next monthly governance review or the Phase 3 review in the Core Execution module, whichever comes first.
Routes that fire from measured values and events act on the reading without waiting for confirmation. Those values include PV2, KPI variance, revenue concentration, dates, and logged events. A playbook’s stated duration starts at confirmation, not at the first score.
Suppose a firm scores red on Gate KPI Integrity and amber on the other four dimensions. The red dimension proposes Gate Locking and Evidence Wiring, because routes fire from each dimension rather than from the composite. Each amber dimension enters Capital Monitoring and Amber Path with a 30-day pulse check.
The Three Remediation Playbooks
Three red playbooks cover the five dimensions, and each one names an owner and a stated duration. Tier Structure Adoption or Capital Tracker Reality red proposes Tier Mapping and Tracker Standup. Gate KPI Integrity or Evidence Coupling red proposes Gate Locking and Evidence Wiring.
Governance Forum Discipline red proposes Forum Activation and also routes to the Exit and Acquisition Layer module. Tier Mapping and Tracker Standup inventories every active project with current spend and funding source, then maps each to its tier. It publishes caps in the finance portal and stands up the tracker with weekly feeds. The CFO owns it with a finance analyst, over 4 weeks.
Gate Locking and Evidence Wiring locks gate KPIs for every active project at its current tier and documents retroactive locks as retroactive. It wires Vision Canvas assumptions as gate criteria with amber-on-break automation. It makes a red Sales Velocity Engine PV2 signal block Tier 3 advancement and runs a test of one full gate cycle. The CFO owns it with the COO, over 3 weeks.
Forum Activation sets up the Monthly Capital Governance Forum and runs the first forum to agenda. The CFO, as chair, owns it with the COO, and it takes 2 weeks to activate. Each owner runs at most three red playbooks at once, so a third red still opens and only a fourth queues. A RACI lens can help leadership confirm who owns each open playbook.
Wiring Upstream Evidence into Gate Decisions
The Capital Tracker runs on weekly spend feeds and weekly KPI status from the KPI Precision Grid module. The tracker names no supply chain feed alongside those two. Amber auto-email fires, and the team arms variance bots with the two-alert SOP. Two consecutive variance alerts trigger the finance SOP for a revised quarterly outlook.
A red PV2 signal from the Sales Velocity Engine module blocks Tier 2 to Tier 3 advancement for every revenue-dependent project until PV2 turns green. The CFO registers the scenario engine in the AI Deployment Canvas register. At a score of 5, kill consequences route to affected modules automatically.
A red Pipeline Hygiene Enforcement or Velocity Metric Integrity score in the Sales Velocity Engine module also reaches the Agile Capital Allocation module. That module then flags PV2-dependent gate decisions as unverified for the next Forum. That flag holds until the red Sales Velocity Engine dimension reaches amber.
Imagine a T3 project that depends on an Intelligent Foundations Vision Canvas assumption that breaks. The linked gate KPI turns amber when the break occurs. A second consecutive checkpoint over the break condition turns it red and freezes the tranche. A unit economics lens can help leaders judge whether the T3 LTV to CAC threshold still holds.
The Monthly Capital Governance Forum and Kill Discipline
The Monthly Capital Governance Forum runs at 60 minutes with the published 10/15/20/10/5 standing agenda. The chief financial officer chairs the meeting, and the chief operating officer attends. Advancement follows two consecutive green checkpoints, and the Forum may hold or kill with a recorded reason.
Kill is an explicit agenda option at every meeting, rather than a rare and dramatic act. The Forum archives minutes automatically and keeps them searchable for Exit and Acquisition Layer diligence. Under Capital Monitoring and Amber Path, the CFO counts kill decisions per quarter, since zero kills for a year is a smell rather than a success.
That playbook also reviews the tracker weekly and confirms that each gate review applies the two-checkpoint rule mechanically. It audits exceptions quarterly against board approval and refreshes scenario inputs.
Killed projects route their consequences to the Change Enablement Sprint, AI Deployment Canvas, and Integrated Tech Stack modules. When a killed project affects more than 10 people or any customer-facing process, the Change Enablement Sprint module runs a wind-down communication sprint. A signaling theory lens suggests that a visible kill record tells sponsors the Forum applies its published rules.
Frequently Asked Questions
- What five dimensions does the Agile Capital Allocation diagnostic measure?
- The diagnostic measures Tier Structure Adoption, Gate KPI Integrity, Capital Tracker Reality, Governance Forum Discipline, and Evidence Coupling. Each dimension scores from 0 to 5 against written anchors, with an equal weight of 0.20. Red dimensions propose remediation playbooks, amber dimensions enter monitoring, and green dimensions hold.
- How do tier caps and gate rules prevent unstructured capital decisions?
- Tier caps run T1 up to $25K for 4 weeks, T2 above $25K to $100K, T3 above $100K to $500K, and T4 above $500K. Capital releases only when all gate KPIs show green for two consecutive checkpoints. A gate unmet after two checkpoints requires a mitigation plan at the Forum.
- What happens when a dimension scores red on the diagnostic?
- Red scores from 0.0 up to but not including 2.0 propose an owning remediation playbook. Tier Structure Adoption or Capital Tracker Reality red proposes Tier Mapping and Tracker Standup. Gate KPI Integrity or Evidence Coupling red proposes Gate Locking and Evidence Wiring, and Governance Forum Discipline red proposes Forum Activation.
- How does the Monthly Capital Governance Forum enforce discipline?
- The Forum runs at 60 minutes with the 10/15/20/10/5 standing agenda. The CFO chairs with the COO present, and advancement follows two consecutive green checkpoints. The Forum may hold or kill with a recorded reason, and kill is an explicit agenda option.
- Which upstream feeds wire evidence into capital decisions?
- The Capital Tracker shows weekly spend feeds and weekly KPI Precision Grid status. KPI Precision Grid variance alerts update project KPI status, and a red PV2 signal blocks Tier 2 to Tier 3 advancement for revenue-dependent projects. The AI Deployment Canvas module governs scenario modeling, and killed projects route consequences to three named modules.
- What does an owner do next when working with World Consulting Group on capital allocation failure?
- World Consulting Group delivers the Agile Capital Allocation diagnostic as a service within VWCG OS. The first step of the engagement is a scoring pass of the five dimensions against the written anchors. Each red dimension then proposes its own playbook, so the first playbook depends on which dimensions score red.
