For most of the last fifteen years, business software has been sold one way: per seat, per month. You count your users, multiply by a number, and pay it whether those users log in daily or twice a quarter. The model built some of the largest software companies in the world. It is also, increasingly, the thing buyers are most tired of — and the sales stack is where the cracks are showing first.
Per-seat pricing was an answer to a specific problem
It’s worth remembering why per-seat pricing won in the first place. When software moved to the cloud, vendors needed a billing model that was predictable, easy to forecast, and that grew as the customer grew. Per-seat delivered all three. A growing company adds people, adds seats, and the vendor’s revenue scales right alongside it. For tools where usage is roughly even across users — a document editor, a chat app, a shared workspace — it’s a fair proxy. Everyone uses it about the same amount, so charging per head approximates charging for value.
The model breaks down the moment usage stops being even. And in outbound sales, usage is never even.
Sales is the worst possible fit for per-seat
Look at how an outbound team actually consumes a dialer. Your top performer dials three times as much as your median rep. Newly hired reps spend their first weeks ramping, barely touching the phone, while occupying a fully priced seat. Reps churn — outbound roles have some of the highest turnover in the company — leaving seats that get paid for until someone remembers to deprovision them. Territories shift. Pipelines go quiet and busy in cycles.
Per-seat pricing charges a flat rate across all of that variance. You pay the same for the rep dialing 120 times a day and the one who’s out on leave. The bill tracks headcount, which is the thing you’re trying to grow, rather than usage, which is the thing that actually creates value. It is, functionally, a tax on building the team.
Buyers have noticed. The complaint shows up in every renewal conversation: “We’re paying for seats we don’t use.” It’s not a negotiating tactic. It’s an accurate description of a pricing model applied to the wrong category.
What replaces it
The alternative isn’t novel — it’s how your electricity, your cloud compute, and your phone minutes have always worked. You pay for what you consume. Usage-based pricing has already taken over the parts of the software world where consumption varies wildly: cloud infrastructure led the way, data and communications tools followed, and the model is now working its way up the stack toward the applications sales teams use every day.
In dialing specifically, the consumption unit is obvious: the minute. ZenCall’s pay-per-minute dialer charges $0.02 a minute for United States calls and lets you add unlimited reps with no per-seat fees — the bill is a direct function of how much your team actually talks to prospects. Add a rep and your cost doesn’t move until that rep starts dialing. Run a quiet week and you pay for a quiet week. The model aligns cost with work, which is the thing per-seat pricing was never able to do for this category.
The catch consumption pricing creates — and how the good versions solve it
There’s a legitimate objection to usage-based pricing: it can feel unpredictable. If every action costs something, buyers worry the bill becomes impossible to forecast. This is the real reason per-seat survived as long as it did — finance teams love a number they can multiply.
The strong versions of consumption pricing answer this by keeping the variable cost low and per-unit, and by holding the rest of the platform on a flat, predictable footing. Dialing scales with minutes, but the surrounding system — the part that holds your data — shouldn’t nickel-and-dime you. That’s why the better consumption-priced platforms pair pay-per-minute calling with a built-in customer relationship layer on simple, flat tiers.
In practice that looks like a CRM that’s free to start — one seat and up to 50 active deals at no cost — with paid plans that raise the limits on clean, flat pricing: $49 a month for 3 CRM seats with unlimited deals, $99 a month for 10 seats, $249 a month for unlimited seats. The dialer stays pay-per-minute underneath all of it. You get the cost-alignment of consumption pricing on the part that varies (calling) and the forecastability of flat pricing on the part that shouldn’t (your system of record). Finance gets a predictable platform line; the team gets a calling cost that tracks actual work.
Why the dialer and the CRM converge under this model
There’s a second shift happening alongside the pricing one, and they reinforce each other. As per-seat economics collapse, the logic of buying a separate dialer and a separate customer relationship tool — each with its own seat licenses — collapses with it. If you’re no longer paying per seat for calling, paying per seat for a CRM your reps half-use starts to look like the next obvious thing to cut.
Consolidation follows naturally. A platform that puts calling and the customer record in one product eliminates a category of cost (the second tool’s seats), a category of friction (the integration between them), and a category of data loss (the calls that never sync cleanly). The pricing trend and the product trend point the same direction: toward fewer tools, priced by usage, with the record built into the place the work happens.
What this means if you’re buying in 2026
You don’t have to predict the whole future of software pricing to act on the part that’s already here. When your next dialer renewal comes up, the questions worth asking have changed:
- Does the price track usage or headcount? If it’s still per-seat, you’re paying the tax this whole shift is moving away from.
- Is the variable cost actually low and the platform cost predictable? Consumption pricing only helps if the per-unit rate is small and the flat parts are honest.
- Does the system of record come with it, or are you about to buy a second per-seat tool to sit next to the first?
Per-seat pricing isn’t disappearing tomorrow. But in outbound sales — the category it fits worst — the move toward paying for what you use is already underway. The teams getting ahead of it are the ones whose bills finally reflect the work, instead of the org chart.