Test a capital decision

One asset · before effort and capital move

Operational Decision Review

Before effort and capital move: are you even acting on the right variable?

Test a capital decision
Decision Governance · Ironclad Castings · Operational Decision Review
What you can defend today — and what you can’t yet · claim permission ladder
L4 · Observed / bounded0
L3 · Conditional read0
L2 · Screening only1
L1 · Prohibited until evidence9
1 allowed · 0 conditional · 9 prohibited. Blocking variables keep the read below decision-defensible. All ROI, payback, NPV, IRR refused on the record.Source · ZLab claim ladder

If the leading hypothesis is wrong

how much of the capital ends up in the wrong place?
70% of CAPEX potentially misallocated
If utility-led CAPEX is funded and this is the true driver, an estimated 40–70% of CAPEX targets the wrong driver (process load remains).Source · ZLab full report
What you’re seeingOperational Decision ReviewPress the read at every evidence level — what holds, and the capital at risk if it’s wrong.
By handArgued for weeks; a call no one could defend in the room.
Other toolsAudits & models observe the asset; they stop before the decision.
hover to take control

In days, not weeks: whether you're solving the right problem, what you can defend, and what's at risk if you're wrong.

What you’re seeingOperational Decision Review · what to question firstEvery move that could change the call, placed by what it costs to learn against how much it moves the decision — then ranked: fund now, defer, or hold.
By handA to-do list ordered by whoever asked loudest.
Other toolsDashboards list tasks; they don't rank what actually moves the call.

You leave with the dominant misframing, a capital-at-risk range, and a go / no-go you can defend, with no savings claims we can't yet stand behind.

What lands on your desk

  • A go / no-go you can defend, plus the admissibility state: does this decision deserve your confidence yet.
  • The dominant misframing: whether you're optimizing the right variable at all.
  • A decision risk map: what's financially fragile, and where.
  • A capital-at-risk range: what's exposed if the read is wrong.
  • The rival scenarios still in play, and an evidence pack tracing every claim to its source.
  • The next decision path: the cheapest evidence that would move the call.

Why it's different

  • A consultant hands you an opinion; an audit observes the asset; a dashboard shows data; an AI writes something fluent.
  • None of them tells you the decision might be mis-framed. This one does, before effort and capital move, and with no savings number we can't yet defend.

Everyone else produces an output: a deck, a dashboard, a report, a fluent paragraph. We govern whether it has earned the right to stand. A model can produce a recommendation; it can't decide whether the recommendation is admissible.

FAQ

Questions before you bring us the asset

Who is this for?

The team deciding whether to bid, retrofit, or commit on one asset, before resources move, when they don't want to decide blind.

What do I leave with?

A go / no-go you can defend, the dominant misframing of whether you're acting on the right variable, a decision risk map, a capital-at-risk range, and the cheapest next evidence that would move the call. No savings claims we can't yet stand behind.

How is this different from a consultant, an audit, a dashboard, or an AI?

A consultant hands you an opinion; an audit observes the asset; a dashboard shows data; an AI writes something fluent. None of them tells you the decision might be mis-framed. This one does, before effort and capital move.

Bring us the asset.

Test a capital decision