A daily 30-minute stand-up in a team of 10 costs 5 person-hours a day. Over a month that’s more than 100 hours. At a fully loaded hourly cost of 1,500 ₽ that’s roughly 160,000 ₽ a month for the privilege of saying out loud what could have been read.
This isn’t about talking less. It’s that a synchronous meeting is the most expensive way to move information, and it should be spent only where it’s genuinely required.
Why daily calls cost so much
The cost isn’t the duration. A meeting in the middle of the day cuts it in half. The hour before goes to “it’s about to start anyway”, the time after goes to getting back into context. Half an hour of meeting easily becomes an hour and a half of lost time.
Everyone pays, two people benefit. In a round-robin status with 8 people, each listens to seven other reports, of which one or two concern them.
The information isn’t preserved. What was said aloud can’t be found a day later. The same thing written stays available forever, without “what did you say on Monday?”.
It filters for speed, not correctness. On a call the person who formulates fastest wins, not the person who’s right.
What can go async
Not everything. Let’s be honest about the split.
Moves across well:
- The daily “what I’m doing” status.
- Reporting results.
- Collecting ideas and proposals.
- Signing off a document or an estimate.
- Assigning routine work.
Moves across badly (needs a live conversation):
- Working through a conflict.
- Feedback on someone’s work — especially critical feedback.
- Kick-off brainstorming, where the speed of back-and-forth matters.
- A decision where the parties disagree and have to reach an agreement.
The rule: async carries information excellently and attitude poorly. Anything where emotion and trust matter stays on a call.
How an async status works
The replacement for a daily stand-up is a short written message in the project chat, with the same structure, at the same time (say, before 11:00):
Yesterday: finished the homepage build, sent to the client for sign-off
Today: catalogue revisions, starting the form integration
Blocked: waiting on analytics access from the client — can't start the report
Three lines, two minutes to write, ten seconds to read. The third one is the point: blockers are the whole reason this exists. The first two lines are usually visible in the tracker anyway.
If tasks are tracked in a system, the status gets shorter still: the “yesterday” and “today” lines aren’t needed at all, because the manager can see movement on the board. What’s left is the blocker and anything that didn’t fit into tasks. A daily digest from a bot in Telegram or MAX, for instance, covers that part by itself.
A weekly rhythm instead of daily meetings
A workable setup for a team under 20 is one meeting a week plus a written flow:
| What | Format | Time |
|---|---|---|
| Daily status | written, in the project chat | 2 min per person |
| Weekly priorities | 15–20 min call, Monday | whole team |
| Problem solving | call as needed | participants only |
| End-of-week wrap | written, Friday | 5 min per person |
| One-on-one | call every 2 weeks | manager + team member |
Don’t cut the one-on-one: it’s the only format where things surface that a person won’t write in a group chat.
Rules without which async becomes chaos
1. Response time is fixed. Async doesn’t mean “eventually”. Agree: a reply within the working day, urgent things by phone. Without a response norm, async culture turns into waiting.
2. Every message has an addressee and a question. “Thoughts, everyone?” in a 12-person chat gets zero answers. “Igor, can you approve the estimate by Wednesday?” gets an answer.
3. Context lives in the message. An async message is read without you present. If understanding it requires scrolling up, it won’t work.
4. Decisions are written down. Agreed on a call — one person posts the outcome to the chat. Otherwise in two weeks everyone has their own version.
5. Don’t port the bureaucracy. If the written status turns into a page-long report, people will stop writing it. Three lines is the ceiling.
Handling the pushback
Cancelling stand-ups almost always draws objections, and they’re predictable.
“I won’t know what the team is doing.” If that’s true, the problem isn’t the meeting format — it’s that there’s no system showing current work. The stand-up is a workaround: a manager gathering by voice the data that should be on a screen.
“People will stop talking to each other.” Usually the opposite: removing a compulsory daily ritual gets people talking on purpose and voluntarily.
“Writing takes longer.” Longer for the writer, faster for everyone else. Two minutes of writing against half an hour of listening, times eight.
“We have urgent issues.” Urgent things are handled by a call the moment they arise, not by waiting for tomorrow’s stand-up. A daily meeting actually slows urgency down: “we’ll discuss it in the morning.”
Making the switch in two weeks
Week 1. Keep the stand-ups but add the written status. Everyone will see that half the meeting is a re-reading of what’s already written.
Week 2. Cut daily meetings down to twice a week. Watch what actually breaks: usually nothing.
Week 3. Keep one meeting a week. After a month, assess: did you drift back to calls, and did anyone end up less informed?
One caveat: before cancelling stand-ups there must be a place where work is visible. Otherwise you’re simply removing the only information channel and you’ll get exactly the “I don’t know what the team is doing” problem. The order is: tracker first, then fewer meetings.
What it saves
A team of 10 with a daily 30-minute stand-up:
5 person-hours a day × 21 working days = 105 h/month
105 h × 1,500 ₽ = ~157,000 ₽/month
Switching to one weekly meeting leaves about 15 hours a month. The saving is on the order of 135,000 ₽ a month, before counting the fragmented day.
Treat the figure as an order of magnitude: some of the freed time inevitably goes into written communication. Realistically, about two thirds comes back.
Bottom line
Going async isn’t “communicate less” — it’s ceasing to use the most expensive channel for things text carries perfectly well. Status, reporting, sign-off — in writing. Conflict, feedback, disagreement — by voice.
There’s one precondition: a place where current work is visible without asking. If tasks live in chats, the stand-up can’t be cancelled — it’s the only way to learn what’s happening. How to fix that is in our breakdown of why tasks get lost in chats, and the written agreements for remote work are in the team working agreement.
Gosudarynya shows workload and deadlines across the team in real time, and the bot sends a digest to Telegram or MAX — which makes the stand-up unnecessary. 7 days free, no card.