← Back to Blog Friday 13th of November 2026

The Cheapest Cable Bid Cost Us $3,100 More. Here's the TCO Math.

The short version

We approved the Nexans copper bid that was $2,300 higher than the lowest quote. The project still came in $200 under budget. The "cheaper" bid would have cost us around $3,100 in rework, testing, and two extra days of lost connectivity on the third floor. That's the whole story in two sentences.

If you take one thing from this: per-foot cable pricing is not the price of the project. The number on the quote is the start of the math, not the end of it.

I'm not a network engineer. I'm the person who signs the purchase orders. That's exactly why the gap between "quoted" and "actual" caught my attention—my job is to explain to finance why the number moved. Simple, really. Except when it isn't.

Who I am, and why I'm writing this

Office administrator for a 280-person company across three locations. I've managed facilities and office-supply ordering since 2021—roughly $120,000 annually across about a dozen vendors, north of 70 orders a year. I report to operations and to finance, which means I get to explain both the good numbers and the bad ones.

In October 2024, our operations director asked me to support a cabling refresh in two buildings: 60 drops, a mix of Cat6a copper on the horizontal runs and a few fiber runs for the backbone. He forwarded two contractor bids. One used Nexans copper cable. The other used a cheaper brand I'll just call Vendor B.

The difference on the first page: about $2,300. That's the number I had to defend internally. That's the number I picked wrong the first time.

The $2,300 mistake, itemized

We went with Vendor B initially. I thought that was the responsible call—lower quote, matching specs on paper, and the contractor had done decent work for us on smaller jobs. I signed it mid-October.

Cable arrived. Installer started pulling. Two days in, the crew's multimeter flagged a high-resistance run on the second floor. Then another. Then a third. The crew blamed the batch. Vendor B blamed the terminations. We burned six working days—no, seven, I'd have to check the email thread—arguing about which one was right.

What nobody told me: the crew was using a $45 bargain multimeter for quick checks (this was late 2024, the kind you buy at a hardware store). It passed the cable at the spool and failed it at the run. We couldn't trust either reading, so I approved $380 for a calibrated tester and we re-tested all 22 suspect runs. That's when we found the real problem. The "Cat6a" in Vendor B's spec sheet didn't match the Cat6a we were expecting. Same label, different conductor gauge, different performance on long runs. I assumed "Cat6a" meant the same thing across vendors. Didn't verify. Turned out it didn't.

End result: ripping out 22 drops, reordering cable, two extra install days, and about $3,100 in costs that never appeared on the original quote. I ate the overtime out of my department budget. I still kick myself for not asking both contractors for the actual manufacturer spec sheet and a signed test report before signing. If I'd done that, we'd have saved six weeks of arguing.

One more detail, because it matters: the installer was "flexible." What I mean is, they showed up when it was convenient for them, not when the schedule needed them. Flexibility, in a cabling project, is a cost line.

What the TCO comparison actually showed

After Vendor B failed, I went back to the second bid—the one that used Nexans copper cable—and asked them to justify the $2,300 gap line by line. Their answer wasn't a sales pitch. It was a list:

  • Pre-terminated lengths measured on site, so the crew wasn't cutting and crimping on ladders
  • Signed test reports per run
  • A compatibility check against our existing patch panels and switches before the first pull
  • A four-hour callback window if any run failed testing

We approved it. The install finished in two days with no failed runs. The callback never happened. The final invoice came in $200 under the quote, because the contractor used shorter run lengths than the estimate assumed.

That's the TCO argument in one paragraph: the higher unit price bought me a shorter project, fewer surprises, and a number I didn't have to defend to my operations director twice.

Not obvious until you've been burned by the other option. After that, it's obvious.

The questions I had to field (and one that made me laugh)

"Why not Nexans superconducting cable?"

A colleague in R&D forwarded me a press release about Nexans superconducting cable and asked why we didn't "just use the best." I had to explain that superconducting cable is a grid-scale and industrial product—cryogenic cooling, substation-grade infrastructure, lead times measured in quarters, not weeks. It's not a drop-in for a 60-run office refresh. It's not even in the same procurement category. Good technology, wrong project.

"Nexans vs Broadcom"—is that a real comparison?

Another manager sent me a comparison article with roughly that title and asked me to "look into it." I had to point out that Nexans makes cable and Broadcom makes semiconductors. One is the road, the other is the engine. The only reason it's worth mentioning is that these things circulate in office email threads and eventually reach whoever signs the purchase orders. Now I have a stock reply: different category, different budget line, no decision to make on my end.

The n93 request

One Friday afternoon, a facilities request landed in my inbox: "Order n93-compatible cables for the third-floor conference room." I spent 40 minutes on supplier sites before walking down the hall to ask what n93 actually was. It was the Nokia n93—a phone we stopped using years ago—still sitting in a storage closet. I bought a $12 charger cable from a local shop and moved on. I mention it only because this is what half my purchasing day actually looks like. The other half is the $14,000 cable project.

When the cheap option is actually fine

I don't want to overcorrect. Some projects don't justify TCO analysis. If you're buying 10 patch cables for a small office, buy the cheap ones and don't think twice. Standard runs, standard terminations, low stakes—the cheapest option is usually the right one.

The TCO logic kicks in when three things are true at once: the project is hard to redo (in-wall cable), the failure is hard to diagnose (long runs, mixed equipment), and the consequence is visible (staff without network, a director asking why the schedule slipped). My $14,000 project hit all three. Your 10-cable order doesn't.

One caveat I learned the hard way: the "expensive" contractor isn't automatically the reliable one. In our case, the Nexans bid was reliable because they documented every run—not because the brand on the box was premium. If I'd switched to the higher bid without demanding the test reports and spec sheets, I'd have paid more for the same risk. The documents were the TCO, not the logo.

Now I keep a four-line checklist before signing any vendor bid over $5,000: manufacturer spec sheet, test report commitment, callback window, signed change-order process. Four lines. Takes ten minutes (note to self: do it every time, not just when you remember). Saves the kind of six-week mess I just described.

Anyway—worth the ten minutes.

Leave a Reply