All posts Forward-Deployed Model

OpenAI's DeployCo, Anthropic's Ode, and the case for an independent forward-deployed partner

The short answer

OpenAI’s Deployment Company is majority-owned and controlled by OpenAI and builds systems that connect OpenAI models to your data, while Ode with Anthropic, a standalone company Anthropic founded with Blackstone and Hellman and Friedman, works “Claude-first”, and TechCrunch reports it will use rival models if needed. OpenAI launched the Deployment Company on 11 May 2026 with more than $4 billion from 19 partners and an agreement to acquire Tomoro, an applied AI consultancy whose clients include Tesco, Virgin Atlantic and Supercell. Anthropic announced the venture on 4 May 2026, with Goldman Sachs among its backers, and it revealed its name, Ode with Anthropic, on 15 July 2026, built on the acquisition of Fractional AI. In August 2026 it acquired the consultancy Casper Studios.

Both build real systems with real engineers. What neither can do is be indifferent about which model your company ends up built around, and that indifference is the whole asset in a model market where the leading option keeps changing. So the question a CIO faces is no longer who embeds the engineers. It is who owns the result when they leave.

Key takeaways

  • The forward-deployed model stopped being a differentiator in 2026. Between April and July, Google Cloud, Anthropic, OpenAI, AWS and Microsoft set up embedded delivery, and Meta announced a team to do the same. Embedding engineers is table stakes, not a pitch.
  • A lab-owned delivery arm is first-party-model by construction. The Deployment Company connects OpenAI models to your systems. Ode calls its own rule “Claude-first”. That is an incentive, not an accusation, and it decides what gets recommended in week one.
  • The platforms sell model choice and self-sufficiency, not portability. Microsoft Frontier Company runs many models on Microsoft’s platform. AWS promises you will not need its engineers afterwards, and the systems keep running on AWS. Microsoft keeps the platform, AWS keeps the cloud.
  • Google took the third route. At Cloud Next in April 2026 it committed a partner fund and put its own engineers alongside Accenture, Capgemini, Cognizant, Deloitte, HCLTech, PwC and TCS. By October, Accenture and Cognizant had each set up a Gemini group of their own. The integrators keep most client relationships, Google keeps the model underneath.
  • Europe is where the arms differ most. The OpenAI Deployment Company has Tomoro’s base in Edinburgh and London, which is in the UK, outside the EU. Ode lists no European office, and Anthropic’s European route is a reported Hg venture. Whoever you hire, ask which legal entity holds your data, in which jurisdiction, and whether the deployer duties land on you.

OpenAI Deployment Company vs Ode with Anthropic vs Microsoft Frontier Company, side by side

The table compares seven routes, counting the independent one, on what decides the contract rather than on engineering talent, which all seven can hire. “Not published” means not in the company’s own material or in the coverage cited here, as of October 2026. Consultancies and system integrators now run forward-deployed practices of their own, a further route, compared with an embedded team in forward-deployed engineer vs consultant vs system integrator.

Launched and ownerModel lock-inContext and evals at exitPricing modelEuropean presence
OpenAI Deployment Company11 May 2026. Majority-owned and controlled by OpenAI; more than $4 billion from 19 partners led by TPG.Connects OpenAI models to your data, tools and controls. Once the Northslope deal closes, possible joint engagements with Palantir.Not published. A case study on deploy.co describes “building custom evaluation systems”.Not published.Tomoro’s Edinburgh and London teams (UK, outside the EU); forward-deployed roles in London, Edinburgh and Paris.
Ode with AnthropicAnnounced 4 May, named 15 July 2026. A standalone company founded by Anthropic, Blackstone and Hellman and Friedman; valued at $1.5 billion (WSJ, via TechCrunch).“Claude-first”, with rival models if needed.Not published. Casper, bought in August, builds “context within Anthropic products”.Not published.No European office listed: San Francisco, New York, Raleigh-Durham, Dubai.
Microsoft Frontier Company2 July 2026. A Microsoft operating business, not a separate company; $2.5 billion and 6,000 experts.Many models, one platform: Microsoft’s.Partly exportable, layer by layer, in our Frontier Company analysis.Not published. An analyst reads it as free deployment paid back by consumption.LSEG, Unilever and Novo Nordisk among launch customers.
AWS Forward Deployed Engineering30 June 2026. An internal Amazon unit with $1 billion.Runs in your own AWS environment, so the cloud is the lock-in.A “governed, versioned knowledge graph” in your AWS account. Evaluations not mentioned.Shared goals and business results, “not billable hours”. No price published.No European FDE customer named at launch.
Google Cloud, through partners22 April 2026: a $750 million partner fund. On 8 September, Google to train up to 1,000 Accenture FDEs; a Cognizant group in October.Gemini Enterprise.The integrator’s contract decides.The integrator’s fees.Google FDE teams in CVC portfolio companies.
Meta Enterprise SolutionsReported in May and June 2026 as a planned team, part of a Meta restructuring. No customer named.Meta’s own AI systems, business agents first.Not published. Its data engineers are to prepare client data “for Meta’s AI systems”.Not published for the team.Not published.
Independent partnerNot applicable. No model vendor on the cap table.Chosen per workflow by evaluation.Code, context and evals in your estate, able to run on another model, if the contract says so.What the contract names: fixed, or tied to outcomes.EU-only if you require it.

