Per-client pricing is the only sane SaaS model for agencies

The default that doesn't work#

Most B2B SaaS prices per seat. Slack, Notion, Linear, Figma, the whole stack. Per-seat pricing works well when the SaaS is a productivity tool used by every team member, constantly, and where adding a seat correlates with adding capacity.

For agency reporting tools, none of these conditions hold.

The tool isn't used by every team member constantly. The data team might use it daily; the strategy team checks it monthly; the senior partner sees the final brief and that's it.
Adding a seat doesn't add reporting capacity in proportion. A junior hire who logs in three times a month doesn't double your reporting throughput.
The value of the tool scales with client count, not headcount. A 5-person agency with 30 clients gets more reporting value than a 20-person agency with 5 clients.

Per-seat pricing applied to agency reporting tools produces predictable friction: every staffing change becomes a billing event. A new junior account manager: that's $X more per month. A freelancer for a one-month sprint: do we pay the seat fee for the month or hold off and have them share a login? An intern: are they a seat?

These conversations don't add value to anyone. They just create friction.

What per-client pricing measures instead#

Per-client pricing ties the cost to the relationships the agency manages. A 30-client roster costs the same regardless of whether 5 or 50 people on the team touch it.

That maps cleanly to how agencies actually generate revenue:

Revenue scales with clients (retainer fees)
Capacity scales with clients (each client needs N hours/month of work)
Tool value scales with clients (more clients = more reports = more value from automation)

When the cost basis matches the value basis, pricing conversations are simple. "I have 30 clients. The tool is Agency tier. Done."

The hidden tax of per-seat#

For agencies specifically, per-seat pricing has a second hidden tax: it punishes you for hiring. Every new hire adds to the SaaS budget without changing what the SaaS does. So hiring decisions get tangled up with SaaS budget decisions in ways that don't reflect actual value.

We've watched agency operators delay hires by 60-90 days because the SaaS-stack cost implications of "add three more seats across our tools" felt too large to absorb without a budget review. That's a real operational cost imposed by a pricing model that doesn't match the work.

The objection#

The most common objection to per-client pricing is: "but a 50-person agency with 5 clients should pay more than a 5-person agency with 5 clients, right? Big agencies have deeper pockets."

This conflates two things: what the tool is worth to the agency (per-client) and what the agency can pay (per-revenue, per-headcount, etc.). The first is the right basis for pricing. The second is a fairness or extraction argument that pricing models shouldn't litigate.

If a 50-person agency with 5 clients gets less value from a per-client priced tool than the agency thinks they should pay, the right answer is that the tool isn't the right fit for them. Not that the pricing model should be rewritten to extract more from them because they happen to be larger.

Where we landed#

SendBriefs prices per client. The tier ladder is:

Solo: up to 5 clients
Agency: up to 25 clients (the median sweet spot)
Agency Pro: up to 75 clients
Enterprise: unlimited

Adding team members is free at every tier. The unit of payment is the unit of value, and the staffing decisions you make are not pricing decisions.

This isn't a clever positioning move. It's just what pricing should look like when you think about whose problem you're solving and what they're paying for.

More essays in the Friday Brief.