A Three-Week Freelancer and a Twelve-Month Invoice
The short answer: most contractors and clients do not need a paid seat. Use guest access or a read-only portal for short engagements and client visibility, and buy a real seat only for a contractor embedded for months alongside the team.
A designer joins for a three-week sprint, and someone adds them to the project tool, the file storage, the chat workspace, and the design system. Four seats appear on four different invoices, and three of them are still there in November.
This is one of the most reliable ways small teams overspend on software. It rarely feels like a decision, because each individual addition costs little and takes ten seconds.
The underlying question is simple and almost never asked at the right moment. What does this person actually need to do, and which of your tools charges for that?
Ask What They Do, Not Who They Are
Vendors do not price by employment status. They price by capability, so the meaningful question is whether the person needs to create and edit, or only to read and respond.
Almost every mature product separates those tiers. The names vary between guest, viewer, collaborator, member, and external user, and the boundary between free and billable sits somewhere in that list.
Job title tells you nothing useful here. A contractor writing code needs the same seat as an employee writing code, while a client reviewing a proposal often needs no seat at all.
Scope the access before the engagement starts. Ten minutes with the list of tools and the tasks involved usually removes two or three seats you were about to buy.
The Four Access Patterns Behind Every Vendor’s Terminology
The first pattern is full membership. The person is inside your workspace with edit rights, appears in your directory, and consumes a paid seat in almost every product.
The second is guest or external access, usually limited to specific projects or channels. Many vendors allow a number of these at no charge or at a reduced rate, and this tier covers most contractor work.
The third is a share link or portal, which requires no account at all. Client-facing products use this deliberately, since making clients sign up is friction the vendor also wants to avoid.
The fourth is the read-only viewer, common in dashboards, documentation, and analytics. Whether it costs anything is genuinely unpredictable across vendors, which is why it belongs on your checklist rather than in your assumptions.
How Six Common Tool Categories Count People
The table shows the typical pattern per category. Treat it as a starting point for the question you ask the vendor, since individual products differ within every row.
| Tool category | Typical free tier for outsiders | What usually triggers a paid seat | Common trap |
|---|---|---|---|
| Project management | Limited guests on specific projects | Assigning tasks or editing boards | Guests promoted to members by habit |
| Chat and messaging | Single-channel or connected external users | Full workspace membership | Contractors added to every channel |
| File storage | External sharing by link | Storage under your organisation | Departed users keep sync access |
| Design tools | Free viewing and commenting | Editing files | One edit session upgrades the seat |
| CRM | Rarely any free external tier | Any login at all | Clients given logins for transparency |
| Code hosting | Public or outside collaborators | Private repository access | Access outlives the contract |
| Accounting | Accountant seat often included | Additional staff logins | Bookkeeper counted as a full user |
The trap column is where the money goes. Every entry there describes a permission granted for a good reason and never revisited afterwards.
The accounting row is worth singling out. Many vendors include a dedicated accountant or bookkeeper seat at no extra charge, and teams routinely pay for a standard seat instead because nobody read the plan page.
Where the Quiet Overspend Actually Hides
Mid-engagement upgrades are the first source. A contractor who was a commenter needs to edit one file, someone changes the role, and the workspace quietly moves to the next billing tier.
Offboarding gaps are the second and larger source. Deactivating a login often leaves the seat allocated, and on an annual plan the paid count holds until renewal regardless of who is using it.
Duplicate coverage is the third. The same contractor may sit in three tools that overlap, and the work could have happened in one of them with links to the others.
Auto-renewal closes the loop. A seat count set during a busy quarter renews unchallenged twelve months later, which is why our SaaS subscription audit guide recommends a calendar reminder before every renewal date.
What This Costs and How the Billing Behaves
Seat pricing is straightforward until people arrive and leave mid-term. Confirm current pricing and proration rules on each vendor’s official site, since terms as of 2026 vary widely by plan.
| Billing behaviour | What typically happens | How to manage it |
|---|---|---|
| Adding a user mid-term | Prorated charge on the next invoice | Batch additions to one date |
| Removing a user mid-term | Seat often held until renewal | Remove on the billing page, not just the login |
| Annual versus monthly | Annual locks the seat count | Keep contractors on monthly tools where possible |
| Guest allowances | Free up to a published limit | Track the count before it tips over |
| Plan minimums | Small teams pay for unused seats | Check the minimum before downgrading |
| Overage on usage tiers | Charged after the fact | Set an alert rather than reviewing invoices |
The removal row causes the most surprise. Teams assume that disabling an account stops the charge, and on many plans the seat remains billable until someone changes the subscription itself.
If your stack leans annual, the trade-off is worth revisiting deliberately. Our comparison of per-user versus flat-rate pricing covers when a fixed price beats a growing headcount.
The Security Question Hiding Inside the Billing Question
Seat decisions are access decisions, and the cheaper option is not always the safer one. A share link that needs no account also needs no password, and anyone who receives that link inherits the access.
Guest tiers usually sit outside your identity provider. That means a departing contractor keeps working credentials until someone removes them by hand, because single sign-on cannot revoke an account it never issued.
Weigh that against the saving on a short engagement. For a two-week job a guest seat is fine, and for a year-long one the auditable, centrally revocable seat is worth paying for.
Ownership of the output matters just as much. Files created under a contractor’s personal account can leave with them, so check whether your plan transfers ownership automatically or requires a manual step before the account closes.
Write the removal step into the engagement itself. A line in the contract about returning access on the final day converts an easily forgotten task into a deliverable.
Which Access Model Fits Your Engagement
Freelancer joining for a two-week sprint: Use guest access wherever the vendor offers it, and grant it per project rather than workspace-wide. Put a removal date in the calendar on the day you add them.
Contractor embedded for six months alongside the team: Buy the real seat and stop optimising. Guest limitations create daily friction that costs more in lost time than the seat costs in money.
Client who wants visibility into progress: Share a portal, a link, or a read-only view instead of an account. Most tools built for agencies have this feature precisely because clients are not team members.
External accountant or bookkeeper: Look for the dedicated accountant seat before buying a standard one. It is frequently included and carries the permissions the role actually needs.
Agency subcontracting part of a project: Decide whether the subcontractor works in your workspace or their own, and do not let it happen by accident. Splitting a project across two workspaces creates a handover problem at delivery.
Team whose contractor list changes every quarter: Keep the tools they touch on monthly billing even at a higher unit price. Flexibility is worth more than the annual discount when headcount moves constantly.
Five Questions Worth Asking Before You Buy
Support chat answers these in minutes, and the answers are rarely on the pricing page. Ask them once per tool and keep the replies with your subscription notes.
First, what exactly makes someone billable here? Ask for the boundary in terms of actions rather than role names, because the marketing labels are inconsistent across the industry.
Second, how many guests does our plan include, and what happens at the limit? Some products stop admitting guests, and others silently move you to a higher tier.
Third, does removing a user reduce the bill immediately or at renewal? This single answer determines whether an offboarding checklist saves money this month or next year.
Fourth, can we downgrade mid-term if the team shrinks? Many plans allow upgrades at any time and defer downgrades to the renewal date, which is worth knowing before a busy season.
Fifth, who owns content created by an external collaborator? Ask specifically about files, boards and repositories, since the default varies and the answer matters most on the day the engagement ends.
A Fifteen-Minute Routine That Keeps It Honest
Start with a single list of every tool that charges per seat, with the renewal date next to each one. Most teams cannot produce this list from memory, which is itself the finding.
Then match each external person against the tasks they perform this month, not the tasks they performed when they joined. Roles drift upward and almost never drift back down.
Remove access on the billing page rather than the admin page. Confirm that the paid seat count actually dropped, since the two screens frequently disagree.
Finally, attach the check to a recurring date instead of a memory. A quarterly pass costs a quarter of an hour and reliably finds seats nobody has used since spring.
Scope the Access Before You Send the Invite
The decision is easier when it happens before the engagement rather than during it. Write down which tools the person touches, what they must do in each, and which tier covers that.
Grant the smallest access that lets the work proceed, and put the end date in the calendar at the same moment. Nearly every wasted seat began as a reasonable grant that outlived its reason.
That habit costs a few minutes per contractor and removes the most common form of software waste in small teams. It also makes the renewal conversation far shorter.
FAQ
Does a contractor who only comments on work need a paid seat?
It depends on what they need to do. Most tools distinguish between someone who only views or comments and someone who edits, and only the second usually consumes a paid seat. Check the vendor's own definition rather than assuming, because the labels differ between products.
Do I need to buy seats for clients who just want to see progress?
Usually the client-facing sharing feature exists precisely so you do not have to. Guest links, client portals, and shared views let outsiders see specific items without joining your workspace. The limitation is that they cannot participate in internal threads.
What happens to billing when I add someone mid-month?
Most vendors bill from the moment you add the person and issue a prorated charge on the next invoice. Removing them later does not usually refund the remainder of the term, which is why short engagements are worth batching.
Can we keep paying for someone who has already left?
Yes, and it is the most common form of quiet overspend. A deactivated account often keeps its seat until someone removes it from the billing page, and annual plans hold the paid count until renewal.
Is it acceptable to share one login between two contractors?
Read the agreement rather than guessing, since terms differ. Some vendors restrict accounts to named individuals and prohibit sharing, and audits do happen on larger accounts.
Some links may be affiliate links. We may earn a commission at no extra cost to you.
This article was written with AI assistance. It is researched and fact-checked, not based on personal hands-on testing unless explicitly stated.
Comments
Post a Comment