What It Really Takes for an ISP to Add Mobility
Should your ISP add mobility? Georgette Lopez-Aguado, Rick Seemann, and Larry Weidig talk through what it takes to become an MVNO, how deep to go into handsets and eSIM, why one bill matters, and why mobility earns its place through retention more than growth.
With Rick Seemann (VP of Product Management, Sonar Software), Larry Weidig and Georgette Lopez-Aguado
October 27, 2026 · 35:16 listen
Watch this episode
Watch it here, or listen in your app of choice.
Show notes
I was traveling in Puerto Rico when a carrier outage took out my phone. There are no payphones on the corner anymore.
I could borrow the hotel's phone, but if the person I needed to reach was on the same carrier, their phone was down too. I felt very isolated.
That's the lens I bring to a question many ISPs are asking right now: should we add mobility? In our latest Bandwidth Podcast episode, we dig into what it takes to become an MVNO. My short answer is that it's a customer relationship decision, not a network decision.
Customers judge the whole experience
Most customers couldn't tell you which carrier an MVNO rides on. They absolutely know whether they spent 45 minutes trying to activate their phone.
They judge you on five simple questions. Is it easy to buy? Does it work? Can I get help quickly? Do I get one bill? Do I trust you?
That's why I'd put the customer experience ahead of owning the network. You're not building towers. You're deciding whether to own another critical relationship, and for most of us, our phone is never far away, awake or asleep.
ISPs already have the hardest parts: the billing relationship, the customer's trust, local support, and technicians who walk into homes. Adding mobility expands a relationship you already have.
Mobility isn't an add-on
Expanding a relationship doesn't make it simple. Every product you add multiplies the provisioning headaches, support scenarios, training, vendors and customer expectations.
The biggest mistake is assuming mobility behaves like internet. It doesn't. People expect their phones to work everywhere, and their tolerance for downtime is much lower.
The details change too. Taxes, fees and filings for mobility aren't the same as for internet. Bringing a new internet customer over doesn't involve porting or regulatory tasks. Bringing a phone customer over does.
Rick said it plainly on the show: if you bring mobility into your catalog as an add-on, you're paving the road to failure.
How deep should you go?
Mobility runs as deep as you let it. It's a spectrum, and you can stop at any step:
- Resell wireless service and nothing else
- Bundle wireless with internet
- Add premium support
- Sell devices, with or without trade-ins, or let customers bring their own
- Offer international plans, or business mobility
- Become a full wireless retailer
Every layer adds operational complexity. So the real question is what business you want to be in.
Larry would stop short of handsets. Model lifespans are short, the cost is high, inventory is hard to manage, and theft and fraud come with the territory. eSIM is where he'd draw the line.
Rick would go as deep as he could automate: activation, number ports and plan changes, all self-serve in the customer portal. Different answers, same takeaway. You don't have to do everything.
One bill, one number to call
Nothing destroys a bundled experience faster than "call this other company" or "call this other department." The customer thinks: I bought this from you, so you own the problem, even if another carrier powers the network.
Billing is more emotional than we like to admit. Multiple invoices, confusing taxes, activation fees and different payment dates all chip away at trust. One clean monthly invoice tells customers they're dealing with one company.
There's a wrinkle, though. Rick told us about an operator who went the other way on purpose. As services were added, the total on the bill kept growing, and in that market customers started leaving once it passed a certain size. So they ran two brands, an ISP and a wireless company, out of the same location. Sisters, not twins.
I still vote for one bill. But it's a good reminder that none of this is one-size-fits-all.
Think retention first
Mobility probably won't be your growth engine. Margins are thin, and you're not competing with the national carriers' marketing budgets. Where it earns its place is retention.
People rarely switch internet providers over wireless alone, but they hesitate to leave when everything is bundled. Nobody wants to go from one bill to four, each prorated to a different date. You can buy acquisition. You can't buy retention.
Then comes the day a national carrier overbuilds you and offers free mobility for a year. My first thought is don't copy them. They play a different game with different economics, and they can subsidize what you can't.
Compete on local support, faster resolution, community involvement, install quality and trust. They may have deep pockets, but they don't have deep ties to your community. And if a customer only shops on price, it may be okay to let them go and focus on the ones who value service.
Be excellent at a few things
We went back and forth on whether ISPs should stop trying to become everything companies. Where I landed: operators have to keep evolving, because business models keep changing. But the brand has to stay coherent.
Ask what your customers already trust you to solve, and expand naturally from there. Be excellent at five products rather than mediocre at fifteen.
Mobility isn't really about adding another product. It's about deciding how much more of your customer's digital life you want to own. Each step deeper creates new chances to strengthen the relationship, and new operational responsibilities.
The winners won't be the ISPs with the longest feature list. They'll be the ones who deliver the easiest, most consistent customer experience.
Listen to the Full Episode
Catch the full conversation on the Bandwidth podcast.
Available now on Spotify, Apple Podcasts, and the Bandwidth YouTube Channel.
If you enjoyed this episode, be sure to subscribe wherever you get your podcasts so you never miss a conversation.
Questions, answered.
Should an ISP become an MVNO?
+
It depends on how much more of the customer relationship the ISP wants to own. ISPs already hold the billing relationship, trust, local support, and in-home technicians, so mobility extends a relationship they have. It also multiplies provisioning, support, training, vendors, and expectations, so it should not be treated as a simple add-on.
How deep should an ISP go into mobile service?
+
Mobility is a spectrum, from reselling wireless service to bundling, premium support, devices, international or business plans, and full wireless retail. Larry Weidig would stop short of handsets and draw the line at eSIM. Rick Seemann would go as deep as the ISP can automate activation, number ports, and plan changes through self-service.
Why is mobility harder than adding another internet product?
+
Customers expect phones to work everywhere and tolerate far less downtime. Mobility also brings number porting and regulatory tasks, and its taxes, fees, and filings differ from internet service.
Does unified billing matter for an ISP mobility bundle?
+
One clean monthly invoice tells customers they are dealing with one company, and multiple invoices and payment dates erode trust. Rick Seemann described an operator that ran separate ISP and wireless brands on purpose because customers in its market left once the combined bill grew too large, so the right answer can vary by market.
How should a regional ISP respond when a national carrier offers free mobility?
+
Do not copy the promotion. National carriers play a different game with different economics. Compete on local support, faster resolution, community involvement, install quality, and trust, and accept that customers who shop only on price may leave.
