The Client Onboarding Process That Saves 10 Hours Per Project

Article

10 Oct

You know that feeling when you've finished the design kickoff call and the client says "I'll send you some inspiration boards by next week". Two weeks later, you're chasing them for content. The timeline slips. You're redesigning layouts because half the copy you need hasn't arrived. You're firefighting instead of designing.

This happens because you don't have an onboarding process. And if you don't have one, you're losing roughly 10 hours per project to back-and-forth, confusion, and waiting around.

I used to be that designer. I'd get excited about a project, jump straight into the design phase, and then spend weeks in content limbo. The fix wasn't rocket science. It was implementing a structured onboarding that happens before any design work begins. That single change has saved me hundreds of hours and, more importantly, it's made my clients happier because they know exactly what's happening and when.

The Pre-Project Questionnaire That Actually Gets Completed

Most designers use questionnaires that are either useless or too long. They ask about "design preferences" without asking the questions that matter. Then clients ignore half of it anyway.

Your questionnaire needs to be strategic. It should be long enough to get what you need, but short enough that busy people will actually complete it. Aim for 15 to 20 key questions, not 50.

Here's what you actually need to know:

Brand fundamentals. Ask for their existing brand guidelines, logo files, brand colours, tone of voice guide, and any competitor sites they admire. Don't ask "what are your design preferences?" Ask "which three competitor websites do you respect and why?" The answer tells you far more.

Existing content and assets. What do they already have? Product images, testimonials, team photos, videos? Get a clear inventory before you start designing. If they have to shoot new photos, you need that timeline upfront.

Goals and success metrics. Why are they rebuilding their site? More leads, more sales, better user experience, updated branding? What does success look like six months after launch? These answers guide every design decision.

Technical requirements. Do they need e-commerce? Blog functionality? Member login? Form collections? Scheduling tools? Squarespace handles most of these, but you need to know what's required so you can scope the build correctly.

Integrations and third-party tools. Are they using email marketing software, CRM systems, analytics tools, or anything else that needs to talk to the website? Get this list before design starts.

Timeline and revision expectations. How soon do they need this launched? How many revision rounds do they expect? What's their availability for feedback calls? Lock this in writing before you start.

Use a Google Form or Typeform for this. Make it mandatory before the kickoff call. If they can't be bothered to fill it in, that's a red flag about how engaged they'll be throughout the project.

Set Up the Squarespace Site Before the First Design Call

Don't wait for the kickoff call to create the site. Do this the day after they sign the contract.

Create a new Squarespace 7.1 trial site on a test domain. Set up the basic structure: pages, menus, collections for blog or portfolio if needed. Add them as a contributor with editing access so they can see everything in progress without being able to mess with your settings or delete sections you've built.

Send them a Loom video showing them how to log in, where to find things, and what they'll be able to do throughout the process. Set the expectation that this is a living document that they'll watch evolve.

Before the kickoff call, you've already confirmed the site structure is right. You've saved yourself an hour of "wait, can Squarespace do X?" conversations. You've made the client feel like work has already started.

Content Collection: The Part Everyone Struggles With

This is where most projects grind to a halt. You've done the design, but you're waiting for the homepage headline, the service descriptions, the about page copy, the team bios.

Make content collection a formal part of your onboarding, not something that happens randomly during the project.

Create a detailed content brief. For each page, specify exactly what you need: headline (character count if possible), subheading, body copy, call-to-action text, images (dimensions and subject), and any metadata. Make it granular. Don't say "about page copy". Say "about page hero section: headline (max 60 characters), subheading (max 120 characters), main body text (300-400 words), team bios (4 bios, 75 words each with headshot photos, minimum 1200 x 1200px)."

Set a deadline for content submission. Make it clear what happens if they miss it. "We'll proceed with placeholder content and you'll review it during the testing phase." Having a deadline stops "I'll send it later" from becoming "I'll send it in three months".

For clients who genuinely can't produce copy, offer copywriting as an add-on. Price it appropriately. Don't absorb the cost because they didn't plan ahead.

