Tag: Market Signals

  • AI: creating or destroying jobs?

    AI: creating or destroying jobs?

    The AI-jobs argument has split into two camps that aren’t actually arguing about the same thing.

    Jensen Huang told CEOs at GTC that firing people for AI shows “no imagination” — radiologists, he points out, are more numerous now than before AI entered radiology. Marc Andreessen calls the displacement narrative “completely fabricated” and points to Jevons Paradox: cheaper labor produces more demand, not less. The WEF Future of Jobs Report still projects net +78 million jobs globally by 2030. Challenger’s Hiring Plans index was up 157% year-over-year in March.

    A week later, Block laid off 40% of its workforce. Jack Dorsey said engineering work that needed weeks now happens in a fraction of the time. Block is still hiring AI engineers.

    So which is it?

    My read: both sides are right. They’re answering different questions about different decades. Most of the public argument is two conversations pretending to be one.

    The optimist case

    Three pieces hold it up.

    The historical record is strong. Keynes wrote in 1930 that his grandchildren would work fifteen-hour weeks. Reality 2025: OECD average is thirty-seven hours, Americans clock 1,976 hours a year. Mechanization, electrification, the computer, the internet — every general-purpose technology was forecast to end work, and every one produced more jobs than it eliminated. In 1900, 41% of Americans worked in agriculture; today it’s 2%. The jobs went somewhere.

    Jevons Paradox is real. When something useful gets cheaper, demand rises. If AI makes cognitive work twenty times cheaper, you don’t end up with one-twentieth the cognitive work. You end up with twenty times the cognitive work, deployed against far more problems. Andreessen’s “Super-PhD in every field” captures it.

    A big chunk of the labor market is hard to displace. Licensed jobs (medicine, law, accounting), unionized jobs (skilled trades, transit, public safety), and public-sector roles add up to a large fraction of US employment. Not protected because they’re irreplaceable in some technical sense — protected by institutions that move slowly.

    Each piece is correct. The question is whether they’re enough.

    Where the optimist case breaks

    Radar chart of AI capability versus observed usage across eight occupations from the Anthropic Economic Index, showing the deployment gap.
    The deployment gap: theoretical AI capability dwarfs observed usage by occupation. Source: Anthropic Economic Index.

    The Anthropic Economic Index plots theoretical AI capability against observed AI usage by occupation. The two lines look almost nothing alike — capability is broad and high; usage is narrow and concentrated. There’s a gap between what AI can do and what it’s actually doing.

    Read that gap two ways. The optimist reading: deployment is slow, friction is real, the labor market reabsorbs shocks like it always has. The harder reading: the gap is the queue — it’s where displacement comes from over the next five to ten years, not from new capability but from deployment catching up to capability that already exists.

    94% of cognitive job tasks are theoretically automatable today; 33% actually are. The space between is the transition zone. It’s not science fiction. It’s not contested. Most of it will close. Block’s layoffs sit on the second reading.

    The historical-record argument also has a footnote that doesn’t get enough weight. AI is the first general-purpose technology to automate cognitive labor at scale. Every prior wave automated muscle, then narrow categories of cognitive work — but never the universal category of “thinking and writing and analyzing and deciding.” The tractor displaced farm hands; they moved into office work. The PC displaced typewriters and clerks; they moved into knowledge work. AI doesn’t have an obvious “moved into” destination, because the destination of every prior wave is the category AI now automates.

    The TIME / Contextual AI benchmark chart makes the universality vivid. AI surpassed human-level performance on handwriting recognition around 2015, then speech, then images, reading, language, common sense, math, code generation. The rate at which new tasks fall is increasing.

    The trades-and-physical-work counterargument is weaker than it looks. Yes, 57% of jobs depend on physical presence or craft work AI can’t currently replicate. But 70% of positions inside blue-collar companies — the dispatcher, the accountant, the customer-service rep — are white-collar-adjacent and fully exposed. And if displaced knowledge workers all migrate into trades, wages collapse from saturation. Bank of America projects billions of humanoid robots by mid-century with hardware costs falling from $35,000 to under $15,000; one analyst projects robot-hours at four to six euros. Even physical work has an expiration date.

    So the optimist case is strong for a long-run answer. It’s much weaker for the next ten years.

    The displacement case

    Not “AI replaces all jobs.” That’s the optimists’ caricature, and once you reach for it the displacement case looks weak. The serious version is more specific.

    Three vertical bars on dark navy: high-skill rising, middle-skill shrinking with downward arrow, low-skill stable — the AI barbell economy.
    The barbell economy: high-skill productivity rises, low-skill stable, the middle hollows out.

    It’s structural: the middle is being squeezed. The labor market is shifting from a K-shape into a barbell. High-skill technical roles are more productive — the same Anthropic data shows code, analysis, and research at the top of the productivity-gain distribution, with usage approaching 60% of theoretical capacity. Low-skill physical roles in care, hospitality, manual handling, and trades are stable for now. The middle is shrinking: bookkeeping and paralegal work, content writing and copywriting, junior finance and analyst roles, customer service, entry-level coding, marketing copy, translation, project coordination, junior tax preparation.

    Germany has already seen roughly 90,000 AI-related job losses in the first months of 2026. The risk is not mass unemployment in aggregate. Aggregate unemployment can stay low for years while the middle hollows out. The risk is a split labor market — and a split society — in which the people who staffed the middle no longer have a clear path up or sideways.

    The Anthropic Economic Index BLS panel makes this concrete: hiring of younger workers in AI-exposed occupations has slowed, even as overall employment numbers haven’t moved much. That’s what early-stage hollowing looks like — the entry-level rung disappears first, before the established middle does.

    Five years of that compounds into something the historical record didn’t have to absorb.

    My read — the three-phase shape

    Horizontal timeline 2025 to 2040+ split into three colored zones: red displacement, amber strain, cyan abundance — AI jobs transition phases.
    Three phases of the AI jobs transition: displacement (2025-2030), strain (2030-2035), abundance (2035+).

    The clearest three-phase framing is German — chronological, not parallel.

    Phase one — displacement (~2025-2030). AI displaces knowledge work faster than the labor market rebuilds. The middle hollows. Aggregate unemployment may not move much; entry-level paths in white-collar roles narrow sharply. The optimists are right that the technology eventually creates new categories. They’re wrong about the timing.

    Phase two — strain (~2030-2035). Strain shows up in places that aren’t unemployment: tax-base erosion, weakened consumer demand, capital returns rising while labor’s share of national income falls to historic lows. Public-sector and licensed-job cushions hold initially but come under fiscal pressure. The political consequences sharpen.

    Phase three — abundance (after ~2035). The deflation the optimists describe arrives. Costs collapse across categories. What costs $100 today costs a few cents. The median 2040 lifestyle, on a flow-of-services basis, looks something like today’s high-net-worth lifestyle on every dimension except positional goods. Both Andreessen and Huang are right about the destination.

    That’s the timeframe trap. Both sides are correct on their respective horizons. The honest version of the optimist case includes the transition pain. The honest version of the displacement case includes the recovery.

    What this means for how leaders think about the next ten years: the question isn’t “do we believe in AI displacement, yes or no.” That question is roughly answered. The task is to assume real displacement in the middle, plan for it, and carry the organization through to the recovery in a way that keeps the institution and its people whole.

    Three things I’m watching

    1. Whether the entry-level signal becomes a leading indicator. The slowing of hiring for younger workers in AI-exposed occupations is, in my read, the most important early signal. Aggregate employment numbers lag; entry-level absorption leads. If the slowdown becomes a structural break, phase one stops being a forecast and becomes a measurement.
    2. Whether the licensed and public-sector cushion holds when fiscal space tightens. The structural-protection argument is strong only as long as the institutions that protect those jobs don’t themselves come under fiscal pressure. Phase two erodes the tax base. The question is whether legislatures and regulators are protecting genuinely-essential public-sector employment or post-hoc subsidizing the share of the workforce the private sector can no longer place.
    3. Whether the recovery looks like restored employment or restored income. Phase three is consistent with both. Jobs come back in new categories — the historical track record. Or they don’t come back at scale and the recovery is income-shaped: UBI-like distribution of the deflation surplus rather than wage-based participation. These look very different politically. The shape of phase two is what determines which one we get.

    No one has confidence on these three questions yet. I’m watching them because the answers will tell us, in roughly the next five years, what the transition phase actually costs.

    The destination is not in serious doubt. The road is.

  • Inference cost has collapsed. Enterprise AI business cases haven’t caught up.

    Inference cost has collapsed. Enterprise AI business cases haven’t caught up.

    GPT-4 class inference cost $20 per million tokens at launch in early 2023. In April 2026, equivalent performance runs $0.40. Most enterprise AI business cases were built somewhere in the middle — and haven’t been updated since.

    That gap is not a technology story. It is an arithmetic problem wearing a strategy hat.

    What moved

    Inference costs have declined faster than the bandwidth price collapse of the early internet era, faster than PC compute, and considerably faster than any enterprise finance model anticipated. Artificial Analysis tracks it live: the cheapest capable models today run under $0.50 per million tokens. A flagship model that cost $10 per million tokens eighteen months ago now costs $2–3. The price range between the cheapest and most expensive capable options has widened past a thousand-to-one.

    The driver is compounding. Better training efficiency produced more capable models at lower operating cost. Competition between providers accelerated the pass-through. Specialised chips entered the stack. The result: a cost curve that looks less like traditional software pricing and more like solar panel economics — each year’s curve is below where last year’s curve said it would be.

    What did not move

    Enterprise AI business cases.

    S&P Global found that 42% of companies abandoned most of their AI projects in 2025. Cost and unclear value were the top reasons cited. IBM put the share of AI initiatives delivering expected ROI at 25%. MIT found that 95% of AI pilots delivered zero measurable P&L impact (MIT NANDA, State of AI in Business, 2025).

    These numbers are real. But the interpretation of why projects fail is often imprecise.

    Projects approved in 2023 and 2024 were scoped against the pricing environment of 2023 and 2024. The cost models that informed the go/no-go decisions used token prices that no longer exist. The ROI denominators were anchored to infrastructure assumptions from a period when GPT-4 access cost $10–20 per million tokens. The business cases that were rejected on cost grounds — the ones that landed below the internal ROI hurdle by a thin margin — were rejected against a cost basis that is now a fraction of what it was.

    That is not a technology failure. It is a modeling lag.

    Andreas’s view

    My read on this: there are two different things getting conflated in the ROI conversation. One is genuinely poor outcomes — wrong use case, shallow integration, insufficient change management. That is real and deserves scrutiny. The other is a systematic understatement of AI’s economic potential because the cost assumptions in the business case never got refreshed. Those two phenomena look identical in the data.

    I don’t think the 42% abandonment rate or the 25% ROI hit rate tells us much about what AI can do at today’s prices. It tells us how enterprises perform against business cases built on 2023 assumptions. The projects that got killed for cost reasons in Q4 2024 would look different rerun against Q2 2026 pricing.

    My expectation is that the organisations getting ahead of this are running a specific exercise that most are not: taking the cost assumptions out of every AI initiative that was rejected or stalled in 2023–2025, replacing them with current market rates, and seeing which cases cross the ROI threshold now. Not all of them will. But some will — and the decision to revisit them is a spreadsheet exercise, not a technology project.

    Three things I’m watching:

    • Whether finance teams are treating inference cost as a stable input or a variable. Most enterprise budget models treat infrastructure cost as a constant. Inference cost is not a constant — it has been declining faster than almost any other enterprise input cost in the last three years.
    • The spread between unit cost and total spend. Per-token costs have collapsed, but total enterprise AI spend is forecast to jump 65% in 2026 — from roughly $7M average to over $11M (IDC). Volume is expanding faster than unit costs are falling. The budget impact of AI is still growing, even as the underlying unit economics are dramatically more favourable than they were.
    • How capital allocation committees handle the remodel request. The institutional question: if a CFO approved a 2023 AI business case that underperformed, how does the organisation handle finance coming back and saying “the cost structure changed — the case should have worked, we just used the wrong numbers”? That conversation is coming.

    What this reveals

    The collapse in inference cost is well-understood in developer circles. Engineers who run inference workloads reset their unit economics continuously — it is operational reality. The delay is in the enterprise business case layer, where cost assumptions travel up through approval chains, get embedded in multi-year plans, and calcify.

    The cost curve does not care about the approval cycle. It moved while the slide decks were in review.

    This is not an argument that all AI investments look better at current pricing — some of those failed pilots would have failed regardless, and the organisational conditions for AI success (clear scope, embedded workflows, meaningful accountability) have not gotten easier. But a non-trivial fraction of the projects that stalled on cost now live in territory where the math is different. Identifying them is a shorter path to AI ROI than starting new initiatives from scratch.

  • Vertical AI is winning the deployment race

    Vertical AI is winning the deployment race

    Horizontal AI slab at the bottom with three taller vertical columns rising from it labeled by domain
    Horizontal is the substrate. Vertical is the value layer.

    Gartner’s April read says eighty percent of enterprises will have adopted at least one vertical AI agent by year-end, and thirty percent of all enterprise AI deployments will be vertical-specific. Bessemer’s vertical AI report from this month is even more direct: vertical AI companies founded after 2019 are reaching eighty percent of traditional SaaS contract values while growing four hundred percent year-over-year. This is not a minor adjustment to the deployment landscape. It is a structural redirection of where the value of agentic AI accrues.

    For boards in 2026, the implication is that the right framework for thinking about AI vendor strategy is no longer horizontal-versus-vertical. It is which verticals you bet on, and how early. Deployment speed defines advantage in this cycle, and the deployment race is now a vertical-by-vertical race.

    The shift: vertical specialization beats horizontal generality at the workflow layer

    Horizontal AI tools — the chat assistants, the general-purpose copilots, the broad productivity overlays — are still the largest category by usage. They are not the largest category by enterprise value. The reason is structural. A horizontal copilot is good at fifty things. A vertical agent is excellent at five things that are deeply embedded in a specific workflow.

    When the enterprise needs to extract value, depth wins over breadth. Abridge in clinical documentation. Harvey and EvenUp in legal. Hebbia in financial research. Specialized clinical-coding agents at major payers. The vertical players ship integrations into existing systems, understand the regulatory and accuracy constraints of the domain, and deliver outcomes that horizontal tools cannot match without significant configuration effort that customers refuse to undertake.

    The defensibility of vertical players is also higher than the market priced in 2024. The data flywheel inside a regulated vertical is genuinely hard to replicate. The customer relationships are stickier because switching costs include re-credentialing within the regulator’s expectations, not just re-implementing software.

    Two rectangle shapes side by side, one wide and shallow, the other narrow and deep
    Wide-shallow loses to narrow-deep at the workflow level.

    The role change is the chief AI buyer becomes a portfolio manager

    Inside enterprises, the executive responsible for AI vendor strategy is increasingly running a portfolio of vertical specialists alongside the foundation-model contracts. The horizontal tools form a substrate. The vertical agents form the high-value layer. The portfolio manager has to balance ROI realization against integration overhead, and has to decide which verticals to deepen versus which to defer.

    The skill set for this role is closer to portfolio investment management than to traditional procurement or IT leadership. The portfolio manager has to read product roadmaps, anticipate vendor consolidation, manage concentration risk, and time entry into emerging verticals where category leaders have not yet emerged. None of this is in the standard procurement or CIO playbook.

    Most large enterprises have not formally structured this role yet. The work is happening inside the CIO function or inside individual line-of-business AI initiatives, with no portfolio-level coordination. The result is double-procurement of overlapping vertical capability and missed early-mover advantage in verticals where the category leader will not stay reasonably priced for long.

    The strategic consequence reshapes acquisition strategy

    For enterprises in regulated industries — banks, insurers, hospital systems, large law firms, accounting firms — the vertical-AI thesis has a direct M&A implication. The category leaders in each vertical are trading at premium multiples now and will trade at higher multiples by 2027 once their data flywheels and customer concentrations are visible in audited financials. The window for acquisition at reasonable multiples is open in 2026 for most verticals. It will close.

    For incumbents who do not acquire, the implication is partnership at scale. The vertical specialists need distribution that incumbents already have. The incumbents need capability that the specialists already have. The deal terms will tilt toward the specialists as their growth rates remain visible. Incumbents that delay partnership decisions to 2027 will pay more for less favorable terms.

    For boards governing AI strategy, the directive question is whether the company is buying or building or partnering for vertical AI capability — and whether that decision is being made deliberately for each vertical, or by default by the absence of a decision. Default-by-absence is the mode most large enterprises are operating in. It is the most expensive mode.

    Four labeled doors in a corporate hallway with one chosen and three closed
    Per vertical: buy, partner, build, or wait — pick deliberately.

    So what boards should do this quarter

    Map the AI vendor portfolio with horizontal versus vertical breakdown. If the breakdown is more than two-thirds horizontal, the company is missing the value-creating layer. If it is unmapped, that is a more urgent finding.

    Designate an executive owner for vertical AI portfolio strategy with explicit authority across line-of-business silos. The decisions are too consequential to be made silo by silo. The horizontal-tool decisions can stay with the CIO. The vertical-agent decisions need a portfolio view.

    For each major vertical relevant to the business, assign a clear posture: acquire, partner, build, or wait. Defaulting to wait by not deciding is the same as deciding to wait — and in most verticals it is the wrong decision in 2026. Execution speed will separate leaders from followers in this cycle.