When doing is cheap, deciding is everything

If generation costs approach zero, value migrates to whoever can tell good output from bad. What that does to a company.

There is a standard argument that runs through most AI coverage right now: automation drives down the cost of production, so the economy shifts toward creativity, toward things machines cannot replicate, toward the ineffable human. It is a reassuring story. I do not think it is the right one. Or rather, it is the right destination but wrong on what the scarce input actually is.

The scarce input is not creativity. It is judgment. The ability to tell good output from bad output, fast, in cases you have never seen before, at a scale no human reviewer workflow was designed for. Call it the judgment economy: the regime where generation is abundant and the binding constraint is whoever can evaluate that generation correctly.

I have spent the last several years sitting at the intersection of revenue, technology, and operations, first as CTO, then COO, now CRO at Devlyn, a company that operates hundreds of optical retail locations. We generate, review, and deploy a very large number of decisions every day: pricing decisions, inventory decisions, scheduling decisions, customer interaction decisions. As generation costs fell, first with software tooling, now with language models, I watched where the pressure landed. It landed on judgment, every time. Not on the people who produced the work. On the people who could tell, quickly and reliably, whether the work was right.

This essay is about what that shift actually means for how a company prices its output, organizes its talent, builds moats, and thinks about margin. It is not abstract. Every mechanism I describe I have seen play out in an operating company or can model from first principles of cost economics.

The arithmetic of zero-marginal-cost production

Start with a simple model. Call the cost of producing one unit of work C. For a long time, C was dominated by labor: a writer writes a paragraph, an analyst builds a model, an engineer implements a feature. As C falls, through better tooling, better models, better automation, the equilibrium quantity of production rises dramatically. This is basic microeconomics. When something gets cheaper, you get more of it.

But getting more output does not mean you can use more output. Every unit of output still has to be evaluated before it enters a downstream decision. And the cost of evaluation, call it R for review, does not fall at the same rate as C. R is bounded below by human cognition, by how fast a person can read, understand context, spot a flaw, and make a call. When C drops by 10x and R stays flat, review becomes the bottleneck. The entire production pipeline backs up at the evaluation step.

This is the core mechanism. It is not complicated. What is interesting is the second-order consequences it produces throughout an organization.

At Devlyn, I watched this happen in slow motion as we adopted AI-assisted workflows. We could generate draft communications, draft pricing recommendations, draft shift schedules, in seconds. The constraint shifted almost immediately to the people who could look at that output and say, with confidence: ship it, don't ship it, or here's what's wrong. The generators became abundant. The evaluators became scarce. We started paying closer attention to who our reliable evaluators were, and what made them reliable. That is when I started thinking seriously about the economics of judgment as a standalone input category.

What judgment actually is (and is not)

Judgment is not expertise, though expertise helps. It is not experience, though experience is one input. Judgment is the capacity to evaluate output correctly in cases that are partially novel, where the full context was not present in training, where the edge case was not in the playbook, where the right answer requires integrating multiple signals that are individually ambiguous.

This is why it is hard to automate. You can train a model on historical evaluations. But if the distribution of cases shifts, new market, new product, new regulatory environment, new customer segment, the model's evaluation accuracy degrades exactly when you need it most. Humans with good judgment do not degrade as fast, because they are reasoning from principles rather than pattern-matching on examples. The reasoning is slower, but it is more robust to distribution shift.

This is also why judgment is hard to hire for. You can screen for credentials. You can screen for experience. You cannot easily screen for the ability to reason correctly about a case you have never seen before. It requires a different kind of evaluation process, one that presents genuinely novel situations, not variants of familiar ones.

In the context of The Judgment Economy, the argument I work through is that the historical proxies we used for judgment, degrees, titles, tenure, credentials, are becoming noisier signals precisely as the value of the underlying thing increases. We need better ways to identify and price judgment, because the market for it is becoming the market for the highest-leverage input in production.

What this does to pricing

If you run a professional services firm, or a software company, or any business where output quality is what customers actually pay for, the zero-marginal-cost production environment changes your pricing model fundamentally.

