You Got the Low Price. Then the Bill Arrived.
I remember the email like it was yesterday. It was from a project manager, cc'ing my boss. The subject line was a single word: "Overbudget."
We had signed off on a purchase order for a batch of Adtran 624s and 916es—about 40 units, if I recall—for a major fiber extension project. The quote from Vendor A was roughly 12% less than the incumbent. On paper, it was a win. My boss was happy. I felt good about the negotiation.
Then the invoices started rolling in.
The line items for "configuration service," "expedited shipping for the 854-v6 (which wasn't in the original scope but was 'necessary')," and a restocking fee for a single ONT we ordered by mistake added up to a figure that made the original 12% saving look like a rounding error.
I'm not 100% sure of the exact final number without digging through the system, but I remember that the 'budget vendor' choice ended up costing us about 4% more than if we'd just gone with the established supplier. It was a classic case of being penny-wise and pound-foolish.
The Problem Isn't Price. It's TCO.
Most buyers—especially on the engineering side—focus on the unit price of a router, switch, or 211 Desktop ONT. They get a spreadsheet with three columns: Vendor, Model, Price. They sort by price ascending. They pick the cheapest.
That's the surface problem. The surface problem is that we treat network equipment like a commodity.
But the deeper problem—the one that keeps procurement managers like me up at night—is that we often don't have a system to measure the real cost. We don’t have a way to track the cost of a failed ONT installation, the hours spent troubleshooting interoperability between an old Adtran MX2800 and a new switch, or the downtime caused by a config error we paid the vendor to prevent.
The question everyone asks is, "What's your best price on the Adtran 8110?" The question they should ask is, "What's the total cost of owning this device for three years, including support, training, and the risk of a truck roll?"
The Hidden Cost of 'Free' Support
Let me give you a specific example from my notes. In Q2 2024, we were comparing two vendors for a small batch of Adtran TA908e VOIP gateways. Vendor A gave us a hard quote: $2,100 per unit, with a $4,200 annual support contract. Vendor B quoted $1,850 per unit, with "free" setup and no mention of a support contract in the proposal.
I almost went with Vendor B. On the surface, saving $250 per unit and getting free setup? It's a no-brainer, right?
But I made a call to the Vendor B's sales engineer. Not to negotiate, but to ask a simple question: "If the device bricks, who do I call, and what's the hourly rate?" The answer was $175/hour for a remote engineer, with a 4-hour minimum. The 'free setup' was for a basic config, not the MPLS integration we needed.
I calculated the TCO over 3 years for 10 units. Vendor A: $25,200 (hardware + support). Vendor B: $18,500 (hardware only) + potential support costs that could easily hit $2,500 to $7,000, depending on issues. The risk profile for Vendor B was unacceptably high.
I told the engineering team, “I know Vendor A looks expensive. But their support contract caps our risk. With Vendor B, we have no cap.”
The Danger of the 'One-Stop Shop' Myth
This is where my perspective on expertise comes in. I've dealt with plenty of vendors who claim they can do everything—fiber access, routing, switching, VoIP, even the cabling. I'm naturally skeptical of this.
A vendor who says, "We can handle all your Adtran needs plus your Cisco core switching" might be great at one but mediocre at the other. I'd rather work with a specialist who knows the Adtran 916e inside out than a generalist who can sell it but can't configure it.
The vendor who once told me, "This optical transport project isn't our strength—here's a specialist who does it better" earned my trust for everything else. That honesty is rare, and it's valuable.
So, What's the Real Solution?
I don't have a magic bullet. But after tracking hundreds of orders over six years, I've developed a simple framework for buying network gear. It's not rocket science, but it works:
- Define the full scope before you get a price. Don't just say "I need an Adtran 624." Say "I need an Adtran 624 configured for MPLS with a 3-year NBD support contract and on-site installation within 30 days." This reduces scope creep and hidden fees.
- Build a TCO calculator. Don't just compare the hardware price. Include support, training (if needed), shipping, and a cost for expected downtime. Give it a risk weighting.
- Ask the 'dumb' questions. When you're negotiating, ask: "What's not included in this price?" The silence is often very telling.
- Trust your gut on the relationship. If a sales engineer is evasive about how they handle a catastrophic failure, that's a red flag. Price doesn't matter if the network is down.
This isn't about Adtran. It's about how we buy. But Adtran's broad portfolio—from the 211 Desktop ONT to the high-end MX2800—means you'll often have multiple sourcing options. The key is to make sure the option you pick doesn't come with a hidden bill. In my experience, the best vendors are the ones who help you avoid surprises, not the ones who offer the lowest initial price.
