Maiife

ROI · Before code exists

Plan review

What does catching a bad spec before the build save?

Anything written before code: PRDs, specs, agent plans.

%

Wrong module, a caller nobody listed, a utility that already exists.

%

A review that can't match the plan to real code declines to score rather than guess.

days

Agents rebuild quickly; the loss is mostly re-review and re-planning.

days

Edit a paragraph instead of a pull request.

min

Charged against every spec, including the clean ones.

$

Fully loaded cost of one engineering hour — salary, benefits, overhead. Use your own.

The formula

Nothing on this page is hidden.

defects caught = specs × defect rate × detection rate
hours saved    = defects caught × (days after build − days in spec) × 8
hours spent    = specs × review minutes ÷ 60

net / month    = (hours saved − hours spent) × rate

Reading time is charged against every spec, including the clean ones.