How to Onboard a Client With a Branded Portal Before the First Request

This guide is for agencies, studios, consultancies and freelancers who are taking on a new client. By the end you'll have a branded portal, a welcome note, an invited contact and one tested request, so the client knows where everything goes. It takes about 45 minutes and suits beginners.

Before you start

To onboard a client with a client portal, create their portal, add their brand details and files, define the request types they can send, write a short welcome note, invite their contact with a no-password link, and send a first test request together. Do it before the first real job and the client already knows where to send things.

Most onboarding goes wrong in a different way. The kickoff call happens, a folder of files changes hands, and then the first request arrives as a forwarded email with half the detail. This guide fixes that by teaching the client where requests go before they have one.

Gather these first. Each one saves you a stall halfway through:

• The client's website. Dora sets up the portal from it, so you don't type out brand basics by hand.
• Logo, brand files and guidelines. If the client has them handy, upload them in Step 2. If not, you'll ask for them there.
• The main contact's email address. One person gets the first invite. You'll add others later.
• A short list of the work you do for them. Five or six lines is plenty. It becomes your request types in Step 3.
• One person who owns the relationship. Someone has to send the welcome note, run the test request and answer the first question. Pick them now.

Do one more thing before you open anything: write down how onboarding works today. CoordinateHQ's onboarding guide starts the same way, by documenting your existing workflow and finding the pain points. Jot down where your last client's first request came from, what details you had to chase, and what got lost. That list tells you which steps below matter most for you.

Finally, decide what you want to come through the portal and what can stay in email. The honest answer is usually "everything can come either way". Clients can send requests and reply by email, and Dora keeps the portal up to date. You're only deciding where the record lives.

Step 1: Create the client portal

Give each client their own portal from day one. One home per client means requests, files and approvals live in one place instead of four threads, two chat apps and someone's text messages.

A client portal is a private space where a client sends requests, finds files and signs off on work. A branded client portal puts your name and logo on it, so it looks like part of your studio rather than a tool you borrowed. If you want the long version of this setup, there's a separate walkthrough on how to set up a client portal for your whole agency. This step is just the per-client part.

Here's how to do it:

1. Open Dora and add a new client.
2. Enter the client's website. Dora reads it and sets up their portal in about a minute, so the portal already reflects who they are.
3. Check the portal name. Use the client's company name, not a project name. Projects end. The client stays.
4. Confirm your logo and name show on the portal. Clients should see your brand as the one welcoming them.
5. Skim what Dora pulled in from the website. Fix anything that looks off, like an old logo or a wrong company name.

If you're setting up your very first client, that's free. Your first client costs nothing, forever, so this is a safe place to practice.

Example. Say a design studio signs a new retainer client, a regional outdoor-gear brand. The owner adds the brand's website and the portal appears under the studio's name with the client's details in place. Ten minutes later the studio has a branded home for the retainer, before a single request exists.

A live 30-minute session on building a client onboarding portal with project tracking shows one way of doing a similar job with a project tracker. You don't need a tracker here. The client isn't managing a project, they're sending asks.

The usual mistake: building one generic portal and planning to customize it later. "Later" turns into never, and the client's first impression is a portal that doesn't look like theirs or yours. Set it up from their website now. It's faster than cleaning up a template afterwards.

Step 2: Add brand details and files

Add everything you'll need to start work now, not when a request is waiting on it. Clustdoc defines client onboarding as welcoming a new client, collecting the information and documents you need, and getting the working relationship started. The collecting part is the one that usually drags.

Put the answers in the brand library so they're in one place for your whole team. That means the designer who joins in month three doesn't have to ask the client for the logo again.

Do this:

1. Upload logos in every format you have. Vector first, then PNG.
2. Add fonts, or note which fonts the brand uses and where to get them.
3. Add colors. Hex codes are best, and a screenshot of the palette is fine if that's all you have.
4. Upload the client's brand guidelines, the document that says how the brand looks and sounds. If they don't have a formal one, upload their best past work instead.
5. Add anything else you'll reuse: product photos, a voice-and-tone note, templates, past campaigns.
6. Make a short list of what's missing, then ask the client to add it themselves. You've already shown them where it goes.

For a longer list of what to collect before kickoff, use this client onboarding checklist for agencies. Don't try to collect everything in week one. Collect what the first three requests will need.

Example. A web agency is onboarding a new client for a site refresh. Before kickoff, the agency uploads the logo it pulled from the client's site, adds the colors and fonts, and lists what's missing: the vector logo, the font files and the latest product photos. The client uploads those into the portal that afternoon, rather than sending them in three emails over two weeks.

