Every channel partner makes the same decision over and over: build a capability in-house, buy it as a packaged product, or lean on a partner to deliver it. For most of the stack the instinct to build and own is the right one, because ownership is where control and margin live. For one capability it's a trap. International regulatory and compliance capability takes months or years to build, never really finishes because the rules keep moving, and carries a downside you can't recover from when you get it wrong. This playbook gives you a simple test for making the call on any capability, and shows why regulation fails that test as a build every time.
Why build, buy, or partner is a decision you make constantly
It's not a one-time architectural choice. Partners make this call continually, layer by layer, as the portfolio grows and the market shifts. Enterprise and SMB demands change fast, AI has landed on everyone's desk at once, and the partners who come out ahead are the ones acting as trusted advisors rather than reselling a box and waiting two years for the refresh. Deciding what to own and what to lean on others for is central to that role, not a distraction from it.
What should channel partners build and own themselves?
Start with what you should keep. The customer relationship is yours, and no model worth considering touches it: your contract, your account, your renewal. On top of that sit the things that make you valuable, the managed services you wrap around the connectivity, the advisory work, the sector knowledge, and the day-to-day support your customers chose you for. These are core to your value and stable enough to be worth owning. Build them, own them, and defend them.
Where does building it yourself go wrong?
The answer, almost every time, is regulation. Becoming a regulatory expert in every market you sell into is the build that looks reasonable on a slide and turns into a project with no end date.
The obligations also aren't where partners expect them. The common misconception in wholesale voice is that reselling keeps the regulatory burden with the carrier. In most markets the opposite is true: the moment you sell voice to an end customer, the regulator treats you as the service provider of record, and you inherit carrier-level obligations without a carrier-level compliance team. Three examples show how fast it adds up:
- Emergency services: A patchwork, not a single rule. The US, UK, EU markets, and Australia all mandate emergency access and caller location, each in its own way, and the obligation to get the caller found lands on you.
- Lawful intercept and KYC: Some markets won't let you go live without proving native intercept capability, and regulators increasingly hold every link in the chain accountable for a number. If you can't prove who your end customer is, the fraud becomes your enforcement action.
- Licensing and numbering: The one that catches partners out most often. Your provider's license often doesn't cover you, so you need your own registration, universal service contributions, and verified local addresses before a number can be allocated.
Two things make it worse: none of it holds still, so any expertise you build starts decaying immediately and keeping current becomes a permanent job. And doing it by the book, the licenses, the registrations, the local knowledge, takes months or years and real money that customers won't wait for.
Scaling internationally isn't a technical problem; it's a compliance and operations problem wearing a technical disguise. The trunks and the provisioning all work. What stops partners is the regulatory requirement they didn't know they needed.
The asymmetry of getting it wrong
Here's the part that should change the math. The cost of getting a capability wrong isn't the same across your stack, and regulation sits at the far end of it. Get the product wrong and you might annoy a customer, which is recoverable. Get regulation wrong and you can annoy a government, which is a different category of problem entirely. Because the downside isn't symmetrical, the build-versus-partner calculation can't be either.
Underneath sits a more general error: trying to be an expert at everything. A good MSP is excellent at certain things. Turning it into a regulatory expert to serve a subset of multinational customers is a large investment for a narrow use case, when it already leans on partners for plenty else. Regulation is where that logic applies with the most force.
The build, buy, or partner test
So how do you decide, for any capability, which of the three to choose? Three questions do most of the work.
1. Is it core to your value?
Does a customer choose you specifically because of this capability? If yes, it belongs in the build column. If a customer would never know or care whether you built it or sourced it, it's a candidate to buy or partner.
2. Is it stable, or does it change constantly?
Something stable enough to build once and maintain occasionally can be a sound investment. Something that changes on someone else's schedule is a moving target, and building it means a maintenance cost with no end.
3. What's the cost of getting it wrong, and is it recoverable?
Some mistakes cost you a renewal. Others cost you the right to operate. The less recoverable the downside, the stronger the case for a partner who does it full time.
Run those honestly and most capabilities sort themselves. Core, stable, and recoverable is yours to build. Commoditized, stable, and non-core is often cheapest to buy. Not core, always changing, and catastrophic to get wrong belongs with a partner.
Apply the test to international regulation and it fails all three at once: not core, constantly moving, and the least recoverable cost on the list. Three strikes. Regulation is not a build.
There's a clean field test, too. Before chasing a deal in a new market, ask the boring question: what does it actually take to operate there legally? If you can answer it, you can scale there. If you can't, you aren't live in that market, you're just exposed in it.
4. Does leaning on a partner mean losing control?
This is the objection that stops most partners, and it rests on a misunderstanding of what control is. Handing regulation to a partner doesn't mean handing over the customer. A co-sell model takes away the parts you were never really in control of anyway. The real loss of control is selling into a country whose rules you don't understand, where one change catches you out and you have no way to fix it. That's not a control problem, it's a risk problem, and owning a risk isn't the same as owning control. Framed that way, the arrangement reads as less risk, a faster route to market, and a lower cost to serve global customers.
What this looks like in practice
The pattern under all of this is simple: keep what makes you valuable, and hand off what would only ever be a liability to build. International regulation is the clearest thing to hand off, which means keeping the customer, the brand, and the relationship while a licensed carrier carries the regulatory and carrier-of-record load underneath. That's the model Pure IP runs with partners, structured around how involved you want to stay.
Run any capability through the same three questions and it sorts into one of three choices:
- Build: when it's core to your value, stable enough to maintain, and a mistake is recoverable. Example: the customer relationship, your managed services and advisory work.
- Buy: when it's useful and stable but not core, and a customer wouldn't know or care who made it. Example: commoditized tools and off-the-shelf products in your stack.
- Partner: when it's not core, it changes constantly, and getting it wrong is hard to recover from. Example: international regulatory and compliance capability.
If it's the capability you've been trying to build without ever finishing, explore the Channel Partner Program or talk to our team.
For a closer look at the regulatory traps behind all this, watch our on-demand session, Avoid Regulatory Pitfalls of International Wholesale Telecom.
