A Five-Year VCF Stay Is Still a Priced Decision
London Stock Exchange Group signed a five-year VMware Cloud Foundation deal. Broadcom professional services will deploy VCF 9.0. LSEG has used VMware for more than a decade. The price is not in the announcement. The CIO called it an “engineered private cloud” next to existing cloud partnerships.
That’s the problem.
The parent pack is the VMware Broadcom stay vs exit page: perpetual versus VCF, the support path, portable VCF on AVS, and third-party cover.
This is not an exit. Tesco is fighting. Western Union left. T-Mobile is litigating support on the way out. LSEG stayed and bundled. A five-year VCF lock without a published price is still a license-position decision. If you copy the “we stayed” headline without the file, you have a press release. You do not have a position.
What LSEG and Broadcom actually announced
On 19 May 2026, LSEG and Broadcom issued matching releases. A new five-year agreement is “centered on VMware Cloud Foundation.” The initiative “complements LSEG’s existing cloud partnerships.” LSEG has used VMware across parts of its technology stack for more than a decade. VCF will support LSEG’s private cloud platform for parts of its infrastructure. Broadcom will provide professional services to roll out VCF 9.0 across LSEG’s environments.
No contract value appears in either release.
“Extending our use of VMware Cloud Foundation supports an engineered private cloud for our operations, while giving us the flexibility to support new services and workloads as our technology needs evolve,” said Andrew Knight, LSEG CIO for Infrastructure and Cloud.
Luigi Freguia, Broadcom’s President of EMEA Sales, called it confidence in VCF as a secure and resilient platform for market infrastructure.
Treat the announcement as a named stay, not a census. One operator renewed. The price is still your problem.
The five-year VCF stay is still a license event
Look at your own VMware file. Most SAM teams still have a row that says “vSphere” and a renewal date that says “next conversation.” Those two facts do not tell you whether the quote walking in is a like-for-like refresh or a five-year Cloud Foundation conversion with professional services attached.
If your reports still treat “we stayed” as the outcome, you are reading a reporting layer. You have a headline. You do not have a commercial outcome.
This is not a criticism of the teams building those reports. Traditional SAM tools were built to prove completeness, not to price five years of VCF 9.0 against the SKUs you operate, with the rollout as its own line, this week. An analysis that arrives after the CIO has forwarded the LSEG story is a document. One that arrives during the meeting is a decision input.
Do not let the vendor frame the next meeting as “a serious operator just committed for five years.” Do not let your own side frame it as “we should stay because LSEG stayed.” Both sentences skip the file. LSEG did not publish the price. That is the commercial object.
Picture your procurement director, sixty days out. The CIO has the LSEG line. Finance wants stay versus the exits they have been reading about. If you cannot put a stay-on-VCF case on the table that survives contact with this deployment (this week), you have a customer story, not a stay case.
Broadcom in the building to deploy 9.0 is not a free implementation. It is a commercial line in the same contract as the licenses. If your stay model prices five years of VCF and treats the rollout as “project, not license,” you will understate the lock.
A five-year term signed in 2026 runs past 2028. A large share of VMware users are looking to reduce use by then. Those clocks do not match. Locking five years because a peer stayed also locks past the year a large share of the market said it wanted a smaller footprint. That can be the right call. It is only a call if you priced stay, shrink, and leave against this estate before you signed.
Multi-cloud next to VCF is not a free option
Knight’s line is specific. Extending VCF supports an engineered private cloud. The releases also say the initiative complements existing cloud partnerships.
Those partnerships are on LSEG’s own paper. In April 2025 LSEG named AWS the preferred cloud provider for Markets, Risk Intelligence, and FTSE Russell. In 2022 LSEG and Microsoft signed a ten-year deal to architect data infrastructure on Azure and jointly develop data and analytics products. A five-year VCF agreement does not retire either file.
If your file treats “we stayed on VMware” as “we chose private over public,” you have misread the counterparty. The public-cloud spend does not pause while you write a five-year Broadcom check. The VCF spend does not become cheaper because you also have a hyperscaler.
The flexibility Knight described is an architecture claim. It is not a license position until you recast it against this deployment: which SKUs in the VCF 9 bundle you will operate, which you will pay for and park, and what that costs for five years against the estate you already run.
Previously you could pick and choose parts of the stack. Broadcom now sells the complete suite. If you cannot name the operate-versus-park split before you sign, you are buying the bundle as a headline.
What to have before you copy the stay
Produce a decision pack before the next VMware conversation, not a press-release recap.
| What you produce | Why it changes the meeting |
|---|---|
| Five-year VCF quote on this estate | LSEG did not publish a price. Your stay case is a number on your cores, not a customer story. |
| VCF 9.0 SKU list versus what you operate | Broadcom sells the complete suite. Name what you will run and what you will pay for and park. |
| Professional services as its own line | Deployment of 9.0 is in the LSEG contract. Price the rollout separately from the licenses. |
| AWS and Microsoft commitments next to VCF | LSEG kept both. A stay is not a cloud exit. Residual public-cloud spend through the lock. |
| Stay versus shrink versus leave, dated | A five-year lock closes doors on a clock you can keep. Price all three before you sign. |
Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is no, you have a stay rumor, not a license position. You do not have LSEG’s price. You have your estate.
The decision layer, not another inventory
You already have discovery data, a CMDB full of VMware records, and a renewal date on a spreadsheet. The gap is not another inventory. The gap is turning that estate into a decision: what five years of VCF 9.0 costs against the SKUs you operate, what professional services add, and whether a stay next to AWS and Microsoft is a priced lock or a headline. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. Audit defense is the ELP if Broadcom asks; IFMP is the host topology on the VMware file you already have.
If you are heading into a VMware renewal or a Cloud Foundation conversation and your current tools still need three weeks to turn a stay plan into a priced position, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let the vendor frame this as “a serious operator just committed for five years.” The right question is: what are we actually running, what does five years of VCF 9.0 cost against that estate, what does the rollout add, and what do we still pay AWS and Microsoft through the same window? That is a data question, not a sales question.
LSEG stayed. The price is undisclosed. Tesco, Western Union, and T-Mobile are the other headline. Neither headline is your license position. The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
