Client Portal for Web Design Feedback: What It Should (and Shouldn't) Do

You've decided you want a client portal. Somewhere your design clients can leave feedback on the site instead of it arriving as an email with three attachments, a text about the header, and a comment your project manager mentioned in passing on a call.

Before you pick one, it's worth being clear on what a portal actually needs to do — because a lot of them are built to look impressive in a sales demo and turn out to be more setup than your clients will ever use.

The One Requirement That Matters More Than Any Feature

A client portal has exactly one job: be easier for the client than whatever they're doing now. If it's harder than texting you, they'll keep texting you, and you'll have paid for a tool that sits empty while the real feedback still arrives in your DMs.

This sounds obvious, but it's the thing most portals get wrong. They add login flows, project boards, tagging systems, and multi-step forms — all genuinely useful for you — and forget that the client's side of the interaction needs to take about as much effort as sending a text. If it doesn't, adoption fails silently. Nobody complains that the portal is too complicated; they just quietly go back to email.

See what a portal looks like when it's built for the client's side too →

What a Web Design Feedback Portal Actually Needs

A link, not an account they have to remember. Your client should be able to bookmark one URL — invite-only, private to them — and use it every time, without a "forgot password" flow standing between them and reporting something.

A way to show, not just describe. Design feedback especially benefits from this — "the spacing here looks off" is much clearer as a 20-second screen recording than as a paragraph. If your portal only accepts typed text, you're still going to get "the button looks weird" with no further detail.

Automatic context. Page URL, browser, device — captured without your client having to know what any of that means or copy-paste it themselves. This is the difference between fixing something in one pass and sending a reply asking "which page, and on what?"

Visible status. The single biggest reducer of "just checking in" messages is a client being able to see, themselves, that something is "In Progress" or "Fixed" without emailing you to ask. This alone removes a huge share of the noise in a typical client relationship.

Scoped privacy. One client should never see another client's feedback, project, or history. This matters more than it sounds — it's the difference between a portal and an open comment board.

Features That Sound Useful and Mostly Aren't (For You)

Kanban boards with a dozen columns. Design feedback for a small agency doesn't need "Backlog → Triage → In Design → In Dev → QA → Staging → Done." It needs "Submitted → In Progress → Fixed." More columns mean more decisions your client has to make about where something belongs, which they won't make correctly, which means you'll be re-sorting their input anyway.

Browser extensions on the client's side. Any step that requires your client to install something before they can leave feedback is a step some percentage of them will never complete. A link that works in any browser, on any device, wins every time over "first, install this Chrome extension."

Public comment threads. Some portal tools let anyone with a link comment, which is fine for a design mockup review but wrong for an active client site — you don't want a former employee, a competitor, or a random visitor able to leave feedback meant only for your paying client.

How Lantern Handles This

Lantern gives every client their own portal on this exact model: one invite-only link, no browser extension, no account juggling. Clients submit feedback by typing a description or recording a short screen capture — genuinely useful for design work, since "move this two pixels" is easier to show than to write — and the page, browser, and device attach automatically.

Statuses are simple by design: new, in progress, fixed, closed. Your client can check any time without messaging you, and if you run WordPress or Umbraco sites, the report button can live directly inside the CMS admin your client already logs into, rather than a separate portal they have to remember exists. For a broader look at how that's set up, see the client portal page.

Pricing is flat: £12.50/month for up to 5 clients on the Individual plan, £30/month for unlimited clients on the Team plan, with a 14-day free trial and no card required to start.

A Quick Test Before You Commit to Any Portal

Send yourself the sign-up flow as if you were your least technical client. Time how long it takes to submit one piece of feedback, start to finish. If it's under a minute and didn't require installing anything, it'll probably get used. If you found yourself frustrated at any point, so will they — and they'll go back to texting you instead.

Start your free trial — no card required →

Add your first client and send the portal link in the next five minutes. See if it actually gets used before your next design review call.