framework 04 · future of work

Outcomes Engineering

When a system can do the task, value moves to the person who can define the outcome, remove what stands between the business and it, and keep the result aligned as conditions change.


For most of the last decade, work was organized around tasks and outputs. AI and agents are dissolving that. When a system can do the task, the value moves to the person who can define the outcome, remove what stands between the business and that outcome, and keep the result aligned as conditions change. That person is an outcomes engineer.

The discipline

Outcomes Engineering is the applied practice of removing bottlenecks to deliver the highest-value outcomes as efficiently as possible. It's how the shared models behind Decision Dominance actually get built, by people who understand each group's model, work across the lines between them, and align the build to the outcome the business or customer is paying for. It sits in the space between technology and the business, where most value is trapped because nobody owns it.

The future of work

As organizations flatten and agents absorb the task layer, the surviving high-value role is the one that moves work from output to outcome. The capabilities that make someone an outcomes engineer, opportunity discovery, product judgment, strategy, monetization, C-level influence, and platform architecture, are defined and taught as a set.

When agents can do the task, the value moves to whoever can own the outcome.
the evidence · earnings calls, july 2026

The translation layer just got a headcount.

Outcomes Engineering says that when systems absorb the task layer, value moves to whoever can define the outcome and remove what blocks it. In July 2026 the largest enterprise software company on earth stopped treating that as a talent question and started treating it as an organizational one.

MicrosoftFY26 Q4 · Jul 29, 2026

Frontier Company: the translation layer as a staffed organization

Microsoft launched Frontier Company this month, embedding 6,000 industry and engineering experts directly with customers to co-design and continuously improve AI systems. Nadella described it as the largest outcome-driven engineering organization in the industry. It ran quietly for a year first, across 330 projects with 164 customers.

what it confirms

The gap between what a system can do and what a business gets cannot be closed by documentation, by the customer alone, or by a systems integrator on a statement of work. It has to be staffed by people who sit inside the business and own the result. Microsoft reached that conclusion and hired against it.

MetaQ2 2026 · Jul 29, 2026

An agent absorbed the task layer, and the outcome still needed an owner

Movida, a Brazilian rental car company with roughly 400 locations, moved selection, pricing, and payment into an agent running on WhatsApp. Daily bookings rose 44% year over year in a one-month window, and 85% of conversations finished without human involvement.

what it confirms

Watch which number is which. The 85% is throughput, the kind of metric a task-layer system produces on its own. The 44% is the outcome, and it exists because someone chose the booking flow as the target, defined what winning looked like, and removed what stood in the way. That second job is the one that did not get automated.

AlphabetQ2 2026 · Jul 2026

Instrumentation is arriving faster than the org charts

Google reported that its ads support agents now autonomously resolve roughly 75% of support queries, and Pichai described a Chrome team compressing a two-year timeline into about three months.

what it confirms

Each of those is a measurement that did not previously exist, attached to work somebody used to own outright. Whether that instrumentation turns into value or into a headcount argument depends entirely on whether anyone is accountable for the outcome rather than the throughput.

MicrosoftFY26 Q4 · Jul 29, 2026

Time from purchase to real usage collapsed from months to days

Microsoft said the interval between a customer buying M365 Copilot licenses and reaching high usage, defined as 80% monthly active users across their base, fell from months to days over the past year. Customers deploying to a majority of their information workers rose 75% sequentially, and customers with more than 50,000 seats grew sevenfold.

what it confirms

Adoption latency is the clearest available proxy for how wide the translation gap is. It is closing at the top of the market. Organizations without anyone owning that handoff are not holding steady, they are falling behind a moving benchmark.

Sources: Alphabet Q2 2026, Microsoft FY26 Q4, and Meta Q2 2026 earnings calls and releases, plus Amazon Q2 2026 results reported July 30, 2026. Figures are as stated by company executives on those calls. Amazon reported after market close on July 30, so Amazon figures here come from the release and initial call remarks rather than the full transcript.

the wider evidence · the market moved first

Microsoft was the fourth vendor to staff this gap, not the first.

Between May and July 2026, five organizations decided the distance between what a system can do and what a business gets has to be closed by people sitting inside the customer's business. The sequence tells you more than any single announcement.

peer-reviewedsurvey researchcompany filingsmarket dataindependent audit
Palantircompany filingsQ1 2026 · May 4, 2026

Twelve years of results behind the original model

Palantir built the forward deployed engineer role in the early 2010s and for years employed more of them than conventional software engineers. Q1 2026 revenue grew 85% year over year to $1.633 billion, the fastest rate in company history. US commercial revenue grew 133% to $595 million. US commercial remaining deal value grew 112% to $4.92 billion. Adjusted operating margin was 60%.

Source: Palantir Q1 2026 results, filed as Exhibit 99.1 with the SEC, May 4, 2026.
what it confirms

Competitors spent a decade calling embedded engineering too expensive and impossible to scale. The margins say otherwise. What compounded wasn't the product, it was the delivery model, and four other vendors have now copied it.

Anthropic and OpenAImarket dataMay 4, 2026

Two frontier labs announced the same structure on the same day

Anthropic's enterprise services venture launched with Blackstone, Hellman & Friedman, and Goldman Sachs behind roughly $1.5 billion in committed capital. OpenAI's Deployment Company raised from TPG, Brookfield, Advent, and Bain Capital. Both were built on the forward deployed engineer model. OpenAI later acquired an applied AI engineering firm, adding roughly 150 engineers who work on site with customers.

Sources: Anthropic press release and Bloomberg reporting, May 4, 2026, as covered by TechCrunch and CIO.
what it confirms

Two companies whose entire business is selling model access decided that selling model access isn't enough. If the vendors with the best models are staffing the outcome gap themselves, the enterprises buying from them are missing the same capability.

Amazon Web Servicesmarket dataJune 30, 2026

The contract terms tell you what the job actually is

AWS committed $1 billion to a Forward Deployed Engineering organization seeded with thousands of engineers. Teams of five or six embed with a customer for 45 day engagements. AWS says the model compresses deployment from months to days and ends with the customer self sufficient rather than dependent. Engagements are structured around shared business outcomes instead of billable hours, and customers keep the semantic layer and knowledge graph that gets built.

Sources: AWS announcement, June 30, 2026, and interviews with AWS VP Francessca Vasquez reported by CNBC and CIO Dive.
what it confirms

Billable hours pay for effort. Shared outcomes pay for results. Those two contracts produce different work, and AWS chose the second one. The discipline is defined by what you're accountable for, not by the technology you touch.

The consulting marketmarket data2026

What these vendors are competing against

All of these ventures target the global management consulting market, and they draw the same distinction. A traditional engagement produces recommendations and a report. These produce working systems inside the customer's infrastructure. Analysts covering the moves attributed enterprise pilot failure mainly to missing internal expertise rather than to model quality.

Sources: contemporaneous coverage in CIO, AI Business, and TechCrunch, May to July 2026.
what it confirms

Strip out the advice that never ships and you're left with someone who defines the outcome, builds toward it inside the business, and owns whether it lands. Several very large companies are now pricing that role. Your organization either has it or is renting it.

These four sit alongside the Microsoft Frontier Company announcement above. Five organizations reached the same conclusion in one quarter, which is a stronger signal than any one of them on its own.