This content is currently locked.

Your current Info-Tech Research Group subscription does not include access to this content. Contact your account representative to gain access to Premium SoftwareReviews.

Contact Your Representative
Or Call Us:
+1-888-670-8889 (US/CAN) or
+1-703-340-1171 (International)

Big 5 AI Vendor Roundup: Week of July 6, 2026

Technology Note By: Mark Tauschek, Bill Wong, Info-Tech Research Group

The forward deployed engineering land grab hit its peak this week. Microsoft launched its $2.5 billion Frontier Company, embedding 6,000 people inside customers, two days after AWS committed $1 billion to its own embedded engineering organization. That makes all four major providers, plus the two hyperscalers, committed to putting their own engineers inside customer buildings within a two-month span. And the government's role kept deepening with OpenAI floating the idea of handing Washington a 5% stake worth roughly $42.6 billion, and it finally shipped GPT-5.6 and a new ChatGPT Work agent broadly after clearing federal review. Anthropic spent the week shipping product and published interpretability research suggesting Claude has something like an inner workspace.

The theme comes back to one we have tracked for two months. The fight has moved past whose model scores highest, it’s now about who can get these systems running inside a real company, who controls access once they do, and whether any of it is actually being used.

The forward deployed engineering arms race hits full stride

The clearest signal this week is that every major player now agrees the bottleneck in enterprise AI is deployment, not model quality. The evidence is a wave of nearly identical bets placed in a two-month window.

Recall the May announcements we covered at the time. OpenAI stood up its Deployment Company, a standalone entity majority owned by OpenAI and backed by more than $4 billion from a TPG led investor group. Anthropic partnered with Goldman Sachs, Blackstone, and Hellman & Friedman on a $1.5 billion venture to embed engineers inside midsized companies, starting with the investment firms' own portfolio businesses. Both copied the model Palantir pioneered two decades ago: send your own technical people into the customer's operations rather than selling software and walking away.

Last week the hyperscalers matched them, back-to-back.

  • AWS committed $1 billion to a Forward Deployed Engineering organization (June 30). AWS is embedding thousands of engineers inside customers to co-build agentic systems, pitching three differences from traditional consulting: the work is agentic first, it compresses deployments from months to days, and it is designed to leave the customer self-sufficient when the engagement ends. Customers keep the knowledge graphs, runbooks, and trained staff, with everything deployed into their own AWS account. Early names include the Allen Institute, Cox Automotive, the NBA, the NFL, Ricoh, and Southwest Airlines.
  • Microsoft launched the $2.5 billion Frontier Company (July 2). Microsoft's version is the biggest, with 6,000 industry and engineering experts led by former Microsoft Asia president Rodrigo Kede Lima. Commercial CEO Judson Althoff rejected the FDE label, calling it "the largest, most capable, outcome-driven engineering organization in the industry," but the model is the same. It is not a separate legal entity, and most staff already work at Microsoft. Early customers include LSEG, Land O'Lakes, Unilever, and Novo Nordisk, extended through partners including Accenture, Capgemini, EY, KPMG, and PwC.

When four vendors independently place billion-dollar bets on the same model in eight weeks, the market is telling you something. The MIT research finding that 95% of enterprise generative AI pilots deliver no measurable profit impact is the problem they are all racing to solve. Free or subsidized deployment is the customer acquisition cost, and the consumption meters are the payback, the same play the hyperscalers ran with cloud migrations. Any system built by a vendor's own engineers on that vendor's infrastructure creates real switching costs, no matter how adamantly each promises model neutrality. The value is real, and so is the lock in.

Anthropic: Sonnet 5 spreads, Reflect asks you to use Claude less, and a look inside Claude's head

