Web design client onboarding is the sequence between a signed contract and the first pixel of design work — and skipping steps here is the single biggest predictor of delays, scope disputes, and missing assets later in the project. A proper onboarding process takes one focused session plus a short async follow-up, not multiple back-and-forth weeks.
This picks up exactly where scope creep leaves off — most scope disputes and missing-asset delays trace back to a rushed or skipped onboarding step, not a difficult client.
Why Onboarding Gets Skipped (And Why That's Costly)
New freelancers, eager to start designing, often treat onboarding as a formality between "contract signed" and "get to work." That instinct causes two of the most common project problems:
- Missing assets stall the build. You're two weeks in and still waiting on a logo file or product photos that should have been collected on day one.
- Misaligned expectations surface mid-project, when they're expensive to fix, instead of at kickoff, when they're a five-minute conversation.
A structured onboarding sequence front-loads all of this before design work starts, not during it.
The Full Onboarding Checklist
Use this in order — each stage unlocks the next.
Stage 1: Contract and Payment (Day 0)
- [ ] Signed contract on file (see contract essentials for what it must include)
- [ ] Deposit invoice sent and payment confirmed before any work begins
- [ ] Client added to your project management tool or client folder system
Stage 2: Asset Collection (Day 0-3)
- [ ] Logo files (vector/SVG preferred, not just a low-res PNG from their old site)
- [ ] Brand colors and fonts, if they have existing guidelines
- [ ] Photos — product shots, team photos, location photos (or flag that stock photography is needed)
- [ ] Existing copy/content, or confirmation that copywriting is a separate scope item
- [ ] Domain registrar login or domain transfer authorization code
- [ ] Current hosting access, if migrating an existing site
- [ ] Any existing analytics or ad account access relevant to the project (Google Analytics, Meta Pixel)
- [ ] List of competitor sites the client likes or dislikes, with specific notes on why
Stage 3: Kickoff Call (Day 2-5)
A single structured call, 30-45 minutes, covering:
- [ ] Confirm scope out loud against the proposal — surfaces misunderstandings before work starts, not after
- [ ] Walk through the timeline and each milestone date
- [ ] Set the communication channel and expected response time (email, WhatsApp, a shared doc — pick one primary channel)
- [ ] Confirm who the single point of contact is on the client side (critical for businesses with multiple decision-makers)
- [ ] Set expectations on revision rounds and what counts as a "round"
- [ ] Ask directly: "Is there anything about this project that's still unclear or that you're unsure about?"
Stage 4: Technical Setup (Day 3-7)
- [ ] Domain and hosting access confirmed and tested
- [ ] Staging environment or design tool access set up
- [ ] Email accounts or forwarding configured if part of scope
- [ ] Any third-party integrations identified (booking systems, payment processors, CRMs) and access requested early — these often have the longest lead time to set up
Stage 5: First Deliverable Expectations (Day 5-10)
- [ ] Client knows exactly what they'll see first (wireframe, homepage mockup, style tile) and when
- [ ] Feedback format is defined — a specific tool (Figma comments, a shared doc, marked-up screenshots) rather than "just email me your thoughts," which tends to produce vague, hard-to-action feedback
A Simple Onboarding Email Template
Send this immediately after the deposit clears, before the kickoff call:
Subject: Let's get [Project Name] started — a few things I need from you
Hi [Name],
Excited to get started! Before our kickoff call on [date], could you send
over:
1. Your logo files (highest resolution you have)
2. Any brand colors/fonts you use, if you have them documented
3. Photos you'd like used (or let me know if we need stock images)
4. Access to your domain registrar, or the transfer code if we're moving it
5. Any competitor or inspiration sites you like the look of
No rush on all of it before the call, but the sooner I have these, the
sooner we can move into design.
Talk soon,
[Your name]
What Good Onboarding Prevents
| Skipped step | Common downstream problem | |---|---| | No asset collection upfront | Design phase stalls waiting for logo/photos mid-project | | No kickoff call | Client and designer have different mental models of scope | | No single point of contact confirmed | Conflicting feedback from multiple stakeholders | | No feedback format defined | Vague, hard-to-action revision requests | | No domain/hosting access check early | Launch delayed at the very last step by a locked account |
Every row in that table maps to a real, common project delay — onboarding is cheap insurance against all of them.
Onboarding for Different Client Types
| Client type | Adjustment | |---|---| | Small local business, one owner | Can often compress Stages 1-3 into a single call | | SME with a marketing contact | Keep the kickoff call, but confirm decision-making authority explicitly — marketing contacts don't always have final sign-off | | Repeat/retainer client | Lighter version — most of Stage 2 and 3 is already known, focus on what's different for this specific project |
Onboarding Sets Up Everything That Follows
A clean onboarding process is what makes the rest of the relationship easy — it's the foundation both referrals and repeat business get built on, because clients remember how organized (or chaotic) the start of a project felt more than almost anything else.
Get New Clients Into a Process Like This Consistently
A great onboarding checklist only matters once you have clients to run it on. Runvax keeps that pipeline moving — finding local businesses with no website and drafting the first outreach message — so onboarding becomes a repeatable process you run weekly, not something you scramble to remember every few months.