Sources for the table: Pulse 2.0 on OpenAI’s launch; deploy.co’s home page, Northslope release and careers page; TechCrunch on Ode’s valuation and its Claude-first rule; Ode’s launch release, Casper release and careers page; TechCrunch on Microsoft’s commitment, Microsoft’s launch post and Directions on Microsoft; Amazon’s announcement and TechCrunch on AWS; Google’s Next ‘26 keynote and partner fund, TechCrunch on Accenture, CIO Dive on Cognizant and the CVC release; Reuters on Meta via BNN Bloomberg and The Information via PYMNTS.

The empty cells matter as much as the full ones. None of the six arms publishes a price. Two announcements say where the context ends up: AWS puts the knowledge graph in your own AWS account, and Ode’s Casper deal builds “context within Anthropic products”. None says who keeps the evaluation sets when the engagement ends. The nearest thing to an answer is a single partnership, in which Ode describes building AI into PointClickCare’s platform “along with the evaluation, observability, and governance to run them at scale”. That describes one deal, not a default term. Nor does any announcement say which legal entity processes a European customer’s data. None of this is evidence of a problem. These are questions nobody will answer for you unless you ask them.

What is the OpenAI Deployment Company?

The OpenAI Deployment Company is OpenAI’s forward-deployed engineering business, majority-owned and controlled by OpenAI, launched on 11 May 2026 with more than $4 billion from 19 partners led by TPG. It trades as OpenAI Deploy Co. at deploy.co, where it describes forward-deployed engineering as “how OpenAI brings AI into production”.

It is buying delivery capacity as well as hiring it. Tomoro, an Edinburgh and London applied AI firm, came first, and by July the Deployment Company was calling it a “recent acquisition”. On 8 July 2026 it agreed to acquire Northslope, the first member of Palantir’s Vanguard: Elite network, with customers across the US, Europe and the Middle East. That deal is subject to regulatory approval. After closing, Northslope may support “joint commercial engagements … in partnership with Palantir”, and it describes itself as “The AI Application Layer for your Palantir Operating System”. A system built that way sits on two vendors’ roadmaps, not one, and needs a Palantir platform licence underneath.

Ode with Anthropic: is it part of Anthropic?

Not as a division. Ode with Anthropic calls itself “a standalone company”, founded by Anthropic, Blackstone and Hellman and Friedman, and it builds Claude-first. Its 15 July launch release lists a consortium of investors behind it that includes Goldman Sachs, Apollo and Sequoia. According to the Wall Street Journal, as reported by TechCrunch, Anthropic, Blackstone and Hellman and Friedman each committed $300 million. Blackstone conceived it, according to TechCrunch, after it noticed a gap while using large consulting firms and small AI services boutiques to implement AI across its portfolio companies. One of those boutiques, Fractional AI, became the foundation of Ode, and ended an 11-month partnership with OpenAI when it was acquired. Its co-founders, Chris Taylor and Eddie Siegel, now run Ode as CEO and CTO.

In Ode’s launch release, Garvan Doyle, Anthropic’s head of forward-deployed engineering for the Americas, aimed Ode at “mid-size companies” moving AI into their operations, a segment that overlaps with Europe’s mid-caps. Every office Ode lists, though, is in San Francisco, New York, Raleigh-Durham or Dubai, and TechCrunch reports only that it aims to keep scaling, “internationally too”.

