How to Set Up a Client Portal for Your Agency in One Afternoon

If you run an agency, studio, consultancy or any team that does custom work for clients, this guide gets you a live, branded client portal with your first client onboarded. You'll define the requests clients can send, brand the portal, add a client and set their monthly allowance, send the invite, and run a real test request. Budget about three hours; no technical skills needed.

Before you start

Gather these first so you don't stall halfway through.

• A platform chosen. This guide uses Dora, but if you're still comparing, Zapier's roundup of customer and client portal software covers seven options. It's an overview, not an endorsement.
• Your logo, brand colors and website URL. The website is what Dora uses to set up your portal.
• One real client to pilot. Pick someone who sends work regularly and is friendly enough to give honest feedback.
• Their last 10 requests. Scroll your inbox or Slack. These are the raw material for Step 1.
• A monthly request allowance in mind. For example, "8 requests a month on this retainer." A rough number is fine.

A quick opinion before we start: don't build a portal from scratch with a no-code app builder. The build isn't the hard part. The hard part is whether clients send complete requests and sign off, so spend your afternoon on request types and onboarding, not on layouts.

Step 1: Define your request types

A portal is only useful if clients know what to ask for. Guides from Zoom and Cognito Forms both start the same way: decide what the portal needs to do before touching any settings. For an agency, that means request types.

1. Open your pilot client's last 10 requests.
2. Group them by what the client was actually asking for. You should land on 3 to 6 groups.
3. For each group, write down the 3 or 4 things you always need to start (for example: target audience, deadline, reference examples).
4. Name each type in the client's language, not yours. "New landing page" beats "Web design deliverable."

Example: a design studio looks at 10 requests and ends up with four types: logo, social media set, landing page, and revision. Each gets a one-line note on what's needed. A logo needs brand personality words and competitors to avoid. A revision needs the original file and what to change.

The usual mistake: building a long form for every type. Clients abandon long forms or fill them with "TBD." Keep the list short and let Dora's AI account manager ask for whatever's missing in the thread, then write the brief for you.

One boundary: people who ask about portals online often want logins, service views and invoice payment in one place, like this small-business owner on Reddit. Dora handles requests, files and approvals. Invoicing stays in your billing tool.

Step 2: Brand the portal

A portal that looks like your agency feels like part of your service, not a third-party tool you've pushed onto clients. This is also where a branded client portal earns trust on the very first click.

1. Sign up for Dora and add your agency's website. Setup takes about a minute and pulls in your basics.
2. Check your agency name and upload your logo if it didn't come through cleanly.
3. Preview what a client will see. Your logo and name appear on the portal and on every email Dora sends.
4. Write a short welcome message (see below).

Portal tools typically offer a few branding touches. SimplePractice's setup guide, for instance, covers a custom domain, a welcome email before first sign-in, and a greeting on first sign-in. In Dora, your branding is included by default. A portal on your own domain is a custom white-label setup, so book a demo if you need it. Most small teams don't need it on day one.

Example welcome message: "Hi! This is where you'll send us requests, find your files and approve work. Easiest start: just email us like always, and we'll keep everything here organized."

The usual mistake: skipping the welcome message. Without it, the first thing a client sees is an empty portal and no instructions, and they go back to email without telling you.

Step 3: Add your first client

Your portal is just a shell until a client lives in it. Cognito Forms treats adding clients as a core setup step, and the same goes here.

1. Add your pilot client from their website, so their name, logo and brand details fill in.
2. Open their brand library and upload what you already have: logo files, color palette, fonts, brand guidelines.
3. Add the request types from Step 1 as the examples you'll tell this client about.
4. Set their monthly request allowance, using the number you chose earlier. You can warn the client or queue extra requests when they go over.
5. Decide how extra work is handled: send it as an estimate the client approves in one click.

Example: a 5-person agency starts with its most active retainer client, a 6-request-a-month brand refresh. It sets an allowance of 6, uploads the brand kit, and leaves the other 14 clients in email for now.

The usual mistake: importing every client at once. Don't. Your first client is free, forever, so pilot with one, fix what you learn, then add the rest. After that, it's $10 a month per client with unlimited team seats.

Step 4: Invite the client

The invite is the moment the portal becomes real, and it's where most rollouts quietly fail. Clients ignore tools that arrive without context.

1. Before sending, set your sign-off rules. Turn on auto-approval so work that sits unanswered gets approved after a set number of days (the default is 7). Pair it with one-click approval and nudges for quiet clients.
2. Send the invite. The client signs in with no password.
3. Add a personal note on top of the automated message. Two sentences is plenty.
4. Tell them what to send first: a real request, today, not "whenever."

Clients don't have to learn a tool. They can reply to any update from their inbox, and your team still sees everything in the portal.

Example note: "Hi Priya, we've set up a place for your requests and files. Nothing changes about how you reach us. Email us as usual, and this keeps it all organized. First up: can you send the Q3 social ask?"

The usual mistake: inviting without explaining what to send first. A portal with a login and no instructions gets opened once and abandoned.

Step 5: Run a test request

Nothing in this step comes from a source; it's recommended practice from setting these up. Test before the client does the real thing, because that's where you'll find the gaps in your request types.

1. Send a deliberately vague request by email, the way a rushed client would. Try "make a banner."
2. Send a second request through the portal, with a bit more detail.
3. Check what Dora did. Did she ask for the size, placement, copy, deadline and brand assets? Did she turn the answers into a clear brief?
4. Confirm files landed in the right place in the brand library.
5. Walk one piece of work through approval, both by one click in the portal and by email.

Example: "make a banner" comes back as a complete brief covering the campaign, dimensions, copy, brand colors and due date, with no back-and-forth from you. Compare that to your own creative brief clients will fill in and see which one the client actually completes.

The usual mistake: testing only as the admin. Open the invite as the client, on your phone if you can, and use your colleague as a second pair of eyes.

Then measure it. Before launch, note how many of your pilot client's requests needed a follow-up question and how many days sign-off took. After two to four weeks, compare. There's no case study to point to here, so your own numbers are the proof.

Common mistakes

Dora isn't the right tool if you need invoicing, contracts, a CRM or internal project planning (Gantt, sprints, time tracking) inside the same portal. Keep those tools and use Dora for the client side. For more ways small teams trip up, read these client portal mistakes.

FAQ

How does a client portal work?

Clients get a branded space for requests, files and approvals, so nothing lives in scattered email threads. With Dora they can also skip the portal entirely: their email intake turns messages into briefed requests, and they can reply to updates from their inbox.

Do clients have to log in?

No. They can send requests and answer updates by email, and the invite signs them in without a password. The portal is there when they want a clear view of requests and files.

Checklist

1. Define 3 to 6 request types from your pilot client's last 10 requests.
2. Brand the portal: add your website, logo and a short welcome message.
3. Add your first client from their website, upload brand files and set a monthly allowance.
4. Invite the client with a personal note, set auto-approval days and tell them what to send first.
5. Run a test request by email and in the portal, check the brief and approval flow, and compare follow-ups and days to sign-off after a few weeks.

Ready to try it? Try Dora free: your first client is free, forever.