Reviews
Part of Team collaboration: methods, tools and useful context
Team collaboration pricing: plans, fees and buying questions
A practical 2027 guide to team collaboration pricing: plans, fees and buying questions 2027 with current definitions, decisions, checks, and review steps.
The advertised rate for a collaboration tool is small enough that most organizations do not model it at all. They pay it, the team grows, a department buys its own, contractors get added, and three years later the bill is well past what anyone expected and nobody can say exactly when that happened.
The reason is that the price per person is not where the movement is. The movement is in what counts as a person, what happens to the free arrangement you started on, and the two or three step changes between where you are and where you are going. This page is about those.
What to take away
- Find out whether you are billed for people who use it or people who merely have accounts. Count both numbers in your own organization; the gap is usually larger than anyone expects.
- A free tier is priced in history. Understand exactly what happens to old messages before you build a working culture on top of them.
- Separate workspaces bought by separate departments cost more than one, and merging them later is neither free nor tidy.
- Model the step changes, not the monthly rate. The jumps are what actually determine what you pay.
What exactly are you paying for
Establish the unit before anything else, because the same headline rate means different things. Where an offer describes itself loosely, the standard definitions of cloud service models are a fair reference for deciding whether two offers are even the same kind of purchase.
- Provisioned or active. Some arrangements bill for every account that exists; some bill only for accounts that were used in the period. If yours bills for provisioned accounts, then every leaver nobody deactivated and every account created for a trial that ended is on your bill indefinitely.
- Who counts as a member. A person who only reads, a person who only receives automated notifications, and a person who works in it all day may or may not be priced the same.
- How guests are handled. Free with restrictions, discounted, or full price. This is the largest single variable for any organization that works with contractors, clients, or partners, and it is rarely visible on a comparison page.
- Whether connections cost anything. Automated posting from other systems is sometimes limited by count, sometimes metered, and sometimes an entirely separate tier.
- What the billing period does to changes. Whether adding someone mid period is prorated, whether removing someone produces a credit, and whether the count is taken at a moment or as an average.
Get the answer to each in writing. Two offers with the same rate can differ by a large multiple once these are applied to a real organization.
The free tier is priced in history
Free arrangements in this category are usually generous about people and strict about time. Some limit how far back you can see; some limit total message volume; some remove access to older material rather than deleting it, which sounds better and has the same effect on your day.
The question underneath all of them is how much history you are obliged to keep, which is set by what the content is rather than by what the tier offers. Published records control schedules are a useful model for making that decision by class of content, and it is the decision that tells you whether a history limit is an inconvenience or a disqualifier.
Three questions decide whether the free option is viable for you:
- What exactly happens at the boundary? Are old messages deleted, hidden, or exportable? These are very different answers and only one of them is recoverable.
- Does upgrading restore what you lost? Sometimes hidden history returns on payment, sometimes it is gone. Ask before you rely on it.
- What can an administrator export while still on the free arrangement? If the answer is nothing, the free tier is not free, it is deferred.
None of this makes the free option wrong. It makes it a decision with a known cost, taken deliberately, rather than a saving that turns into a bill at the moment you have the least room to argue.
Where the steps are
Growth in this category does not raise the bill smoothly. It jumps, usually at three points.
| Step | What triggers it | Why it costs more than expected |
|---|---|---|
| Free to paid | History limits become painful, or an obligation appears | You move at the moment your archive is most valuable, which is the weakest possible negotiating position |
| Paid to the governance tier | Needing single sign on, automatic provisioning, retention control, or administrative export | The higher rate applies to every account, not only to the ones that needed the feature |
| One workspace to a managed set | Departments that bought separately must be merged | Merging is manual, some history does not move, and both bills run in parallel while it happens |
The second row is worth planning around. The requirement that pushes an organization up a tier is almost never a communication feature. It is a governance feature, and it arrives predictably: with the first regulated customer, the first serious dispute, or the first time somebody asks for a record. The same pattern applies to mail governance, and it is just as easy to see coming and just as commonly ignored.
The fragmentation problem
The most expensive shape in this category is several teams paying separately for the same product.
It happens naturally. One team starts on the free arrangement, another buys a paid one on a card, a third joins somebody else's workspace as a guest. Nobody is doing anything wrong, and the result is multiple bills, no shared history, guests where colleagues should be, and no administrative view of anything.
Consolidating later costs money in three ways: the merge itself, the period where both are paid, and the history that does not survive the move. If you can see this forming, the cheapest moment to fix it is now. If it has already formed, count the total across every card before you conclude that a single managed arrangement is more expensive, because frequently it is not.
Build the model
Fill this in with figures you look up yourself. What matters is the fields; the rates change constantly.
| Line | What to enter |
|---|---|
| Accounts that exist | Including everyone nobody deactivated |
| Accounts actually used last month | The gap between these two lines is money |
| People who only read or receive | And whether a cheaper level exists for them |
| Guests and external participants | Now, and honestly, in a year |
| Separate workspaces in the organization | Including any you only found out about while reading this |
| Tier required | Set by governance needs, not by messaging features |
| History retention required | Driven by obligation or by how far back people genuinely search |
| Connections and automation | And whether any are metered |
| Export capability | Which tier it starts at, since this is your exit |
| Administrative time | Hours per month for channel hygiene, guest reviews, and offboarding |
| Cost of consolidating | If you already have more than one workspace |
Run it at today's size and at the size you would consider a good outcome in three years. Then compare the second figure against what the alternative costs, including doing nothing new and using the tool that came with something you already pay for, which is the option the selection method treats as a serious candidate rather than a fallback.
Common questions
When is the right moment to negotiate?
Before you are dependent, which in practice means at the first renewal rather than the third, and while you still have a working export. Anything you agree while your entire archive is inside the product is agreed from a weak position.
Should we pay annually?
Annual is cheaper and normally fixes your account count. In a team whose size moves a lot, particularly one using contractors, the monthly premium buys real flexibility. Check specifically how mid term additions are priced, because that is where an annual commitment quietly stops saving money.
Is the per person rate worth comparing at all?
Only after you have applied the unit definitions above. Two offers at the same rate can differ by a wide margin once guests, inactive accounts, and the tier your obligations require are counted. The habit of converting every offer into your own units, described in the comparison method, matters more here than in most categories.
What is the most commonly missed line?
Administrative time. Somebody spends hours every month on channels, guests, and access reviews, and it never appears on a price list. Cost it at a real internal rate and it frequently exceeds the subscription, which changes what "cheap" means in this category, along with the administration overhead you were already carrying.
