The News
RapidScale, represented by Field Chief Revenue Officer Jaime Konzelman, joined the AppDevANGLE podcast to discuss the cascading effects of Broadcom’s acquisition of VMware on enterprise infrastructure strategy. The conversation covered the dramatic contraction of the VMware partner ecosystem (from over 4,000 partners to roughly 126 worldwide), the total cost of ownership realities enterprises face when evaluating migration, and how VMware Cloud Foundation 9 is repositioning private cloud as a credible platform for both application modernization and AI workloads. The discussion also addressed what genuine AI-ready infrastructure looks like in practice and why reactive migration decisions driven by licensing sticker shock tend to produce worse outcomes than deliberate, portfolio-level planning.
Analyst Take
The partner collapse is a procurement crisis, not just a vendor story
Three years into Broadcom’s ownership of VMware, the narrative has shifted. The initial shock of SKU consolidation and licensing price increases has given way to something more operationally consequential: enterprises are discovering mid-cycle that the partner they built a procurement relationship with no longer exists inside the program. Moving from 4,000+ partners to 126 is not a trimming exercise; it’s a structural reorganization of how VMware reaches the market. For ITDMs, this is a supply chain problem disguised as a software licensing problem. The instinct to shop for alternatives based on invoice delta is understandable but incomplete. The real cost exposure lives downstream: refactoring, reskilling, application dependency mapping, and operational continuity risk during transition.
ECI Research data reinforces this directly. According to ECI Research’s Google GovTech Survey, 32.6% of respondents selected “Total Cost of Ownership (Upfront pricing, long-term maintenance costs, and consumption predictability)” as the factor that carries the greatest weight in their final technical selection process. That’s the single largest response in the category, and it’s consistent with what RapidScale is encountering in the field: customers who led with license cost comparisons and then had to walk back to a full TCO model when the hidden costs surfaced. The software line item is visible. The operational debt from a poorly sequenced migration is not, at least not until it’s too late.
Migration timelines make the math uncomfortable fast
Konzelman’s framing of credible VMware migration as “an application portfolio program, not a hypervisor swap” is analytically sound and frequently ignored. Moving a workload is not the same as modernizing it. Relocating complexity to a different substrate without addressing the application layer simply changes the cost center without resolving the underlying risk. For developers and platform engineers, this is the distinction that matters most: a lift-and-shift preserves the technical debt while adding migration overhead, whereas a refactor-in-place strategy using VCF9’s Tanzu capabilities creates conditions for genuine modernization.
The timeline math is sobering. ECI Research’s Google GovTech Survey found that 40.1% of respondents selected “13 to 24 months” as the average timeline required to completely modernize a single high-priority legacy application. Enterprises running hundreds of VMware-dependent workloads should be doing that math explicitly before committing to an exit strategy driven primarily by licensing frustration. The wave-based approach RapidScale describes, starting with lower-risk workloads to validate performance and data integrity before committing to a full migration, is the operationally defensible posture precisely because it acknowledges that timeline reality.
VCF9 and the collision of infrastructure and platform engineering
The more strategically interesting part of this conversation is VCF9’s positioning at the intersection of infrastructure management and application platform engineering. The integration of Spring lifecycle management and Tanzu into the core bundle is a deliberate attempt to collapse the organizational boundary between the team that keeps the lights on and the team that ships software. Konzelman’s observation that organizations using VCF9 can now scan Spring environments, automate patching, and manage application lifecycle from the same platform they use for compute and storage is a meaningful capability shift, and one that most enterprises haven’t fully inventoried against what’s already in their bundle.
For platform engineers and DevOps teams, this matters because infrastructure provisioning remains a persistent drag on developer productivity. The visibility problem is real too: ECI Research’s Google GovTech Survey found that 55.2% of respondents selected “Partial visibility (Deployment frequency is tracked, but lead time or MTTR is not)” when asked how much visibility development leaders have into developer productivity metrics. Better platform integration doesn’t automatically fix that measurement gap, but it creates the architectural conditions under which instrumentation becomes tractable. That’s the honest version of the VCF9 value proposition: not that it solves developer productivity, but that it removes a category of structural friction that has been blocking progress.
AI infrastructure is where the real stakes appear
The closing section of the conversation is where the strategic stakes clarify. Konzelman’s framing of AI readiness as the ability to “run production AI securely, economically, and as close to the data as possible” is a defensible definition. The private cloud argument for AI workloads rests on three factors: data locality (inference quality degrades with data movement), GPU utilization economics (stranded acceleration in public cloud is expensive), and security posture (regulated workloads require control over where model weights and training data reside).
The demand signal for AI-assisted development is already substantial. According to ECI Research’s Google GovTech Survey, 49.6% of respondents selected “26% to 50%” when asked what percentage of their organization’s code they expect will be assisted or generated by AI within the next 12 months. That level of AI integration into the software delivery lifecycle creates a direct infrastructure dependency: the teams writing AI-assisted code need inference capacity that is predictable, compliant, and economically sustainable at production scale. Enterprises that make their VMware migration decision without modeling that AI infrastructure requirement are optimizing for a cost structure that will look different in 18 months.
Looking Ahead
The VMware partner consolidation story will continue to generate enterprise urgency through 2026 and into 2027 as multi-year contracts expire and organizations that deferred the migration decision are forced to act. RapidScale’s position as one of roughly 126 remaining managed services partners gives it a structural advantage in a market where validated expertise is now genuinely scarce. The firms that win in this environment will be the ones that lead with portfolio-level discovery and TCO modeling rather than hypervisor replacement pitches, because that’s the conversation enterprises actually need to have.
The longer-term signal here is the convergence of infrastructure platforms and application modernization tooling. VCF9’s direction is not unique to VMware; every major infrastructure vendor is making a version of this bet. What’s distinctive is the depth of existing enterprise lock-in that gives VMware a captive audience for that value proposition. Enterprises that engage seriously with the full VCF9 capability set, rather than treating it as a cost-center line item, are likely to find that the modernization runway is longer and more productive than the alternatives suggest. The organizations that don’t will spend the next several years paying for migrations that don’t actually reduce their operational complexity.
Stay Ahead of Application Development Trends
Get weekly analyst insights, research notes, event coverage, and AppDevANGLE updates delivered directly to your inbox.
Subscribe for Weekly Insights
Join technology leaders, practitioners, and GTM teams following the trends shaping modern software delivery.
Looking for deeper research access?
Explore ECI Research reports, survey insights, and market analysis through the ECI Research Portal.
