# Per-ticket vs per-seat pricing: which pricing model should my team choose?

issues.house · August 21, 2026

> The Direct Answer Per-ticket pricing charges a fee for each individual case, issue, or transaction processed — you pay in proportion to volume...

## The Direct Answer

Per-ticket pricing charges a fee for each individual case, issue, or transaction processed — you pay in proportion to volume. Per-seat pricing charges a fixed recurring amount for each named user who accesses the system, regardless of how many tickets those users touch. Neither model is universally cheaper; the right choice depends on your ticket-to-agent ratio, how often occasional stakeholders need access, and whether your costs scale with volume or with headcount. As of 2026, most B2B issue-ops and case-management platforms offer both models, and the decision typically swings on one number: tickets processed per active user per month. If that ratio is high (roughly above 150–200 tickets per user monthly), per-ticket pricing usually wins. If it is low, or if many light users need read access, per-seat almost always wins.

**Also worth reading:** [SaaS pricing metrics comparison: which pricing model and metric should your B2B SaaS use in 2026?](https://issues.house/knowledge/saas_pricing_metrics_comparison_which_pricing_model_and_metric_should_your_b2b_saas_use_in_2026.php) · [B2B Issue Management SaaS Pricing in 2026: Per-Seat, Usage-Based, or Hybrid?](https://issues.house/knowledge/b2b_issue_management_saas_pricing_in_2026_per-seat_usage-based_or_hybrid.php) · [What is a support ticketing system and how do I choose the right one for my B2B team?](https://issues.house/knowledge/what_is_a_support_ticketing_system_and_how_do_i_choose_the_right_one_for_my_b2b_team.php)

The distinction matters because the two models create opposite incentives. Per-seat vendors want you to add users; per-ticket vendors want you to process more cases. A compliance team handling 40,000 regulatory inquiries a year with eight full-time analysts faces very different economics than a public-affairs desk where 60 people occasionally log in but only five work cases daily. Understanding which side of that divide you sit on is the first step in any pricing evaluation.

## How Each Model Actually Works

Under per-seat pricing, you pay a flat monthly or annual rate per named user. Typical B2B support and case-house platforms price seats between $25 and $150 per agent per month depending on tier, with enterprise plans negotiated down from list. Every person who logs in — even once a quarter — consumes a seat unless the vendor offers free viewer or read-only roles. Budgeting is straightforward: multiply headcount by seat cost, add a growth buffer, and you have your annual number.

Per-ticket (sometimes called per-resolution or per-case) pricing charges a small unit fee per ticket created, resolved, or both. Unit rates commonly range from $0.50 to $5.00 per ticket depending on complexity, channel mix, and contract volume commitments. Some vendors tier the rate so marginal tickets get cheaper as volume grows; others charge flat. The critical detail is what counts as a ticket. Does an internal note count? Does a reopened case count twice? Does an automated bot resolution count? These definitions can swing effective cost by 30–50%, so they belong in the contract, not in a sales conversation.

A hybrid model is increasingly common in 2026: a base platform fee plus either capped per-seat charges or metered ticket overages. Airlines use analogous logic with available seat miles — revenue is measured against capacity consumed — and event operators do the same when they price season tickets per seat while single events are priced per admission. Wisconsin's Badgers volleyball program, for example, prices season packages per seat while individual match tickets carry their own dynamic prices; the same structural choice exists inside software contracts.

## Comparison Table: Side by Side

| Feature | Per-Ticket Pricing | Per-Seat Pricing |
| --- | --- | --- |
| Cost driver | Case volume | Named users |
| Typical range | $0.50–$5.00 per ticket | $25–$150 per user/month |
| Predictability | Low; varies with demand spikes | High; fixed headcount cost |
| Best fit ratio | >150–200 tickets/user/month |

Canonical: https://issues.house/knowledge/per-ticket_vs_per-seat_pricing_which_pricing_model_should_my_team_choose.php
Markdown: https://issues.house/knowledge/per-ticket_vs_per-seat_pricing_which_pricing_model_should_my_team_choose.php/index.md