She Bundled Calling Into Every Seat, Paid for a Third of Them
Hana's margin came entirely from a platform vendor's per-seat cut, only as durable as their goodwill.
A branded calling product she prices, bills, and owns, with margin nobody can take at the next renewal.
Hana runs the managed-services side of a mid-size MSP that resells UCaaS seats to about 1,500 SMB employees across a mixed customer base: law firms, clinics, a couple of small logistics shops.
She does not own the phone platform underneath her business. She owns the relationship: the support line customers call, the renewal conversation every year, the invoice with her logo on it.
For a while that was enough. Then the math started to bother her.
We talked to Hana about the quarter she stopped resenting her own margin.
What did you do first?
I did what most MSPs do. I resold the platform vendor's seat, marked it up a little, and called that my product. It worked fine as long as the vendor stayed reasonable.
But every renewal cycle, the vendor got a little more aggressive about who "owned" the customer relationship: bundling in their own upsells, talking to my customers directly, changing pricing tiers without much warning. I was the face of the business. I wasn't the one steering it.
What was the breaking point?
It wasn't one dramatic call, it was a slow realization during a QBR with my biggest customer. They asked what else I could offer them: could I give their staff a branded calling app, something with our name on it, something that felt like our product instead of a rental.
I didn't have an answer. I could resell someone else's white-label softphone, but that meant putting a second vendor between me and my customer, inheriting their roadmap, their price hikes, their outages. Or I could try to build something myself, which for an MSP with no mobile dev team was not a real option.
I had margin sitting in front of me and no way to reach it.
How did that feel? And commercially?
Frustrating, honestly. I had the customer relationship, the support contract, the trust, the parts that are supposed to be hard to build. And I was watching all the recurring, sticky revenue accrue to a platform vendor who barely knew my customers' names. I felt like I was renting out my own storefront.
The commercial part is what actually kept me up:
- My margin came almost entirely from the platform vendor's per-seat cut, so it was only as durable as their goodwill.
- I had no product of my own to point to.
- A buyer would look at my revenue and see someone else's pricing decisions baked into every dollar of it.
I needed a recurring product I actually controlled: priced by me, billed by me, defensible on my own terms.
Margin was rented, not owned
it came entirely from the platform vendor's per-seat cut, only as durable as their goodwill
Biggest customer wanted a branded calling app
reselling a second vendor's softphone meant inheriting their roadmap and price hikes; building in-house was not an option
Switched to Cloud Softphone active-user billing
bundle the branded app into every seat, pay only for the ~35% who register and place a call
Branded app became the highest-margin line
~$63/month COGS across 1,500 seats, priced at an $8-13 premium, 64-77% gross margin
What changed?
I found Acrobits Cloud Softphone, and the thing that actually sold me wasn't a feature list. It was how the billing worked.
I could roll a branded softphone into every single seat as a standard part of the package: everyone gets it, no upsell friction, no "do you want this add-on" conversation. But Acrobits only bills me for the users who actually register and place a call. Provisioning the whole base costs me nothing extra.
That single fact turned the math from "another cost to justify" into "a product I could actually price."
It just worked the way I needed it to work, quietly, in the background, so I could stop worrying about whether I'd bet on the wrong app and start thinking about what to charge for it.
How they used Acrobits
The law firm's case-management CRM went into a Custom Web Tab. A regional law firm lived inside their CRM all day and hated tabbing out to a separate phone app. Hana dropped the CRM into a Custom Web Tab, a window inside the branded app that shows any web tool, and passed their login through automatically. Open the tab, already signed in, no second password. Click a phone number in the CRM, the app dials it. To the paralegals it looked like one piece of software instead of two.
A logistics customer's ticketing portal fired native alerts through the IPC SDK. Their dispatchers run a helpdesk-style dispatch operation and wanted ticket alerts to show up the way a phone call does: a real notification, a badge on the icon, not a browser tab they might miss. Wired in through the IPC SDK, a bridge that lets a web tool trigger the phone's native notification behavior, a new ticket buzzes like an incoming call.
Neither took a mobile developer. Both took an afternoon of configuration. No ticket, no vendor roadmap.
If you had to teach this to someone, what is the one idea?
Unified communications happens in the UI, not in a server room.
For years, "unified comms" meant some platform decision made far away from the person actually holding the phone. It's actually decided on the screen in someone's hand: whether their CRM, their calls, and their tickets live in one place or three.
The mechanism that gets you there is Custom Web Tabs and the IPC SDK. Once I understood that, I stopped thinking of the app as a cost center and started thinking of it as the thing I sell on top of the platform, not underneath it.
What they needed
- Billing that tracks real usage, not provisioning counts, so bundling the app into every seat costs nothing extra
- A recurring product she controls, priced by her and billed by her, defensible at the next platform renewal
- White-label branding so the app carries her name, not a second vendor's
- Customer-specific tools inside the app on her own timeline, without a mobile dev team
- A real bridge to the phone: native notifications, badges, click-to-dial, contact context
Technical detail
Features that did the work
Active-user billing
pay only for subscribers who register and place a call, not every provisioned seat. Bundle the app across the whole base at no extra cost.
White-label branding
the app carries the MSP's brand, not Acrobits' and not a second vendor's.
Custom Web Tabs
any web tool (a case-management CRM, a ticketing portal) renders as a native tab inside the branded app. 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 triggers the phone's native notifications and badges. A new ticket buzzes like an incoming call. Standard web code, native behavior.
And the business?
This is where it actually pays off. We provisioned the branded softphone across all 1,500 seats under Acrobits' white-label active-user pricing, which runs $0.12 per active user.
Only about 35% of provisioned seats ever register and place a call in a given period, call it roughly 525 billable users out of 1,500 provisioned. That works out to around $63 a month in COGS to cover the entire customer base, provisioned or not.
On the revenue side, I price the branded app as an $8-13 per-seat premium across the full provisioned base, not just the active slice. That lands gross margin somewhere in the 64-77% range, depending on the customer mix.
Because the cost only scales with the ~35% who actually use it, and I'm charging across the full 100%, the delta is pure margin, and it's margin nobody can take away from me at the next platform renewal. On a typical 1,000-seat customer, breakeven is around 28 retained, active subscribers. Everything past that is funding my sales team.
Stop pricing your margin around what someone else lets you keep.
If you own the customer relationship, you can own a recurring product too. You just need the billing to track real usage instead of provisioning counts, and the math stops being a source of anxiety.