VoIP
Why the platform behind your voice service matters more than you think
Why the platform behind your voice service matters more than you think
If you’re already reselling hosted voice to your customers, you’re ahead of most Print IT businesses in the UK. Our research found that only 26% of companies in your sector currently offer voice services, so just being in the market puts you in the minority.
But here’s the question worth asking: how much do you actually know about the platform powering what you sell?
For most resellers, the honest answer is: not much. And that’s not a criticism, it’s how the market was designed. The traditional model is that you sign up as a partner, get a portal, learn how to provision users, and off you go. What’s happening underneath is largely invisible.
The problem is that what’s happening underneath matters quite a lot.
Most platforms are built on the same foundations
Here’s something worth knowing about the hosted voice market: despite the appearance of choice, the vast majority of platforms available to resellers are built on the same open-source codebases. Asterisk and FreeSWITCH are the two most common. They’re free, widely used, and have been the engine room of VoIP for decades.
That shared foundation means that most platforms, whatever logo is on the front, share the same core architecture, the same limitations, and the same points of failure. If your current platform is built on open-source components, there’s a high chance the product you’re reselling is architecturally almost identical to the alternatives sitting in your competitor’s portfolio.
This matters for three reasons.
Resilience
In a traditional VoIP architecture built on open-source components, when a call is made, it gets bound to a specific server. If that server has a problem mid-call, the call drops. The user can’t even hang up cleanly.
Most providers paper over this with redundancy arrangements, multiple servers and failover protocols, but the underlying fragility remains. The call is still tied to a server at the point of establishment. True distribution, where the call can survive the failure of any single node without the user noticing, requires owning and controlling the code at a fundamental level. That’s not possible when you’re building on top of code you didn’t write and can’t modify at will.
Innovation speed
Open-source platforms evolve on their own schedule. When a provider builds on top of open-source code, any changes they make to the codebase have to be maintained across every subsequent version of that upstream code. New features are added, old bugs are fixed, the codebase shifts, and any customisation the provider has made is at risk of breaking.
The practical result is that providers using open-source foundations are slower to innovate. Adding new features is more complex, more risky, and more expensive than it would be for a platform built entirely in-house. The people who wrote the underlying code aren’t the people maintaining the product layer on top of it.
If the platform you’re selling is built on open-source foundations, you’re reselling a product whose evolution is constrained by code your supplier doesn’t control.
What this means for you as a reseller
If the platform you’re selling is built on open-source foundations, you’re reselling a product whose evolution is constrained by code your supplier doesn’t control. That affects your ability to differentiate, your customers’ experience, and ultimately your retention rates.
The alternative, platforms built entirely on proprietary code, owned end to end, are in a small minority. But they exist. And the difference is measurable: faster feature development, genuine fault tolerance, and a support team that actually understands every line of the product they’re backing.
When you’re choosing who to partner with for voice services, the architecture question is worth asking. Not because the answer is complicated, but because it clarifies very quickly who is genuinely building something and who is repackaging someone else’s work.
Want to understand what’s powering your current voice platform? Or explore what a proprietary alternative looks like in practice? We’re happy to walk you through it.
