Per-seat pricing punishes the teams it claims to serve

Every agency owner has done this math at least once. A contractor joins for a six-week build, and before you invite them you pause and think: is this person worth another line on the invoice?

That pause is the problem. Not the price. The pause.

Per-seat pricing is a perfectly reasonable model for a company where headcount is stable and everyone is full time. Client work is not that company. Client work is a core of three or four people surrounded by a rotating cast of specialists: a designer for two weeks, a backend contractor for a sprint, a QA person who shows up twice a year and is worth every cent when they do.

What you actually buy when you skip a seat

When the seat feels expensive, you do what everyone does. You keep the contractor outside the system. They get a shared doc, a Slack channel, and a weekly call. And in exchange for saving fifteen dollars a month, you buy:

• A translation layer. Someone on your team now spends part of every day copying context out of the tool and into a message, then copying updates back the other way.
• Time you cannot see. Their hours arrive at the end of the month as a number in an email. You find out the work went over when there is nothing left to do about it.
• An estimate nobody agreed to. The scope you quoted lives in your system. The scope they think they are building lives in their head.
• A reconciliation job. At payout time, someone matches an emailed invoice against work they were not watching.

Fifteen dollars a month is cheap. Four hours of a senior person reconciling numbers is not.

The incentive runs the wrong way

Here is the uncomfortable part. A per-seat tool makes more money the more people you add, which means the tool is quietly incentivised to be the thing you ration. You end up designing your operating model around a billing model. That is backwards, and once you see it you cannot unsee it.

The right question is never “who deserves a login.” It is “who needs to see the truth for the work to go well.” Usually that is everyone touching the project.

Signs the pricing is running your process

• You have a shared login. (Everyone has, at some point. It is a symptom, not a moral failing.)
• Contractors submit hours by email or message rather than logging them.
• Your client-facing statuses are maintained by hand because the people doing the work are not in the system.
• You have delayed inviting someone for longer than their engagement will last.

What we did about it, honestly

We are not going to pretend we invented free software. Beacon has a per-member price too, and we publish it plainly rather than hiding it behind a call. What we tried to do is make the shape of the plans match the shape of the work.

The Free tier is not a demo with the useful parts removed. It carries the whole loop, clients through estimates through time through payouts, capped at three members and two active projects. That is deliberate. If you are a freelancer with two clients, you should be running the real system, not a trial version of it, so that the day you bring in a contractor nothing about your process has to change except the plan.

And on paid plans, the developer you hire for six weeks is a member like anyone else. They log their own time against the task or estimate it belongs to. They see the estimate they are working against, including the hours it was approved at. When the work is done they mark it ready for payment, and it attaches to the estimate rather than arriving as a PDF you have to interpret.

The counter-argument, taken seriously

There is a real case for per-seat pricing: it scales cost with value, and it stops a fifty-person company paying the same as a three-person one. Fair. We are not arguing for flat pricing at any size.

The argument is narrower than that. It is that seat anxiety is a specific failure mode for small teams with variable headcount, and that a plan structure which makes you hesitate before inviting the person doing the work has failed at its job, no matter how defensible the spreadsheet behind it looks.

Common questions

Do contractors need their own account?

Yes, and they should. Shared logins destroy the one thing that makes payouts arguable-proof: knowing who logged what, and who approved it. Beacon has three roles, and a developer only sees the projects and estimates they are on.

What if someone only works one week a quarter?

Then they cost you one member for the months they are active and nothing for the months they are not. The point is that the decision should be about the work, not about whether the seat is justified.

Is the free plan actually usable?

For a solo operator with a couple of clients, yes. It gets tight fast at three members, which is when the paid plans start to make sense. See the pricing page for exactly where the lines fall.

Price your tools the way you price your work: so that the right decision is also the easy one.