It's one of the most anxiety-inducing things in freelancing: a client pays, you start work, and then they just... disappear.
No approvals. No feedback. No "pause the project." Nothing.
You keep messaging. You don't want to seem pushy. You don't know if they hated the work, ran out of time, or if something happened in their personal life. You're stuck in an awkward limbo — money received, work half-done, relationship unclear.
This situation comes up constantly in freelancer communities. And the advice is usually: "Send a polite check-in email" or "Offer a refund if you can afford it."
Both are fine advice for managing a crisis.
But neither is the real solution.
The Real Problem Isn't Chasing — It's Onboarding
When a client ghosts you mid-project, it feels like a communication problem.
It usually isn't.
It's an onboarding setup problem. Specifically: you never agreed what happens when either party needs to pause, slow down, or become unavailable.
Most freelance projects start with:
- a scope agreement (what you'll deliver)
- a price agreement (what they'll pay)
- a start date
That's it. There's no framework for what happens during the project when communication breaks down, delays happen, or real life gets in the way.
So when it does — and it does, for agency clients and independent clients alike — both sides are operating in a vacuum. You don't know what they expect from you. They don't know what you need from them. The silence grows uncomfortable. Nobody wants to be the one to make the awkward call.
What You Set Up in Week One Changes Everything
The fix isn't a clever follow-up email template. It's what you establish before work starts.
Specifically, three things that belong in every client engagement from day one:
1. A response-time agreement
"I'll send you a weekly update on Fridays. I need your feedback within 3 business days to keep the timeline on track."
This sounds obvious, but most freelancers don't say it out loud, let alone put it in writing. When you do, you create a shared expectation. If a client goes quiet past their own agreed window, you have standing to say something — without feeling like you're being pushy.
2. A pause/resume protocol
"If you need to pause the project for any reason, just let me know. We'll freeze the deliverable list where it is, and I'll hold your spot for [X weeks]. After that, we'll need to rebook."
This one conversation at the start removes 90% of the awkward silence when real life happens. The client knows there's a proper way to hit pause — and they'll use it. Without it, they don't know if pausing means losing their money or burning the relationship, so they go quiet instead.
3. A missed-input escalation path
"If I don't hear back within 7 days after sending work for review, I'll send one follow-up. If there's no response within 14 days, I'll treat the deliverable as approved and move forward."
This protects you. It also helps clients who have a tendency to let things pile up — they know there's a deadline on their feedback, not an open-ended waiting game.
The Language That Makes This Feel Natural
Here's how to introduce this at kickoff without making it sound like a terms-of-service reading:
"One quick thing before we get started — I've found projects go smoothest when we agree upfront on the communication rhythm. I'll send work for review on [day]. I ask for feedback within [X days] so I can keep your timeline on track. If anything comes up on your end and you need to pause, just say the word — I'd much rather know than guess. Does that work for you?"
One paragraph. Two minutes. And you've removed most of the situations that cause client ghosting.
What Good Onboarding Does to the "Client Disappeared" Scenario
Compare two versions:
Without onboarding framework:
- Client pays. You start work. Client disappears.
- You have no agreed response window to reference.
- You don't know if chasing them is pushy.
- You don't know if the silence means they hated the work.
- You're stuck.
With onboarding framework:
- Client pays. You start work. Client goes quiet past their agreed 3-day window.
- You send one follow-up: "Hey — I sent the first draft on [date]. Just checking in as we agreed on a 3-day turnaround for feedback. Let me know if you'd like to pause or reschedule."
- If nothing: second follow-up at day 14, invoking the missed-input protocol.
- You're not guessing. You're operating inside a structure both of you agreed to.
The second version doesn't prevent emergencies. But it removes the ambiguity that makes them so painful to navigate.
The Deeper Pattern
Client ghosting almost always has a real-life trigger — a health issue, a business problem, a budget change, a moment of embarrassment about the work.
You can't prevent those triggers. But you can build a container that makes it easy for a client to come back and say "I need to pause" — instead of letting silence become a habit.
Most clients who disappear mid-project don't want to. They want an easy, shame-free way out of an awkward situation.
Your onboarding process can give them that. The pause protocol is it.
If you want the specific templates for the response-time agreement, the pause/resume protocol, and the missed-input escalation path — including the exact language for both the kickoff conversation and the follow-up emails — they're part of the Agency Onboarding OS.
Free version: the checklist at /checklist covers the full setup you need to start your next client project with none of this ambiguity.
Top comments (0)