DialStack moves the phone system inside the vertical SaaS platforms you hold, so the margin, the stickiness, and the call data stay in the asset you own.
Or read the docs first. We get it.
Voice as a new line on the P&L. Illustrative.
A platform that sends voice elsewhere is not avoiding a cost. Its customers already buy a phone system, just from someone else. The revenue and the margin leave with them.
That is the share of potential ARPU a platform leaves on the table when its customers buy their phone system from a third party instead of from the platform itself.
Embedded voice runs at roughly 50 percent EBITDA margins. Software economics on a line item the customer already budgets for.
When voice lives inside the platform, each call lands in the record as structured data instead of vanishing into a disconnected provider's system.
DialStack makes VoiceAI an easier line to open. Whether theirs or ours, VoiceAI is easier to position when it's natively embedded inside the voice surface customers already use.
The ARPU lift shows up in the first quarter. The valuation story builds from there.
Customers who run their phone system inside the platform are stickier. Voice wires the product into the daily front-desk workflow, and leaving means replacing the phones too. The platform stops being one tool among many and becomes the way the business answers its customers.
Every call becomes structured data in the platform: who called, when, for how long, and what happened next. That depth of first-party customer data strengthens data integrity as a valuation asset when it is time to take the company to market.
Regulated voice is a diligence problem when your portfolio company carries it, and a non-issue when DialStack does. We hold the regulatory load permanently, so the platform books the revenue and the data room stays clean.
Pick one platform in the portfolio and bring an operating partner and an engineer. You'll talk directly with a founder, and we'll walk through the architecture, the vertical, and the economics together.
Thinking about this across the whole fund? We are glad to start with a portfolio-level conversation instead.