Odit Frontier Partners · Advisory Services
Studio active LinkedIn ↗

Home / Dispatches / D-001

Dispatch · D-001 Capital architecture · Frontier tempo 26 January 2026

The Cheetah Principle — why speed, not mass, determines alpha in African capital markets.

A short note on tempo as a design variable in frontier capital. The studio's Strategy & Innovation Lab is configured around the observation that frontier alpha is determined less by capital mass than by the fit between capital tempo and the operating cadence of the receiving environment. This dispatch sets out the principle and its implications for instrument design.

Capital architecture intended for frontier environments often fails not because the architecture is poorly designed in absolute terms, but because it is designed at a tempo the receiving environment cannot absorb. The instrument arrives. The window has already closed. The architecture is structurally elegant. It is operationally late.

The Cheetah Principle is the studio's working name for the observation that, in frontier capital systems, tempo is a first-order design variable. It is not a metaphor. It is a constraint that, when ignored, quietly determines whether deployed capital can be used as intended.

What the principle states

Frontier operating environments — in much of the African continent and in comparable jurisdictions elsewhere — run on compressed decision cycles. Cash positions move quickly. Counterparty windows open and close inside days, not quarters. Operating institutions resolve commercial questions through judgment and direct contact, often before a contract is drafted. This is not informality. It is a high-velocity system tuned to its conditions.

Capital architectures designed under the assumption of slow institutional cadence — months of review, multi-stage approval, retrospective monitoring — arrive late by construction. The receiving institution either declines the capital, restructures around it (losing the operating logic that justified the funding), or accepts it and operates outside the architecture's intended boundaries because the architecture would not permit the operating reality.

Why tempo is the design variable

In environments with deep institutional buffer, tempo is hidden. Slow capital is absorbed by treasury functions, regulatory grace periods, and credit lines that bridge gaps. The architecture and the operating reality run on different clocks, and the buffer reconciles them. Tempo, in those environments, is not where outcomes are decided.

In environments without that buffer, tempo is where outcomes are decided. A drawdown decision that takes twenty business days is not capital deployed at speed; it is capital deployed late, with the architecture intact and the opportunity gone. The instrument is not wrong on its terms. It is wrong for the cadence it is operating in.

Capital that arrives at the wrong tempo is not slow capital. It is, structurally, no capital at all — the architecture has been delivered, but the deployment window it was supposed to enter has already closed.

What this implies for design

Treating tempo as a design variable changes three things at structuring time:

  • Response loops are compressed inside the operating cadence of the institution being funded — not inside the cadence of the capital partner's internal processes. The capital partner's reporting cycle is not the design constraint. The operating institution's is.
  • Decision rights are front-loaded into the instrument. Triggers, conditions, and acceptable variances are specified at structuring, embedded in the architecture, and exercisable inside the loop. Case-by-case negotiation is removed from the hot path because the hot path will not wait.
  • Structures remain stable under velocity — meaning they can run at the tempo of the operating environment without losing coherence. Speed without structure is breakage. Structure without speed is irrelevance. The work is to design for both.

Where the principle applies

The principle is not universal. In low-velocity environments — where deployment windows are months and the cost of slowness is absorbed elsewhere — tempo is not the binding constraint, and other variables dominate the design. The principle applies where the operating environment runs faster than the capital architecture is built to handle, and where the mismatch is the failure mode.

That description fits a substantial part of frontier private capital. It is the design problem the studio's Strategy & Innovation Lab is configured around.


The full version of this dispatch is available as PDF above. The PDF includes the original framing and additional commentary on terrain fit, the limits of the analogy, and the relationship between tempo and capital legitimacy.