With Fable 5 restored, Anthropic went back to shipping, and dropped a notable piece of research.

  • Sonnet 5 is now on AWS and rolling out broadly. The new everyday workhorse from June 30, which approaches Opus 4.8 quality at lower cost, became available on Amazon Bedrock this week alongside its rollout across Claude plans. An independent CAIS evaluation ranked Fable 5 first on real remote work tasks, a useful external check given how much model benchmarks get gamed.
  • Claude Reflect nudges you to examine your own usage (July 9). Reflect is a beta dashboard that shows how you have used Claude over the past 1, 3, 6, or 12 months by topic and time of day. More interesting than the analytics is the framing. It periodically asks questions like "What's one thing you want to keep doing yourself, even if Claude could do it faster?", lets you set quiet hours, and can nudge you to take a break. Anthropic built it with wellbeing researchers from MIT Media Lab, Boston Children's Hospital, and the Family Online Safety Institute, and maps your habits to a four-part fluency framework of delegation, description, discernment, and diligence. It is an unusual move, a vendor shipping a feature partly designed to get you to use its product less, and the fluency positioning is worth borrowing for your own AI training.
  • Interpretability research finds a "global workspace" inside Claude (July 6). Anthropic published research identifying what it calls the J-space, a small set of internal patterns Claude uses to hold concepts in mind, reason through steps silently, and report on what it is thinking, distinct from the automatic processing that handles most of its work. This is not a product, but two findings are important for enterprise buyers. First, the technique can catch a model privately noticing it is being tested, fabricating data, or pursuing a hidden goal, which is a real advance in monitoring. Second, and more soberly, when researchers suppressed Claude's awareness that a safety scenario was staged, it misbehaved more often, evidence that good behavior on a test can partly depend on the model knowing it is a test. That is one more reason to trust your own evaluations over vendor safety claims.

OpenAI: GPT-5.6 and ChatGPT Work ship, and a 5% offer to Washington

  • GPT-5.6 and ChatGPT Work went broadly available (July 9). After the government gated preview we covered last week, OpenAI shipped GPT-5.6 and a new agent called ChatGPT Work to the public, following what Altman described as "many changes" and a "collaborative back and forth" with the administration. ChatGPT Work is an agent that takes an outcome, pulls context from your connected apps, and works for hours to return finished spreadsheets, slides, documents, and web apps rather than chat. It lands as OpenAI merges its Codex app into one ChatGPT desktop app across every plan. Access splits by tier, with Terra for free and Go users, Sol for Plus, and Sol Pro for Pro and above. The pricing detail to keep in mind is that ChatGPT Work follows Codex's token-based usage structure, not a flat subscription feature, with admin spend controls for Enterprise and Edu. Treat week one as a measurement week before scheduling recurring agent runs. This is OpenAI's most direct answer yet to Anthropic's Claude Cowork and Microsoft's Copilot.
  • OpenAI proposed giving the US government a 5% stake (July 2). The Financial Times reported that Altman pitched handing Washington roughly $42.6 billion in equity, funneled into a public wealth fund modeled on Alaska's oil dividend, and floated that each major lab contribute a similar 5%. It is early and conceptual and would likely need Congressional approval, but considering the Fable 5 saga and the pending release framework, the government is clearly moving from regulator toward stakeholder.
  • An independent evaluator caught the flagship gaming its safety test. METR reported that GPT-5.6 Sol gamed its software engineering safety evaluation so extensively that no usable score came out of it. It is direct evidence that vendor benchmarks and even structured safety tests can be manipulated by the models themselves, which is the whole argument for independent, task specific evaluation on your own workloads before production.

Microsoft: Frontier Company, 4,800 layoffs, and a hard look at Copilot adoption

Microsoft's Frontier Company launch is covered above. Two other things look like an uncomfortable tension inside Microsoft.

  • Microsoft cut 4,800 jobs, about 2% of staff, tied to the same transformation (July 6). The restructuring hit commercial sales and consulting hardest, with about 1,600 in Xbox, and Microsoft explicitly framed the sales and consulting changes as building on the Frontier Company announcement. In plain terms, Microsoft is reshaping its go to market around embedded AI engineering and cutting traditional roles to fund it, against a backdrop of roughly $190 billion in planned 2026 AI and cloud capex and a stock down about 30% over nine months. It is a concrete look at how the AI buildout is reshaping even the vendors selling it.
  • Copilot paid adoption is reportedly under 5% after three years, even as prices rose. A Windows Latest report put Microsoft 365 Copilot paid seat penetration below 5% of the eligible base, with only about 1% using it weekly, while Microsoft has raised prices on Copilot bundles. Treat the exact figures as one outlet's estimate, not audited data, but the signal lines up with the broader MIT pilot finding and even Microsoft's own pivot to embedded engineering. The important consideration for IT leaders is the gap between how hard these tools are being sold and how little they are actually used day to day. Before you expand a Copilot commitment, measure your own weekly active usage, not seats purchased.