The ties to Anthropic are close and stated openly. Ode works with Anthropic’s applied AI team, and its rule is to implement Anthropic’s technology whenever possible. Anthropic keeps its own internal team for what a spokesperson called strategic, mission-aligned deployments. Siegel put the model question this way: “model selection matters, but it’s not where the majority of calories are spent.”

The Deployment Company is the opposite structure. OpenAI majority-owns and controls it, and describes it as giving customers one experience whether they work with OpenAI, the Deployment Company, or both. If the question behind “is Ode part of Anthropic” is “how independent is the advice”, the honest answer is: more independent than DeployCo on paper, and still Claude-first in practice.

How is Microsoft Frontier Company different from the OpenAI Deployment Company and Ode?

Microsoft Frontier Company is an operating business inside Microsoft, not a separate company with outside investors, and it builds on Microsoft’s platform rather than on one lab’s model. Directions on Microsoft reports it is not a spin-off, reads it as a make-over of Microsoft’s existing consulting organisations, and notes it is not clear whether the $2.5 billion budget is new money. Microsoft’s launch post promises customers will not be locked into a single model. Neither lab arm promises that in those terms: Ode is Claude-first and uses rival models if needed, and the Deployment Company builds on OpenAI models. So the lock-in question moves down a layer, from the model to the platform your context, data and agents run on. Which layers leave in a form another platform can read is set out in Microsoft Frontier Company: whose intelligence does it protect?, and is not repeated here.

What actually changed this year

For most of the last decade the forward-deployed engineer was a Palantir peculiarity: send engineers into the customer’s environment because the customer cannot write a specification for a problem they have never seen solved. Vendors copied the idea slowly. Independent firms built practices on it. It was still niche enough in 2025 that explaining it was half of every sales conversation.

Then, in ten weeks of 2026, the largest AI companies in the world all moved into it, by acquisition, partner funds, reorganisation or a new internal unit. Google Cloud went first at Cloud Next on 22 April, funding the integrators rather than becoming one, apart from its own forward-deployed teams in CVC’s portfolio. Anthropic followed on 4 May with private equity partners, then filled Ode with people who had already done the work by buying Fractional AI and, later, Casper Studios. OpenAI launched its Deployment Company a week later, alongside an agreement to acquire Tomoro, and in July agreed to buy Northslope. Meta’s move came through a reorganisation: Reuters reported on 3 June that its new Enterprise Solutions team “will send squads of forward-deployed engineers to embed with enterprise customers”. AWS followed on 30 June with a dedicated internal unit, which CNBC reported as the first initiative of its kind from a hyperscaler (Google’s April move had gone through partners), and Microsoft closed the stretch two days later with Frontier Company.

The second wave went through the integrators. On 8 September Google said it would train up to 1,000 Accenture forward-deployed engineers, in a group that, according to TechCrunch, “will live under Accenture”. In October Cognizant set up a Gemini Frontier Capability Group to house more than 18,000 engineers it brands Frontier Certified. AWS took the same turn on 1 October, extending its forward-deployed organisation to partners through a Partner-Led FDE motion with three new credential pathways. The CIO Dive report on Cognizant also notes that Gartner has cautioned buyers to look out for providers packaging traditional IT consulting as forward-deployed work and charging a premium for “hastily rebranded services”.

Read those moves together and one conclusion is unavoidable: the labs have concluded that the bottleneck in enterprise AI is not model capability. It is everything between a capable model and a system that runs in your company on Monday morning. It is now the stated position of the companies that build the models.

That settles the argument about the delivery model. It opens a different one. The integrator route, where Accenture, Deloitte and the rest run forward-deployed teams under their own name, is covered in who really does forward-deployed engineering now. This post stays with the labs and the platforms.

What the lab-owned arms are genuinely good at

Being fair about this matters, because a buyer who reads only the criticism will discount the rest.

A delivery team owned by a model vendor has three real advantages. It sees the roadmap before you do, so it can build against a capability that ships next quarter rather than working around its absence. OpenAI says this outright: its Deployment Company engineers will build for where OpenAI’s frontier capabilities are headed. It has the shortest possible escalation path when the model behaves strangely on your data, which is worth more than it sounds at three in the morning during a rollout. And it has engineering density in one model’s tooling that an independent generalist takes longer to match.

