Three signs you need a client portal
First, you can't find the version of the deliverable a client is asking about. The file is in Slack, or Drive, or someone's email. You spend ten minutes searching every time and the client notices.
Second, you're forwarding the same status update to multiple stakeholders on the client side because they don't share an inbox. The other partner asks 'are we on track?' and you re-type the answer for the third time.
Third, approvals are happening over email with 'looks good!' in reply and no record of which version was approved. Three weeks later the client says 'wait, I never agreed to that' and you have to scroll through fourteen emails to find the right reply.
Any one of those is a sign. All three at once is a fire alarm. Time to install a portal.
What a good client portal does
Six things. (1) Single source of truth for each project's status — 'on track / waiting on you / blocked / in review / done'. (2) Per-task and per-comment visibility controls so the client sees what you want them to see and not what you don't. (3) Approval workflow with a typed signature or click confirmation, recorded with timestamp. (4) Magic-link client access — no password, no account to create, just a URL the client opens. (5) File link management with visibility flags (internal / client / public). (6) An activity timeline per project so you and the client can both see what happened, when, and who did it.
A bad client portal is just a shared folder with a fancy URL. The point is the structure: visibility controls, approval workflow, status board. Without those, the portal is just project management with extra steps.
The five real options in 2026
Five honest choices, in rough order of fit for service teams.
1. ProjectKit by whatcanido — best for service teams
From $29/month. ProjectKit is purpose-built for agencies, design studios, dev shops, and consultancies. Per-task visibility, magic-link client access, approval workflows, status board, activity timeline, and (uniquely in 2026) a built-in MCP server so clients can also submit projects through Claude or ChatGPT.
Trade-off: the data model is fixed (projects → tasks/milestones/approvals/comments/files). You can't model a custom workflow. If your work doesn't fit that shape, Monday or ClickUp.
2. Basecamp — best for flat-rate generalist teams
$99/month flat. Basecamp's reason to exist is the flat rate (any team size) and the focused feature set (to-dos, messages, schedule, docs, chat). Client access works but the client needs a Basecamp guest account, which adds friction.
When to pick it: 20+ internal users, generalist project work, you want chat + project management in one tool. When to skip: client-facing portal is the main use case, you have a small team, you want the agent layer.
3. Monday.com — best when you need custom workflows
$9-$24/seat/month Basic to Pro. Monday is a no-code workspace builder. Powerful, configurable, infinite views. You spend the first week building the workspace before you use it for real work. Guest seats for clients are paid.
When to pick it: your workflow doesn't fit a standard project shape (e.g., you run campaigns with stages-within-stages and custom approval logic). When to skip: you want to use it the day you sign up; you don't have a person who can build it.
4. Notion + Notion Sites — for the DIY camp
$10-$18/seat/month. You can build a passable client portal in Notion: per-client database, status badges, embedded files, public pages for the client side. The trade-off is you spend a weekend or three building it and you maintain it forever.
When to pick it: you love Notion, your team is already there, your customisation needs are specific. When to skip: you want approvals with typed signatures, magic-link access without an account, or you want to focus on client work instead of building tools.
5. Salesforce Experience Cloud — when nothing else fits the enterprise process
$25-$150+/seat/month depending on which Salesforce edition you're attached to. Enterprise-grade portal infrastructure with deep customisation. Useful if you already live on Salesforce and need a branded customer-facing portal at scale.
When to pick it: you're at 100+ employees, you already run on Salesforce, you have a Salesforce admin on staff. When to skip: anything smaller than that — it's overbuilt and overpriced for a 5-person agency.
How to decide for your agency
Three questions in order. (1) How many internal users do you have? Under 10 → ProjectKit Studio ($29) or Agency ($59). 10-25 → Basecamp ($99 flat) or ProjectKit Team ($129). 25+ → Basecamp or Monday Pro. (2) Do you need the agent layer (clients submitting via Claude or ChatGPT)? Only ProjectKit supports it natively. (3) Does your work fit projects/tasks/milestones cleanly? If yes, ProjectKit is the fastest setup. If no, Monday or Notion.
Time-to-first-real-use matters more than price. Pick the tool you can start using in real client work this week, not the one you can theoretically scale into in two years. The migration tax is real but smaller than the cost of not having a portal at all.
Frequently asked questions
Do my clients really want a portal?
Most clients are neutral — they want their projects shipped on time with no surprises. The portal is mostly for you (the agency) to communicate status without drafting weekly emails. Clients adopt the portal once they realise it answers their questions faster than emailing you.
How do I get clients to use the portal instead of emailing?
Two things. (1) The link in every kickoff email and every status update; never paste status into the email body. (2) The portal answers their question before they ask: status board shows where the project is, what's blocked, what's waiting on them. The path of least resistance to 'is my project on track' should be the portal, not email.
What if a client wants to bring their own portal tool?
Rare but happens. Two options: (1) Mirror the status into their tool weekly, treat their tool as a downstream of yours. (2) Use their tool as primary and your internal one as a private backend. Option 1 scales better.
Do I need a portal if I only have one client?
No. One client + shared Drive + weekly email is fine. Get a portal when you have 3+ active clients or 3+ internal team members involved with each client.
How is the agent layer relevant to a client portal?
In 2026 a meaningful share of inbound client requests come through Claude or ChatGPT (a client asking their AI to 'start a new project with our agency, here's the brief'). ProjectKit's MCP server lands those requests directly in your project queue. The client doesn't have to log into the portal to start a project; the portal is just where the work tracks once started.
Try ProjectKit
Client portal + project management for agencies, design studios, dev shops. Magic-link client access, approval workflows. From $29/month.
Start free →