A client asking for a standing weekly call is rarely asking for a meeting for its own sake, they're usually solving for anxiety about progress, or they've been burned before by updates that turned out to be vague or misleading. Agreeing to a recurring call without understanding the real need fills a calendar with meetings that may not actually be what's needed.
Meeting the real need isn't refusing calls altogether. It's understanding what a call would give them that an async update genuinely can't.
Usually solving for anxiety about progress, not literally needing a meeting
A request for more frequent live contact often reflects uncertainty about whether things are actually on track, not a genuine preference for meetings. Address the underlying uncertainty and the request for calls sometimes resolves on its own.
Ask what a call would actually tell them that an update wouldn't
A direct, curious question, what would a weekly call give you that a written update doesn't, often surfaces the real concern, trust in the update's accuracy, wanting a chance to ask questions live, rather than a genuine scheduling preference.
In Stelaah, a project's real, current status stays visible on the record, so an async update can be genuinely substantive and current, not a vague summary that leaves questions unanswered. See how projects works.
Offer a tighter, more predictable async rhythm before defaulting to a call
A more frequent, more detailed written update, still async, often addresses the real underlying need for reassurance without adding a recurring meeting to everyone's calendar. Offer this as a real alternative, not a lesser substitute.
Agree to calls at real decision points, not as a recurring default
Reserve live calls for moments that genuinely benefit from real-time conversation, a decision point, a genuine ambiguity, rather than a fixed weekly slot regardless of whether there's anything to actually discuss.
Make async updates genuinely substantive, not a reason the client stopped trusting them
If the client's request stems from past updates that felt vague or unreliable, fix that directly, make updates specific and honest, rather than treating the call request as the actual problem to solve.
A simple checklist
If you do nothing else, do these five things:
- Ask what a call would actually give them that an update doesn't.
- Offer a tighter, more substantive async rhythm as a real alternative.
- Reserve live calls for genuine decision points, not a fixed default.
- Fix vague or unreliable updates directly if that's the real cause.
- Address the underlying uncertainty, not just the calendar request.
Do that, and the client gets the reassurance they actually need, without a calendar full of status calls neither side really needs.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
