Here is a deal that almost died for the wrong reason.
The customer said, “We need Hyper-V.” The partner logged it as a technical requirement, qualified the opportunity out of any VMware conversation, and moved on. Reasonable enough. That is what a stated requirement is supposed to mean.
Except it was not technical. When someone finally asked why Hyper-V, the answer had nothing to do with the hypervisor. The customer had priced VMware Cloud Foundation, run into the 72-core minimum, and done the math against an environment that needed a fraction of that. They were not making a platform decision. They were making a licensing decision; about a license they were never going to have to buy.
That deal was recoverable. A lot of them are right now, for the same reason: the way this infrastructure gets bought has changed, and customer assumptions have not caught up.
What it costs you to take the requirement at face value
Disqualifying a VMware-anxious customer is not a neutral act. A hypervisor question is almost always the front door to a much larger infrastructure conversation, and everything behind that door leaves with the deal:
- Managed cloud, sized to the workload they actually have
- Backup and DR, usually the easiest second yes
- Managed network attach, from monitoring or managed firewall through full SD-WAN
- A multi-year recurring relationship instead of a one-time migration project
For a broker, that is the difference between a single transaction and a compounding commission stream. For a VAR, it is the difference between a refresh cycle and an annuity. Either way, the customer who says “we need Hyper-V” is not telling you they have no budget. They are telling you they are afraid of a number, and only one of those ends the conversation.
Three questions before you disqualify
You do not need to be an engineer to run these.
- Is this a true technical dependency? Rarely, and when it is, it usually points back at VMware rather than away from it. Applications get built and certified against VMware or a public cloud provider, because that is where the install base is. A hard dependency on some other hypervisor is uncommon enough to treat as a flag rather than a fact. Ask what specifically breaks. If the customer can name the application, the vendor, and the certification, you have a real constraint. If the answer is vague, you have just found the actual conversation.
- Is this a cost, licensing, or commitment concern? Most of the time, yes. Worry about over-committing to core minimums, about renewal exposure, about what happens at true-up. That is a conversation we have a direct answer for.
- Where did this requirement come from? Headlines and hallway conversations shape assumptions fast, and not always accurately. If the requirement traces back to something the customer read rather than something they priced, there is room to correct the record without arguing with them.
None of that is a rebuttal. It is discovery. You are not telling the customer they are wrong, you are finding out what they are actually solving for. Below are the three assumptions those questions surface most often.
Assumption 1: the 72-core minimum applies here
Be precise on this one, because your customer will check. If they are buying VMware Cloud Foundation licensing, the 72-core minimum is real. Telling them otherwise costs you credibility the first time they verify it.
Here is what they are missing. With 11:11 Managed Cloud, your customer is not buying VMware licensing at all. It is bundled into the infrastructure they consume. There is no license SKU for them to hit a minimum on, because they are not the licensee. We are. What they buy instead is a pool of resources sized to the environment they actually have. If that is 8 vCPU, 32 GB of RAM, and 1 TB of storage, that is what they buy.
The customer is not wrong about the minimum. They are wrong about which purchase they are making.
Assumption 2: DR is cheaper to keep in house
Ask what their DR environment costs. Most will give you a number that stopped being accurate years ago.
Running your own recovery site means paying for a second environment: hardware, colocation, power, hypervisor licensing, and the staff time to keep replication healthy and actually run the test failovers. That used to be the cheap part. Many customers already owned perpetual vSphere licenses and paid maintenance for support, so the recovery site largely rode along on what they had already bought.
Not anymore. The secondary environment now gets licensed from scratch and licensed like production, for infrastructure that sits idle waiting for a bad day.
From 11:11, the customer buys replication licensing and consumed storage. That is the bill. No second set of hardware, no colocation footprint, no power draw, no hypervisor licensing on the target side, and the replication health checks and test cycles are our job rather than an FTE’s. This is one of the rare cases where a fully managed service lands under do-it-yourself on hard costs alone. Most customers have never run that comparison, because until recently nothing forced them to.
Assumption 3: VMware must cost more
This is the belief sitting underneath the other two, and it is flatly untrue. 11:11 lowered our pricing after the 2024 changes. Not held it, lowered it.
Hardware scarcity pushes the math further in the same direction. Every do-it-yourself alternative starts with buying equipment in a market where lead times and pricing are both moving targets. A consumption model carries none of that exposure. No purchase order, no lead time, no risk that the refresh scoped in the first quarter costs materially more by the third.
A recent comparison on an 84-VM environment, five-year TCO, hard costs only, no soft-dollar arguments about staff time:
- The do-it-yourself Nutanix option came in roughly $250,000 higher than the 11:11 IaaS option.
- The public cloud option was eliminated first. Production alone priced at double the 11:11 IaaS cost, before anyone reached the question of whether the applications were tuned to run there.
That second point is worth sitting with. Public cloud gets pitched as the obvious destination for an environment coming off VMware, but plenty of these workloads are not ready for it and the applications were never designed for it. Results vary by environment, but the assumption that VMware is automatically the expensive option does not survive a direct comparison.
Gartner’s work on mid-market CIOs evaluating VMware alternatives lines up with what we see in the field. They are shopping on affordability, migration effort, existing skills, ISV support, operational efficiency, and backup compatibility. That is the checklist running in your customer’s head, and it maps almost line for line to what 11:11 Managed Cloud delivers.
Bring it to us before you walk
11:11 has acquired seven VMware CSPs, is the current VMware CSP of the Year, and has more than doubled its VMware core count since 2024, while a good part of the market moved the other direction. We did not back away from VMware when it got complicated.
So, if VMware licensing or cost assumptions are showing up in your customer conversations, get your 11:11 channel manager on the phone before you disqualify the opportunity. We will work through the platform specifics, the licensing questions, and whether Managed Cloud is the right fit. Worst case, you confirm the requirement was real. Best case, you just saved a deal you were about to give away.
FAQ
Why are customers moving away from VMware right now?
Licensing and pricing changes have prompted a lot of organizations to reassess their infrastructure strategy. Gartner finds that CIOs evaluating alternatives are driven mainly by cost, migration effort, ISV ecosystem compatibility, and operational efficiency. Most of those concerns are about terms, not about the technology.
Does the 72-core VMware minimum apply to 11:11 Managed Cloud?
No. The 72-core minimum is a real term of VMware Cloud Foundation licensing and applies if your customer buys VCF licenses directly. With 11:11 Managed Cloud they are not buying VMware licensing at all. It is bundled into the infrastructure they consume, and they buy a resource pool sized to their environment with no core floor.
My customer says they need Hyper-V. How should I handle it?
Ask what specifically breaks on VMware. Real hypervisor dependencies are uncommon, and when they exist they tend to point toward VMware rather than away from it, since VMware and the major public clouds are what ISVs certify against. If the customer cannot name the application and the certification behind the requirement, it is almost certainly about cost, licensing, or familiarity.
Why would managed DR cost less than a customer running their own recovery site?
The cost structures are not comparable. A self-managed DR site carries hardware, colocation, power, hypervisor licensing for the secondary environment, and staff time to maintain replication and run tests. With 11:11 the customer buys replication licensing and consumed storage, and the management is included. Licensing changes have made that secondary environment considerably more expensive to stand up alone than it was under the perpetual-license model most customers budgeted against.
Is VMware more expensive than the alternatives?
Not as an IaaS consumption model. 11:11 lowered pricing following the 2024 changes, and in a recent five-year TCO comparison on an 84-VM environment using hard costs only, the do-it-yourself option came in about $250,000 higher and public cloud priced at roughly double for production alone. Results vary by environment.
Who do I contact with VMware questions on a specific account?
Your 11:11 channel manager. We can work through platform specifics, address licensing assumptions, and help you figure out whether Managed Cloud fits the account.
