Technology refresh cycles create natural decision points where organizations reconsider vendor relationships. Equipment reaching end of life forces purchasing decisions, and those moments often prompt questions: Should we stay with our current platform? Would switching vendors save money? Could we achieve better results with different technology?
These questions intensify when organizations face large-scale refreshes involving dozens of devices across multiple product categories. The capital expenditure feels substantial, renewal costs seem high, and vendors promoting “better value” alternatives create doubt about whether current infrastructure choices remain optimal.
A recent engagement with Andy Mohr Automotive Group illustrates this dynamic. The organization faced over forty Meraki appliances reaching end of life – a mix of switches and security appliances deployed across multiple dealership locations. Initial planning pointed toward a partial vendor migration: refresh aging Meraki firewalls while switching to third-party switches that appeared to offer lower initial costs.
This scenario plays out frequently in the networking industry. Organizations perceive cost savings in mixed-vendor approaches without fully accounting for hidden expenses, operational complexity, and lost integration value. But with thoughtful analysis comparing total cost of ownership rather than just hardware prices, many organizations discover that standardizing on a single platform delivers better financial and technical outcomes.
Through comprehensive evaluation of the technical implications, operational costs, and available pricing programs, Stratus Information Systems helped Andy Mohr understand the complete picture. By consolidating on Meraki equipment and leveraging a Meraki Enterprise Agreement, the organization not only refreshed all end-of-life equipment but achieved greater cost savings than the mixed-vendor approach while maintaining the operational simplicity that made Meraki attractive initially.
When dozens of network devices approach end of support simultaneously, organizations face compressed decision timelines and significant budget impact.
The Scale of the Challenge
Andy Mohr’s situation involved over forty devices across multiple product families:
These devices reaching end of life simultaneously reflected a deliberate deployment strategy from years earlier—a comprehensive network refresh that standardized the organization on Meraki across all locations. However, that coordination now meant the entire infrastructure required attention within a similar timeframe.
Financial Impact
Refreshing forty-plus devices represents substantial capital expenditure. Organizations naturally scrutinize spending at this scale, evaluating whether current vendors deserve continued business or whether competitors offer better value.
The reflexive assumption that mixing vendors saves money stems from comparing list prices on individual components. Third-party switches often advertise lower hardware costs than brand-name equivalents. Without accounting for licensing models, management complexity, and integration value, these comparisons seem to favor vendor diversification.
Operational Disruption Risk
Large-scale equipment refreshes also create operational risk. Coordinating installation across multiple locations, migrating configurations, and validating functionality requires careful planning. Organizations want to minimize disruption while ensuring refreshed infrastructure operates reliably.
Switching vendors mid-refresh amplifies these risks. Teams must learn new management interfaces, adapt to different configuration approaches, and troubleshoot integration between dissimilar platforms – all while maintaining business operations that depend on reliable network connectivity.
The appeal of mixing vendors stems from several perceived advantages that don’t always materialize in practice.
Apparent Cost Savings
Third-party network switches often show lower hardware prices than premium vendors. A direct price comparison between a commodity switch and a Meraki MS switch reveals a gap that seems to favor the lower-cost option.
However, this comparison typically omits several factors:
When accounting for total acquisition and operational costs over a three-to-five-year lifecycle, apparent hardware savings often diminish or disappear entirely.
Avoiding Vendor Lock-In
Some organizations view single-vendor networks as risky, believing diversification provides flexibility and negotiating leverage. This perspective assumes vendors extract premium pricing from captive customers unable to switch easily.
While vendor lock-in represents a legitimate concern in some technology categories, network infrastructure operates differently. Standards-based protocols mean switches and firewalls from different vendors can interoperate. Organizations aren’t technically locked in – they’re choosing integration value that multi-vendor environments sacrifice.
The flexibility to switch vendors exists whether or not you actually exercise it. Organizations gain little practical value from maintaining multi-vendor networks solely to preserve theoretical switching options they may never use.
Best of Breed Approach
The best-of-breed philosophy suggests selecting the optimal vendor for each infrastructure component rather than accepting compromise by standardizing on one platform. Organizations might choose Vendor A for switches, Vendor B for wireless, and Vendor C for security – each selection representing the “best” in its category.
This approach made more sense in earlier networking eras when integration between infrastructure components was limited. Modern networks integrate deeply-switches prioritize wireless traffic, firewalls reference user identity from authentication systems, and analytics correlate data across infrastructure layers. These integrations work more seamlessly within single-vendor platforms than across vendor boundaries.
Beyond initial hardware prices, multi-vendor networks create ongoing costs that aren’t always obvious during procurement.
Management Complexity
Each vendor provides different management interfaces with unique workflows, terminology, and capabilities. IT teams must learn and maintain expertise across multiple platforms rather than deepening knowledge of a single system.
This complexity manifests in several ways:
Integration Limitations
Networks function as systems, not collections of independent devices. Cisco Meraki’s unified platform provides tight integration between switches, wireless access points, and security appliances—all managed through a single dashboard with correlated visibility.
Mixed vendor environments lose this integration:
Support Complexity
When problems arise in single-vendor networks, one support organization handles the entire issue. Multi-vendor networks create finger-pointing scenarios where each vendor blames other components for problems.
An issue affecting application performance might involve switch QoS configuration, wireless channel interference, and firewall throughput. With Meraki managing all components, support teams address the complete environment. With mixed vendors, organizations coordinate between multiple support channels, each focusing only on their products.
Lifecycle Management Burden
Different vendors operate on different release cycles, support timelines, and end-of-life schedules. Managing mixed environments means tracking multiple product lifecycles, coordinating upgrades across platforms, and planning refreshes for different vendor equipment on different timelines.
Standardized environments simplify lifecycle management. Organizations track one vendor’s roadmap, plan refreshes on coordinated schedules, and maintain consistency across the infrastructure.
Cisco’s Meraki Enterprise Agreement (EA) addresses the cost concerns that drive organizations toward mixed vendor strategies while preserving single-platform benefits.
How Enterprise Agreements Work
Enterprise Agreements bundle licensing across an organization’s entire Meraki deployment—switches, wireless access points, security appliances, and cameras—under a single multi-year contract. Rather than purchasing licenses individually for each device, organizations commit to organization-wide licensing receiving volume discounts in return.
Key EA characteristics:
Financial Benefits
The cost advantage from EA pricing can be substantial. Organizations might see 20-40% savings on licensing costs compared to individual device purchases, with exact discounts varying based on deployment size and commitment terms.
For Andy Mohr’s forty-plus device deployment, EA pricing transformed the financial equation. What appeared as a costly Meraki-only refresh became more economical than mixing vendors when accounting for:
Operational Benefits
Beyond direct cost savings, EA structures simplify ongoing operations:
Simplified Renewals: Organizations renew the entire EA rather than tracking individual device licenses. Renewal conversations happen once every three or five years instead of managing continuous license expirations.
Budget Predictability: Multi-year EA commitments create known costs for the agreement duration. Organizations budget confidently without worrying about mid-term price increases or unexpected license expenses.
Organizational Flexibility: Adding devices to existing deployments doesn’t require new procurement processes. EA customers simply add licenses to their agreement at established pricing rather than negotiating individual purchases.
Understanding EA benefits provided the financial framework for equipment decisions, but the technical refresh strategy required thoughtful planning to maximize value.
Switch Modernization: MS220 to MS150
The MS220 switches reaching end of life represented Meraki’s previous-generation access switching platform. While these switches served the organization well, newer models offered improvements worth considering during the refresh.
Stratus recommended the MS150 series—Meraki’s recently released switch line providing:
The MS150 series also aligned well with Meraki’s product roadmap. Rather than deploying previous-generation equipment simply because it matched what was being replaced, the MS150 refresh positioned Andy Mohr’s infrastructure for the next refresh cycle.
Firewall Consolidation: Standardizing on MX95
The existing deployment mixed MX84 and MX100 security appliances matched to individual location requirements. Some dealerships needed the MX84’s capabilities while others required the MX100’s higher throughput.
However, this mix created operational complexity:
Stratus recommended standardizing on the MX95 – a model providing sufficient capacity for all locations including those previously using MX84s. This consolidation delivered several benefits:
Simplified Operations: IT teams manage one firewall model with consistent configuration, features, and troubleshooting approaches
Multi-Gigabit Throughput: The MX95’s capacity supports increasing bandwidth demands as automotive technology evolves and dealerships implement more connected systems
Deployment Flexibility: Standardized appliances simplify replacing failed units or reconfiguring site-to-site VPN meshes when locations change
Spare Parts Efficiency: Maintaining spares for one model costs less than covering multiple appliance types
Total Cost Analysis
The complete proposal included:
When compared against the original plan—mixing third-party switches with partial Meraki firewall renewal—the all-Meraki approach with EA pricing actually cost less while delivering:
Changing customer perspective from “Meraki seems expensive” to “comprehensive Meraki refresh is the best value” required demonstrating complete lifecycle economics.
Total Cost of Ownership Framework
The analysis compared five-year TCO across three scenarios:
Scenario A: Mixed vendor (third-party switches + Meraki firewalls)
Scenario B: Partial Meraki refresh without EA
Scenario C: Complete Meraki refresh with Enterprise Agreement (recommended)
The TCO analysis revealed Scenario C provided the lowest total cost over five years despite appearing more expensive when comparing only initial hardware prices. EA licensing discounts and reduced operational costs offset any hardware premium, while the organization gained superior equipment and operational benefits.
Technical Value Articulation
Beyond cost, the recommendation emphasized technical advantages:
Operational Continuity: Teams already proficient with Meraki management retain that expertise rather than learning new platforms
Integration Preservation: Analytics, troubleshooting, and automation capabilities that span switches and firewalls remain intact
Simplified Growth: Adding new locations or expanding existing sites uses familiar equipment and processes
Consistent Security Posture: Security policies apply uniformly across infrastructure without manual translation between different vendor platforms
Andy Mohr’s successful outcome depended on more than just understanding EA pricing—it required a partner willing to invest time in comprehensive analysis and negotiate on the customer’s behalf.
Beyond Transactional Sales
Commodity resellers process orders as submitted. If a customer requests third-party switches, they quote third-party switches. This approach seems responsive but often misses opportunities to serve customer interests better.
Consultative partners question underlying assumptions. “Why are you considering third-party switches?” leads to understanding customer motivations—usually cost concerns—which then enables addressing those concerns more effectively.
Pricing Strategy and Negotiation
EA pricing isn’t publicly published. Customers need partners who understand how to position EA opportunities with Cisco, structure proposals maximizing discount eligibility, and negotiate terms benefiting the organization.
Stratus worked with Cisco account teams to ensure Andy Mohr’s EA pricing reflected their deployment size, commitment terms, and specific requirements. This coordination resulted in pricing making the all-Meraki approach more economical than mixed-vendor alternatives.
Proposal Development
Presenting technical and financial analysis required creating comparative scenarios, TCO models, and clear articulation of trade-offs. Most organizations lack time or analytical resources to develop this depth of evaluation internally.
Partners providing strategic guidance rather than just equipment quotes enable informed decisions based on complete information rather than incomplete price comparisons.
The Andy Mohr refresh demonstrates principles applicable to any organization evaluating major network infrastructure decisions.
Evaluate Total Lifecycle Costs
Hardware prices represent a fraction of network infrastructure costs over typical 5-7 year lifecycles. Organizations should account for:
Vendors appearing cheaper on hardware may cost more overall when these factors are included.
Consider Operational Implications
Technical decisions create operational consequences lasting years. Mixed-vendor networks might save money initially but create ongoing complexity that consumes staff time and creates friction during troubleshooting.
Single-platform environments simplify operations, accelerate troubleshooting, and allow teams to develop deeper expertise rather than maintaining surface-level knowledge across multiple platforms.
Leverage Volume Programs
Organizations with significant infrastructure deployments should explore volume licensing programs like Meraki Enterprise Agreements. These programs often transform economics in ways that surprise organizations assuming enterprise pricing is out of reach.
Work with Strategic Partners
The difference between transactional resellers and strategic partners becomes most visible during complex refresh decisions. Partners willing to invest time in analysis, present alternatives, and negotiate on customer behalf deliver value beyond equipment supply.
For organizations evaluating network infrastructure refreshes, considering vendor changes, or wanting to understand whether Enterprise Agreement pricing might benefit their deployments, contact Stratus Information Systems to discuss your specific requirements. Our experience with Cisco security solutions and Meraki deployments helps organizations make infrastructure decisions balancing cost, capability, and operational simplicity.
Andy Mohr’s refresh achieved multiple objectives simultaneously: replacing end-of-life equipment, standardizing on superior hardware, maintaining operational simplicity, and reducing total cost compared to alternatives that initially seemed more economical.
This outcome wasn’t accidental-it resulted from comprehensive analysis, understanding complete cost structures, leveraging available pricing programs, and working with partners committed to long-term customer success rather than transaction volume.
Organizations facing similar refresh decisions benefit from questioning initial assumptions about vendor mixing and cost savings. Often the approach delivering best value combines equipment consolidation with strategic volume programs creating economics that commodity alternatives can’t match.