Login details deserve extra care. Don't collect them in a plain email thread where they sit forever in someone's inbox. Use your password manager's sharing feature instead.

The usual mistake: asking for files over email and losing them. An attachment in message eleven of a thread is a lost file. If a client emails you a logo anyway, don't scold them. Drop it into the library yourself so the next person finds it in the right place.

Step 3: Define request types

Decide what a client can ask you for, and what you need to know every time they ask. This is where onboarding turns into client request management: a clear set of choices, with the right details attached to each.

Start from the work you do and the pain points you wrote down earlier. CoordinateHQ pairs workflow mapping with defining goals, and your request types should follow the same logic. If you always chase the same three details on social posts, those three details belong on the "new social post" type.

Here's the process:

1. Open your list of the work you do for this client.
2. Group it into 3 to 6 request types. Examples: new design, edit to existing work, bug fix, new page, question.
3. For each type, write the details you always need. Keep it to what you'd otherwise chase: goal, deadline, audience, reference links, sizes or formats.
4. Set the types up in Dora so they appear as clear choices when the client starts a request.
5. Share the client's own request address so they can also just email you. With email intake, Dora turns that email into a request, asks for whatever's missing, and writes the brief.

That last step is the point of the whole guide. A client who emails "can you tweak the hero image?" still ends up with a proper request, and nobody had to learn anything new. If you want to see what a good brief looks like, this guide to a creative brief clients fill in shows how to keep the questions short enough that people actually answer them.

Example. A marketing agency onboarding a local fitness studio sets up four request types:

Four types cover almost everything that studio will ask for. If something doesn't fit, the client emails it and Dora sorts it out.

The usual mistake: creating too many categories. Fifteen request types makes the client stop and think about which one to pick, and a client who has to think about the form will email you instead. If two types need the same details, merge them. You can always add one later once a pattern shows up.

Step 4: Write a welcome note

Write a short note that says what the portal is, where to send things, and what happens next. That's a client portal welcome message in three jobs. It sets expectations before the first request, which is much easier than correcting habits afterwards.

Zoomforth's B2B guide frames onboarding as a framework aimed at reducing churn and speeding time-to-value. A welcome note that tells the client exactly what to do first is the cheapest way to speed that up.

Keep it under 120 words. Here's how:

1. Open with one warm sentence: who you are and that you're glad to be working together.
2. Say what the portal is for in one line: requests, files and sign-off, all in one place.
3. Give one example of a first request, so the client has something concrete to copy.
4. Say that email works too. Clients don't need to log in to ask for things.
5. Say when they can expect a reply, such as "within one working day".
6. Sign it with a real name from your team.

Here's a note you can copy and edit:

Hi Priya,

Welcome aboard! We've set up a private space for everything we do together: requests, files and sign-off, all in one place.

To start, just tell us what you need. For example: "Can we update the homepage banner for the spring sale?" You can send it through the portal or by email. Either way, we'll ask for anything we're missing and write it up so nothing gets lost.

You'll hear from us within one working day. If we need something from you, we'll ask once, clearly.

Looking forward to it,
Sam

That's about 100 words. Notice what it leaves out: no process diagram, no policy list, no five-page welcome packet. Anything the client needs later, they can ask for.

You also don't need to be the one answering every follow-up. Your AI account manager answers clients when they mention Dora on a request, asks for what's missing, and updates the brief. Decisions about the work stay with your team, so the note can honestly promise a fast reply without you sitting by your inbox.

Example. The design studio from Step 1 adapts the note for its outdoor-gear client. The example request becomes "Can we resize the trail-pack hero for the newsletter?" The client sends exactly that as their first request, and it's already in the right shape.

The usual mistake: writing a long manual nobody reads. If the note needs scrolling, it's too long. Cut anything the client can learn by doing it once.

Step 5: Invite the contact with no password

Invite the main contact with a no-password link, and tell them it's coming. This is where many clients decide whether the portal is easy or annoying, so keep it light.

Plenty of onboarding setups still work the other way. HoneyBook's onboarding guide describes setting up client access and sharing a user name and password. That works, but it's our view that every password a client has to remember is a reason to fall back to email. With Dora, the invite signs them in, so there's nothing to forget and nothing to reset.

To invite clients to the portal:

1. Send a quick heads-up first: an email or a message saying "You'll get an invite from us in a few minutes. It's the private space we told you about." Two lines is enough.
2. Add the main contact's email address to the client's portal.
3. Send the invite. It carries your name and logo, so it looks like it came from you.
4. Put your welcome note in the heads-up email, so it's the first thing they read.
5. Make sure the contact knows they can still just reply to any email from you. That's the safety net.

