How an MVNO Launched a Branded Calling App in Five Weeks, Not a Year
Talia's MVNO had subscribers, SIMs, and a brand, but every call showed the network she leased, not her name.
A branded calling app, live in five weeks, on her own roadmap instead of a vendor's.
Talia runs product at a data-only MVNO. That means her company sells phone plans and SIM cards under its own brand but rents the actual network from someone else.
It had subscribers, SIMs, a logo people recognized, and a wholesale deal with a real network underneath.
What it did not have was its own voice experience. Every call went through the phone's built-in dialer, so the underlying network's brand sat on the call screen, not Talia's.
So you needed a voice product. What did you do first?
I looked at what our wholesale switch vendor offered. They had a generic softphone bundled with the SIP trunk deal, free to plug in.
I almost took it. But it was not our brand, and it was not our roadmap. If we ever wanted to change how it worked, we would be filing a request into someone else's backlog. So we shelved it and looked at building our own app instead.
What was the breaking point?
The in-house build. I got the quotes: an iOS developer, an Android developer, App Store experience, push infrastructure, and then someone permanently on call for every OS update, because phones update and apps that do not keep up just stop working.
The number came back north of half a million dollars in year one. Realistically $500,000 to $1 million once you counted maintenance. And it was not one-time. It was a new team, forever, for a product that was supposed to be a bundled feature.
How did that feel? And commercially?
Like we were being punished for wanting to compete. We were not chasing the next big telecom innovation. We just wanted subscribers to see our name when they made a call.
The cost of waiting was real:
- We kept bundling data-only SIMs with no voice story.
- Competitors with an app-based brand picked off the customers who wanted one thing to open on their phone.
- We were stuck between a seven-figure build and a rented app with someone else's name on it.
Voice was the missing product
the built-in dialer showed the leased network's brand, not the MVNO's
In-house build quoted $500K to $1M
plus a permanent engineering team, for what should be a bundled feature
Launched on Cloud Softphone in 5 weeks
connected to the existing SIP backend; about $5K setup and $600/month
Voice became a real line of business
on the MVNO's timeline, not a vendor's backlog
What changed?
We found Cloud Softphone from Acrobits. What sold me was the math and the timeline together.
We connected it to the SIP backend we already had. No new infrastructure, no ripping out our wholesale voice trunks. Acrobits handled the App Store and Play Store submissions under our own developer account, so the listing was ours, but we did not have to learn the submission process.
From signing the deal to a fully branded app live on both stores took five weeks. Not five weeks to a demo. Five weeks to subscribers downloading it.
How they used Acrobits
Connected to the existing SIP backend. No rip-and-replace. Acrobits handled App Store and Play Store submission under the MVNO's own developer account.
The subscriber self-care portal went into a Web Tab. The web page where people already managed their account now lives inside the dialer. Balance and usage are right there, no separate login, no separate app.
Low-balance alerts fire as native badges via the IPC SDK. When a balance drops, the account portal triggers a real red badge on the app icon, the kind you get for a missed call. It feels like the phone is telling you, not a website. No native mobile code required.
If you had to teach this to someone, what is the one idea?
Unified communications happens in the UI, not in some server-room switch.
For a long time I thought "unified communications" meant a big enterprise phone system with a hundred backend features. It does not. It happens on the screen the subscriber is looking at: their balance, their usage, their calls, all in one place.
The mechanism is Web Tabs plus the IPC SDK. Once I understood that, our roadmap stopped being "what can we ask the vendor to build" and became "what do we already have that we can bring inside."
What they needed
- Voice under her own brand, not the leased network's, on the call screen
- To skip a $500K+ in-house build and a permanent phone team
- To plug into the SIP backend she already ran, with no rip-and-replace
- App Store and Play Store submission handled under her own developer account
- Active-user billing so dormant SIMs in a drawer cost nothing
Technical detail
Features that did the work
Web Tabs
the existing self-care portal renders as a native tab inside the dialer. Balance, usage, top-up, no second login.
IPC SDK
the portal inside that tab triggers native badges and notifications. A low balance buzzes like a real alert. Standard web code, native behavior.
White-label branding
the app and both store listings carry the MVNO's brand, not Acrobits'.
Active-user billing
pay for subscribers who register and place a call, so unactivated SIMs cost nothing.
Full-service publishing
Acrobits handles App Store and Play Store submission under the operator's own developer account.
And the business?
Voice stopped being the thing we were missing and became a real line of business.
The numbers:
- Launched in five weeks for about $5,000 setup and $600 a month to run.
- The in-house alternative was $500,000 to $1 million and a whole new engineering team.
- Active-user billing means voice costs scale with actual usage, not with how many SIMs we ever shipped. A promo that hands out ten thousand SIMs does not wreck our margins if half never activate.
And because the self-care portal and the low-balance alert run inside the app we already have, the next thing we add is on our timeline, not a vendor's backlog.
Don't spend a year and a seven-figure budget rebuilding something that already exists just to put your logo on it.
Rent the engine, own the brand and the roadmap, and let voice become a real line of business on your timeline instead of a vendor's.