The Client Who Ghosted Us After Week Two
I need to tell you about a web development client we onboarded in early 2024. They were a mid-size catering company, great people, solid budget of $22,000 for a full booking platform rebuild. The sales call went beautifully. They were excited. We were excited. Everyone shook hands (virtually) and said "let's do this."
Two weeks later they stopped responding to emails.
It took me three follow-ups and an awkward phone call to find out what happened. Turns out, they expected us to manage their existing hosting migration as part of the project. We expected them to handle that on their own, since it wasn't in the proposal. But nobody had actually said that out loud during the kickoff. They felt blindsided. We felt confused. The project eventually continued, but we'd already lost trust before we'd written a single line of code.
That was the moment I sat down and built an actual onboarding checklist. Not a generic template I found on Google. A real one, built from every mistake we'd made over the previous two years.
Why Most Onboarding "Processes" Don't Work
Here's what onboarding looked like at our agency before the checklist: the project manager sent a welcome email, scheduled a kickoff call, and then started working. That was it. Three steps, no structure, and a lot of assumptions.
The problem is that service companies tend to focus all their energy on winning the deal and then treat onboarding as a formality. Something you rush through so you can get to the real work. But onboarding IS real work. It's where you set every expectation that determines whether this project goes smoothly or turns into a nightmare.
I talked to a friend who runs a 15-person marketing consultancy. She told me she lost a $35,000 client last year because of an onboarding failure. The client assumed they'd get weekly video reports. Her team assumed email summaries were fine. Nobody discussed it. Six weeks in, the client was frustrated and felt like they were being ignored. By the time she realized the disconnect, the relationship was damaged beyond repair.
This stuff happens constantly. And it's almost always preventable.
The Checklist, Step by Step
I'm going to walk you through what we actually use now. This isn't theoretical. We've onboarded 40+ clients with this process over the past two years, and our client retention rate went from about 68% to 89%. I'm not saying the checklist is the only reason, but it's a big one.
Step 1: The Pre-Kickoff Email (Send Within 24 Hours of Signing)
Before the kickoff meeting, send the client a structured email with three things:
- A summary of what was agreed in the proposal, including deliverables, timeline, and price
- A list of what you need from them before work can begin (access credentials, brand assets, content, whatever applies)
- The date and agenda for the kickoff call
This email does something subtle but important. It shifts the client's mental model from "we just bought something" to "we're starting a collaborative process." It also puts your version of the scope in writing before the project begins, which matters if there's ever a dispute later.
I'll be honest, I resisted this step for months. It felt overly formal. But the first time a client replied with "wait, I thought the logo redesign was included" and we caught it BEFORE the kickoff, I was converted.
Step 2: The Kickoff Meeting (30-45 Minutes, No Longer)
Keep this focused. I've seen agencies turn kickoff meetings into two-hour brainstorming sessions. That's not onboarding. That's a workshop, and it belongs later.
The kickoff covers five things:
- Introductions and roles. Who on your team does what. Who on their team is the decision-maker vs. the day-to-day contact. This matters more than you think. I once spent two weeks getting feedback from someone who turned out to have no authority to approve anything.
- Scope review. Walk through the deliverables line by line. This isn't exciting. It's necessary. Ask them to confirm each item. "You're getting X, Y, and Z. Not A, B, or C. Does that match your understanding?"
- Timeline and milestones. Not just "we'll be done in 12 weeks." Break it into phases. Tell them what happens in each phase and what you need from them by when. Make their deadlines clear. Client delays are the number one cause of project timeline slip, and they almost always happen because nobody told the client they had a deadline.
- Communication cadence. How often will you update them? Through what channel? Who should they contact with questions? We defaulted to weekly email updates plus a Slack channel, but some clients wanted biweekly video calls. The point is to agree on it upfront, not discover a mismatch six weeks in.
- What's out of scope. This is the most important part and the one most people skip. Explicitly name two or three things that are NOT included. "We're building the booking platform, but we're not handling your email marketing setup, your domain transfer, or your payment processor integration." Yes, it feels awkward. Do it anyway.
Step 3: The Access and Credentials Handoff
Create a shared document (we use a simple spreadsheet) where the client fills in every credential, login, and access point you'll need. Server access, CMS logins, analytics accounts, social media credentials if relevant, API keys, hosting panel, domain registrar, whatever.
Set a deadline for this. Make it within five business days of the kickoff. Follow up if they miss it. I cannot overstate how many projects get delayed because the team is ready to start but doesn't have the FTP password or the staging environment credentials.
One thing we learned the hard way: always ask who else has access to these systems. We once made changes to a client's staging site, and their internal IT person overwrote everything because nobody told him we were working in there.
Step 4: The Scope Boundaries Document
This is separate from the proposal. The proposal says what you will do. The scope boundaries document says what happens when someone wants to change what you do.
Ours is one page. It covers:
- How change requests work (submit in writing, we estimate hours and cost, they approve before we start)
- What counts as a "small ask" that we'll absorb (under 2 hours, at our discretion)
- What counts as a change request (anything that adds deliverables, extends timeline, or requires new functionality)
- Who can approve change requests (only their designated decision-maker)
I send this as an attachment with the kickoff follow-up email and ask them to confirm they've read it. Most clients actually appreciate this. It shows professionalism and prevents those awful conversations later where someone says "I thought this was included" and you say "it wasn't" and nobody has anything in writing.
Step 5: The 2-Week Check-In
This is the one I almost didn't include, and now I think it's the most important step.
Two weeks into the project, schedule a 15-minute call with the client. Not a progress update. A relationship check-in. Ask three questions:
- Is communication working for you? Do you feel informed?
- Is anything surprising you about how the project is going?
- Is there anything you expected that hasn't happened yet?
This call has saved us from at least four client blowups. In one case, a client told us at the two-week mark that they were confused by our project management updates because they didn't understand the status labels we were using. A tiny issue. But if it had festered for two months, they would have felt lost and frustrated the entire time.
The Things People Get Wrong
I've shared this checklist with about a dozen other agency owners and consultants. The pushback is always the same: "this is too much process for small projects" or "my clients would find this annoying."
On the first point, scale it down for small projects. For a $3,000 engagement, the pre-kickoff email and the scope boundaries doc are still worth doing. Maybe the kickoff meeting is 15 minutes instead of 45. But the core elements still apply. I've seen scope disputes on projects as small as $1,500.
On the second point, no client has ever told me this process was annoying. Not once. They've said "this is really organized" and "I wish our last agency did this." Clients don't want less process. They want to feel like someone is in control. A structured onboarding tells them you've done this before and you know what you're doing.
What This Actually Prevents
Let me give you the concrete list of problems this checklist has prevented for us:
- Scope disputes. Down from roughly one per quarter to maybe one per year. And when they do happen, we have documentation.
- Access delays. Average time to get all credentials went from 2.5 weeks to 5 days. Because we set a deadline and follow up.
- Communication mismatches. We haven't had a client complaint about communication frequency since we started confirming cadence in the kickoff.
- Surprise stakeholders. We always know who the decision-maker is now. No more designing something for two weeks only to learn that the CEO needs to sign off and has completely different taste.
- Ghosting. We've had exactly one client go quiet after implementing this process, and it turned out to be because their company had a leadership change. Not because of anything on our end.
The Uncomfortable Truth
Here's the thing nobody tells you about client onboarding: it's not glamorous. There's no clever hack. It's just being deliberate about things that most people leave to chance.
The catering company client from my opening story? We eventually delivered their project, but the relationship never fully recovered. They gave us a lukewarm testimonial and didn't come back for a second engagement. All because we assumed instead of asked during the first week.
Every project starts with onboarding. If you get that wrong, you're playing catch-up for the entire engagement. If you get it right, most of the problems that plague service companies just don't happen.
Build the checklist. Use it every time. Adjust it when you learn something new. That's the whole secret.
