Client portal pricing has a structural problem. The value of a portal rises with how many clients use it, and the price rises the same way. Teams respond rationally by rationing access: only the main contact gets a login, everyone else gets forwarded emails, and within a quarter the portal is a place three people visit and status updates have gone back to the inbox.
Worth being clear at the start about what kind of portal this page describes, because the term covers three different products.
Three things called a client portal
The branded product portal. Your logo, your domain, your visual design, often your own onboarding flow. It is part of what you sell. Dock, Assembly, Copilot, SuiteDash, and Moxo aim here. If the portal is a feature of your product experience, buy one of these. InfoLobby is not it, and configuring it to look like one will disappoint everybody.
The document exchange. A secure place to swap files. Accountants and law firms use these heavily. Usually bundled with practice management software.
The shared operational workspace. Clients see the actual records your team works from: their projects, requests, deliverables, status, and files. There is no separate portal layer to keep in sync, because there is no separate layer. This is what InfoLobby does well, and it is the honest scope of this page.
How it works here
You invite the client's people to a workspace. They get their own account and see the records in that workspace, at the permission level you set: Read Only, Read and Write, or Admin.
Every plan includes unlimited users. Inviting eleven people from a client instead of one does not change the bill. This is the whole argument, and it is worth doing the arithmetic on.
At twenty client contacts, portal products charging per external user commonly run $200 to $600 a month. InfoLobby plans are $29, $59, or $129 depending on tier, regardless of how many clients you invite. The saving matters less than the behavior change: when access is free, you stop rationing it, and the portal becomes where status lives rather than a place you occasionally point people.
Keeping internal work internal
This is the part to get right before inviting anyone, because the failure mode is embarrassing.
Access is granted per workspace. The pattern that works is a workspace per client, holding only that client's records, plus a separate internal workspace holding your pipeline, margins, internal notes, and anything half-finished.
Two rules:
One workspace per client. Do not put five clients in one workspace and try to filter by client. Permissions are at the workspace level, so a shared workspace means shared visibility.
This is the one place where plan choice actually constrains the design, so check it before you start. Starter includes 3 workspaces, Team 10, and Business 25. One workspace per client plus an internal one means Starter suits two clients, Team suits nine, and Business suits twenty-four. Beyond that you need Enterprise, or you group smaller clients into a shared workspace and accept that they can see each other's records. Unlimited users is genuinely unlimited; workspaces are not, and that is the number to plan around.
Internal commentary stays internal. If your team needs to discuss a deliverable candidly, that discussion belongs on a record in the internal workspace, not as a comment on the record the client can read. Decide this convention on day one and write it down, because it is not enforced for you.
What the client actually sees
| Table | Key fields | Visible to client |
|---|---|---|
| Projects | Name, status, start date, target date, owner | Yes |
| Deliverables | Name, project, status, due date, approved date | Yes |
| Requests | Description, submitted by, priority, status, resolution | Yes |
| Files | Document, type, version, uploaded date | Yes |
| Internal Notes | Project, note, author | No, separate workspace |
The client sees a real view of the work, not a summary someone maintains separately. That is the actual advantage over a status document: nobody has to update it, because it is the same record your team already updates.
Add a request form so clients can raise things without logging in at all. Embedded web forms create records directly, which is often better than a login for occasional contact.
Where a real portal product wins
Be honest about these before choosing.
- Branding. Clients log into InfoLobby and see an InfoLobby workspace. There is no white-labeling, no custom domain, no theming to your brand. For agencies where presentation is part of the sell, this is a real objection and worth weighing properly.
- Self-service signup. Clients are invited, not self-registering. Consumer-scale onboarding where thousands create their own accounts is not the model.
- Billing and payments. No invoicing, no payment collection, no subscription management. Portals that exist mainly so clients can pay you need different software.
- E-signature. No legally binding signature capture.
- Curated portal UX. Clients see a database interface, which is capable and not especially soft-edged. Technically comfortable clients are fine with it. Others may need more hand-holding than a purpose-built portal requires.
Who this suits
Good fit: agencies and service teams sharing project status, deliverables, and documents; businesses that want every client contact in the system rather than rationing seats; teams whose portal content is genuinely their operational records; relationships where structured, current data matters more than visual polish.
Poor fit: anyone selling the portal as part of a branded product experience; consumer self-service at scale; portals whose main job is billing or signature.
Related
- Custom CRM for the relationship side of the same records
- Project operations for the delivery work behind the portal
- Complaint management software for when client requests are problems
InfoLobby plan pricing and limits, and the competitor claims on this page, were last checked on 2026-08-20. Competitor pricing changes often and varies by region, so confirm current figures on the vendor's own pricing page before deciding. Our plans are on the pricing page.
