Your calendar is full. Not with deep work or creative projects, but with meetings. Check-ins, syncs, stand-ups, "quick chats" that are never actually quick. Every one of them fragments your day and kills your productivity.
There's an alternative that most of your clients will accept if you present it right. Async communication. Messages, emails, and updates exchanged on each person's own schedule, without requiring everyone to be in the same room (or Zoom call) at the same time.
Here's how to propose it without alienating your clients.
What Async Communication Actually Means
Async is short for asynchronous. It just means communication where people don't need to respond in real time. Email is async. Slack messages are async (when used properly). Recorded video updates are async. Shared documents with comments are async.
Meetings and phone calls are synchronous. Everyone has to be present at the same time.
Most freelance work doesn't require real-time communication nearly as often as we default to it. The habit of scheduling a call for every question is deeply ingrained, but it's not always the best approach.
Why Clients Default to Meetings
Before you can change the pattern, it helps to understand why clients want meetings in the first place.
Meetings feel productive. Sitting on a call for 30 minutes feels like progress, even when nothing actually gets decided. It's the illusion of momentum.
Meetings feel personal. Clients like knowing there's a real human on the other end. Especially with remote freelancers they've never met in person.
Meetings are familiar. Most people's work experience is built around meetings. It's the default tool for getting things done, even when it's not the right tool.
Your job isn't to convince them that meetings are bad. It's to show them that async is often better, for both of you.
How to Pitch Async to a Client
The best time to introduce async communication is during onboarding, before the meeting habit forms. But you can also shift an existing client relationship.
Here's how to frame it:
"I've found that async updates work really well for projects like this. I'll send you a detailed written update every [frequency], and you can review it whenever works for your schedule. If anything needs real-time discussion, we'll absolutely hop on a call. But for routine updates and questions, async tends to be faster and gives us both more flexibility."
Notice what this does. It positions async as flexible and convenient for the client, not just convenient for you. And it keeps the door open for meetings when they're truly needed.
Specific Swaps You Can Suggest
Here are common meeting types and their async alternatives:
Status update meetings become weekly written updates. Every Friday, send a summary of what you completed, what's coming next, and any blockers. The client reads it at their convenience. No 30-minute call needed.
Feedback sessions become shared documents with comments. Instead of walking through changes on a call, share the work with annotations explaining your decisions. The client reviews it, leaves comments, and you respond. This actually produces better feedback because people think more carefully when they write.
Quick question calls become email threads or Slack messages. If the question can be typed out in a few sentences, it doesn't need a meeting. Write it, send it, get an answer when the person is free.
Brainstorming sessions become shared documents or voice memos. Post a few ideas in a document, let everyone add their thoughts over 24-48 hours, then compile the best ones. This gives introverts and slower processors equal footing, which often leads to better ideas.
Project kickoffs are the one exception. Keep these as meetings. The initial alignment and relationship-building benefit from real-time conversation.
Tools That Make Async Work
You don't need fancy software. But the right tools make async smoother.
Email is the backbone. It's async by nature and everyone already uses it. For tracking whether your async updates are being read, Pynglo shows you open and response data so you know your messages aren't disappearing into the void.
Loom or similar screen recorders let you send video walkthroughs instead of scheduling a screen share. Record a 5-minute walkthrough of the design, send the link, and the client can watch it whenever.
Google Docs or Notion work great for collaborative feedback. Leave comments, suggest edits, and discuss changes right in the document. Everything stays in context.
Slack or Teams for quick questions that need answers within the same day, but don't need real-time conversation.
Handling Pushback
Some clients will resist. Here's how to handle the most common objections.
"I prefer talking things through." Response: "Totally understand. How about we keep our [weekly/biweekly] check-in call for anything that needs real discussion, and handle the routine stuff async between calls? That way our meetings are focused on the important topics instead of status updates."
"Async feels impersonal." Response: "I hear you. I'll include some personality in my updates so they don't feel like cold reports. And we can always hop on a quick call whenever you want to talk through something. Async isn't about removing contact, it's about making our contact more efficient."
"I worry things will fall through the cracks." Response: "I actually find that written updates create a better paper trail than meetings. Everything is documented, searchable, and easy to reference later. Nothing gets lost."
Set Async Norms
If you're going to do async well, establish some norms:
Define response time expectations. "I'll respond to messages within one business day" or "I'll check Slack during business hours and reply within a few hours." Without this, clients will wonder if their message got lost.
Establish a regular update cadence. Whether it's weekly or biweekly, consistent updates prevent the "just checking in" messages that clutter both inboxes.
Agree on when to escalate to a call. "If something needs more than 3 email exchanges to resolve, let's hop on a quick call." This keeps async from turning into an endless email thread.
For more on nailing these norms from the start, check out our post on how to set communication expectations with a new client.
The Hybrid Approach
Going fully async isn't realistic for most client relationships. And that's fine. The goal isn't to eliminate meetings entirely. It's to make meetings the exception for things that truly need real-time interaction.
The sweet spot for most freelancers is a regular check-in call (weekly or biweekly) combined with async communication for everything in between. The calls handle the big decisions and relationship maintenance. Async handles the day-to-day.
This gives clients the face time they want while giving you the focus time you need.
The Productivity Payoff
Here's what happens when you shift even half your client communication to async. You get longer blocks of uninterrupted work time. You respond more thoughtfully because you have time to think before replying. Your clients get better answers because you're not ad-libbing on a call.
And honestly, the written record alone is worth the switch. Six months from now, when someone asks "didn't we decide X?", you can search your email and find the exact conversation. Try doing that with a meeting that wasn't recorded.
Async isn't lazy. It's intentional. And for freelancers who need protected time to do their actual work, it might be the most important boundary you set.