Every outbound sales leader has had this conversation: you want to add three reps to hit next quarter’s pipeline target, the CFO opens the tooling line item, and the math stops the hire before it starts. Three new reps don’t just cost three salaries — they cost an additional $1,500-$2,500/month in dialer and CRM seats before anyone makes a call.
This isn’t a budgeting problem. It’s a structural mismatch between how outbound sales teams actually consume software and how the software industry has chosen to price it.
Where per-seat pricing came from
Per-seat pricing made sense in 1999. Salesforce was the first major SaaS CRM, and the assumption baked into its pricing was that every employee with access to the system would use it roughly equally. A 50-person company paying $50/seat would have 50 people logging in daily, updating records, viewing dashboards. The cost-to-value ratio was relatively flat across the user base.
That assumption has held up surprisingly well in some categories. HR software, accounting tools, project management — these are still genuinely used by everyone with a login. The per-seat model fits.
It does not fit outbound sales.
Why outbound is different
On a 10-rep outbound team, three things are true that aren’t true elsewhere in the company:
1. Usage is wildly uneven. Top reps dial 3-5x what bottom-quartile reps dial. AEs use the dialer differently than BDRs. Some reps live in the CRM; others touch it only when they have to. A flat per-seat fee charges every rep the same amount for radically different consumption.
2. Roster turnover is structural. BDR teams typically see 30-40% annual turnover. That’s not dysfunction — it’s the economics of the role. New hires ramp, top performers get promoted to AE, weaker performers exit. Per-seat pricing assumes a stable user base; outbound has a constantly rotating one.
3. The role exists to do one specific thing. A marketing manager logs into HubSpot for dozens of reasons across a week. A BDR logs into a dialer to dial. The breadth of “value extracted per seat” that justifies per-seat pricing in other categories doesn’t exist in outbound.
These three factors compound. A 10-rep team with 35% annual turnover and uneven usage is paying for software it isn’t using, by users who aren’t there, in a way the pricing model doesn’t acknowledge.
The hidden tax on growth
Here’s the part that doesn’t show up in standard TCO calculations: per-seat pricing creates a friction point on every hiring decision.
When a VP Sales wants to hire two more BDRs, they’re not just selling the CFO on two new salaries. They’re selling on two new salaries plus $300-$500/month in seat costs that hit the books on day one, before pipeline shows up. The seat cost is small compared to the salary, but it’s psychologically present in a way that distorts decisions.
The same friction applies in reverse on terminations. Managers delay firing underperforming reps because “we’re paying for the seat anyway.” That’s an irrational response — the seat fee is sunk — but it’s a documented behavior. Per-seat pricing creates a floor on how aggressively teams optimize their roster.
The cumulative effect across a year is significant. Teams running on per-seat models hire slower, fire slower, and over-staff in steady states because the fixed costs of each seat make experimentation expensive.
What consumption-based pricing actually solves
A small but growing category of sales tools has rejected the per-seat model entirely. Instead of charging for the right to use software, they charge for actual use — minutes dialed, calls recorded, transcriptions processed. Consumption-based dialer pricing at $0.02/minute, for example, ties tooling cost directly to revenue-generating activity.
The economic logic is cleaner. A rep who dials 100 calls/day costs more in tooling than a rep who dials 30 — which is exactly right, because the first rep is generating more pipeline opportunity and consuming more infrastructure to do it. The pricing model and the value model align.
The hiring math also changes. Adding three new BDRs no longer triggers a $1,500/month upfront cost. The dialer costs ramp as the new reps ramp into productivity. If a new hire doesn’t work out and leaves in month two, the team isn’t stuck paying for an empty seat.
This isn’t theoretical. Teams that have switched to consumption pricing typically report 30-50% reductions in tooling spend without losing functionality. The savings come almost entirely from cutting the dead-seat overhead that per-seat pricing forced them to absorb.
The CRM half of the equation
Dialers are the obvious place to start because the per-call usage pattern is so easy to meter. CRM is harder.
A rep who looks at a contact record 20 times a day costs the system the same as a rep who looks at it twice. Pricing CRM by usage runs into a different problem: the value of CRM is partly storage and partly access, both of which are fixed-cost.
The cleaner solution most consumption-priced platforms have landed on is flat-rate CRM tiers based on team size — $99 for up to 10 reps, $249 for unlimited — paired with consumption-based dialing. The CRM cost stops scaling with headcount above a threshold; the dialing cost scales only with actual work. A 25-rep team and a 50-rep team pay the same CRM fee.
This pricing structure flips the economics of growth. Per-seat models punish teams that scale; flat-rate models reward them. The 50-rep team paying $249/month for CRM has a meaningfully different cost structure than the 50-rep team paying $5,000/month at $100/seat.
Where per-seat pricing still wins
To be fair: per-seat pricing isn’t always wrong. There are categories where it still maps cleanly to value.
Marketing automation platforms benefit from per-seat pricing because every marketer using the platform is doing meaningfully different work. Customer support tools work because each support rep is processing distinct ticket queues. ERP and accounting systems use per-seat pricing because the user base is stable and the work is uniform.
The pattern: per-seat works when usage is even, turnover is low, and the per-user value is roughly consistent. None of those conditions hold for outbound sales teams.
Per-seat also wins for buyers who want predictable monthly costs. Consumption pricing creates variability that some CFOs hate. A team that dials 50,000 minutes one month and 30,000 the next will see their bill swing by $400, which is real but small relative to the savings.
The shift that’s coming
Pricing models follow market maturity. When a category is new and customers don’t know how to value it, vendors charge per seat because seats are easy to count and easy to sell. As the category matures and usage patterns become legible, pricing tends to shift toward consumption — the same way cloud compute went from fixed-instance pricing to per-second billing, and the way AI APIs are priced per token rather than per developer.
Outbound sales tooling is mid-shift. The legacy vendors (Salesforce, HubSpot, Salesloft, Outreach, Aircall) are locked into per-seat pricing because their financial models assume it. Newer vendors are entering with consumption-based pricing and absorbing the customers who’ve gotten tired of paying for empty seats.
If you’re a sales leader making a 3-year tooling decision in 2026, the question isn’t whether consumption-based pricing will become the dominant model — it almost certainly will, given the underlying economics. The question is whether you want to pay the per-seat tax for another contract cycle while you wait.
For most teams, the answer is no.
