What is a client portal? How it works, with a worked agency example

A client portal is a private login for one client's work

A client portal is a secure website, usually on your own domain, where each client logs in to see only their own work with you: requests, files, messages, status and invoices. It replaces the mix of email threads, shared drives and payment links that most service businesses start with. The client gets one place to ask and check. The agency gets one record of what was asked, delivered and paid.

A portal is not the same as a project management tool with guest access. The difference is that a portal is built around the client's view: what they can buy, submit, approve and pay for, under your branding.

How a client portal works, step by step

Products differ, but the flow is similar. The steps below follow the client journey that ManyRequests documents in its help center.

1. The client buys or is invited. They purchase a service from a catalog or an order form link. After a successful card checkout, a client account is created automatically.
2. The client logs in at the agency's portal address and lands on a dashboard showing their services and requests.
3. The client submits a request. They choose Create Request, pick the service, fill in the request form and can set a due date.
4. The team works and reports status. The request moves through statuses that the client can see. Questions and files go in the request's discussion, not in email.
5. The client gives feedback on the file. They click on an image, PDF or video to pin a comment where the change is needed.
6. The client closes the request by marking it complete, and can leave a review.
7. Billing sits in the same place. The client sees invoices, plan and remaining hours or credits, and can update payment details.

If payment is by bank transfer instead of card, the invoice shows as pending and the client can submit requests once it is marked paid.

A worked example with real settings

Take a three-person video editing studio setting up a portal in ManyRequests, using settings named in its documentation and prices read on 3 October 2026.

The setup order and the things to prepare first are covered in the client onboarding guide.

Common mistakes when setting up a client portal

• Keeping email open as a second channel. If requests are still accepted by email, the portal record is incomplete and clients learn to ignore it.
• Launching without a request form. A blank text box produces vague briefs. Decide the required fields per service first.
• Ignoring seat pricing. Some portals charge per team member, some per client or contact, some a flat fee. The cheapest headline plan is often not the cheapest total.
• Moving every client at once. A staged move with two or three friendly clients finds the gaps sooner. See the staged portal migration plan.
• Skipping the client's view. Check what a client actually sees before inviting anyone. ManyRequests lists a client impersonation mode for this.

When a paid client portal is worth it

A paid portal is worth it once you have enough clients that requests get lost, or once you sell recurring plans and need billing tied to the work. Before that point, several products have a free tier that is enough to try the idea.

If you already know what the portal must do, write it down first using the portal requirements checklist, then compare the client portals for agencies against it.