The old model was: price on inputs. You charge by the hour, by the seat, by access to the people or tools that produce the work. This made sense when production was the scarce step. The hour of the senior consultant, or the license to the software, was the thing you were buying.

When production is cheap and evaluation is scarce, the input-based pricing model collapses. A customer can generate unlimited candidate outputs. What they cannot do is evaluate them reliably. What they are actually paying for is the certification, the confident, accountable assertion that a particular output is correct and safe to act on.

This means pricing should migrate toward outcomes. Not the deliverable itself, but the guarantee attached to the deliverable. The revenue model that survives a world of cheap generation is one where you are pricing your judgment, your accountability, your track record of being right in novel cases. Seat-based licensing and hourly billing are artifacts of a production-scarce world. They are being priced out of existence by the same forces that created the opportunity.

I explore this in more depth in Revenue, Re-Engineered: What a CRO sees that a CTO can't, but the short version is: the CRO's job in this environment is to find the layer of the value chain where judgment concentrates, price it accordingly, and make sure the contract reflects accountability rather than effort. Effort is a commodity. Accountability for outcomes is not.

What this does to org design and labor markets

The organizational consequence of cheap production and scarce evaluation is a specific and somewhat uncomfortable redistribution of leverage. People who can evaluate reliably gain leverage relative to people who can produce quickly. Senior people gain leverage relative to junior people, not because the work is harder, but because the evaluation step requires the judgment that tends to accumulate with experience.

At Devlyn, we have tried to make this explicit rather than leaving it implicit. The principle we operate on is: ownership over hours, outcomes over velocity. A senior engineer on our team is not valuable because they write more code per hour than a junior engineer. They are valuable because they own production readiness, they are the ones who can look at a system change and make a confident, accountable call about whether it is safe to ship. That capacity does not scale with headcount in the way that raw production capacity does.

This has real implications for how you structure teams. In a production-scarce world, you want to maximize throughput of the production step: more engineers, more writers, more analysts. In an evaluation-scarce world, you want to maximize the accuracy and speed of the review step. That often means fewer, better evaluators with clearly scoped accountability, not more reviewers doing redundant checks, but sharper evaluators making confident calls on a well-defined domain.

The labor market consequence is a bifurcation. The middle, people who are competent producers but not yet reliable evaluators, gets compressed. Their output is increasingly replaceable by generation tools. The top, people whose judgment is demonstrably reliable in novel situations, becomes more expensive, because the demand for that capacity is growing and the supply is not. The bottom, people learning to evaluate by doing production work, is still valuable, but only if the organization has a clear path from production to evaluation. If that path is blocked by automation, you lose the pipeline that creates future evaluators.

This is one of the underappreciated risks of aggressive automation. If you automate the production step completely, you eliminate the apprenticeship path. Junior people learn to evaluate by first producing, by seeing what good output looks like from the inside, by making mistakes and understanding why they were mistakes. If the production step is done by a model, that learning pathway disappears. You have to find other ways to develop evaluative capacity, which is harder and less natural.

Where moats come from now

The classic technology moat is a switching cost or a network effect. Once enough people use your platform, it becomes harder to leave; the value of staying compounds. These moats still exist, but they are being compressed by the same forces that are compressing production costs. If the underlying output can be replicated cheaply by a competitor using the same generation tools you use, the switching cost drops. The moat has to be somewhere else.

In a judgment-scarce world, the moat is trust. Specifically, it is the accumulated track record of being right, in novel cases, over time, combined with the willingness to be accountable when you are wrong. This is harder to replicate than a production capability, because it is a function of history, of decisions made and observed, of calls that proved correct under pressure, of accountability that was honored when it was costly.

The price of responsibility becomes a moat in itself. A customer who needs a consequential decision certified, whether to deploy a system, whether to price an asset, whether to make an operational change, is not primarily looking for the lowest-cost generator of options. They are looking for the entity that will be accountable if the call is wrong. That entity charges a premium for taking that accountability on. And the premium is sustainable because the track record required to credibly offer that accountability takes years to build and cannot be faked.

