Client portal and collaboration: what clients actually use
What clients really use in a client portal and what they ignore. Improving delivery habits, queries as a workflow and the power of fewer features.
The short answer
Clients use four things in a portal: sending in a receipt or invoice, approving something, seeing their current result and answering questions from the firm. Almost everything beyond that, from elaborate dashboards to doing their own bookkeeping, is not touched again after the first week. A firm that builds its portal around those four gets better delivery and less email traffic. A firm that rolls out an everything-portal mainly gets support questions.
What clients actually use
Client behaviour is more predictable than portal brochures suggest. What sticks:
- Sending in a photo of a receipt. By far the most used feature, provided it lives on the phone and takes at most two actions: take photo, send. Every extra step, such as picking a category or typing a description, halves the usage. Categorising is work for processing, see Processing purchase invoices automatically, not for a business owner standing in a car park.
- Approving something. A sales invoice that is ready, a return that needs to go out. An approval is a small, bounded action with a clear question and a button. That works precisely because there is nothing to interpret.
- Seeing the current result. Not twelve charts, but the answers to the questions the owner actually has: how am I doing, what should I set aside for VAT, who has not paid my invoices yet. Three figures that are correct beat any dashboard.
- Answering questions. When the firm asks about a specific item ("whose card payment is this, 84 euros?") and the client can answer in two taps, it often happens the same day.
What clients do not use
- Elaborate dashboards. The business owner is not a controller. Charts without interpretation lead either to indifference or to panic over a seasonal effect, and in both cases to a phone call.
- Doing their own bookkeeping. Nearly every attempt to have clients code independently ends in correction work that costs more than the bookkeeping itself. The exception is the client with their own administrative staff, but that person is really a user of the software rather than a portal visitor.
- Browsing document archives. Clients rarely look anything up; they want to hand something in or find something out.
- Messaging features that duplicate email. A general chat in the portal becomes a second inbox nobody maintains. Communication only works in the portal when it is attached to a concrete document or a concrete question.
Improving delivery habits without endless reminders
Poor delivery is rarely unwillingness. It is usually a mix of unclarity (what exactly do I need to send?), friction (it takes too many steps) and the absence of any noticeable consequence. Something can be done about all three:
- Lower the threshold to almost zero. The receipt-photo feature on the phone, a fixed forwarding email address for invoices, and a bank feed so the client never has to deliver bank statements again. Whatever arrives automatically never needs a reminder.
- Make the request specific. "Please send in your records" is a request nobody acts on. "Three documents are missing: the July rent invoice and these two card payments" is a list that can be worked through. That requires the firm to know per administration what is missing, and that is exactly what a good work-in-progress overview makes visible.
- Attach a noticeable rhythm. A firm that delivers monthly figures as soon as the records are complete gives the client a reason to deliver completely. Closing with recorded exceptions when delivery is late is part of that, see Setting up the monthly close.
- Automate the reminder, not the relationship. An automatic message about three missing documents is fine. The conversation with a client who is structurally late, you have yourself.
Queries as a workflow
The biggest time sink in the collaboration is not the delivery but the query: the unclear payment, the receipt without context, the private payment that looks like a business expense. In many firms those questions run through email, and then the predictable happens: the answer arrives in a different thread, is never recorded against the entry, and at year-end someone asks the same question again.
So treat queries as a workflow rather than as correspondence:
- The question is attached to the item or document itself, with the photo or amount included.
- The client receives the questions bundled, weekly for instance, instead of as loose one-offs.
- The answer comes back in the place of the question and becomes part of the file.
- Open questions older than two weeks appear on the exception list of the firm.
The result is twofold: the client answers more often because it costs them less, and the firm records everything without extra work, which also benefits the audit trail.
Fewer features, clear roles
The temptation when choosing a portal is the longest feature list. Practice rewards the opposite: a small number of features that exactly match the division of roles between firm and client. The client delivers, approves, looks and answers. The firm processes, checks, reports and asks. Every feature that breaks that division, such as a posting screen for the client, creates work instead of saving it.
Clear roles also mean that what a client sees can differ per client. An owner with their own administrative employee may do more than a freelancer who logs in once a month. The portal has to handle those differences without the firm maintaining a custom setup for every client.
Next step
Assess your current portal against the four features from the first section: how many actions does a receipt take, how quickly does a question reach the client, and do the figures the client sees match what you report? For comparison, see how the dashboards and reports in Giroo limit the client view of the current result to what they genuinely want to know, while your firm sees the full set of books.
Content reviewed: August 2026.