07
Calculator

Iteration Half-Life Calculator

A calculator that converts your real cycle time into learning cycles per year, then shows how compounding — not raw speed — opens the gap between AI-Born firms measuring iteration in hours and legacy firms measuring it in quarters.

ShareXLinkedInFacebookEmail
250×more iterations / year than legacy

What it does

Iteration Half-Life is the time from strategic intent to measurable impact — how long your organization takes to complete one full cycle of signal detection, analysis, decision, execution, and measurement. Chapter 5 puts the contrast bluntly: "Legacy enterprises measure theirs in quarters. AI-Born enterprises measure it in hours or days." When a competitor's learning loop closes in 8 hours and yours takes 12 weeks, you aren't running the same business faster — you're running a different kind of business.

This calculator takes the one number most teams can estimate honestly — how long a single closed loop actually takes — and turns it into the number that matters: how many learning cycles you complete in a year. Then it does the part most dashboards skip. It models the compounding. An enterprise with an 8-hour Iteration Half-Life completes roughly 1,000 learning cycles in twelve months. A competitor running quarterly reviews completes four. The instinct is to call that a 250× advantage, and Chapter 5 explicitly warns that the instinct understates it: "The difference is structural... You cannot buy that. You can only accumulate it, one closed loop at a time."

The tool also locates your bottleneck. Chapter 5 is emphatic that Iteration Half-Life "is not primarily a technology metric. It is an organizational design metric. The bottleneck is almost never compute. It is decision latency — how long it takes for a signal to reach the person or system authorized to act on it." So the calculator breaks your cycle into its five stages, finds where the hours actually go, and points you at the design change — usually a VP-Agent holding authority over a decision class — that would compress it.

Who it's for: founders, COOs, and transformation leads who suspect they're losing not on product but on iteration speed, and want a defensible number for how fast they're currently falling behind.

Figure: The compounding clock this tool operationalizes — like radioactive decay, each completed cycle shrinks the uncertainty of the next.

Enter how long each stage of a single iteration actually takes. Everything normalizes to hours. Nothing is stored or sent.

Time from a signal existing to someone/something noticing it.
Time to understand the signal and frame options.
Time from options being framed to a decision being authorized.
Time to put the decision into the real world.
Time to observe and record the outcome.
Used only to sharpen the bottleneck note — it never changes the math.
Your iteration cadence appears here

Enter how long each of the five stages takes, then calculate to see your cycles per year against the AI-Born and legacy anchors.

Operationalizes the Iteration Half-Life framework.
Further reading
From the books
  • Book 1, Chapter 5 — "The Operating System: How the Machine Core Runs" (Iteration Half-Life: The Compounding Clock; the IPRE Pipeline; VP-Agents and decision latency).
The Dispatch — N°01

Essays from
the lineage break.

New essays, framework studies, excerpts and pre‑order news. Sent rarely. Never noise.