You have five clients. Each one asks the same question every week: "What's the status of our project?" You use Linear internally, so the data is right there. The obvious move is to add them as guests. But Linear client access through guest seats creates problems that go well beyond the per-seat price tag.
Guest seats give clients full read-write access to your teams. They can see internal comments, edit issues, and poke around your backlog. There's no read-only mode, no branding, no way to show only what's relevant to their project. It's your internal workspace with a different login.
What most teams actually need is a Linear client portal: a separate, curated view where clients see their project status, submit requests through a clean interface, and never touch your internal workflow. That's a fundamentally different product than a guest seat, and the gap between the two is where the hidden cost lives.
Why Linear client access through guest seats falls short
A guest seat in Linear grants full access to every team you add that person to. They can view issues, create new ones, edit existing ones, and comment on anything within those teams. They just can't see teams they haven't been invited to.
That's fine for a contractor who needs to file bugs or update their own tickets. It's the wrong tool for a client who wants to check whether the homepage redesign shipped this week.
There's no read-only mode for guests. No way to show a filtered view of just their project. No way to hide internal discussions, estimates, or labels they don't need to see. You either give them full team access or nothing.
The costs you don't see on the pricing page
The per-seat fee ($8/user/month on Basic, $14 on Business) is the obvious one. But the real costs are structural.
Your internal conversations aren't private
Every issue you create, you're thinking: "Can the client see this?" Internal notes about timeline pressure, budget concerns, team capacity. None of that belongs in front of a client. But with guest access, it's visible by default unless you restructure your workspace around it.
Some teams solve this by creating separate "client-facing" teams in Linear, duplicating issues across internal and external boards. Now you have two sources of truth and twice the maintenance.
Clients see everything, not just their project
Guest access is team-scoped, not project-scoped. If two clients share a team, they can see each other's work. There's no way to filter a guest's view to show only the issues tagged with their label or assigned to their project. Every issue in that team is visible to every guest.
For agencies, this is a dealbreaker. You're either creating a separate team per client (fragmenting your workflow) or accepting that clients can see work that isn't theirs.
Your workspace becomes their workspace
Clients who can create and edit issues will create and edit issues. That's what the UI invites them to do. You'll find client-created tickets mixed into your backlog, issues reassigned, descriptions modified. It's not malicious, it's just what happens when you give someone a tool designed for your internal workflow.
No branding, no polish
A guest sees your raw Linear workspace. There's no way to brand it, add your agency's logo, or create a polished experience. Your client's marketing lead is looking at the same developer-focused interface your engineers use. For agencies selling a premium service, that matters.
The onboarding tax
Every new client stakeholder needs a Linear account, an invitation, team assignment, and a walkthrough of an interface designed for engineers. Your client's marketing lead doesn't want to learn what cycles, triage, and SLAs mean. They want to see a list of tasks and which ones are done.
The math at scale
An agency with 8 clients and 2 stakeholders per client is paying $128/month on the Basic plan, or $224/month on Business. For access that doesn't even fit the use case. That's $1,536 to $2,688 per year.
Guest Seat Cost Calculator
See what you'd spend on Linear guest seats vs a dedicated client portal.
Linear guest seats
€80/mo
€960/year
Helium Rooms Pro
€39/mo
€468/year
That's €492/year you'd save with a dedicated portal — and your clients get a better experience.
What a real Linear client portal looks like
A client portal isn't a cheaper guest seat. It's a different product built for a different job.
Filtered, relevant views. Clients see only the issues that belong to their project, filtered by label, team, or project. Not your entire backlog.
Private internal conversations. Your team discusses implementation details, estimates, and blockers in Linear. Clients see status updates and completions, not the internal sausage-making.
Client-specific request tracking. Instead of clients creating issues in your backlog, they submit requests through a dedicated interface. You triage and prioritize on your side. They track the status of their requests on theirs.
Branded experience. Your agency's logo, colors, and domain. The portal feels like part of your service, not a third-party tool you're making them log into.
No Linear account required. Clients get their own login (or no login at all for public rooms). No need to explain what Linear is or how it works.
The tools that deliver this today
Dedicated Linear client portal tools
Helium Rooms (full disclosure: this is our product) connects to your Linear workspace and lets you create branded, read-only portals per client. You pick which projects, teams, or labels to expose. Clients get login-protected access, can submit requests through the portal, and never see your internal workspace. It's an official Linear integration, so data syncs automatically. There's a free tier if you want to try it.
SteelSync offers similar core functionality with a focus on public roadmaps and release tracking. Lindie existed in this space but is no longer actively maintained.
The key difference from guest seats isn't price (though it's cheaper too). It's that these are purpose-built for the client-facing use case: filtered views, private conversations, branded experience, request tracking. Guest seats give you none of that.
Manual updates (the baseline)
Slack messages, email recaps, telegram messages. This works when you have one or two clients. It breaks at three or more, because you're now a human status bot spending 30 minutes per client per week writing updates that are outdated by the time you send them.
The Linear API (build your own)
Linear has a solid GraphQL API. If you have very specific requirements and engineering time to spare, you can build a custom client portal. The tradeoff: you're now maintaining a second product alongside the ones you're building for clients.
The decision framework
1-2 clients, low-touch: Manual updates or a free tier of a portal tool. The overhead is manageable.
3+ clients, multiple stakeholders: A dedicated portal tool is the clear choice. Not just because it's cheaper than guest seats ($48+/month in seats vs. a flat rate), but because it solves the actual problem: giving clients a polished, relevant, private view of their project.
Enterprise, highly custom needs: The Linear API or guest seats with strict workspace segmentation. You'll need someone maintaining it.
The worst option is defaulting to guest seats because they're there. They're designed for internal collaborators, not external clients. Using them for client access means paying more for less, exposing internal conversations, and creating ongoing maintenance work that scales with every new client you onboard.