What a Client Portal Is, and What It Is Not
The category name covers two completely different products. Buying the wrong one is the most common and most expensive mistake in this market.
A client portal is a place outside your organisation where a client signs in and does something: sees what you owe them, gives you what you owe them, and makes the decisions the work is waiting on. That is the whole definition, and the important word is does. A portal where a client only reads is a document delivery mechanism with a password, and while there is nothing wrong with that, it is not what the category promises and not what changes how an engagement runs.
The distinction that matters commercially is between a portal that stores copies and a portal that shows records. In the first, somebody inside the firm uploads a file, and the portal holds a copy that is accurate at the moment of upload and decays thereafter. In the second, the portal reads the same deliverable, the same information request, the same change request that the internal team is working on, filtered to what the client is entitled to see. The first requires a person to keep two things in step. The second cannot drift because there is only one thing.
The four things clients actually come to do
Across firms and sectors, client portal usage collapses into four jobs. A portal that does these four well will be used. A portal that does twelve things adequately and these four awkwardly will not.
- Answer a request. The firm needs something: a document, a figure, a confirmation. The client wants to provide it against the specific item, not by replying to an email with an attachment and hoping it reaches the right person.
- Sign something off. A deliverable is finished and the firm needs acceptance. This is a contractual act and needs to be recorded as one.
- Find a document the firm sent. Not search a folder tree: find the report from the March committee, now, on a phone, in a meeting.
- See what is waiting on them. One list, in one place, of every decision and every request the engagement is currently blocked on.
What a portal is not
It is not your internal product with rows filtered out. This is worth stating because it is a tempting shortcut and a poor outcome. A client who can see the shape of your internal tooling can also see how much of it is being withheld, and the experience reads as being given a restricted account on somebody else's system rather than a place of their own. The tab that is greyed out is more conspicuous than the tab that was never there.
It is not a replacement for conversation. Firms that adopt a portal hoping to reduce client contact are usually disappointed, and the ones that succeed use it to make contact more useful: the status is already known, so the meeting is about the decision rather than the update.
It is not a document management system. Most firms already have one, the portal reads from it, and a portal that becomes a second store of record creates exactly the drift it was bought to remove.
The landscape, honestly
This market has three distinct groups and they are not really competing with each other, whatever the comparison pages suggest.
The first is secure file exchange with a client-facing wrapper. ShareFile is the reference point here, and products in this group are strong on transfer, compliance and retention. If the job is genuinely moving documents securely, this group solves it and the rest of the category is overhead.
The second is the portal as a standalone product, typically white-labelled and aimed at agencies and smaller professional firms. Clinked, SuiteDash, Ahsuite and Moxo sit in this space with different emphases: branding and workspaces, an all-in-one bundle with billing, simplicity and price, and workflow orchestration respectively. These are good at being a portal and generally have to integrate with whatever runs the work.
The third is a portal that is a view onto a delivery system, which is where professional services automation platforms and firm-specific practice suites land. Kantata, Scoro, Accelo and Rocketlane approach this from the delivery side; SuiteFiles and Karbon approach it from accounting practice management. The portal here is thinner as a standalone artefact and stronger as a window, because the records it shows are the live ones. Atlas by WRX Stack sits in this third group, with the portal reading the same engagement records the delivery workspace does.
The buying question is therefore not which portal is best. It is which of those three problems you actually have.
Signals that you need the third kind
- Somebody inside the firm spends time each week making the client-facing view agree with the internal one.
- Clients ask for status by email despite the portal, because the portal is behind.
- A deliverable exists in three places and you are not certain which is current.
- You cannot answer, without asking somebody, what the client is currently waiting on you for.
- Client sign-off is verbal, and the record of it is a line in a meeting note.