I'm a site acquisition specialist at a mid-size telecom infrastructure company. I've managed roughly 80 small cell and rooftop lease negotiations over the past four years, including a rush deployment for a major sports venue where we had 10 days to secure permissions for 12 nodes. In my role coordinating site access for urban DAS and small cell projects, the one thing that consistently goes wrong—and I mean consistently—is the bandwidth clause.
The Surface Problem: 'My Speeds Don't Match the Lease'
The first call I get, 90% of the time, sounds like this: 'Our connectivity vendor says the site can only deliver 20 Mbps, but your lease agreement guarantees 100 Mbps. What gives?'
I get it. You signed a contract. It says 'dedicated 100 Mbps symmetrical throughput.' You're paying a premium—sometimes 30-40% more than a basic colo agreement—because that throughput is supposed to support your enterprise traffic, your video conferencing, your ERP system. And now you're stuck at 15 Mbps during peak hours.
My first instinct, honestly, used to be to blame the carrier. Last mile issues. Backhaul congestion. It's an easy out—and sometimes it's true. But over the last 18 months, I've started digging deeper into the lease documents themselves. And what I found? The problem isn't always the carrier. Sometimes it's the lease.
The Deep Cause: Three Things Nobody Checks in a Site Lease
Here's where I think the industry gets it wrong. We treat a site lease like a real estate document—square footage, access rights, termination clauses. But for a wireless site, the lease is the service agreement. And there are three things in almost every lease that create performance gaps.
1. 'Best Effort' Wording Masquerading as a Guarantee
I've reviewed leases from SBA Communications and other major tower companies where the bandwidth section says something like 'Provider will make reasonable efforts to deliver up to 100 Mbps throughput.' Legally, that's not a guarantee—it's a target. If you read the SLA attachments (if they even have them), you'll often find carve-outs for 'network congestion,' 'construction interference,' and 'acts of third-party backhaul providers.'
In March 2024, we were negotiating a 5-year renewal on a rooftop site in a dense urban market. The landlord's lease—drafted by their attorney, not a telecom specialist—said 'dedicated fiber connection with 1 Gbps capacity.' But the actual backhaul was a shared wireless link. (I've seen this pattern before, but the numbers still surprised me.) The capacity clause was, to put it politely, aspirational.
2. The 'Shared Infrastructure' Trap
This one is huge. Many site leases, especially on rooftops or in commercial buildings, have a clause that says the lessee (that's you) is sharing the antenna structure or the equipment enclosure with other tenants. The lease might say 'shared enclosure with adequate ventilation and power.' But what that means in practice: your radio is sitting 18 inches from another carrier's radio, both competing for the same cooling, the same grounding, and possibly the same backhaul aggregation point.
I can only speak to domestic operations here—if you're dealing with international logistics, the calculus might be different. But in U.S. markets, I've seen shared enclosures where the aggregate bandwidth demand was 3x the capacity of the incoming fiber. The lease didn't mention that.
3. The 'Phone' and 'Data' Definition Disconnect
Yes, the lease might literally reference 'phone' services. I'm not exaggerating. I have a lease on my desk right now—originally signed in 2018 for a PCS deployment—that defines 'communications equipment' as 'equipment used for the transmission of voice and data signals.' That's it. No throughput spec. No latency requirement. No mention of SLA.
When that lease was written, 'data' meant maybe 3G speeds. Today, we're asking that same site to support 5G NR, CBRS, and enterprise Wi-Fi offload. The lease doesn't—can't—cover that.
The Real Cost: Not Just Speed, But Credibility
People focus on the Mbps number. And sure, if you're paying for 100 Mbps and getting 15, that's a problem. But here's what I've learned from the 60+ site turn-ups I've been involved in: the hidden cost is the time you waste troubleshooting the wrong thing.
When a client calls me saying 'your site is slow,' my standard move is to check the backhaul first. Then the radio configuration. Then the interference profile. That process alone takes 4-6 hours of engineering time—billed at $150-$250/hour. And at the end of it, if the root cause is a lease clause that was never enforceable, I've burned $1,200 in labor and the client is no better off. They still have slow throughput, and now they're angry because they think we're incompetent.
Last quarter alone, we processed 17 site-related speed complaints. In about seven of those, the lease language was the primary issue—not the equipment, not the carrier. (I should add: those seven were all older leases, written before 2020. Newer SBA Communications standard leases are better, but the legacy ones are still out there.)
That $200 savings per month on a 'standard' lease vs. a premium one? If that standard lease doesn't have enforceable throughput language, you're going to spend that much on troubleshooting within the first three months. (Oh, and if you have to break the lease to move to a better site, the early termination fee alone can be $8,000-$15,000.)
The Fix: Three Things to Check Before You Sign (That Take 15 Minutes)
I'm not going to give you a 10-point checklist. That's what the lawyers are for. But based on my experience, if you check these three things before you sign a site lease—and I mean before you sign, not after—you'll avoid 80% of the problems I see.
1. Read the Bandwidth Clause—and the SLA Attachment
Don't just look for the number. Look for the words 'best effort,' 'reasonable,' 'subject to,' and 'material adverse change.' If any of those appear in the same paragraph as your 100 Mbps guarantee, that guarantee is soft. Ask for a hard SLA with a service credit if throughput drops below X% for more than Y minutes.
2. Get a Written Statement on Shared Infrastructure
This is the one nobody asks for. The lease might say 'shared enclosure' without specifying how many other tenants are allowed. What you want—what I always ask for now—is a written confirmation of the maximum number of tenants, the total aggregate backhaul capacity, and whether there's a dedicated path from your equipment to the demarcation point. (Actually, I should add: get the path in writing. I've seen situations where two carriers were sharing a single Category 6 cable run. That's a bottleneck.)
3. Future-Proof Your 'Phone' Definition
If your lease defines 'communications equipment' by a specific technology or service type, that's a red flag. You want a definition that says something like 'equipment used for the transmission of any form of electronic communication, including but not limited to voice, data, video, and IoT.' That covers you when the next generation of technology rolls out.
Yes, the landlord's attorney might push back. But I've used this exact language in three lease negotiations in the last year, and two of them accepted it without issue. The third asked for a cap on power draw—which is reasonable. (Note to self: I should write up that power clause template and share it.)
Conclusion: Your Lease Is a Service Contract. Treat It Like One.
We spend so much time on site selection, RF planning, and equipment specs. But the lease—the document that governs how your equipment connects to the world—often gets treated as a real estate formality. It's not.
In my view, the cheapest lease is almost never the most cost-effective. A standard lease with no SLA and vague throughput language might save you $500 a month on rent. But you'll lose that—and more—the first time you need to troubleshoot a speed issue that turns out to be a lease problem.
This approach worked for us, but our situation was a B2B company with predictable deployment patterns—mostly enterprise sites and venue coverage. If you're dealing with residential or temporary event deployments, the calculus might be different.