Why a Regional Voice Reseller Stopped Owning the Plumbing
Marco runs a regional voice company on an open-source app that had become a second job.
Marco stopped selling a phone app and started selling outcomes.
Marco runs a regional voice company. Nothing glamorous. He sells phone service to dentists, law offices, a logistics firm, a couple of call centers.
For years his edge was simple: he knew his customers by name, and he made their phones work.
Then the world moved to apps. His customers stopped asking for desk phones and started asking for an app on their staff's mobiles, with their own logo on it. Marco said yes, because saying yes is how he had always grown.
That yes is where the story starts.
So you needed an app. What did you do first?
I took an open-source app. Free, open, "you control it." That last part is a joke.
Within three months I had a developer on retainer just to keep it alive. Every time Apple or Google changed something, the app broke, and the breakage was my problem at two in the morning.
I thought I was buying control. I bought a second job.
What was the breaking point?
My best customer, the logistics company, called. They had just bought an AI tool that routes their drivers, and they loved it. They asked: "Marco, can you put this inside the phone app, so dispatchers see it while they are on calls?"
I had to say no. My app had no room for it. And the vendor I leaned on had a roadmap, and my customer's request was not on it. Maybe in two years.
How did that feel? And commercially?
Like I did not own my own business. I was the face to the customer, but a vendor held the pen on my product's future.
And the numbers were worse:
- The app was a cost line, not a growth driver.
- It kept existing customers slightly happier. It won me nothing new.
- To a buyer, it looked like a liability, not an asset.
Open-source app became a second job
developer on retainer, 2 a.m. outages every time Apple or Google shipped an update
Best customer wanted an AI dispatch tool in the app
vendor roadmap said maybe in two years
Switched to Cloud Softphone
reliability became the floor; Web Tabs and the IPC SDK unlocked customer-specific integrations in an afternoon
App went from cost line to highest-margin product
about a coffee per user per year; the asset, not the liability
What changed?
I found Acrobits Cloud Softphone. The first thing that struck me was not a feature. It just worked.
Think about a faucet. You do not think about your faucet. You open the tap, water comes out.
Acrobits carries the hard part underneath: the audio, the video, the engineering that makes a call connect on a thousand different phones and networks. So I stopped firefighting.
Reliability is not a feature. It is the floor you stand on.
How they used Acrobits
The logistics AI tool went inside the app as a Web Tab, wired through the IPC SDK so it could use the phone's real powers: notifications, badges, contacts. When it alerted, the phone buzzed like a real call. The customer thought Marco built it for them. He just enabled it.
The dental clinics' CRM went into a Web Tab with automatic login. Staff open the app already in their account. A patient calls, the record pops. Click a number, the app dials it. An afternoon of work. No ticket, no vendor roadmap.
The reliability layer stopped being his problem. Acrobits carries the cross-device engineering. Everything Marco builds only matters because the calls connect first.
If you had to teach this to someone, what is the one idea?
Unified communications happens in the UI.
For years people thought "unified communications" was something you bought on a big phone system in a server room. It is not. It happens in the screen the person is holding: calls, messages, video, their CRM, their AI tool, all in one place.
And the way you build your own version of it is Web Tabs and the IPC SDK. That sentence changed how I sell.
What they needed
- A base that just works across a thousand phones and networks, so reliability is the floor, not the fight
- Customer-specific tools inside the app on his own timeline, without a developer on retainer
- A real bridge to the phone: notifications, badges, click-to-dial, contact context
- White-label branding so every device carries his logo, not a vendor's
- Active-user billing so he pays for the subscribers who actually use the app
Technical detail
Features that did the work
Web Tabs
any web tool (CRM, AI dispatch, billing portal) renders as a native tab inside the dialer. Auto-login passes the user's identity through, so it feels like one tool, not a website bolted on.
IPC SDK
web content in those tabs reads call state and fires native notifications. Alerts buzz like real calls. Standard web code, native behavior.
White-label branding
every device carries the operator's brand, not Acrobits'.
Active-user billing
pay for subscribers who register and place a call, not every provisioned seat.
And the business?
I stopped selling a phone app and started selling outcomes. Premium audio? A little more. CRM in the app? Let's talk.
I bundled the app, sold it to everyone, and paid Acrobits only for the people who actually used it.
The result:
- The app went from a cost on my bill to the stickiest, highest-margin thing I sell.
- It costs me about a coffee per user, per year.
- When I think about selling my company, that app is the asset, not the liability.
You do not want to own the plumbing.
You want to own the experience. Let someone carry the heavy lift so the faucet always runs, then build whatever your customers dream up, the day they dream it, with no one standing between you and your own roadmap.