If your company has already standardised on one lab, has no intention of moving, and is automating a workflow that is not the one you compete on, buying delivery from that lab is a defensible decision. Say so plainly at the board meeting and it will hold up.

The thing a lab-owned arm cannot do

It cannot run an honest head-to-head model evaluation and act on the result.

Not because its engineers are dishonest. Because the arm exists to increase consumption of the parent’s model, and every incentive above the engineer points one way. Ode is candid about it, which is to its credit: Claude-first, other models when needed. “When needed” is decided by a team whose backers include the company that sells Claude. When the right answer for your document-extraction workflow is an open-weights model running on your own infrastructure at a fraction of the cost, an independent partner writes that in the evaluation and moves on. A lab-owned team has to have a conversation with its own board first.

This compounds over an engagement. The first system gets built around one model’s tool-calling conventions, its context window, its prompt-caching behaviour, its safety filters. The second system inherits the first one’s abstractions. Two years in, the cost of moving is not an API change, it is a rewrite of the layer where your company’s actual knowledge lives. Nobody made a decision to lock in. It accumulated.

AWS: self-sufficient is not the same as portable

AWS made the most testable claim of the six, because it answers the lock-in criticism at the level of the system rather than the model. Its forward-deployed unit, announced on 30 June 2026, embeds pods of roughly five or six engineers who work alongside AI agents, and AWS says they leave behind self-sufficient teams within weeks. CIO Dive reports 45-day sprints. Amazon’s own announcement describes a semantic layer deployed into the customer’s own AWS account, which publishes “a governed, versioned knowledge graph” that agents reason over, and says deployments are structured around “shared goals and business results, not billable hours”. The announcement quoted by TechCrunch promises agentic systems running in the customer’s own AWS environment, plus skills and patterns the team can use independently.

Take the claim at its word and test it against the five layers below. Self-sufficient covers the organisational knowledge: your engineers can run and change the system without AWS staff, and that is a real improvement on a vendor who never leaves. It partly covers the context and the governance evidence, because both sit in accounts you control rather than in a vendor’s tenant. It does not cover the orchestration or the platform underneath. A knowledge graph in your AWS account is yours to use on AWS. Whether it means anything on another cloud depends on its format and its dependencies, and the announcement does not say.

So the question for AWS is narrower than the one for the labs, and easier to put in a contract. Ask which components of the semantic layer and the knowledge graph export, in what format, and what runs if the AWS account is closed. Self-sufficient from AWS headcount is worth having. It is not the same thing as owning the result.

Ownership is the question, not model choice

Model-agnostic is necessary and not sufficient. Swapping the model out solves one layer. Five accumulate during a serious engagement:

  1. The model. Which provider generates the tokens. The only layer most vendor content discusses.
  2. The orchestration. How agents are sequenced, retried, evaluated and rolled back. Usually the vendor’s framework.
  3. The context. The structured, current record of how your business actually works: which systems disagree about a customer, what the exception path really is, how the best person on the team does the job. This is the layer that takes longest to build and cannot be re-bought.
  4. The governance evidence. Audit trail, traceability, access control, retention. The artefacts that prove to a regulator what happened.
  5. The organisational knowledge. Who inside your company can change the system without breaking it.

A contract that gives you the code but leaves the context inside a vendor’s platform has given you the cheapest of the five layers. Ask about layer three specifically. Ask what format it is in, where it lives, and whether it means anything after you stop paying.

This is what we mean by owning your intelligence. We describe Nucleo as a transformation company rather than an agent vendor, but Ode’s own releases since August describe Ode as “an enterprise AI transformation company” too, so the label settles nothing. The difference is where the context ends up. Casper builds it “within Anthropic products”. We build it as a context engine that sits in your estate, in formats any model or cloud can read. Agents run on that intelligence. They are not the thing worth owning.

The four questions a European buyer should add

The comparisons written for a US or UK buyer stop at model neutrality. If you are a European company, the jurisdiction questions are not a compliance footnote, they are part of the architecture. Of the two lab arms, only OpenAI’s has a European delivery base, and it sits in the UK, outside the EU: Tomoro, the Edinburgh and London firm the Deployment Company now calls its “recent acquisition”. In October 2026 it was advertising forward-deployed roles in London, Edinburgh and Paris, and Paris was the only one of those inside the EU. Ode lists no European office. Anthropic’s European route, if it happens, is the Hg venture: offices in London and Berlin, a launch by the end of 2026, and work with businesses Hg owns, according to the FT as relayed by TNW. Anthropic and Hg declined to comment. Google’s route runs through its partnership with CVC, with Google forward-deployed teams in CVC portfolio companies. Google, AWS and Microsoft each sell a residency option: Google Cloud Dedicated, which in France is operated by S3NS, “a standalone French entity”; the AWS European Sovereign Cloud; and Microsoft’s EU Data Boundary.

