Andreas Timm

Tag: technology bets

  • Every knowledge worker is a manager now

    Every knowledge worker is a manager now

    Every knowledge worker is a manager now. Agentic AI has turned individual contributors into managers of AI agents, and first-line managers into leaders of managers of agents. The job descriptions have not caught up yet. The operating models have not caught up yet. The reskilling plans have not caught up yet. All of that is lagging the capability frontier by twelve to eighteen months — and the organizations that close that gap first will operate at a structurally different throughput than the ones still writing job descriptions for the jobs that existed in 2023.

    The shift: agentic AI crosses the line from tool to colleague

    For the first year and a half after ChatGPT, the thing called “AI” in most organizations was a better search box. A more patient editor. A faster rough-draft generator. Useful, but still a single-interaction tool. You asked, it answered, you moved on. The job of the knowledge worker did not fundamentally change — they just had a slightly sharper pencil.

    What changed in the eighteen months leading into 2026 is the arrival of agentic models. The word “agent” in that context is not marketing. An agent is a system that can do a sequence of things, hold state across those steps, make decisions about what to do next, use tools, and come back with a completed multi-step task. That is a categorically different interaction than “ask question, get answer.” It is closer to “give a junior colleague an outcome to produce and trust them to produce it.” The commercial consequence of that shift is the subject of this post.

    Knowledge-worker image candidate K02-HC-pipeline: HC2 — INPUT-AGENT-OUTPUT-JUDGE-SHIP pipeline with human at JUDGE
    Input → agent → output → judge → ship. The human stays at the judgment node.

    The role change: ICs become managers of agents

    The individual contributor job has silently changed. Writing short summaries of long content — once a junior-to-mid task — is now an agent task. The human role is to specify the outcome, check the output, and decide what to do with it. Meeting preparation — the pre-meeting brief of background, context, attendees, prior touchpoints — is now an agent task. The human role is to feed the context, review the brief, and adjust the framing. Drafting a first pass of almost any structured document — a proposal, a plan, an analysis — is now an agent task. The human role is the editor, not the author of the first draft.

    The common thread is that the IC’s job has shifted from doing to specifying outcomes and judging output. Those are management skills. Not in the metaphorical sense — in the literal sense. Framing a task clearly enough that someone (or something) else can execute it. Evaluating whether the execution meets the specification. Deciding when to iterate and when to ship. These are exactly the skills that used to distinguish a first-line manager from a senior IC, and they have become baseline requirements for an IC working with agents.

    Knowledge-worker image candidate K03-HC-editor: HC3 — colleagues editing agent outputs + overlay text
    The new role for the IC: editor of agent output.

    The org change: first-line managers become leaders of managers of agents

    If every IC is now a manager of agents, then every first-line manager is now a leader of managers of agents. Their job is no longer to supervise execution — the agent is doing the execution. Their job is to coach the humans on their team in how to specify outcomes, how to judge output, how to know when an agent is producing garbage, and how to scale their orchestration over time. That is a completely different job than the first-line management job of three years ago, and it requires a different skill set.

    Two structural consequences follow. First, the middle management layer compresses because a first-line manager leading managers-of-agents can reach further than one managing direct executors — the coordination overhead per report drops when the reports are themselves operating on a multiplier. Second, the definition of “span of control” stretches, but not infinitely: the Dunbar layers still govern the number of humans a manager can hold relationships with, even if each of those humans is now operating agents underneath them. The org chart can get flatter. It cannot get unbounded.

    Knowledge-worker image candidate K05-WILD-conductor: WILD — human conductor directs an orchestra of AI agents
    One human, many agents — the conductor metaphor for first-line management at scale.

    The strategic consequence: orchestration is now a baseline skill, not an advanced one

    The skill that used to distinguish senior managers from junior ones — the ability to frame work so someone else can execute it and judge whether their execution is good — is now a baseline IC capability. Orchestration is the new baseline. Writing is the new baseline. Judgment about output quality is the new baseline. The organizations that will operate at structurally higher throughput over the next five years are the ones that reskill their IC population around these baseline orchestration skills, rather than hiring more specialists who each do one thing well.

    Talent leverage, not headcount, becomes the scoreboard. A commercial organization that operates at 300 humans with strong orchestration capability can outproduce a commercial organization that operates at 600 humans with legacy IC job descriptions. The difference is not about working harder. It is about operating model. The 300-human organization has fewer Dunbar breakpoints, shorter decision loops, less cross-functional friction, and a higher per-seat agent-multiplier. All of that is the consequence of a single structural decision made at the job-description layer.

    So what boards should do

    Three actions sit on the CEO agenda over the next two quarters. First, rewrite the IC job descriptions for every knowledge-worker role in the organization so that orchestration and output judgment are explicit baseline capabilities, not bonus ones. Second, rewrite the first-line management job description so that coaching for orchestration is the core of the role, not supervision of execution. Third, audit the reskilling plan against the assumption that every knowledge worker in the organization is now a manager and needs to be trained as one — because the capability frontier has already shipped and the only question is whether the organization catches up in quarters or in years.

    Boards that do not require a reskilling plan at this scope are budgeting against an operating model that does not exist anymore. The plan does not need to be perfect. It needs to exist. The gap between organizations that have this plan and organizations that do not is the structural competitive advantage of the next five years, and it is already being measured — in throughput, in decision velocity, in the quiet retention of the top performers who can see the gap coming.

  • 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.

  • Model deprecation is the new continuity risk

    Model deprecation is the new continuity risk

    Four rectangles in a row with the leftmost ghosted, simple connecting arrows
    A — model lifecycle row.

    OpenAI announced the discontinuation of the Sora web and app experiences on April 26, with the Sora API following on September 24. The first deprecation triggers in two weeks. Enterprises that built workflows on Sora since launch are not facing a model upgrade — they are facing a workflow rebuild on a four-month timeline. This is the first prominent enterprise-facing AI deprecation event of the cycle, and the precedent it sets matters more than the specific product involved.

    Model deprecation is no longer a developer-tier concern. It is an enterprise governance question that deserves a place on the risk committee agenda. The real shift is happening here: AI dependency without continuity is becoming a board-level risk in 2026.

    The shift: dependency without continuity guarantees

    The pattern of the past two years has been to build agent workflows on whichever foundation model was demonstrably best at the time, with little contractual commitment from the model provider about how long that model would remain available. Provider terms have improved — Azure OpenAI’s twelve-plus-six-month commitment for generally available models is the strongest standard in market — but most enterprises have not negotiated equivalent terms with their chosen providers. They built on capability, not on continuity.

    When the provider sunsets the model, the enterprise’s options are bad. Migrate to a successor model that may behave differently in subtle ways — requiring re-validation of every governed use case. Renegotiate at the eleventh hour for extended access at unfavorable terms. Or absorb the operational disruption of the workflow simply not working until rebuilt.

    The Sora event is small in dollar terms but large in precedent. The next deprecation will involve a more enterprise-critical model, and the enterprises that did not see this one coming are not going to see that one coming either.

    A single thread connecting a workflow box to a model box, the thread visibly fraying near the model with a clock above
    Built on capability. Not on continuity.

    The role change is the addition of an AI continuity discipline

    Inside enterprises that take this seriously, a discipline is emerging that did not exist in 2024 — AI continuity management. The work overlaps with vendor management, with disaster recovery, with model risk management, and with regulatory compliance, but it is structurally distinct from all of them. The discipline involves maintaining an inventory of model dependencies by workflow, negotiating continuity commitments at procurement, running successor-model regression tests on a regular cadence, and ensuring that the documentation chain meets the rebuild-readiness standard.

    Most enterprises have not staffed this discipline. The accountabilities are scattered across teams that do not coordinate. The procurement team negotiated the model contract a year ago without a continuity clause. The deployment team is building production dependencies on the model without thinking about migration cost. The risk team has not flagged model deprecation as a category. When the deprecation announcement lands, the company finds out it has no plan.

    The fix is straightforward in concept and slow in practice. Add continuity commitments to the procurement template. Build a model-dependency inventory. Designate an owner for AI continuity at the executive level. Run quarterly successor-model tests. None of this is hard. It is just unglamorous work that does not get done unless someone owns it.

    The strategic consequence is renewed buy-versus-build math

    Continuity risk changes the calculus of where to deploy AI capability. For workflows where the cost of unplanned migration is high — regulated workflows, mission-critical operations, customer-facing experiences with high switching costs — the case for either fine-tuning a frontier model into a controlled deployment, partnering with a vendor offering enterprise-grade continuity commitments, or building on open-weight models the enterprise can host indefinitely is stronger than it was in 2024. The case for relying on whichever model is best on a benchmark this quarter is weaker.

    The math is not simple. Open-weight models lag the frontier, sometimes meaningfully. Self-hosting carries operational cost that the proprietary providers absorb. The vendor lock-in to a single proprietary provider, even with the best continuity terms, is a different kind of risk than open-weight self-hosting carries. Each enterprise has to make this trade-off based on the workflow’s tolerance for capability lag versus its tolerance for continuity disruption.

    What is no longer defensible in 2026 is treating model continuity as someone else’s problem. The Sora sunset is small. The next one will not be.

    So what boards should do this quarter

    Add model deprecation to the risk committee agenda. The first deprecation event lands in two weeks. The board should at minimum understand which workflows are exposed and what the migration plans are.

    Demand a model-dependency inventory. Which workflows depend on which models from which providers, with which contractual continuity commitments. If this inventory does not exist, building it is the priority.

    Reconsider the buy-versus-build posture for mission-critical AI workflows. The 2024 default — use whichever proprietary model is best — was rational at the time. In 2026, with the deprecation precedent now visible, that default deserves an explicit reconsideration. Continuity is becoming a form of resilience. The boards that price it in this quarter will not be the ones rebuilding workflows under deadline.

    References and links

  • 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.

  • What 47 unicorns in one quarter actually means

    What 47 unicorns in one quarter actually means

    What was announced

    In Q1 2026, 47 startups crossed the billion-dollar valuation threshold for the first time — the largest single-quarter cohort in over three years. The pace is concentrated at the seed and early-stage end. Global venture funding hit roughly $300 billion in the quarter, of which 80% — about $242 billion — flowed to AI companies. Four companies (OpenAI, Anthropic, xAI, Waymo) absorbed 65% of all capital deployed.

    Funnel diagram: $300B total venture funding to $242B AI to $188B captured by OpenAI Anthropic xAI Waymo.
    Q1 2026 venture funding — concentration at the top.

    What it means

    Two things become visible at the same time. First, the market is willing to underwrite billion-dollar valuations earlier in the company lifecycle than at any point since the late-2020 boom. The valuation framework is no longer derived from realized revenue. It is derived from deployed compute and team density. Second, capital concentration at the top has reached a level where four companies define the cost of capital for everyone else. A new AI startup raising in 2026 is competing for the same dollars that just priced OpenAI at $122 billion.

    The early-stage explosion and the late-stage concentration are two symptoms of the same conviction: capital has decided that AI is a winner-take-most market, and it is funding accordingly.

    Andreas’s Take

    My read on this: the unicorn count is a lagging indicator of a much earlier decision. That decision was made — quietly, by capital allocators — when the consensus shifted to a single conviction: AI capability gaps will widen, not narrow, over the next decade. From that conviction two strategies follow logically: fund the few names that might dominate the frontier (concentration), and over-fund the early stage so that whatever the next breakthrough looks like, you own a piece of it (proliferation). The 47 new unicorns are the proliferation half.

    I don’t think this is a bubble in the conventional sense. A bubble is a price disconnect from fundamentals. What we’re seeing is a price connection to a forecast about fundamentals. If the forecast is right — capability gaps widen, AI returns accrue disproportionately to a few players — today’s valuations are conservative. If it’s wrong, half of these unicorns will not survive their next priced round.

    What I’d say to boards and CFOs reading these numbers: don’t take comfort from “the market is hot.” Take instruction. Capital is signaling where it expects the next moat to form. The companies absorbing the capital are absorbing optionality, not just dollars.

    Iceberg metaphor: 4 big company circles above water, 47 small dots submerged below as optionality.
    Above the waterline: $188B. Below: optionality.

    Recommendation

    Three things for leaders watching this market:

    1. Treat unicorn-count reports as competitive intelligence, not social proof. Look at which unicorns and what they are building — that is the signal of where the market expects gaps to open.
    2. Reassess your own compute and talent allocation against the new benchmark. If AI startups can attract billion-dollar valuations on team and compute alone, your incumbent organization is competing for the same talent at a different cost basis.
    3. Stress-test your strategic plan against a scenario where capability concentration plays out. What does your business look like if three or four frontier labs control the compute infrastructure and all serious AI deployment runs through them?

    References and related signals

  • MCP became infrastructure and Apple decided to rent cognition

    MCP became infrastructure and Apple decided to rent cognition

    What was announced

    Two announcements in the week of March 2–8, 2026 redrew the agent landscape. Anthropic’s Model Context Protocol crossed 97 million installs, with every major AI provider now shipping MCP-compatible tooling — moving the protocol from experiment to default infrastructure for tool-calling agents. Apple confirmed that the redesigned, AI-powered Siri targeted for release alongside iOS 26.4 will be powered by Google’s Gemini model running on Apple’s Private Cloud Compute. In parallel, Anthropic rolled out memory features to all Claude users and deployed Opus 4.6 as an add-in inside Microsoft PowerPoint and Excel.

    What it means

    The MCP install count makes the connectivity layer between agents and tools a solved problem at the standards level. That is a meaningful shift. For two years, the friction in shipping agents was that every tool integration was bespoke; the integration debt scaled linearly with the number of tools and the number of agents. With MCP at default-infrastructure scale, the integration cost is closer to fixed than linear, and the bottleneck moves from connectivity to orchestration and governance.

    Apple’s decision to rent cognition from Google for Siri is the more strategically loaded story. It signals that even the most vertically integrated consumer-tech company in the world has concluded that building competitive frontier-model capability inside the company is not the right capital allocation. The Private Cloud Compute envelope handles the data-sovereignty argument. The Gemini choice handles the capability argument. The combination is an explicit acknowledgment that frontier-model capability has consolidated at a tier of providers most companies will rent from, not build alongside.

    Andreas’s view

    My read on this: the agent stack is settling into a recognizable shape. Standards layer (MCP, becoming generic). Frontier-model layer (a small number of providers — OpenAI, Anthropic, Google, with regional players underneath). Application layer (where most enterprise value is created). The interesting strategic action for the next 24 months is in the application layer, where the questions are which workflows to embed, which data to expose, and which orchestration logic to own.

    I don’t think Apple’s choice is anomalous. It is the start of a wave. Companies that have been building internal frontier-model capabilities will increasingly find that the math does not work — the capex is consumer-internet scale, the talent is concentrated at three or four employers, and the capability gap to “good enough internal model” widens every six months. The economically rational answer for almost everyone is: rent the cognition, own the integration and the data envelope around it. Apple has now made that a defensible board-level position.

    The way I see it: the most important architectural question right now is whether the cognition layer (rented, frontier-model, expensive but improving exponentially) is clearly distinguished from the integration layer (owned, workflow-specific, where the moat actually lives). Where those layers are blurred, I’d expect companies to find themselves overpaying on one side and under-investing on the other. The Apple-Google deal is the clean reference architecture for how that separation can look.

    Three things I’m watching

    Three things I’m watching as this plays out:

    1. I’ll be watching whether companies architect the cognition layer and the integration layer separately — treating frontier-model providers as utilities while building proprietary infrastructure around workflow integration and the data envelope.
    2. The companies that preserve optionality will be the ones that default to MCP-compatible tooling for new agent integrations. The standards layer is no longer a strategic differentiator — the question is how quickly organizations stop treating it as one.
    3. I’ll be watching how internal frontier-model build efforts hold up against the Apple-Gemini reference case. Where differentiation rests on owning the model, I’m interested to see whether those bets come with a credible 36-month capex and capability projection — and what happens when they don’t.

    References and related signals

    • Crescendo AI: latest AI news and developments
    • Related signal: Anthropic’s Opus 4.6 PowerPoint and Excel integrations move frontier-model capability deeper into the enterprise default tooling, accelerating the rented-cognition pattern.
    • Related signal: NVIDIA GTC 2026 (March) emphasized agentic frameworks and Fortune 500 production deployments — the application layer is where the next wave of enterprise AI value is being created.
    • Related signal: 95% of generative AI pilots still fail to reach production. The connectivity layer being solved does not solve the operating-model layer.
    • Related signal: Apple choosing Gemini over OpenAI for Siri changes the competitive math for every enterprise still scoping a frontier-model partnership.
  • AI is becoming the narrative for layoffs. It is not yet the cause.

    AI is becoming the narrative for layoffs. It is not yet the cause.

    What was announced

    Through the week of February 16–22, 2026, the AI-cited layoff story moved from edge case to mainstream framing. AI was cited as the rationale for 4,680 February job cuts in the U.S. — roughly 10% of the month’s total. Baker McKenzie announced 600–1,000 layoffs (up to 10% of global headcount) framed as a pivot to AI-augmented service delivery. Dow disclosed 4,500 cuts in January with explicit AI-strategy framing. A Harvard Business Review piece in the same window argued that companies are laying off based on AI’s potential, not its measured performance. An Oxford Economics report from January concluded that many AI-cited layoffs were the consequence of past overhiring, not present AI productivity.

    What it means

    Two things are happening at once. First, AI productivity is real for specific workflows and starting to show up in unit-cost reductions. Second, “AI” is becoming the public-facing rationale for cost actions that boards and CEOs have wanted to take for other reasons — overhiring during 2021–2022, deteriorating margins in slower-growth segments, restructuring to a target operating model that was already in motion. The two stories overlap, and the public communication does not distinguish between them.

    For employees, the framing matters because “we are restructuring” and “AI is replacing your role” carry different signals about whether the function comes back. For investors, it matters because the market is pricing AI-cited cost reductions as durable while restructuring-cited cost reductions are typically priced as one-off. CEOs who choose the AI framing get a multiple uplift. That incentive structure tells you why the framing is becoming dominant.

    Andreas’s view

    My read on this: the next 12 months will see a steady drift toward AI-as-explanation in layoff communications, regardless of whether AI is the underlying driver. The reason is not deception — it is signaling. CEOs need a forward-looking story that the cost base will stay reduced, and “AI productivity” is a cleaner story than “we hired too aggressively in 2022.” The public record will eventually reconcile this; quarterly earnings will reveal which companies actually shipped the productivity gain and which simply downsized.

    I don’t think the workforce numbers are yet the right metric to watch. The right metric is the ratio of revenue per employee in the months after the cut. If revenue per employee climbs durably, the AI framing was substantively correct. If it plateaus or reverses while operational quality declines, the framing was a positioning move and the company will be hiring back inside 18 months — at higher cost and lower morale.

    The way I see it: when a CEO presents an AI-cited workforce action, the productivity model behind it should be specific enough to name which workflows, which output measures, which time horizon, and which control group. Where those answers are vague, the action is restructuring with AI vocabulary. That is not necessarily wrong, but the distinction matters — and I think it matters most at the board level, where the conversation should reflect what is actually driving the decision.

    Three things I’m watching

    Three things I’m watching as this plays out:

    1. I’ll be watching whether companies maintain a clear internal distinction between AI-driven productivity actions (with a workflow-level model behind them) and AI-framed restructuring actions (justified by other reasons). Both can be valid; conflating them confuses execution, and the ones that keep the distinction clean are more likely to deliver what they promised.
    2. The companies that track revenue per employee monthly for the 12 months following any AI-cited workforce reduction will have the clearest view of whether the productivity gain actually materialized — and I’ll be looking at that number as the most honest signal in the public record.
    3. I’ll be watching how specific companies get in their external communication around AI-related workforce changes. Vague “AI is making us more productive” framing tends to erode credibility internally faster than a precise statement of which work has been automated and which has been redesigned — and over the next year, that credibility gap will start showing up in retention and hiring data.

    References and related signals

  • Davos 2026 made AI sovereignty the policy line — and the corporate one

    Davos 2026 made AI sovereignty the policy line — and the corporate one

    What was announced

    The World Economic Forum 2026 met in Davos January 19–23 with AI as the dominant agenda item. The conversation converged on three themes: risk-proportionate governance, runtime governance for multi-agent systems, and what Microsoft CEO Satya Nadella framed as “corporate AI sovereignty” — firms owning the intelligence layer that encodes their distinctive capabilities. Anthropic CEO Dario Amodei warned the forum that frontier AI is uniquely well-suited to autocracy, calling for targeted chip-export controls. A WEF press release on the same week reported leading organizations are shifting from “potential” to “performance” — measuring AI by realized output rather than pilot count.

    What it means

    The vocabulary shift is the substantive event. For two years, AI policy discussion at this forum was framed as risk management — what to restrict, what to monitor, what to ban. The 2026 framing is different. It treats AI as critical infrastructure where the governance question is who owns it, not whether it should exist. “Sovereignty” applied to AI is a deliberate echo of “data sovereignty” — a recognition that the layer of intelligence inside an organization is becoming as load-bearing as its data layer was a decade ago.

    For governments, this redirects policy from rule-writing to capability-building: domestic compute, domestic foundation models, controlled exports. For corporations, it redirects strategy from procurement to capability ownership: which models do you fine-tune yourself, which workflows encode your tacit knowledge, and which partners do you let inside the trust boundary. Both translations point to the same architectural question: where does the irreducible cognitive core of your organization live, and who can take it from you.

    Andreas’s view

    My read on this: Davos is a leading indicator of where C-suite vocabulary moves over the next 12 months. “Corporate AI sovereignty” is not a slogan — it is a framing that makes specific decisions easier to defend in a board meeting. Building your own model fine-tunes is sovereignty. Choosing not to send your customer interactions through a third-party model API is sovereignty. Maintaining a private inference cluster is sovereignty. The vocabulary justifies budgets that previously read as duplicative or paranoid.

    I don’t think the sovereignty framing is purely defensive. There is a competitive argument inside it: organizations that operate as pure consumers of frontier models are paying rent on the cognitive layer of their own business. Organizations that operate as owner-operators of a fine-tuned, workflow-embedded intelligence layer pay less rent and accumulate a moat that compounds with their data. The Davos talking points are starting to reflect that distinction.

    The way I see it, the question that matters this quarter is not “what is our AI strategy” but “what would it take to lose access to our primary model provider, and what would happen to the business if we did.” If the answer is catastrophic, the sovereignty argument is operational, not philosophical, and it has a budget implication.

    Three things I’m watching

    1. I’ll be watching whether companies run model-dependency stress tests — simulating the operational impact of losing their primary frontier-model provider for 30, 90, and 180 days. The result is the size of their sovereignty problem, and whether they even know that number tells me a lot.
    2. The companies that preserve strategic optionality will be the ones that draw a clear line between work requiring owned cognition (fine-tuned, embedded, internal) and work that can run on rented cognition (API-served frontier models) — and treat that boundary as a capital decision, not a procurement decision.
    3. I’ll be watching how the policy direction develops across major operating jurisdictions. Sovereignty framing in Davos has a consistent track record of translating into sovereignty requirements in regulated industries within 12–24 months.

    References and related signals

  • When 88% of organizations have adopted AI, adoption stops being the question

    When 88% of organizations have adopted AI, adoption stops being the question

    What was announced

    The Stanford HAI 2026 AI Index landed in mid-January with a set of numbers that close out a debate. Organizational AI adoption reached 88% globally. Global corporate AI investment more than doubled in 2025 to $581.7 billion. Generative AI hit 53% population adoption within three years — faster than the personal computer or the internet. Four out of five university students now use generative AI as part of their coursework.

    What it means

    When adoption crosses the 80% line, the question of “should we adopt” becomes structurally uninteresting. Every relevant comparison group has already answered it. What remains is differentiation — and differentiation in a world of universal access is harder, not easier, than in a world of selective access. The strategic margin moves from access to integration depth, from licenses to workflow penetration, and from procurement decisions to operating-model decisions.

    The investment number is the more telling signal. $581.7 billion of corporate AI investment in a single year is a capital allocation that prices in a specific belief: that AI capability will compound at a rate that makes today’s spending the cheap option in retrospect. That belief either turns out to be correct, in which case the laggards face a permanent gap, or it overshoots, in which case the survivors of the correction still own infrastructure and skills the laggards do not.

    Andreas’s view

    My read on this: the AI Index numbers are not a celebration of momentum, they are a notice of obsolescence. Adoption was the entry-level metric — the one that let companies say “we are doing AI” without committing to anything that mattered. With 88% adoption, that metric is exhausted. The companies that conflate “we have AI deployed” with “we have an AI strategy” will be the ones surprised in 18 months when peers with the same headline adoption rate are operating at a fundamentally different unit-economics base.

    I don’t think the next two years will be about adopting more. They will be about routing work differently — deciding which functions become AI-native, which roles get redesigned, which middle-management layers compress, and which workflows get rebuilt from the ground up rather than augmented. The companies treating this as a tooling question will keep the org chart they had in 2024 and bolt assistants onto it. The companies treating it as a structural question will redesign for AI-native operations and harvest a different cost base.

    My expectation is that boards still reporting on adoption rates are measuring the wrong thing entirely. The number that matters is the percentage of work routed through AI-native processes versus AI-augmented legacy processes. Those are two different cost structures and two different competitive positions. The first is a step change. The second is a feature.

    Three things I’m watching

    1. I’ll be watching whether companies move away from adoption KPIs toward integration-depth KPIs — specifically, the percentage of revenue-generating workflows that are AI-native, not just AI-touched.
    2. The companies that stand out to me will be the ones that build the comparison the AI Index doesn’t make for them: how their spend per FTE on AI infrastructure and tooling stacks up against the 90th-percentile peer in their sector. If that number isn’t visible to leadership, it isn’t informing strategy.
    3. I’ll be watching whether organizations use the next 12 months as a workflow-redesign window rather than a tooling-procurement window. The structural opportunity narrows the moment competitors finish their redesign.

    References and related signals

  • Humanoids crossed from demo to deployment in one week

    Humanoids crossed from demo to deployment in one week

    What was announced

    At CES 2026 in Las Vegas (Jan 5–9), a cluster of robotics announcements crossed the same threshold in a single week. Boston Dynamics unveiled the production-ready electric Atlas with Hyundai committing the first fleet to its Metaplant in Savannah, Georgia, and announced a partnership with Google DeepMind to integrate Gemini Robotics models into the platform. LG demonstrated CLOiD performing real household work — laundry, dishwasher loading, food preparation — in a staged living environment. EngineAI introduced the T800 with a $25,000 starting price and mid-2026 shipping. CES listed 40 companies referencing humanoids on the show floor.

    What it means

    A human factory engineer in navy work clothes works alongside a matte-white humanoid robot at a metal workbench.
    Side by side, not face to face.

    For three years humanoids were a category of demo videos. CES 2026 is where the category became a category of contracts. Production is committed, factories are named, prices are listed, and the foundation-model layer (Gemini Robotics, comparable initiatives at other labs) supplies the cognitive component that previously made every demo brittle. The constraint is no longer “can it walk on stage.” The constraint is “what does the deployment workflow look like, and who owns the integration.”

    From this follows a second-order effect: industrial buyers now have a real procurement question to answer in 2026 — not in 2030. Hyundai’s timeline (Atlas at Metaplant, dedicated robotics factory targeting 30,000 units per year by 2028) is the explicit benchmark. Every competing automaker, every large logistics operator, and every contract manufacturer now sits with a known reference deployment to react to.

    Andreas’s view

    My read on this: the news is not that the robots are good enough. The news is that buyers have decided they are good enough to commit — and the price has moved into range. At $25,000, a humanoid sits below the annual cost of an industrial worker in most developed markets. That shifts the question from “is this technology real” to “where does it amortize fastest.”

    My three takeaways:

    1. The barrier that fell was cognitive, not mechanical. The hardware has been close to ready for years. What changed is that foundation models — think Atlas plus Gemini Robotics — absorbed the cognitive deficit that kept robots out of unstructured environments. CES 2026 looks different because the system is different, not just the chassis. I think anyone framing this as “better robots” is underestimating the speed of what comes next.

    2. The 2030 humanoid timeline is already stale. In my view, this is now a 2026 pilot conversation for any organization with manufacturing, warehousing, or fulfillment in its operations footprint — anywhere unit-level labor is the dominant cost driver. Not as a capex bet, but as a learning investment. The compounding advantage goes to whoever builds operational muscle around these systems first.

    3. The real cost of waiting isn’t hardware — it’s the operating model. Hardware will be available to everyone. What won’t be available off the shelf is three years of deployment experience. My expectation is that late movers won’t just be buying machines from competitors — they’ll be importing the playbook for how to use them.

    References and related signals