9 July 2026Ricardo Rodriguez, CTO5 min read

The marginal cost of correctness is going to zero. Knowing what "correct" means isn't.

When producing the right answer becomes cheap, the bottleneck moves to specifying it. Almost no company has written theirs down.

Ben Glickenhaus put a line in front of a lot of engineers recently: the marginal cost of correctness is going to zero, and you need to internalise what that means for how you practise software engineering.

He's right, and the implication runs well past engineering.

For most of the history of software, correctness was rationed. Tests, types, documentation, code review, careful error handling — all obviously good, all competing for time against shipping. Being thorough was a trade-off you argued about in planning. When the cost of that thoroughness collapses, the argument disappears. There's no longer an excuse for the untested path or the undocumented decision.

The constraint just moved

But cheap correctness only helps if something defines what correct is.

In code, we're lucky: correctness is comparatively well specified. A test encodes it. A type system encodes it. A schema encodes it. Hand an agent a failing test and it can iterate against a definition of done that somebody wrote down.

Now try the same thing one level up, in the business.

There's no test suite. There's a person who knows. Sometimes there's a document, usually out of date, often contradicted in practice by the person who knows. The specification exists — companies are astonishingly consistent about these decisions — but it lives in heads and habits, not anywhere a system can read.

So you get the failure mode that defines this era of enterprise AI: agents that are flawlessly correct against the wrong specification. The output is well-formed, confident, fast, and wrong in a way that takes a human who knows the business about four seconds to spot and about four weeks to systematically prevent.

Specification is now the scarce skill

If producing the answer is cheap and defining the answer is expensive, then the valuable work in a company shifts decisively toward definition.

That's a real change in what good operators do. Less doing the task; more articulating, precisely enough for a machine, how the task is judged. What the exceptions are. Which rule wins when two conflict. Where the boundary sits between "decide it" and "escalate it".

Most organisations have never had to be that explicit, because humans are extraordinarily good at absorbing ambiguity. A new joiner watches, asks, gets it wrong twice, and calibrates. That tolerance is exactly what let the specification stay unwritten for twenty years — and it's exactly what agents don't have.

What we'd do first

Take one process that actually matters and costs real money — refunds, approvals, onboarding, incident response. Write down how it truly works, including the exceptions people apply without thinking. Then check that against what actually happened over the last quarter.

The gap you find is the real state of your operation. Everyone we've done this with has found one, us included. Close it and you've built something more durable than any automation: a definition of correct that a system can be held to.

Cheap correctness is arriving whether you prepare or not. The companies that benefit are the ones that can say what they mean.

← All posts

Make your company legible to AI.

Book a call →