How to Calculate Break‑Even for Flat‑Rate vs Per‑Agent
This guide shows you how to calculate the break‑even point between flat‑rate and per‑agent help desk plans so you can choose the most cost‑effective option for your team.
On this page
Before you can compare pricing models you need three pieces of information: the flat‑rate monthly fee, the per‑agent monthly fee, and a realistic estimate of how many agents and tickets you will handle each month. With those numbers in hand you can follow the steps below to see exactly where one model becomes cheaper than the other.
1. Gather Your Pricing Data
Start by collecting the current price sheets for every help desk you are evaluating. Record the flat‑rate monthly cost (including any base ticket allowance), the per‑agent monthly cost, and any overage charges for tickets that exceed the included allowance. Also note whether the per‑agent plan has tiered pricing that changes at higher seat counts. Having these figures in a single spreadsheet makes the later calculations straightforward and reduces transcription errors.
2. Define the Cost Model for Each Plan
Write a simple formula for each pricing model.
- Flat‑rate total cost = flat monthly fee + (overage tickets × overage fee per ticket).
- Per‑agent total cost = per‑agent fee × number of agents + (overage tickets × overage fee per ticket, if the plan imposes ticket limits). If a per‑agent plan offers unlimited tickets, the overage term drops out. Document the formulas so you can reuse them when you test different scenarios.
3. Estimate Monthly Ticket Volume
Look at the last three to six months of ticket data, or use a forecast if you are launching a new support channel. Calculate the average monthly ticket count and the peak month. This range lets you see how costs behave under normal load and during spikes. If a flat‑rate plan caps tickets, note the cap and the per‑ticket overage fee; if a per‑agent plan caps tickets per agent, multiply the cap by the expected agent count.
4. Calculate Break‑Even Agent Count
The simplest break‑even point ignores ticket overages and compares only the fixed fees:
Break‑even agents = flat‑rate monthly fee ÷ per‑agent monthly fee.
For example, a flat‑rate plan at a given monthly fee and a per‑agent plan at a given per‑agent fee give a break‑even number of agents. Below that number the per‑agent plan is cheaper; above it the flat‑rate plan wins. This number is a useful baseline before you add ticket‑volume considerations.
5. Adjust for Ticket Volume Limits and Overage Fees
Add the overage component to each model. If the flat‑rate plan includes a ticket allowance and charges a per‑ticket overage fee, and you expect to exceed the allowance, add the overage cost to the flat‑rate total. Do the same for the per‑agent plan if it has a ticket cap. Re‑calculate the break‑even agent count with the adjusted totals. This step often shifts the break‑even point by several agents, especially for high‑volume teams.
6. Compare Total Cost at Expected Scale
Plug your actual or projected agent count and ticket volume into both adjusted formulas. Create a small table in your spreadsheet with three columns: scenario (low, expected, high), flat‑rate total, per‑agent total. The scenario where the lower total switches from one model to the other is your practical break‑even point. This comparison also highlights how seasonal spikes affect the decision.
7. Run Sensitivity Scenarios
Vary the key inputs one at a time: increase agents, increase tickets, change overage fees up or down. Record how the break‑even agent count moves. Sensitivity analysis shows whether your decision is robust or if a small change in volume could flip the cheaper option. If the break‑even point is highly sensitive, consider a plan with more flexible terms or a provider that offers a free tier for low volumes — NeuraDesk provides a free flat‑rate option with AI reply suggestions and shared inbox included.
Common Mistakes to Avoid
- Using only the base per‑agent price and ignoring tiered pricing that kicks in at higher seat counts.
- Forgetting to include overage fees for tickets that exceed a plan’s allowance.
- Assuming ticket volume stays constant; always model a peak month.
- Comparing plans with different feature sets (for example, one includes a knowledge base while the other does not) without adjusting for the value of those features.
- Relying on a single snapshot instead of testing a range of realistic scenarios.
A clear break‑even analysis lets you pick the pricing model that matches your team size and ticket volume today while leaving room for growth. Try NeuraDesk free to see how a flat‑rate help desk works for your support workflow.
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free