Build a client portal for your agency's customers: what it needs, and when custom is worth it
Short answer: A client portal is a private, logged-in page where each of your agency's clients can see their own files, approvals, reports, invoices and messages, and nobody else's. Before you pick a tool, write down the five jobs it must do and the four security questions it must pass. For most agencies a ready-made portal subscription or a shared workspace is enough, and a custom build only pays off when your process is unusual, your client count is large, or the portal is part of what you sell.
You are tired of clients emailing for files, approvals and status, and you want one place to send them, built your way.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Decide what the portal must do and what must stay private, then choose the cheapest option that meets that list. That order matters, because agencies usually pick a tool first and discover its limits after the first client logs in. This page gives you the requirements list, a security and ownership checklist, published costs for common options at 10, 50 and 200 clients, and a rule for when a custom build is worth it.
Other pages on this site cover the basics, so this one does not repeat them. For a tool-by-tool comparison read agency client portal software. For setup steps read how to create a client portal for your agency. For the build cost read custom client portal cost. This page is the planning layer before those: what the portal needs, how to judge any option, and what to ask whoever builds it. A portal is a project with an owner, not a one-off tool install, so decide at the start who in your agency will look after it, who adds each new client, and who answers when a client cannot log in. Without that person, even a well-chosen portal slowly stops being used.
What the portal needs to do
Write your own list, but most agencies need these five jobs. Mark each as must have, nice to have or not needed.
- Files in and out. The client uploads logos, access details and briefs, and downloads finished work. This is where most email chasing comes from. A tool such as Content Snare, a service that sends clients a checklist of things to supply, exists for exactly this job.
- Approvals. The client sees a draft, says yes or asks for changes, and the answer is recorded with a date. See building a client approval portal for creative work.
- Status and reports. What is done, what is next, and the results of campaigns.
- Messages and decisions. One thread per project instead of ten email chains.
- Invoices and contracts. The client sees what they owe, and signed documents are stored. See building e-signature into a client portal.
Then list three non-negotiables of your own, for example your logo and web address on the portal (often called white label, meaning it looks like yours, not the vendor's), single sign-on with the client's Google account, or a client who can see several projects.
The security and ownership checklist
A portal holds your clients' files and sometimes their customers' data. Ask these questions of any tool, freelancer or agency, including me.
| Question | What a good answer looks like |
|---|---|
| Can client A ever see client B's data? | Access is restricted per client by design (in a database this is called row level security), and the builder can show you how it is tested |
| Where are the secrets kept? | Secret keys stay on the server and never appear in code the browser downloads. Supabase, a database service, says its secret key must never be used in the browser or exposed to customers |
| Who can log in, and how are logins protected? | Individual accounts, no shared passwords, a limit on login attempts, and a log of who did what |
| Who owns the data and can I get it out? | You own the content, and there is an export in a normal file format. Ask for the export before you sign |
| Who owns the code if it is custom? | Written into the contract. See who owns custom software code you paid for |
| What happens to a client's data when they leave? | You can delete it and show that you did |
| Backups? | Named frequency and a tested restore. Supabase, for example, lists no daily backups on its Free plan and 7 days on Pro, and says files in storage are not in its backups |
Agencies often also upload client documents into AI tools. If your portal will do that, read uploading client documents to an AI tool first and tell clients in your contract.
Ready-made versus custom: the real options
| Option | What it is | Published cost (as of November 2026, USD) | Fits when |
|---|---|---|---|
| Shared folder or shared page | A Google Drive folder or Notion page shared per client | Notion lists Free, then $10 (Plus) and $20 (Business) per member per month billed yearly, or $12 and $24 billed monthly (as of November 2026); guests are free but see only pages shared with them | Under about 10 clients, simple files and notes |
| Client portal subscription | SuiteDash, an all-in-one client portal and CRM, or similar | SuiteDash lists $19, $49 and $99 a month (START, THRIVE and PINNACLE), with unlimited clients and staff on every plan and storage of 100 GB, 500 GB and 2 TB; extra storage is listed at $5 a month per 250 GB, and white labeling is listed from the START plan | 10 to 200 clients with a standard process |
| Request-collection tool | Content Snare, which collects client content against a checklist | Content Snare lists $35, $71 and $119 a month on annual billing ($42, $85 and $143 monthly), with limits on active requests (20, 50, 100) and team users (2, 5, 10) | Your pain is chasing clients for assets |
| No-code build | A portal assembled in Airtable (a spreadsheet-style database app) or Bubble (a no-code app builder) | Airtable lists $20 and $45 per editing user per month on annual billing; read-only collaborators and form submissions are not charged. Bubble lists plans from Free (50,000 workload units a month) to Starter at $32 a month on annual billing (175,000 units), and its paid plans are measured in workload units, so cost can grow with use | You want your own layout and can maintain it |
| Custom build | Software written for you | Priced by the hours of work; see the cost article | The portal is core to your offer or your process is unusual |
Other portal products exist, so check any vendor's own page for current prices, because plans and caps change, and the headline "unlimited clients" does not mean unlimited storage or features.
What it costs at 10, 50 and 200 clients
Using only the published numbers above, and nothing else:
- 10 clients: a shared Notion page or a SuiteDash START plan is enough. Content Snare Basic fits if you rarely have more than 20 requests open at once.
- 50 clients: shared folders get hard to police. SuiteDash is not priced by client count, so the plan depends on storage and features, not head count. Content Snare's active-request limit (20 on Basic, 50 on Plus) may force a higher plan.
- 200 clients: storage, staff roles and the time to onboard each client decide the choice more than the sticker price. This is where agencies start to price custom work against a year of subscriptions.
Whatever you choose, add the hidden cost: the hours to set up each client. If a portal takes 30 minutes to set up per client and you onboard 100 a year, that is 50 hours, and you can price that.
When a custom portal is worth building
- The portal is part of the product you sell, so it needs your brand, your logic and your data.
- Your process does not fit a subscription (for example approvals that depend on a client's own sign-off chain).
- You have outgrown the subscription's caps and are paying for several tools stitched together.
- You need connections to your CRM, billing and calendar that no ready-made tool offers.
- You already built something with a no-code tool and it has become slow, costly or fragile.
Skip custom if you have fewer than about 15 clients, your needs are files and approvals, and nobody on your side will own the system. A subscription you can cancel is a safer start.
A per-client onboarding checklist
Every new client should go through the same short list, so the portal is set up the same way each time and nothing is forgotten:
- Create the client's space and add only the people who need it, using their own email addresses.
- Upload the starting material: the contract, the brief, the project plan and the contact list.
- Send the welcome message with the one-page guide and a date for the first check-in.
- Ask the client to complete their first task in the portal during the first week, for example uploading their logo.
- At day 30, check that they have logged in and used it. If not, ask why.
What to do when a client leaves
This is the step most agencies skip, and it is the one clients ask about. Write down the exit routine before you need it: remove the client's logins, give them an export of their files, approvals and messages in a normal file format, delete or archive the rest on a stated date, and record that you did. If you keep copies for legal or tax reasons, put that in the contract, with how long you keep them. Keep the portal's own backups in mind too: Supabase, for example, says its Free plan has no daily backups and that files stored through its storage service are not included in database backups, so a custom build needs its own plan for files.
Rolling it out so clients actually use it
A portal that clients ignore is just another inbox. Pick one client to pilot, move one live project into it, and tell every other client: "From now on, files and approvals go here, and I will not act on email attachments." Send a two-minute walk-through, a short video or a one-page guide. Check logins at 30 days: if a client has not logged in, ask why before you build more. Keep one fallback: say what to do if someone cannot get in.
Blur Studio: build, finish and care
Where I fit is narrower than "we build portals". A portal usually reaches me in one of three states: not started, half built in a no-code tool that has become hard to maintain, or live and in need of care. For a new build I start from your five jobs and the security checklist above. For a half-built one I review what exists, fix the access rules and finish the missing parts instead of starting over. For a live one I handle updates, backups and changes. The details are on the business page, and nothing here depends on using me.
How I'd approach this
Week one: list your five jobs and mark must haves; count your clients and the clients you expect in a year; and run the security table against your top two options. Week two: pilot with one client on the cheapest option that meets the must haves. Week three: ask that client what they used and what they ignored. Decide at day 30: keep the subscription if it works, or write a one-page brief for a custom build, with the jobs, the connections, the export requirement and the ownership clause. Blur Studio builds the custom version, including connections to your CRM and calendar, finishing half-built portals and ongoing care, if you want help with that brief: see the business page.
Related guide: signs a marketing website is not enough.
Questions people ask
What is a client portal for an agency?
It is a private area where each client logs in to see their own files, approvals, reports, messages and invoices. It replaces long email threads with one place per client. See what a client portal is.
Do I need a custom client portal?
Usually not at first. A subscription or a shared workspace covers files, approvals and messages for most agencies. Consider custom when the portal is part of what you sell or your process does not fit any tool. See custom client portal cost.
How do I keep one client from seeing another client's data?
Ask the vendor or builder how access is restricted per client and how it is tested. In a custom database build, row level security (rules that limit each login to its own rows) is the usual method. Secret keys must stay on the server.
Can I make the portal look like my own brand?
Some subscriptions let you use your logo and web address, often called white label, and some limit it to higher plans. Check each vendor's page for the plan you would buy.
What should I ask before I sign with a builder?
Who owns the code and data, whether you get an export, how backups work and are tested, how logins are protected, and what ongoing care costs. See who owns custom software code.
Is a shared Google Drive or Notion page good enough?
For a handful of clients with simple needs, yes. It gets harder to manage as clients grow, because permissions are per page or folder and approvals are not recorded. Notion guests only see pages shared with them individually.
How much does a portal cost per month?
As of November 2026, SuiteDash lists $19 to $99 a month and Content Snare $35 to $119 a month on annual billing, with different limits. Custom builds are priced by the work. Check vendor pages for current plans.
More in this topic: Websites: custom builds, portals, lead capture and site care (9 guides) →