Why You Should Never Chase a Freelancer for Updates (And What to Do Instead)

• The $5,000 Ghosting Scenario
• Know Your Enemy: The Ghost-in-Training
• Silence is Not 'Deep Work'
• The Micro-Win: The 'No-Chase' Protocol Template
• Take Back Control

The $5,000 Ghosting Scenario

You hire a freelance developer to build a mobile app MVP. For the first week, everything is great. But by week three, the developer stops providing proactive updates.

You find yourself sending messages every Thursday: "Hey, just checking in on progress!"

The developer replies 24 hours later with a vague: "Yes, working on it, will send a build soon."

This cycle continues for two months. Eventually, the developer ghosts completely. You are left with no code, no app, and £5,000 lost in escrow.

Here's the truth: You fell victim to the Ghost-in-Training. In my experience managing cross-timezone engineering teams across the US and UK, you can manage around a missed deadline, but you cannot manage around poor communication. Chasing updates is a symptom of a fatally flawed working relationship.

Know Your Enemy: The Ghost-in-Training

The Ghost-in-Training doesn't disappear immediately. They fade away slowly.

But it gets worse: They start by missing a daily update, then they ignore a Slack message for 12 hours, then they push a weekly sync by two days. They are testing your boundaries. If you accept their poor communication and continue to chase them for updates, they realize they have zero accountability. They will prioritize other clients who do enforce boundaries, leaving your project to rot.

Read more: 5 Massive Red Flags to Watch for When Hiring a Freelance Developer

Silence is Not 'Deep Work'

Many founders excuse poor communication by telling themselves, "They are just putting their head down and coding. Great developers are naturally bad communicators."

This is a dangerous myth in 2026. Software development is a collaborative business discipline, not magic. A professional developer understands that providing visibility into their progress is 50% of their job. If you have to ask a developer what they are doing, they have already failed at that job.

Missed deadlines are a scheduling problem. Poor communication is a character problem. Look at any top repository on GitHub—contributors over-communicate their progress to maintain trust. You should expect the same.

The Micro-Win: The 'No-Chase' Protocol Template

You must establish extreme communication boundaries on Day 1, before any code is written. Copy and paste this exact protocol into your onboarding document:

The End of Day (EOD) Async Update Protocol: "We do not rely on synchronous Zoom calls. I require a 3-bullet-point asynchronous update at the end of your working day, posted in our shared Slack channel:

• What I did today: (e.g., 'Built the Stripe integration')
• What I'm doing tomorrow: (e.g., 'Testing webhooks')
• Blockers: (e.g., 'I need the production API keys from you')"

If you implement this EOD async update and the developer violates it twice in the first two weeks, fire them. Do not give them a third warning. Do not chase them down to ask why they missed the update. If a freelancer cannot meet basic communication standards during the "honeymoon phase" of a project, they will inevitably ghost you when the work gets difficult.

Take Back Control

You are the CEO, not a babysitter. Stop begging your contractors for updates. Set the protocol, enforce it ruthlessly, and only work with professionals who respect your peace of mind and Western working standards.

Read more: The 10 Percent Rule: Why You Should Always Start With a Paid Demo Project