Project Frontier Jorge Menéndez-Pidal

006 / Essay ·

AI is getting cheaper. So why are firms hiring people to install it?

The price of AI is collapsing, yet postings for forward-deployed engineers rose eightfold in 2025. Agents can be copied at the price of compute; plugging them into a firm cannot. Cheaper AI raises demand for the people who implement it, and whether that boom lasts depends on whether AI learns to implement itself.

Cheaper AI raises the demand for the people who install it, and their pay. The price of artificial intelligence is collapsing. For a fixed level of capability, the cheapest model that reaches it has become between nine and several hundred times cheaper each year, depending on the task. You would expect the people who sell and install AI to be among the first casualties: if the product gets cheaper and better every month, surely it needs less help. The opposite is happening. Job postings for forward-deployed engineers, the people AI companies send into client firms to make their models work, rose more than eightfold on Indeed between April 2025 and April 2026.

This is not a hiring fad. It follows from a feature of AI that is easy to miss when looking at token prices. An AI agent can be copied at the price of the compute it uses. The work of plugging it into a company cannot.

Figure 1

The puzzle in two numbers

Price of a fixed level of AI capability
÷9 to ÷900

per year, depending on the benchmark (Epoch AI, 2025)

Job postings for forward-deployed engineers
×8.3

April 2025 to April 2026: 643 to 5,330 postings (Indeed data reported by Business Insider)

The price series tracks the cheapest model that reaches a given score on a benchmark over time. The range reflects different benchmarks and thresholds. Postings measure demand for a role, not the number of people hired, and a count of open postings includes standing requisitions that stay open for months.

The short version
  • An AI agent costs the price of its compute every time it runs. Getting it to run inside a firm (connecting it to systems and data, redesigning the workflow, checking its output) is a one-off cost per workflow, paid in skilled labour.
  • When agents get cheaper, every workflow built around them is worth more, so firms want to build more of them. Cheaper AI therefore raises demand for the people who implement it.
  • The same technology substitutes for the workers who perform tasks and complements the workers who deploy it.
  • If implementers are scarce, cheaper AI shows up as higher implementer wages rather than as more automation. Whether the boom lasts depends on a race between falling AI prices and AI's ability to implement itself.

A job invented for a problem

The forward-deployed engineer was popularised by Palantir, whose software was too complex to hand over and leave. The firm sent engineers to sit with the client, learn the data and the workflow, and build the deployment on site. AI companies have revived the role for the same reason. OpenAI, Anthropic and Cohere have all built or expanded forward-deployed and applied-AI teams, and the job now appears at software firms, consultancies and banks.

What these engineers do is not exotic. They connect a model to the firm's databases and tools, decide which steps of a process an agent should take and which a person should keep, prepare the data, write the evaluations that tell the firm whether the agent is doing the job, and redesign the workflow around it. None of this is about making the model smarter. All of it is needed before the model can do anything useful inside a particular firm.

The part of AI that does not scale

Here is the economic point. Once a workflow has been built, agents can be added at constant cost: a thousand more invoices processed means a thousand more calls to the model, at whatever the model costs. The work of building the workflow is different. It is done once per task, it costs roughly the same whether the firm processes a thousand invoices or a million, and it has to be done by people who understand both the technology and the business.

In the language of economics, AI agents have a constant marginal cost in compute, and implementation is a fixed cost in organisation. In the research note this essay draws on, I build that single assumption into a standard model of automation, in which firms decide task by task whether a person or a machine does the work. Everything else follows from it.

Jevons, one step removed

In 1865 William Stanley Jevons observed that more efficient steam engines had increased Britain's consumption of coal rather than reduced it: cheaper power made it worth using in many more places. Cheaper AI has a Jevons effect too, but it falls on the input that makes AI usable rather than on AI itself.

The mechanism has two parts. When the price of agents falls, each workflow a firm has already built becomes cheaper to run, the firm cuts its prices and sells more, and every task it automates is now worth more. And tasks that were not worth automating at yesterday's prices become worth it today. Both push in the same direction: the firm wants to implement more workflows, and each one needs implementers. The model makes this exact. As agents get cheaper, the demand for implementation labour rises, whatever the firm's size or industry.

So the same technology is a substitute and a complement at once. It substitutes for the people who used to perform the tasks it takes over. It complements the people who deploy it. Asking whether "AI replaces workers" mixes up two groups whose fortunes move in opposite directions.

Figure 2

Cheaper AI, dearer implementers

Implementers employed and their wage as the price of AI agents falls, both indexed to 100 before the fall (Research Note 003, Propositions 2 and 3). The second dial sets the elasticity of supply of implementation labour, from zero (no more implementers can be found at any wage) to infinite (as many as needed at the going wage). Stylised parameters, not estimates: demand elasticity 2, linear comparative advantage across tasks, one unit of implementation labour per task, a quarter of tasks automated before the fall.

Where the shortage shows up

Demand for implementers rises whenever AI gets cheaper. What happens next depends on whether they can be found. The people who can do this work are scarce: they need engineering skill, an understanding of how businesses operate, and experience with a technology that barely existed three years ago. In the short run, their number is close to fixed.

When it is, the figure above shows the result. Cheaper AI does not lead to more automation, because there is nobody to build the extra workflows. It leads to higher wages for the implementers there are. Postings rise because demand rises, but hiring cannot follow, so the price adjusts instead. The value of all the workflows that would be worth building at the lower AI price, and cannot be built, goes to the people who can build them.