Setting Expectations: What's Included and What Isn't

The biggest source of scope creep is unclear expectations. Write down exactly what's included in the project scope. Revision rounds, design options, features, training, timeline, everything.

Be specific. Not "unlimited revisions" but "two rounds of revisions on the homepage, one round on secondary pages". Not "we'll set up your email signup" but "we'll integrate your Mailchimp list and embed the signup form on the homepage and footer".

Include what's explicitly not included. Stock photos? That's an add-on. Additional pages beyond the quoted scope? That's an add-on. Custom coding beyond CSS? That's an add-on.

Put this in writing in your proposal and your project onboarding document. Reference it the moment someone asks for something outside the scope. It's not you being difficult. It's you having been clear from the start.

The Kickoff Call Agenda That Works

This call should never be a fishing expedition where you're asking questions that should have been answered in the questionnaire. You've already got that information. This call is about alignment and relationship building.

Here's the structure:

First five minutes: quick social warmup. You're human. They're human. Build a connection.

Next ten minutes: walk through your onboarding process. Show them the questionnaire responses you received, confirm you understood them correctly, flag any gaps. This demonstrates that you actually read what they sent you.

Next fifteen minutes: the exciting part. Show them three to five reference sites you've found that match their goals and aesthetic. Walk through what you like about each one. Ask what resonates with them. Start building a shared vision.

Next ten minutes: confirm the site structure and features. Walk through the Squarespace pages you've already set up. Confirm this is right.

Final five minutes: timeline and next steps. Content deadline, design phase timeline, testing phase, launch date. When you'll show them work, when you need feedback, how revisions work.

Record the call. Send them a summary document afterwards. This level of documentation prevents misunderstandings later.

Tools That Support the Process

You don't need a thousand tools, but a few good ones make this workflow significantly smoother.

Dubsado or HoneyBook for proposals and contracts. These platforms handle your questionnaire, they collect signatures, they're integrated with your workflow. They're worth the subscription cost.

Google Forms or Typeform for your questionnaire. Google Forms is free and integrates with Sheets, which is helpful for analysis. Typeform looks prettier and feels more professional, if that matters to you.

Notion for your project documentation. Create a template with your scope, timeline, revision policy, contact information, and key decisions. Share it with the client. Update it as the project progresses. Your client knows where to find information. You have one source of truth.

Loom for video walkthroughs. Instead of typing out "here's how to log into Squarespace", record a two-minute video. Clients retain the information better. It feels more personal.

Don't over-engineer this. Pick tools that you'll actually use consistently. Inconsistency is worse than no system.

How Good Onboarding Reduces Scope Creep

Scope creep happens because expectations were never clear. With a formal onboarding process, scope creep dramatically decreases because everything is documented and agreed upfront.

When a client asks for something that's not in scope, you have a document that says exactly what's included. You're not saying no because you're being difficult. You're saying "this is outside what we agreed, and I'm happy to include it as a paid add-on" because you've got it in writing.

Most importantly, having clear scope lets you push back on the urgent requests that come up mid-project. "I know you'd like the testimonials section to be a slider instead of a grid, but that wasn't in our original scope. I can add it as a $300 change, or we can keep the grid layout we designed together and stay on our original timeline."

Clients respect clarity. They'll grumble about cost, sometimes, but they'll respect that you've set boundaries and you're sticking to them professionally.

The Handoff: When You Actually Start Building

Once you've completed onboarding, you have everything you need to start design and build work without delay. The questionnaire is complete. The content is submitted. The site structure is confirmed. The scope is locked. Expectations are set.

This is when the actual design phase begins. And you'll notice immediately that your workflow is smoother. You're not waiting for information. You're not having scope conversations mid-project. You're building the website you promised to build, on the timeline you agreed to.

That 10 hours you save? It comes from eliminating unnecessary back-and-forth, not from rushing or cutting corners. It comes from being organised and professional. And that saves you money, which means you can charge appropriately for the value you're delivering.

Start implementing this onboarding process on your next project. You'll notice the difference immediately.