Resist the urge to invite everyone on day one. Start with the one person who'll send most requests. Add the finance contact, the second stakeholder or the intern later, when they actually need access. One confident user beats five confused ones.

Example. The web agency emails the client's marketing manager on a Tuesday morning: "Heads up, an invite is coming in five minutes. Click it and you're in. No password." The manager clicks, lands in a portal with the agency's logo and the client's own logo, and sees the files they uploaded the day before. Nothing to set up, nothing to remember.

Approvals live in the same portal. Later, when the client signs off on work, one-click approvals happen right there, so you won't need a second login for that either. Clients do their part with one click.

The usual mistake: inviting everyone at once, or skipping the heads-up. A cold invite from an unfamiliar sender looks like spam, and a flood of invites to people who don't know why they got one makes the client wonder what they signed up for. One person, one heads-up, one invite.

Step 6: Send a first test request

Send one small, real request together with the client, so they see the full flow once. Clients learn a tool by using it, not by reading about it, so a ten-minute test run beats any welcome packet.

Pick something low-stakes but real: a small edit, a social post, a question. Real matters, because a pretend request teaches the client to expect pretend answers.

Here's how to run it:

1. Ask the client to send the request however they like: through the portal, or by email.
2. Watch what happens. Dora reads the request, spots what's missing and asks the client for it in the thread.
3. Check the brief. It should read clearly enough that a teammate who's never met the client could start work from it.
4. Deliver the small piece of work, and ask the client to approve it. Show them the one-click approval so they've done it once.
5. Ask the client two questions: "Did you know where to send that?" and "Is there anything you'd have wanted to know first?"
6. Fix whatever they say. Adjust the welcome note, drop a request type, or tighten a required detail.

Then confirm the client knows where each type of thing goes: new asks go to the portal or your email, files go to the brand library, sign-off happens on the work itself. If they can say that back to you in one sentence, you're done.

Example. The marketing agency's fitness-studio client sends the test request as a one-line email: "Need a post for Friday's open class." Dora asks which platform and whether there's a photo. The client answers by email. The agency delivers the post, the client approves it in one click, and the whole thing takes a day. The next request is a real campaign, and it arrives in the right shape.

How to know it worked

There's no client case data behind this guide, so here's a simple way to test it on your own work. It uses Zoomforth's idea of speeding time-to-value as the measure of onboarding success.

1. Baseline. For your last three new clients, count how many first requests arrived outside the portal and how many details you had to chase.
2. Intervention. Run these six steps for your next three clients.
3. Outcome. Compare the same two counts, plus the days from invite to the first complete brief.
4. Timeframe. Review after each client's first 30 days.

If the chase count drops and the invite-to-brief time shrinks, the setup is working. If not, look at Step 3 first, because vague request types are the most common cause.

The usual mistake: waiting for the first big project to find problems. If the flow is broken, you want to learn that on a small edit, not on a launch with a deadline.

Common mistakes

Even a tidy setup can slip. Here are the problems agencies hit most, and the quickest fix for each. For a longer list, see these client portal mistakes small agencies make.

One more pattern is worth naming: the client who still sends requests through three different channels. That's normal in week one. The answer isn't a stricter rule, it's making every channel lead to the same place. There's a short piece on how to stop clients sending requests in different channels if you want to go deeper.

Checklist

Run through this before you tell the client they're all set.

1. Create the client portal. Add the client's website, name the portal after the company, and confirm your logo and name show.
2. Add brand details and files. Upload logos, fonts, colors, guidelines and past work to the brand library, and ask the client to fill in what's missing.
3. Define request types. Pick 3 to 6 types, list the details you always need for each, and share the client's request address.
4. Write a welcome note. Keep it under 120 words, give one example request, and say that email works too.
5. Invite the contact with no password. Send a heads-up, then invite the main contact only, and add other stakeholders later.
6. Send a first test request. Run one small real request together, check the brief, get a one-click approval and confirm the client knows where each thing goes.

When all six are ticked, the client knows exactly where to send things, and you've skipped the scattered threads before they started. Set up your first client portal free with Dora: your first client is free, forever.

Frequently asked questions

What are the steps to onboard a client with a client portal?

There are six: create the portal, add brand details and files, define request types, write a welcome note, invite the contact with no password, and send a test request. Do them in that order, before the client's first real job. The whole thing takes about 45 minutes for one client.

Do clients have to log in to the portal?

Not with a password. The invite signs them straight in, and after that they sign in with a link sent to their email. Clients can also send requests and reply by email, and Dora keeps the portal up to date, so they only open it when they want to see where things stand.