The best returns will come from changing the workflow
EM outlook ·
Through 2027, we expect focused deployments to earn their keep before blanket rollouts do. Customer-support evidence shows a useful mechanism: assistance can raise completed work and help novices improve. shows the competing cost as attention shifts toward agents. The winning deployment converts that capability into a recurring outcome someone values.
What this means
Fund a workflow with a buyer, a baseline and a recurring payoff. Count quality, new capacity and service improvements as well as hours saved; count integration, review and ongoing operating costs against them.
Why we take this view
The next operating year should favor deployments built around measurable existing work. Broad rollout requires more coordination and training before benefits reach the same decision-maker who bears the cost.
What has to hold
The organization uses the extra capacity or better result; output with no demand has little economic value.
The comparison includes rollout costs, repeat operating costs and work shifted to another team.
The strongest rival
Broad access produces valuable experimentation and new capabilities that narrowly specified projects would miss.
Implementation and review costs absorb the operating gains, leaving even well-liked tools below their full cost.
What would change our mind
Repeat-use evidence shows accepted outcomes improving after integration, review, training and operating costs are included.
The apparent gain disappears when transferred work, delayed defects or unused capacity are counted.
Test full recurring deployment costs against accepted outcomes, beyond task productivity and self-reported value.
Where this could lead
A focused workflow pays for its AI
Base case ·
The buyer gets a recurring improvement worth more than implementation and operating costs: faster service, better quality or capacity that would otherwise be unavailable.
What would make it happen
We expect the clearest near-term returns where a deployment improves work with an existing buyer and an observable outcome.
Conditions
The improved result has actual demand or avoids an actual cost.
Savings or new value survive integration, review, training and repeat operation.
The buyer chooses what the extra capacity is for: better service, a previously neglected need, or work the team could not afford to attempt.
Watch for
The buyer keeps funding the workflow after measuring its full costs.
Accepted outcomes improve over repeated use without shifting an unpaid burden to another team.
People enjoy the assistance, but the organization cannot turn it into enough useful extra work or better service. Integration and review absorb the benefits, and broad rollout loses its case.
What would make it happen
The first renewal and operating cycles can expose costs that a demonstration or initial enthusiasm misses; persistence into 2028 would weaken the focused-deployment thesis.
Conditions
Output grows faster than demand for it, or the gain does not reach the budget that pays for the system.
Integration, quality loss or ongoing supervision costs more than the usable benefit.
Watch for
Usage remains high while completed outcomes and customer value stay flat.
Renewals shrink after the buyer includes costs previously omitted from the business case.
Why this connects to When is an AI deployment worth its total cost?
EM interpretation
Accepted work is where capability becomes economic value. A slower process can still pay if it produces something better or previously impossible; a faster draft can lose money if nobody needs it or finishing it costs too much.
The buyer’s gain and the supplier’s investment return are separate calculations.
A positive deployment return does not specify whether employment expands or contracts.
Perspectives
Joel Becker
author reporting technical-worker self-assessments · 2026-05-11 · From the author’s own work
The survey reports substantial perceived value gains, while distinguishing value from task speed and cautioning that respondents can misestimate what AI contributes.
Sources and passages
Publication date of the authored source.
Self-report in a technical-worker sample, not audited customer economics or a measured effect on national productivity.
Valuation scholar writing on his personal blog · 2026-08-20 · From the author’s own work
Damodaran argues that AI investment should be examined through the business outcomes required to justify its price or capital cost. Different assumptions about markets, margins and reinvestment can produce different valuations; technological plausibility does not guarantee an investment outcome.
Sources and passages
Original publication date; the source preface records two updates on 21 August 2026.
A proposed valuation framework, not a comprehensive independent audit of AI companies.
The retained article records updates after its original publication; its numerical examples are not adopted as EM estimates.
Publisher publication date, checked on original page.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
This acceleration makes human attention the bottleneck for agent output.
Retained extracted text, character offsets [767, 839). Context (EM paraphrase): The authors report rising internal output alongside agent use and interpret human attention as a constraint. Adoption is not randomized; the report does not establish a general causal productivity effect.
Publication date displayed by the original publisher.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
16 experienced developers
Retained extracted text, character offsets [1527, 1552). Context (EM paraphrase): Methods: developers worked on 246 real issues in familiar open-source repositories using early-2025 tools. This population does not represent all developers or later systems.
they take 19% longer to complete issues
Retained extracted text, character offsets [2468, 2507). Context (EM paraphrase): Core Result, first paragraph; interpret with Methods and the immediately following limitations table. Reported result for the 2025 study, not a current universal estimate.
Publication date displayed by the original publisher.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
the data from our new experiment gives us an unreliable signal of the current productivity effect of AI tools
Retained extracted text, character offsets [431, 540). Context (EM paraphrase): Opening discussion, paragraph beginning Unfortunately. Subsequent paragraphs describe participation, task selection and time measurement.
Publication date displayed by the original publisher.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
Participants self-reported a median 1.4–2x change in the value in their work due to AI tools.
Retained extracted text, character offsets [1308, 1401). Context (EM paraphrase): METR surveyed 349 technical workers in February–April 2026. The range reflects self-reported value under different question formulations, not a confidence interval or observed causal return. METR gives reasons to doubt the magnitude and distinguishes value from speed.
Original publication date retained in source metadata; later source edits remain part of the exact cited snapshot.
Full retained article body reviewed; public display uses a short excerpt and attributed interpretation. Underlying numerical claims and linked evidence are not independently verified by inclusion.
Exact work/snapshot and SHA256 verified in the 29 October SELECT-only corpus packet; full private source text is not republished.
there will be room for significant disagreement on the reach of AI and its value as a business
Retained extracted text, character offsets [53311, 53405). Context (EM paraphrase): Damodaran proposes testing what future revenues, margins and reinvestment would justify AI company prices and capital spending. The original post is dated 20 August 2026; its retained preface records two 21 August updates. This is an analytical framework, not proof that a price or industry-wide bubble verdict is correct.
Version 2 submission date displayed by ; first submitted 23 April 2023. The versioned abstract is the cited object.
Versioned author abstract checked directly. The HTML rendering displayed a conflicting 2026 manuscript date, so this edition cites only the clearly versioned abstract and does not assign that later date to the study.
Original public source read on 30 October 2026. An exact retained Stream identity has not been resolved for this edition.
by 15\% on average
Version 2 abstract, second sentence. EM context: staggered introduction among 5,172 customer-support agents; the outcome is issues resolved per hour, not company profit.
Less experienced and lower-skilled workers improve both the speed and quality of their output
Version 2 abstract, third sentence. EM context: benefits differ by experience; the most experienced workers show small speed gains and small quality declines.
Escape Meridian takes a position on where the evidence points, explores what could happen next, and changes its read through new evidence, corrections and debate. The outlooks are our judgments; the sources retain their own voices.
About this edition
EM outlooks authored 30 October 2026 from the retained 29 October source review, supplemented by five original public sources checked on 30 October. Employment evidence centers on US workers and selected workplaces; capability evidence centers on software tasks. Outlook dates express EM judgments about the stated outcomes, not dates forecast by the cited authors. Source publication, access and evidence-review dates remain distinct.
