Per-client billing is the safer default for most MSPs in 2026: one flat monthly fee per client is predictable to quote, easy for the client's budget holder to approve, and your margin improves every time that client hires. Per-seat billing wins in a narrower case — stable, audit-heavy clients who want the invoice to track exactly who was trained. The trap to avoid is committing to your own model before you know how your platform prices its seats.
TL;DR
- Per-client billing: one flat monthly fee per client, covering everyone. Predictable revenue, one-line quoting, margin improves when the client grows.
- Per-seat billing: a fee per trained user. Fair at quote time, but revenue drops every time the client shrinks — and support cost does not.
- The hidden variable: if your platform bills you per seat, client growth eats your margin under per-client pricing. Ask before you set your model.
- White-label per-client reporting — one branded PDF per client per month — pairs naturally with per-client billing.
- Mixing is legitimate: per-client for managed relationships, per-seat for fixed-scope projects.
Should MSPs bill security training per seat or per client?
| Per seat | Per client | |
|---|---|---|
| Pricing basis | Each trained user | One fee covers all users |
| Revenue predictability | Moves with client headcount | Flat and forecastable |
| Quoting effort | Count seats, prorate starters and leavers | One line item |
| Margin as the client grows | Revenue grows with re-quoting | Margin grows (cost flat) |
| Margin as the client shrinks | Revenue drops with it | Margin compresses slightly |
| Admin burden | Seat reconciliation every month | None |
| Best for | Enterprise-style, audit-heavy clients | Most SMB clients |
How per-seat billing works
Under per-seat billing, the client pays for each user enrolled in security awareness training. A 40-person client is one invoice at a per-seat rate; when they hire 12 staff next quarter, the invoice grows with them — after you re-quote it.
Advocates call this fair, and at quote time it is: the price tracks the value delivered. The problems appear in the operations. Someone reconciles seats every month. Starters and leavers get prorated. Disputes follow — the client insists they never onboarded that contractor. Automation removes some of the friction: Cyber Aware's auto enrolment, for example, syncs users from Microsoft 365 or Google Workspace and removes leavers cleanly, so the platform seat count stays honest. The reconciliation you still do is your own invoicing.
Per-seat also makes training feel optional. When every seat is a line item, clients trim seats to save money — and the untrained tail of the workforce is exactly where phishing lands. Verizon's Data Breach Investigations Report found a human element in roughly 60% of breaches; the seats a client trims are usually the ones a phisher would pick.
How per-client billing works
Under per-client billing, you quote one flat monthly fee that covers the client's whole team, whatever its size. The quote takes a minute, the client's approver sees a single line, and renewal is a conversation about value, not seat counts. Revenue per client is fixed and forecastable.
When the client grows from 40 to 60 staff, your revenue does not move — which is only a problem if your platform bills you per seat. That pairing decides everything, and it is the reason to interrogate the platform before you set your own price list.
The deliverable that justifies the flat fee should arrive automatically. White-label reporting built per client — Cyber Aware's human risk reporting exports a fully branded PDF for every client — means the monthly proof-of-value lands without you building spreadsheets, which is what makes a flat fee defensible at renewal.
Why per-client wins for most MSPs
- Quoting speed. One number instead of a seat count and a prorating table. Deals close faster.
- Budget approval. SMB budget holders approve flat monthly costs far more readily than variable ones.
- Margin behaviour. Headcount growth is the normal trajectory of a healthy client. Under per-seat it is revenue you must re-quote; under per-client it is margin.
- Stickiness. A flat security line item bundles into your managed-services relationship. Seat-based add-ons invite the client to shop each seat.
- The deliverable fits the model. One client, one risk score, one branded PDF per month — the proof of value arrives without seat-by-seat accounting.
When per-seat is the better fit
- Procurement transparency. Enterprise-style clients whose procurement requires line-item pricing per user.
- Stable, audited headcounts. Clients where seats rarely move and every trained user is a compliance record.
- Fixed-scope projects. A one-off compliance program for a defined cohort is naturally priced per seat, not per client.
If two or more of these describe the client, per-seat is honest pricing. If none do, per-client will be easier to sell and easier to run.
What decides which model fits
- Headcount stability. Swinging headcounts punish per-seat invoicing and reward flat fees.
- Your platform's cost model. Per-seat platform cost under per-client pricing converts client growth into margin loss.
- Procurement expectations. Some clients require per-user transparency; you cannot override procurement with preference.
- Bundling. Training bundled into a managed agreement suits per-client; sold standalone, per-seat maps to the quote.
- Your admin capacity. Seat reconciliation is a monthly tax — decide who pays it.
The margin trap both models share
The model you sell is not the model you pay. If the platform charges per seat and you bill per client, every client hire is margin walking out the door. If you bill per seat and the platform bills flat, shrinkage is your problem and growth is pure margin. Before you commit, ask the platform two questions: what happens to our cost when a client grows 30%, and what happens to a seat when a staff member leaves? An enrolment system that removes leavers automatically — as Cyber Aware's does through Microsoft 365 and Google Workspace sync — protects your margin more than the headline rate does.
The value case behind the fee is worth defending either way. KnowBe4's 2026 Phishing by Industry Benchmarking Report puts phishing susceptibility at 33.2% before training and 4.2% after twelve months of sustained monthly training and simulation. The Australian Signals Directorate's Annual Cyber Threat Report 2024-25 puts the average self-reported cost of a cyber incident for a small business at $56,600. A flat monthly training fee is the cheapest line on that comparison — the model you bill it under just decides who does the admin.
FAQ
What is per-seat billing for security awareness training? A fee per trained user. Revenue tracks client headcount, quoting requires seat counts and prorating, and the invoice moves whenever the client's workforce moves.
What is per-client billing? One flat monthly fee covering the client's whole team. Quoting is a single line item, revenue is predictable, and client growth becomes margin instead of re-quoting work.
Can an MSP mix both models? Yes. Per-client for ongoing managed relationships, per-seat for fixed-scope projects with a defined cohort. Just make sure the platform's cost model supports whichever segment it applies to.
How do I handle clients whose headcount swings wildly? Per-client with an agreed size band, reviewed annually — or per-seat if the client's procurement requires it. A flat fee for a headcount that halves is a margin conversation you will lose.
Does per-client billing work for very small clients? Yes — it is easiest at small sizes, where seat reconciliation costs more admin than the fee difference is worth.
One last thing
Before you write your price list, put one question to every platform on your shortlist: show me what happens to our cost when a client grows 30% and when a leaver departs. The comparison page is a place to start the shortlist. The answers will tell you which billing model you can afford to offer — and which one quietly bleeds.