Seat limits are treated as a pricing footnote. For a small team, they are the reason approvals quietly moved into a group chat and stopped being recorded anywhere.
Most organizations do not decide to abandon their review process. They decide to buy a marketing platform, choose the tier that fits the budget, and discover afterward that it includes one user account. From there the outcome is determined. Either everyone shares a login, or approval happens somewhere outside the tool. Nobody chose either. The plan chose.
This is worth naming because the failure is usually diagnosed as a discipline problem. A manager notices that posts are going out without review, or that nobody can say who approved a claim that turned out to be wrong, and concludes the team is being careless. The team is not being careless. It is working around a constraint that makes the intended process impossible.
What a review process actually requires
"Someone checks it before it goes out" describes an intention. Implementing it requires three things, and a plan can satisfy one or two while failing the third.
Distinct identities. The system has to know who did what. If two people use one account, the record shows the account, not the person. Every downstream benefit of having a review process — accountability, the ability to reconstruct a decision, the ability to fix a recurring problem at its source — depends on this and disappears without it.
Distinct permissions. A reviewer and a drafter need different capabilities. If everyone with access can publish, review is voluntary. Voluntary review is what happens when there is time, which is not the same as a process. The meaningful boundary is that the person who wrote something cannot be the person who releases it.
A state between draft and live. There has to be somewhere a finished item waits. Without it, "ready for review" is a message someone sends rather than a condition the system holds, and items in that state are visible only to whoever remembers them.
A plan with additional seats at identical permission levels satisfies the first requirement and not the second. A plan with roles but a single seat satisfies neither in practice. Both are common.
What entry tiers actually include
Seat allowances cluster tightly across the market, and the pattern is consistent enough to plan around.
Constant Contact's Lite plan includes one user; Standard includes three; unlimited users arrive at Premium. Mailchimp's lower tiers similarly cap users and audiences, with higher allowances at higher tiers. The specifics change and should be verified on each vendor's current pricing page, but the structure holds: the cheapest plan assumes one person, and the tier where a team of three or four can each have appropriate access is usually two steps up.
The mismatch is that the entry tier is priced for a small organization, and small organizations are precisely the ones where one person does not do all the marketing. A three-person business has an owner who wants final say. A nonprofit has a director who must see anything going to donors. A practice has a compliance-conscious partner. These are exactly the situations requiring review, and exactly the plans that do not support it.
The two workarounds, and what each costs
Shared credentials. One login, passed around. It appears to solve the problem at no cost, and it is the more common choice.
What it costs: the audit trail becomes meaningless, since every action is attributed to one account. Permission boundaries vanish, because everyone holding the password has full capability, including deletion and list export. Offboarding becomes a real exposure — when someone leaves, the credential they know still works until somebody remembers to change it, and changing it means redistributing a new shared secret to everyone else. If the platform holds contact data, this is a security problem rather than an inconvenience, and it is the kind that surfaces at the worst possible moment.
Approvals move to chat or email. The draft is screenshotted or copied into a message, someone replies "looks good," and the drafter publishes.
What it costs: the approval record lives in a different system from the thing approved, and the two are linked only by timing and memory. Six months later, establishing what was approved means searching a chat history for a screenshot. It is also lossy — a screenshot shows a rendering at one width, not the links, the sender address, the audience selection, or the unsubscribe handling, all of which are things a reviewer should be checking. The social media approval workflow guide describes what a reviewer needs to see, and most of it does not fit in an image.
Both workarounds also share a subtler cost. They make the process feel informal, and informal processes are the first thing dropped under time pressure. A review step that lives inside the publishing system is a gate. A review step that lives in a chat thread is a courtesy.
Why "we'll just be careful" fails at the third person
Two people sharing a login can often manage. They talk constantly, they know what the other is working on, and the gaps are visible.
The third person breaks it. Coordination that was a conversation becomes a system, and the system does not exist. Someone publishes something another person was still editing. Two people schedule content for the same slot. An item marked ready by one is understood as awaiting review by another. None of these require anyone to be careless; they require only that three people cannot hold the same picture in their heads without a shared record.
This is also the point at which the cost of the workaround exceeds the cost of the correct plan. Two hours a month spent reconciling who did what, at any realistic hourly value, is more than the difference between tiers. Teams rarely make this comparison because the tier difference appears on an invoice and the reconciliation time does not appear anywhere.
What to check before you buy
Seat allowances belong in the evaluation at the same level as contact pricing, and the question is more specific than how many users are included.
How many users does the tier under consideration include? Do those users have distinct permission levels, or identical access? Is there a role that can create and edit but not publish or send? Is there a state where an item waits for review, visible to reviewers without being searched for? Is there a record of who approved what and when, retained and retrievable? Can access be revoked for one person without disrupting everyone else?
Then count the people who genuinely need access — including the ones who only ever look. A board member who reviews the newsletter quarterly still needs a way to do it. Compare that count against the tier, and price the tier that fits rather than the one advertised.
NextStep includes role-based permissions and approvals within its workspace rather than reserving them for a higher tier, which reflects a view that a three-person team needs review more than a solo operator does, not less. Whether that matters depends entirely on whether anyone other than the author is supposed to see things before they go out.
The point
A review process is not a nice-to-have that mature organizations add later. For a small team it is the mechanism preventing a single mistake — a wrong price, an unverified claim, a message to the wrong audience — from reaching everyone at once, with no larger organization around it to absorb the error.
That mechanism requires three people to be able to log in as themselves, with different capabilities. If the plan does not permit that, the process will not exist, whatever the intention was when it was written down. Check the seat count before the feature grid.