Which legal entity processes the data, and where. A delivery contract signed with a US parent can route your inference traffic under disclosure obligations your own regulator did not choose. Data residency and legal jurisdiction are separate questions, and only the second one decides who can compel access.

Where does inference actually run, and which subprocessors sit underneath. Ask for the list, in writing, including the ones the vendor considers its own supply chain rather than yours.

Who carries the deployer duties. Under the EU AI Act, obligations split between the provider of a system and its deployer, and Article 26 sets out what deployers of high-risk systems must do, and most companies are deployers without having noticed. If the vendor’s contract is silent on this, you are the deployer, and if the vendor builds a system you put into service under your own name, you may be its provider as well.

What happens to the evidence if you switch vendors. Audit trails and traceability records are not portable by default. If they live in the departing vendor’s platform, your ability to answer a regulator about last year’s decisions leaves with them.

Where this leaves the decision

The buyer’s question has moved on from who embeds engineers to what those engineers leave behind, and whose roadmap it is tied to.

If the workflow is commodity and the model or the platform is already chosen, buy the delivery from the lab or the platform you already run on and get on with it. If the system you are building will hold the knowledge that makes your company difficult to copy, hire someone whose only loyalty is to the outcome, and get the answer about the five layers in writing before anyone starts.

FAQ

What is the OpenAI Deployment Company? A business OpenAI launched on 11 May 2026 to embed forward-deployed engineers inside organisations and build production systems that connect OpenAI models to the customer’s data, tools and controls. It is majority-owned and controlled by OpenAI, backed by more than $4 billion from 19 partners led by TPG, and trades as OpenAI Deploy Co. It started by agreeing to acquire Tomoro, an applied AI consultancy with about 150 forward-deployed engineers and deployment specialists, and on 8 July 2026 agreed to acquire Northslope, the first member of Palantir’s Vanguard: Elite network, subject to regulatory approval.

Is Tomoro part of the OpenAI Deployment Company? Yes, by every public sign. OpenAI agreed to acquire Tomoro, an Edinburgh and London applied AI consultancy whose clients include Tesco, Virgin Atlantic and Supercell, when it launched the Deployment Company on 11 May 2026. By 8 July the Deployment Company was calling Tomoro its ‘recent acquisition’, and tomoro.ai now redirects to the Deployment Company’s own site, deploy.co.

What is Ode with Anthropic? A standalone company that describes itself as an enterprise AI transformation company, founded by Anthropic, Blackstone and Hellman and Friedman, with Goldman Sachs, General Atlantic, Leonard Green and Partners, Apollo, GIC and Sequoia in its investor consortium. Announced on 4 May 2026 and launched under its name on 15 July 2026, it is built on the acquisition of the applied AI firm Fractional AI and bought the consultancy Casper Studios in August 2026. Its engineers embed inside client companies and build systems Claude-first.

Is Ode part of Anthropic? Not as a division. Ode calls itself a standalone company, founded by Anthropic, Blackstone and Hellman and Friedman, and each of the three committed $300 million, according to the Wall Street Journal as reported by TechCrunch. It works closely with Anthropic’s applied AI team on a Claude-first principle, and TechCrunch reports it will use rival models if needed. The OpenAI Deployment Company is a different case: OpenAI majority-owns and controls it.

OpenAI Deployment Company vs Ode: what is the practical difference? Control and model policy. The Deployment Company is controlled by OpenAI and builds around OpenAI models and OpenAI’s roadmap. Ode, founded by Anthropic with two private equity firms, works Claude-first, and TechCrunch reports it will use rival models if needed. Both embed engineers, both are tied to one lab, and neither answers by default what you own when the engagement ends.

Which deployment arms have a presence in Europe? Of the two lab arms, only the OpenAI Deployment Company has a delivery base in Europe, and it is in the UK, outside the EU: Tomoro’s Edinburgh and London teams, plus one EU forward-deployed role advertised in Paris. Ode lists no European office, and Anthropic’s European route is a consultancy with Hg that the FT reported on 23 October 2026. Among the platforms, Microsoft names LSEG, Unilever and Novo Nordisk among its launch customers, and Google embeds its own engineers in CVC’s portfolio companies.

