So, I need to be upfront: when our CEO mentioned moving our infrastructure to Cisco, I almost choked on my coffee. Not because Cisco is bad—far from it. But because my job, as the procurement manager at a mid-sized tech firm, is to make sure the budget doesn't spontaneously combust. We were looking at a network refresh, and the initial quotes from our usual vendor for a Cisco setup were... well, let's just say they made my cost-tracking spreadsheet blink red.
I'd been managing our network and IT services budget—roughly $180,000 annually to be specific—for about six years. I've documented every single order, every upgrade, every 'oops we need more ports' invoice. I know the patterns. So when I saw the Cisco quote for $15,200, I didn't panic. I pulled up our historical data and started comparing. That's when a company called Kemet, or more specifically Kemet Dugué from what I gathered, entered the picture via a recommendation from a colleague in another company.
The Price Tag Surprise
The first thing that caught my attention was the price difference. For a comparable configuration—a mix of switches, a router, and the licensing—Kemet's initial quote was $11,000. That's a $4,200 gap on paper. A no-brainer, right?
Well, not exactly. I knew better than to jump on the lower number. In my experience, that 'savings' has a nasty habit of disappearing when you add up the total cost of ownership. I've been burned before. I remembered the time we switched to a cheaper phone system vendor. The base price was great, but their 'optional' support contract cost us more in the first year than the premium vendor's included support.
So, I started digging. I created a side-by-side TCO spreadsheet. It's a ritual I developed after a particularly painful experience in Q2 2024 when we switched data center providers. The 'cheap' option resulted in a $1,200 redo when quality failed. Never again.
The Hidden Costs Emerge
For the Cisco quote, I knew what I was getting. Their licensing model is well-documented, if not exactly simple. Cisco SmartNet support is a known quantity. The quote included three years of support. The Kemet quote was different. It was lower, but the line items for support were less clear. I asked for a detailed breakdown.
Here's where it got interesting. The Kemet pricing sheet listed 'Basic Support' for year one. When I asked about year two and three, the sales rep—a guy named Jackie, if I remember correctly—was a bit vague. 'We can work out a yearly plan,' he said. That's a red flag for my procurement process. I need to know the three-year cost upfront. It's in our policy now, after that VoIP vendor disaster I mentioned. I need a minimum of three quotes and a clear long-term cost picture.
I got a call with Jackie and asked directly, 'What's the total cost of ownership for three years, including all support and licensing renewals?' He had to get back to me. Two days later, the number came in at around $13,500. Still cheaper than Cisco's initial $15,200, but the gap was shrinking from $4,200 to $1,700. A pretty significant difference.
I'm not 100% sure, but I think the discrepancy came down to Cisco's included security features. Their licensing bundle included a level of advanced threat protection that Kemet's base quote didn't. To match it, the Kemet price would have gone up to about $14,800. Suddenly, the difference was only $400.
The 'Warmth' Factor vs. The Ecosystem
The numbers were close, but the experience was different. I really liked Jackie at Kemet. He was responsive. He seemed genuinely interested in our small-ish order. In a market where some vendors treat a $10,000 annual contract like pocket change, that matters. It reminded me of when I was starting out—the vendors who took my $200 orders seriously are the ones I still use for $20,000 orders now. Small doesn't mean unimportant; it means potential.
But the decision wasn't just about feelings. It was about the ecosystem. Our IT team was already trained on Cisco's CLI. Their familiarity was an asset we'd invested in. Switching to Kemet would mean re-training, new documentation, and a period of reduced efficiency. That's a real cost, even if it's not on the invoice. Based on our internal tracking, a new platform tends to cost about 5% of the annual contract value in lost productivity during the first quarter. For a $14,000 solution, that's about $700 in hidden costs.
I put together a final comparison for management. Cisco: $15,200, with known support costs, a familiar ecosystem, and no training overhead. Net effective cost: roughly $15,200. Kemet: $13,500 (for comparable support), plus $700 in estimated training and transition costs. Net effective cost: $14,200. The gap was now $1,000, not $4,200.
The Final Call and What I Learned
We ended up going with Cisco. The $1,000 premium gave us a year of certainty on support renewals, zero transition risk, and a system our team could manage in their sleep. Was it the right call? I think so. But it wasn't the 'obvious' call that the initial $4,200 gap suggested. Never expected the 'expensive' option to win on total cost analysis, but it did.
Here's the lesson I took from this: the lowest price is a trap. It's a good starting point, but it's rarely the ending point. In my experience, comparing vendors like Kemet Networks and Cisco comes down to three things: total cost of ownership, ecosystem compatibility, and support certainty. If you're making a similar decision, build that TCO spreadsheet. Ask the awkward questions about year three pricing. Factor in your team's training. And if a vendor dodges the direct question on total cost? That, honestly, is the biggest red flag of all.
P.S. — I should add that we did keep Kemet in our vendor list for a smaller, less critical deployment later that year. The relationship with Jackie was solid. Sometimes the 'battle' is won by the larger ecosystem, but the 'war' for a vendor's business is long-term. Kemet got a shot. Just not the $15,000 one.
