Guides
Why do new design clients disappear right after the onboarding kickoff?
Clients vanish after kickoff for four repeatable reasons, and each one is visible in your own kickoff notes before the project quietly stalls.
What to take away
- Clients rarely leave because they changed their mind. They leave because the kickoff left the money, the decision maker or the next step unresolved.
- The four causes that repeat across studios are a budget never confirmed in writing, a stakeholder who was not in the room, a kickoff with no dated next action, and a first deliverable that arrived late or thin.
- Fix the kickoff agenda before you fix the sales pipeline. A stalled project is cheaper to rescue in week one than in week six.
- Every kickoff should end with a written recap the client replies to. Silence after kickoff is the warning sign, not the disappearance.
- Accessibility duties sit with the client's obligations under the ADA and WCAG 2.2. Name that in the recap and refer any specific question to a qualified auditor.
The gap between a signed proposal and a working project
A kickoff feels like progress. The contract is signed, the deposit has cleared, and the client is enthusiastic on the call. Then the replies slow, the asset folder stays empty, and by week three you are sending a follow-up nobody asked for.
The disappearance is almost never sudden. It is the visible end of something that went wrong in the first meeting, and the studio usually has the evidence in its own notes.
Four causes account for most of it.
Cause one: the budget was never said out loud
The proposal stated a number. The kickoff never restated it. The client then hears a scope conversation as a cost conversation and goes quiet to avoid a fight.
Restating the Contract Figure
Proposal only
- Client hears
- scope talk
- Risk
- silence, fight
- Action
- none
- Range
- unclear
Kickoff restated
- Client hears
- cost talk
- Risk
- confirmed coverage
- Action
- say figure back
- Range
- name trigger
Say the figure back at kickoff, in the client's own words, and confirm what it covers. If the number came from a range, name the range and the trigger that moves it.
Cause two: the person who signs is not the person who decides
A marketing coordinator signs. A founder, a spouse or a board actually approves the homepage direction. The coordinator cannot answer your questions, so the project waits while they ask someone else.
Who Can Approve Design?
Ask who can approve without checking
get name, calendar, channel
project waits, coordinator asks others
Ask at kickoff who can approve a design without checking with anyone. Get that name, that person's calendar, and their preferred channel.
Cause three: the kickoff produced no dated next action
The meeting ends with "we will send over the content." No date, no owner, no folder. Nothing is late because nothing was due.
Dated Kickoff Close
- Studio deliverable with date
- Client deliverable with date
- Next call date and owner
Close every kickoff with three dated items: what the studio delivers, what the client delivers, and when the next call happens.
Cause four: the first deliverable arrived late or thin
The first thing you send sets the client's expectation for the whole build. A mood board that misses the brief, or a sitemap three days late, tells them the project is optional.
Ship the first deliverable early and small. A one-page direction summary in 48 hours beats a full concept deck in two weeks.
A worked example of a kickoff recap
Send this within one business day, in the client's own tool, and ask them to reply confirming it.
- Restate the approved scope and the contract figure, and name what sits outside both.
- Name the single client approver, their backup, and the channel you will use.
- List the client's obligations with datescontent, images, brand files, logins, sign-off windows.
- List the studio's next two deliverables with dates.
- Set the next call and the agenda for it.
- State that accessibility requirements follow the ADA and WCAG 2.2, and that a qualified auditor confirms conformance rather than the studio.
A client who will not reply to that recap is telling you something. Escalate in week one, not week six.
What to check when a project goes quiet
- Was the contract figure repeated at kickoff and confirmed in writing?
- Did the actual approver attend, or only the day-to-day contact?
- Does the recap list dated client obligations and studio deliverables?
- Has the first deliverable shipped, and did it match the brief?
- Has anyone asked the client directly what changed?
The onboarding and delivery guide covers the full sequence from contract to launch. When a project does stall, the project delivery checklist is the fastest way to find which item was skipped.
Two external references are worth reading before you rewrite your kickoff. The Department of Justice guidance on web accessibility and the ADA explains why accessibility belongs in the first conversation, not the last.
The DOJ ADA guide for small businesses sets out the barrier-removal framing that applies to a client's existing site. If reviews are part of your closeout, the FTC guide to soliciting and paying for online reviews states what a request may and may not do.
Common questions
How soon after kickoff do clients usually go quiet?
Most stalls show up between day five and day fourteen, and the trigger is almost always an unanswered question the client could not resolve alone. If you have not heard back within a week of the recap, ask directly what changed.
Is a slow client the same as a lost client?
No. A slow client is often a client with an internal blocker you never saw. A lost client stops replying to the recap, the invoice and the calendar invite at the same time.
Should the studio chase the client or pause the project?
Pause in writing and say what restarts it. Chasing without a pause teaches the client that deadlines are optional, and it hides the real problem from your own pipeline numbers.
Who owns accessibility questions raised at kickoff?
The client owns its obligations under the ADA and WCAG 2.2. The studio should name the standard in the recap and refer any conformance question to a qualified auditor rather than answering it itself.