This is a fundamentally different basis for competitive advantage than most technology companies have been building toward. It is closer to the basis that law firms, accounting firms, and insurance companies have operated on, where the product is not the deliverable but the warranty attached to the deliverable. In AI-Native, the framing I use is that the companies that will compound in this environment are not the ones with the best generation capability. They are the ones with the best-calibrated judgment, the most reliable track records, and the contract structures that reflect accountability for outcomes.

The CRO lens: margin migrates to the evaluation layer

From a revenue and margin perspective, the judgment economy has a specific and legible shape. Gross margin concentrates at the layer of the value chain where evaluation happens. This is true in professional services, in software, in operations. The production layer commoditizes. The evaluation layer, wherever it sits, retains margin.

The CRO's job is to find that layer and price it correctly. In practice, this means three things.

First, unbundle what you are selling. Most legacy pricing bundles access, production, and evaluation into a single fee. In a world where production is cheap, this bundle misprices everything. Customers who only need access pay too much. Customers who need evaluation pay too little. Unbundling lets you price each layer at its actual market value, which means pricing evaluation at a significant premium to production.

Second, make accountability explicit in the contract. If you are selling judgment, the contract should reflect that. This means warranties, guarantees, service levels tied to outcomes rather than effort. It also means being specific about what you are accountable for and what you are not. Vague accountability is worth nothing; specific, bounded accountability for a defined outcome is worth a lot.

Third, invest in your track record as a revenue asset. Every decision your organization makes, and is held accountable for, contributes to a corpus of demonstrated judgment. That corpus is an asset. It should be managed as an asset, tracked, analyzed, used to improve evaluation accuracy, and cited as evidence in customer conversations. The customer who is considering paying a premium for your judgment wants to see the evidence that the premium is warranted. Your track record is that evidence.

At Devlyn, we have started treating our operational decision history this way. The calls we made about inventory positioning, pricing adjustments, scheduling changes, the ones we made and owned, are a record of our judgment in action. When we can point to that record, we can price our judgment at a level that reflects its actual value. When we cannot, we are back to competing on production cost, which is a race to the bottom.

The practical consequence

The conclusion is not complicated, but it requires discipline to act on. If you are running a company, an operating unit, a product team, a revenue function, the question to ask is not "how do I produce more?" It is "how do I evaluate faster and more reliably, and how do I build the contract structures that let me charge for that?"

The companies that will compound in the next decade are not the ones that generate the most output. They are the ones that can certify output at scale, that have the evaluative capacity, the track record, and the contract structures to make that certification valuable to customers who need consequential decisions made correctly.

This is a different kind of organizational capability than most companies have been building toward. It is slower to develop, harder to replicate, and, precisely because of those properties, more durable as a basis for competitive advantage. The judgment economy does not reward velocity. It rewards accuracy, accountability, and the trust that accumulates from being both, consistently, in cases that matter.

That is what it means for deciding to be everything when doing is cheap. Not that decisions are harder, though they often are. But that the economic value of making them well, and being willing to own the outcome, has never been higher.

Frequently asked questions

What is the judgment economy? It is the regime that emerges when the cost of producing work falls toward zero. Generation becomes abundant, but every unit of output still has to be evaluated before it can be acted on, and the cost of evaluation does not fall at the same rate. Value migrates to whoever can tell good output from bad, fast, in cases they have never seen before.

Why is judgment scarce rather than creativity? Creativity is one of the things generation tools now produce cheaply. Judgment is the capacity to evaluate output correctly in partially novel cases, where the right answer requires integrating ambiguous signals from principles rather than pattern-matching on examples. That capacity is hard to automate, hard to hire for, and slow to build, which is exactly what makes it the binding constraint.

How should pricing change in a judgment economy? Pricing migrates away from inputs (hours, seats, access to production) and toward outcomes and accountability. When customers can generate unlimited candidate outputs, what they pay for is the confident, accountable assertion that a particular output is correct and safe to act on. If you are working out how to price judgment and accountability into a real revenue model, that is the kind of work my team does at Devlyn.