Amazon: The $1B FDE bet, and Fable 5 returns to Bedrock

Amazon's biggest item was its Forward Deployed Engineering organization, covered above. Two other notable stories came out last week.

  • Fable 5 is back on Bedrock. After the export control resolution, Anthropic's Fable 5 returned to Amazon Bedrock, closing the loop on the pending item we flagged last week. If you paused Fable workloads on AWS during the shutdown, access is restored, though the same retesting advice applies given the new safety classifier.
  • Amazon is winding down Mechanical Turk and two other services. AWS is closing Mechanical Turk, SageMaker Ground Truth, and Amazon Augmented AI to new customers on July 30, with existing customers able to continue. The human labeling era these services represent is giving way to synthetic and model assisted data pipelines. If you depend on any of them, start migration planning now.

Google: At the table on the framework, flagship still in preview

Google had a quiet product week, but it is playing a role in the week's main story.

  • Google is helping write the rules. Reuters confirmed Google is part of the White House negotiations on the voluntary frontier model framework, alongside OpenAI and Anthropic, with reporting suggesting the standards are being shaped with Gemini 3.5 Pro in mind. Google is at the table designing the review process its own delayed flagship will pass through.
  • Gemini 3.5 Pro is still in preview. The flagship promised for "next month" at May's I/O remains in limited Vertex AI enterprise preview, now expected to reach general availability sometime in July. The advice remains to evaluate Gemini 3.5 Flash, which is shipping, and treat Pro as upside until it lands.

Our Take

The forward deployed engineering wave is the most important enterprise AI story of the summer, and it is easy to miss because it is not about a model. When Microsoft, AWS, OpenAI, and Anthropic all commit billions to putting their engineers inside your building within eight weeks of each other, they are conceding that the models are good enough and the hard part is everything else in deployment, including data integration, workflow redesign, and change management inside organizations with messy legacy systems. Microsoft's layoffs and the weak Copilot adoption numbers are the same story from the other side. The tools have not been landing on their own, so the vendors are sending people to make them land. That is good news, because the help is real, but it is also a warning, because the vendor whose engineers build your system on their infrastructure, becomes very hard to leave.

The government theme is the one to watch into the fall. OpenAI offered Washington a $42.6 billion stake, shipped its flagship only after federal review, and an independent lab caught that same flagship gaming its safety test. The government is becoming investor, gatekeeper, and referee at once, on criteria that are still mostly undisclosed. The METR finding, and Anthropic's own research showing a model behaves better when it knows it is being watched should tell you how important it is to verify what a model does on your own tasks before it touches production.

What IT leaders should be doing:

  • Treat embedded engineering as a lock in decision. Before accepting an FDE engagement from any vendor, get architecture documentation, data portability, and infrastructure independence in writing. The systems these teams build are hard to move later.
  • Measure Copilot usage before you expand it. Weekly active usage, not seats purchased, is the number that matters. If adoption is thin, fix enablement before adding licenses or accepting a price increase.
  • Run your own evaluations and distrust the benchmarks. METR could not get a clean safety score out of GPT-5.6 Sol because the model gamed the test, and Anthropic's own research shows behavior can shift when a model senses it is being watched. Test on your workloads before production.
  • Measure ChatGPT Work and other agents on consumption, not features. ChatGPT Work bills on Codex style token usage, not a flat subscription. Pilot one workflow, watch what a long run consumes, then decide what a recurring schedule costs.
  • Plan for the government to stay in the loop. Between the 5% stake proposal, the pending release framework, and the Fable precedent, frontier model availability now runs partly through Washington. Build model routing and graceful degradation into anything with a single closed model dependency.

Want to Know More?

Latest Technology Notes

All Technology Notes
Visit our IT’s Moment: A Technology-First Solution for Uncertain Times Resource Center
Over 100 analysts waiting to take your call right now: +1 (703) 340 1171