That has an uncomfortable implication for anyone expecting cheap AI to transform productivity quickly. With the pool of implementers fixed, a fall in the price of AI lowers costs only on the tasks firms have already automated. Figure 3 compares two economies hit by the same 50% fall in the price of AI. They differ only in whether implementers can be found.

Figure 3

One price cut, two economies

Change caused by a 50% fall in the price of AI agents in the model of Research Note 003, with the implementation pool fixed (orange) or freely expandable at the going wage (grey). Same stylised parameters as Figure 2. Production jobs are jobs on tasks that people still perform.

Where implementers are scarce, the price cut lowers unit costs by about a sixth, leaves the number of automated tasks unchanged, and more than triples implementers' wages. Where they can be found, the same price cut doubles the number of automated tasks, roughly triples spending on compute and nearly doubles the cost reduction. Notice the last row: with the pool fixed, production jobs rise, because the firm grows on the back of cheaper existing automation without automating anything new. Displacement comes when the implementers arrive. I take up that point, and what it means for the productivity statistics, in a companion essay.

Will the boom last?

History offers both answers. Enterprise software created an implementation and consulting industry that has outlived several generations of the software itself. Other technologies created roles that were later absorbed into better tools: building a website once required a specialist and now takes an afternoon with a template.

The model points to the variable that decides between the two. Everything above assumes that the work needed to implement a workflow stays the same as AI gets cheaper. But AI is increasingly good at precisely that work: writing integrations, mapping data, generating its own tests and evaluations. If the implementation requirement per workflow falls as models improve, there are two opposing forces. Cheaper agents raise the number of workflows worth building. Smarter agents lower the labour each workflow needs.

Figure 4

A race between two curves

Employment of implementers (orange) and the share of tasks automated (grey), indexed to 100 before the fall, as the price of AI falls. The dashed line shows implementer employment when AI does not learn to implement itself. The dial sets κ in η = η₀·e−κθ, where η is the labour needed to implement a task and θ = −ln(price of AI). Implementation supply has unit elasticity. Research Note 003 (Proposition 5) proves the local version of this race: implementation wages stop rising only if the rate at which AI lowers its own implementation cost exceeds a threshold it derives. The full paths drawn here go beyond that result.

When AI does not help implement itself, implementer employment rises steadily as AI gets cheaper. When it helps a little, employment rises at first and then falls back: a boom followed by a bust, while automation keeps advancing throughout. When it helps a lot, the boom never happens. Which world we are in is an empirical question, and an observable one. The signal to watch is not the price of tokens. It is how many person-weeks it takes to put an agent into production, and whether that number is falling faster than the price of AI.

What the argument does and does not show

The results are theorems in a deliberately simple model: identical firms, a fixed wage for production workers, and implementation as a single kind of labour. The figures use stylised parameters chosen to illustrate the mechanism; they are not estimates, and the magnitudes should not be read literally. The facts in Figure 1 are consistent with the model but were not used to test it. The paths in Figure 4 go beyond the paper's proved results, which are local.

What would prove me wrong

The argument would be wrong if large, public cuts in model prices were followed by flat or falling postings and posted wages for implementation roles; if firms automated more tasks after price cuts without hiring or paying more for implementation; or if, at the same size, young firms with little legacy automated no more than old ones. The first test needs posting data with wages, matched to the dates of price cuts.

What follows

For firms, the binding constraint on AI adoption is unlikely to be the model, which anyone can rent, or its price, which keeps falling. It is the capacity to implement: people, internal tooling and processes that make the next workflow cheaper than the last. Firms that build this capacity now are buying the scarce input, not the abundant one.

For workers, the scarce skill is the combination: enough engineering to build the integration, and enough knowledge of the business to know what the agent should and should not do. It is scarce because few people have both. How long it pays depends on how quickly AI learns to do the integration itself.

For researchers, the argument makes a falsifiable prediction. Large cuts in API prices are public, discrete and set by a handful of providers. If the model is right, postings and posted wages for implementation roles should rise in the months after each cut, and by more where such people are hardest to find. If they do not, the argument is wrong.

The usual question is whether AI will replace workers. The more useful one is which workers AI makes more valuable as it gets cheaper. For now, the answer includes the people who put it to work.

Methods and sources

The model, propositions and proofs are in Research Note 003, Abundant Agents, Scarce Organizations: Implementation Capacity and the Economics of AI Adoption, Sections 3–6 and the appendix; results are checked symbolically and numerically in the replication code. Figures 2–4 are computed in the browser from the paper's linear benchmark with illustrative parameters (demand elasticity ε = 2, comparative-advantage slope β = 3, m₀ = 1.2, implementation requirement η = 1); they are not estimates. Figure 4 adds an implementation requirement that falls with model capability; the paper proves the local threshold (Proposition 5), not the full paths shown. Price trends: Epoch AI, “LLM inference prices have fallen rapidly but unequally across tasks” (2025). Forward-deployed engineer postings: Indeed data provided to Business Insider (2026), 643 postings in April 2025 and 5,330 in April 2026; the series counts open postings, a stock rather than a flow of new vacancies. Lightcast data reported by Fortune (2026) show a larger increase over January–August 2026. Neither series measures wages; the paper's prediction is about both. Jevons, The Coal Question (1865).