Does Meta embed engineers in companies? It plans to. Reuters reported on 3 June 2026 that Meta’s new Enterprise Solutions team, set up in a companywide restructuring around AI, will send squads of forward-deployed engineers to embed with enterprise customers, business agents first. The Information reported that its data engineers are to prepare corporate data for Meta’s AI systems. The coverage names no price, customer or European plan for the team.

Does AWS’s forward-deployed unit leave you independent? It leaves you independent of AWS engineers, which is what AWS claims. It does not leave you independent of AWS. The systems run in your own AWS environment and the knowledge graph its semantic layer builds sits in your AWS accounts, so the skills transfer and the platform stays.

Should we buy forward-deployed delivery from the model vendor itself? It is a reasonable choice if you have already standardised on that vendor’s model, you want proximity to its unreleased roadmap, and the workflow you are automating is not the one your business competes on. It is the wrong choice if the system will hold the knowledge that makes your company hard to copy, because a lab-owned team cannot be indifferent about which model that knowledge ends up shaped around.

Is a lab-owned delivery team model-agnostic? Not by construction. The delivery arm exists to increase consumption of the parent’s model, and its engineers are deepest in that model’s tooling. Ode states it plainly as a Claude-first principle. That is not a criticism of the engineers, it is a statement about incentives. An independent partner can run a head-to-head evaluation and pick the losing vendor’s model without a conversation with its own board.

What should a European company ask that a US buyer might not? Which legal entity processes the data, in which jurisdiction, and under whose disclosure obligations. Ask where inference runs, which subprocessors sit underneath, and whether the deployer duties under the EU AI Act land on you or on the vendor. A delivery contract signed with a US parent can put your inference traffic under a jurisdiction your own regulator did not choose.

What survives the engagement, whoever you hire? Ask for the answer in writing before signing: the code, the integration layer, the evaluation sets, the accumulated context about how your business actually runs, and the right to run all of it on a different model. If any of those five is described as the vendor’s platform rather than your asset, you are renting the result, not owning it.



Nucleo is an AI-native transformation company for European mid-caps. Our forward-deployed engineers build a context engine, the owned, model-agnostic intelligence layer your company runs on, under EU governance. We put agents into production on top of it, and leave it in your estate, in formats another model or cloud can read, when we go. See how an engagement works, or write to us.

Sources: OpenAI confirms Deployment Company launch, acquires Tomoro; Anthropic and OpenAI are both launching joint ventures for enterprise AI services; Anthropic, Blackstone bet the next trillion-dollar AI business is implementation; Kirkland advises Ode with Anthropic on acquisition of Casper Studios; Amazon launches new $1 billion FDE org; AWS creates forward deployed engineering hub; Welcome to Google Cloud Next ‘26; Google Cloud commits $750 million to partners’ agentic AI development; Forward-deployed engineers are the AI industry’s latest talent obsession; The OpenAI Deployment Company to acquire Northslope; The OpenAI Deployment Company and its careers page; Northslope; TNW on Tomoro and the OpenAI Deployment Company; Anthropic, Blackstone, and Hellman and Friedman introduce Ode with Anthropic, an enterprise AI services firm; Ode with Anthropic acquires Casper Studios; Ode with Anthropic and PointClickCare announce strategic partnership; Careers at Ode; Microsoft launches its own AI deployment company with $2.5 billion commitment; Microsoft Frontier Company: AI engineering that amplifies and protects your intelligence; Directions on Microsoft on the Frontier Company; AWS invests $1 billion in forward deployed AI engineers; CNBC on the AWS unit; New FDE pathways for AWS Partners; Digital sovereignty at AWS; What is the EU Data Boundary?; Google Cloud races to catch up in the AI deployment wars with Accenture deal; Cognizant commits to training 18K Google Cloud AI specialists; Google Cloud and CVC launch partnership; Meta enters enterprise AI race with new business agent; Meta is coming for enterprise AI; Anthropic and Hg reportedly plan AI consultancy for European firms; EU AI Act, Article 26: obligations of deployers of high-risk AI systems.

The future belongs to those who see it before it is obvious, and build it while everyone else is still out there scouting for the best AI tools.