a builder's codex
codex · patterns · The Economic Turing Test — outcomes pricing, agent labor, revenue per employee

The Economic Turing Test — outcomes pricing, agent labor, revenue per employee

Convergence

Three operators converge on a shared economic claim: AI agents change the unit of value from per-seat software to outcome-based labor substitution. The benchmark question is the Economic Turing Test — would you hire the agent if you didn't know it was a machine? — which forces outcomes pricing and rewards top performers (and underfunded teams) disproportionately.

Operators

Variation

Implication

For application companies: model your ARR roadmap with outcome-priced agent revenue, not seat-priced software revenue. For team leaders: deliberately undersize teams so substrate absorbs work; over-invest in the top quartile of operators. For evaluation: ask the Economic Turing Test on every agent build — if the answer is no, the agent isn't shipping value yet.

Sources

Open the interactive view →