Do Agencies Need a Client Portal, or Just Better Updates?
By Sebastiaan Jansen · · 9 min read
Most agencies do not need a client portal on day one. What they need is a written update the client can trust, sent on the day the client expects it, saying what shipped, what is blocked, and which decision is waiting. Add a login once the client has to approve a file, pay an invoice, or pull assets without emailing you.
What the login is for
A portal is a login the client uses to see their own work: open requests, files, invoices, and the latest approved scope. A shared page, a guest seat, or a custom site can do the same job. Either the client looks something up, or the client does something. If neither happens this month, the login is overhead.
Looking things up means status, dates, and the last decision, and email handles that fine. Doing things means approvals, uploads, and payments, which need permissions and a file that does not vanish into a thread.
If you cannot name one action the client will take inside the login this month, ship the email first.
When a client portal earns its place
Add the login when at least one of these holds for several accounts, not just for one awkward client.
- The client must approve creative, copy, or a release, and you need a better timestamp than "they said yes in Slack."
- Files move both ways every week: brand kits in, exports out, marks on PDFs.
- Several people on the client side ask for the same status, and they do not share an inbox.
- Invoices or change orders have to sit next to the work they pay for.
- You are handing off access, and email attachments are where things get lost.
One sponsor who "would love a portal" is not a reason. Usually that person wants fewer chase messages, and a Friday note with a single link to the board you already run will get them that.
The login also costs time every week. Someone has to decide what the client may see, archive old projects, and answer "I cannot log in." Once it goes stale, clients learn to ignore it and email you anyway.
When a better update wins
A written update wins when the client buys an outcome and checks in now and then, instead of living in your tools. Software retainers and campaign management often work like this. The client has a day job and does not want a second Monday inbox. They just want to know whether Friday's promise is still Friday.
In that setup, a client communication platform is whatever already reaches them: email plus one shared thread, or a Slack Connect channel with a written rule for what belongs there. The habit matters more than the channel, and a tool that posts updates nobody reads is not communicating anything.
Four habits do more than a new login:
- One owner on your side writes the update, instead of the whole team pasting in fragments.
- Send it on the same weekday with the same subject pattern so the note is searchable. "Northwind / week of 6 Oct" beats a fresh, witty subject every time.
- Keep the note short enough to read on a phone, and keep facts apart from asks.
- Put the decisions the client owes you in a list with dates, not in a paragraph they can skim past.
If three people send three versions of the truth, no new product will fix that.
What the update must contain
Use five blocks. If a block is empty, write "nothing" so the client can see you checked.
- Shipped: what the client can see or use now, with the link.
- In progress: the few items moving this week, named in the client's words. Ticket IDs can sit beside the name, but not in place of it.
- Blocked: the one fact that stops the next step, and the person who can clear it.
- Decide by Thursday: approvals, copy, budget, access. One line each, plus what happens if they stay silent.
- Next date: when they will hear from you again, even if the news is "no change."
Leave out how hard the week was. Cycle time, who was out, and the argument about scope belong in your tracker. The note carries the outcome: "Homepage copy is in review. Comments by Thursday and the page ships on the 18th. Silence and it ships on the 25th with the approved draft."
A worked week: one retainer, two Fridays
Northwind is a fictional product company on a monthly build retainer. The agency runs the work as tickets. Maya, head of product, is the sponsor, and two engineers on her side sometimes ask for status. She has no login.
On the first Friday, the update is split across tools. The producer posts in Slack Connect that onboarding is "almost done." A designer emails a Figma link without asking anything. An engineer asks Maya's engineer for an API key in a separate thread. On Monday, Maya asks what "almost done" means, and the producer has to rebuild the week from three tools. The work itself was fine, but the record of it was scattered.
Then the agency sets a rule. One Friday email goes from the producer to Maya, with her engineer copied. Subject: Northwind / week of 6 Oct. Slack is only for same-day questions. Figma is for design, and the email says whether a decision is waiting there.
The next Friday's note:
- Shipped: password reset is on staging. No production release this week.
- In progress: onboarding checklist, three of five steps in review.
- Blocked: production waits on the billing sandbox key, requested two days ago. Owner is Maya's engineer.
- Decide by Thursday: the empty-state sentence in the "Reset / empty" frame. Silence means that sentence ships.
- Next date: the following Friday, same subject pattern.
Maya replies on Tuesday with the key and a yes on the sentence. The producer does not retell it in Slack. The next note says the key arrived and the release went out Wednesday.
A login would have held the same five blocks behind a password, and Maya would only have opened it after an email told her to. The email was doing the work.
Change one fact and the login becomes the right tool. Say legal must approve every release note, and three people who are not in Slack need the PDF plus a record of who approved it. Now the Friday email becomes a pointer: the file and the approver list live in the permissioned space, and Thursday is the deadline. The email is still what gets a busy person to look. If you cannot tell these two situations apart, you will buy a login for the first and forget to staff it for the second.
A board the client can open
When clients ask for visibility, they usually mean "do not make me wait for a call to find out we slipped." A read-only guest link works if the columns use the client's language: "Waiting on Northwind," "Building," "On staging." Hide spikes and arguments. If the guest sees dozens of cards, they will email you anyway.
The guest link is the list, and the Friday email explains it. When the two disagree, reply to the email. Do not publish a board your own team does not keep current. Agency project management software is the layer under this choice.
Drop the Monday call that only repeats the email, and keep a monthly meeting for roadmap and money. New asks go into the tracker first, then into "Decide by Thursday" if they change a date or a fee. A marketing agency's launch calendar works the same way: if a date is not on the board, it is a rumor.
Each option fails differently. Shared Slack gets noisy and things sink. Email is slower but searchable. A guest seat can show too much. A purpose-built login tends to get abandoned. Pick the tool that fits the action you named, and name who maintains it. Project management consulting is worth paying for when you cannot see your own work, and a poor buy when all you wanted was a nicer login.
Keep the client record separate from the work
You want two layers that point at each other. The work record is tickets: scope, owner, stage, date. The client record covers who Maya is, what she cares about, which meeting produced which promise, and which files she sent. A single chat log falls apart the day the producer is out.
Meeting notes are where this usually breaks. A call creates promises that never become tickets, so the Friday note gets written from memory. One named person, not "the team," should turn each promise into a ticket before the day ends and flag it if the wording is still soft. Turning meeting notes into tickets the same day keeps the note and the board in agreement.
Falrow holds both layers for teams that want one system: requests become tickets, and a client CRM turns Granola notes, files, or a paste into reviewed tickets. You then write the Friday email from the tickets the client is allowed to see. Other tools can keep the same split if you are strict about it. Either way, you cannot run a book of accounts from memory, and that is what client management covers: contacts, history, and the work tied to those contacts. Falrow for agencies is built around tickets, cycles, and a roadmap counted from tickets. It does not replace the email the client already reads.
Score the next ninety days
Give yourself one point for each item you can already do without a new login.
- Send the five-block note every week to your top five accounts, four weeks in a row.
- Show a guest a board that contains only work you can explain without a meeting.
- Turn meeting promises into tickets within one working day.
- Write down one action a client would take in a permissioned space that they cannot take by replying to an email.
With three or four points, a new login is optional. With zero or one, it only puts an empty process on display. Two points, plus a real approval or file problem from the list above, justifies a one-account pilot for a month. Do not roll a login out to every client because the pilot's champion liked the sidebar.
After four Fridays the note should get shorter, because shipped and blocked items are settled facts by then. If it stays long, cut scope or renegotiate the visibility you promised.
FAQ
Do small agencies need a client portal?
Usually not. A small team loses more hours maintaining logins than it saves on status questions. Use a weekly note and a guest link until a client keeps needing to upload, approve, or pay inside a permissioned space. Look again when producers can no longer track every account without the tracker.
What should clients be able to see and do?
Show only what they will open more than once a month: approvals, shared files, invoices, and a short status. Leave out internal stages, rough estimates, and draft arguments. A crowded home screen sends people back to email, and then you maintain two systems while the client uses one.
Is this the same thing as the project tool?
No. The project tool is where your team runs the work. A client-facing login is a filtered view, or a separate app, covering what that account may see and do. Guest access in the tracker works if you hide internal tickets. It fails when guests inherit the board your team uses to think out loud.
How often should agencies send updates?
Weekly is the default for an active retainer or build. Twice a week fits a launch or an incident. Monthly fits quiet work, and the note should say that it is quiet. The Scrum Guide treats the sprint review as a working session on the increment, a different event from a status email. If you run a review, keep it. Keep the email cadence too, even when the news is dull, because silence looks like a slip.