Journal

How to onboard design clients so projects start right

A practical client onboarding process for designers: welcome pack, intake questions, one decision-maker, kickoff and a signed-off brief.

How to onboard design clients so projects start right

Most design projects that go wrong don't go wrong in the middle. They go wrong in the first week, when nobody agreed on who signs off, where files live, or what "done" means. By the time the first review arrives, those gaps have turned into missed deadlines, surprise feedback from a stakeholder you never met, and a scope that has quietly doubled.

Client onboarding is the fix, and it doesn't need special software. It needs a short, repeatable sequence you run every time a contract is signed. Below is the process we use and recommend: what to send, what to ask, what to set up, and what to put in writing before you open Figma or Framer.

Why onboarding matters more than the kickoff call

A kickoff call feels like the start of a project, but it is only one step. Onboarding covers everything between "the client said yes" and "the first real design work begins". That window is where expectations get set, and expectations are much easier to set than to reset.

Good onboarding does three things:

  • Removes guesswork. The client knows what happens next, when, and what you need from them.
  • Collects inputs early. Brand assets, logins and content arrive before they block you.
  • Shows you run a professional process. Clients who feel looked after give clearer feedback and argue less about invoices.

Send a welcome pack within 24 hours of signing

Speed matters here. The client has just committed money and is at their most engaged. Send a short welcome email or one-page document the same day, or the next morning at the latest.

Keep it to one screen. It should include:

  • A one-paragraph summary of what you are building, in plain language.
  • The project timeline with dated milestones, not "week 2" or "phase 3".
  • How you communicate: which channel, your working hours, and your usual reply time.
  • What you need from them, with a due date for each item.
  • A link to book the kickoff call.

Save this as a template and adjust it per project. Writing it from scratch each time is how items get forgotten.

Use an intake questionnaire before the kickoff

Don't spend the kickoff call asking for facts the client could have typed into a form. Send a short questionnaire first and use the call to discuss the answers. A form built in Tally, Typeform or a Framer form works fine; the tool matters less than the questions.

Ask about:

  1. Goals. What should this project change for the business in six months? Push for something measurable, like more demo bookings or fewer support emails.
  2. Audience. Who is it for, and what do those people need to believe before they act?
  3. References. Three sites or products they like and one they dislike, with a sentence on why.
  4. Constraints. Fixed launch dates, legal reviews, existing brand rules, technical limits.
  5. People. Who gives feedback, and who has the final say.

That last question is the one most designers skip, and it causes the most pain later.

Name one decision-maker in writing

Feedback from five people with equal authority is not feedback; it is a negotiation you get pulled into. Before the work starts, agree on one person who consolidates comments and approves each stage. Other stakeholders can contribute, but their input goes through that person.

Put this in your welcome pack or project brief in a single sentence, for example:

All feedback is collected and sent by Maria. Her approval at each milestone moves the project to the next stage.

If a senior stakeholder appears late and wants to reopen approved work, you can point back to this agreement and treat the request as a change rather than a revision.

Run a focused kickoff call

With the questionnaire answered, the kickoff can be 45 minutes instead of two hours. Use it to confirm, not to collect.

A structure that works:

  • 10 minutes: walk through their answers and ask follow-up questions on goals and audience.
  • 10 minutes: review references together and agree on what to take from each.
  • 10 minutes: go through the timeline, milestones and review process.
  • 10 minutes: clarify what is in scope and, just as important, what is not.
  • 5 minutes: confirm next steps and the date of the first review.

Record the call with permission, or take notes live in a shared document. Send a written summary the same day. That summary becomes the reference point when memories differ three weeks later.

Set up the workspace before you design

Give every project the same structure so both you and the client always know where to look. For a typical website project, that means:

  • A shared folder with subfolders for brand assets, content, and deliverables.
  • A Figma file with pages named by stage, such as Research, Wireframes, Design, and Handoff.
  • A Framer project, if you build there, with the client invited as a viewer until handoff.
  • One place for feedback, whether that is Figma comments or a single thread. Not both.

Ask for access to anything you will need later now: domain registrar, analytics, the existing CMS, and stock photo accounts. Login requests that arrive the day before launch are a common cause of delays.

Agree on how feedback and revisions work

Your contract probably says how many revision rounds are included. Onboarding is where you explain what that means in practice. Clients rarely read contracts closely, so restate the rules in plain words.

Cover these points:

  • What counts as one round: a single, consolidated set of comments from the decision-maker.
  • How long the client has to respond, and what happens to the timeline if they are late.
  • The difference between a revision (adjusting what was agreed) and a change (adding something new).
  • How changes are priced and approved before you start them.

Saying this early feels awkward for about a minute. Saying it for the first time in the middle of a dispute is far harder.

Close the first week with a project brief

By the end of onboarding you should have everything needed for a one or two-page project brief: goals, audience, scope, out-of-scope items, milestones, decision-maker and feedback rules. Send it to the client and ask for a short written confirmation, even just "Approved" in an email.

This brief is the most useful document in the project. You will check designs against it, settle disagreements with it, and reuse parts of it in your case study at the end.

Conclusion

Onboarding is unglamorous work, but it decides how the rest of the project feels. A same-day welcome pack, a questionnaire, one named decision-maker, a short kickoff, a tidy workspace and a signed-off brief take a few hours in total. Turn each piece into a template once, and every new client starts from a clear, calm first week instead of a scramble.

Oybek Ruziev

Designer & Framer developer · AidanCreates

Keep reading

All posts