Batch it. AI Central's method is to stop answering comms as they arrive and instead speak a whole week of outbound in one thirty minute sitting: the week plan, the delegations, and the team update, dictated by voice into whatever app is already open. The case for it is arithmetic. Speaking runs at 150 to 220 words a minute against 30 to 45 for typing, so a week of writing fits into the slot a morning inbox used to eat.
Reviewed August 2026.
The cost is the switch, not the message
Most founders handle comms all day, in slices, as things land. AI Central's objection is not that the messages are long. It is that each one arrives unannounced and pulls attention off whatever was underway.
Every Slack ping is a context switch
Context switches, AI Central argues, cost more than the message does. A two line reply is cheap. Reloading everything you were holding in your head before that reply is not. Field forty of those in a day and the day is gone, even though the total typing time would have fitted into a coffee break.
So the fix AI Central proposes is not tighter inbox hygiene or a better notification setup. It is moving the entire week of outbound into a single block, and speaking it rather than typing it.
The best ones do it in one block
One sitting, three passes
The block has a fixed shape in AI Central's version: thirty minutes, one sitting, the week's outbound spoken in full, covering plans, delegations and updates. That is three passes, and the order is deliberate.
- Pass one, the week plan, spoken straight into a planning doc.
- Pass two, the delegations, one per handoff, each carrying full context.
- Pass three, the async update, dictated once and posted everywhere.
The sequence does more work than it looks like it does. The plan produces the priorities, the priorities produce the handoffs, and the handoffs produce the update. Run it in that order and each pass is largely reading back a decision the previous pass already made, which is the real reason thirty minutes is enough time.
Pass one, say the week out loud
AI Central's first move is mechanical: open the planning doc, press the dictation hotkey, speak the priorities. The worked example is a founder saying that the week needs the Q3 budget closed out, the new designer onboarded, and the Friday board meeting prepared for. The words appear as text instantly.
What is actually doing the work is not transcription speed. It is that speaking forces a commitment to a small number of things. A typed plan invites editing mid sentence, optional extras, hedges, a fourth priority nobody will get to. A spoken plan comes out as three named outcomes, because three named outcomes is how people talk.
Pass two, the thought becomes the brief
Delegation is where AI Central puts the most weight, and the instruction is to speak at each handoff with full context rather than firing off a one line ask.
The thought becomes the brief
AI Central's example is worth taking apart, because the density is the point. In a single spoken sentence it names the owner, the task, a deadline of Wednesday, the resource to work from, which is last year's template, and the escalation rule, which is to flag any discrepancies back to the founder. Five decisions, no follow up thread required.
Dictation is what makes that density cheap. The reason most delegated briefs arrive thin is that typing quietly punishes the extra clause, so the caveat gets trimmed, the reference document goes unmentioned, and the person receiving it comes back with two questions. Speaking imposes no such tax. You say the caveat because saying it costs nothing.
Pass three, one update, every channel
The third pass is the status update, and AI Central's rule is that it gets said exactly once.
Dictate the team update once
The example runs to three facts: the Q3 budget on track, the new designer starting Monday, the board meeting moved to Friday at 10am. That single block then goes out everywhere it needs to go, with no retyping per channel. The saving is not just the keystrokes. It is that every channel receives the identical version, so nobody ends up briefed off a shorter variant you wrote when you were tired of typing it for the fourth time.
Why the speed gap holds, and where it stops
AI Central's headline number is that speaking makes you four times faster, with speech at 150 to 220 words a minute and typing at 30 to 45.
Worth being precise about what that comparison covers, because it is raw rate against raw rate. It does not include the pass where you fix a mangled name or tighten a sentence, and it assumes the dictation lands clean enough that cleanup is a trim rather than a rewrite. The stated ranges also bracket the four times figure rather than landing on it: slowest speech against fastest typing is a little over three times, fastest speech against slowest typing is more than seven.
That range is wide enough to absorb a fair amount of editing and still come out ahead, which is why AI Central's practical claim survives the caveat. You produce a week of written comms in the time it used to take to clear a single morning's inbox.
What changes for the rest of the week
The block is only half the argument. The other half is what happens on the four and a half days after it, once the plan, the briefs and the update are already out.
You stop being the bottleneck
AI Central's framing is that replies become seconds rather than sessions, because the heavy thinking has already been spoken and sent. The team moves faster and the founder's attention goes to the work only the founder can do. Note what this does not claim: the messages do not stop arriving. What changes is who is waiting on whom. A team that received a full brief on Monday is not idling on Wednesday waiting for a clarification.
How to run your first block
The method transfers cleanly if you keep the order and resist the urge to edit while you speak.
- Put thirty minutes in the calendar as a recurring block, at the start of the week, before the inbox is open.
- Set a dictation hotkey you can hit without thinking, since every pass starts with it.
- Open the planning doc first and speak the priorities before anything else, so the rest of the block has something to derive from.
- Give every delegation the same five parts: owner, task, deadline, the resource to work from, and what to escalate.
- Say the team update once, then paste it into each channel unchanged.
- Leave all editing to the end. Fixing text mid dictation reintroduces exactly the stop start pattern the block exists to remove.
One useful side effect: if you cannot dictate the week plan in a couple of minutes, you do not have a week plan yet. The block surfaces that on Monday rather than on Thursday.
Do I need a particular tool for this?
AI Central's walkthrough runs on Wispr Flow, hotkey triggered dictation that types into whichever app is focused, which is what lets the plan, the briefs and the update all get spoken without leaving the tool you were already in. The batching is the method, the dictation tool is what makes thirty minutes realistic. There is a free version to start with.
How long does the block actually take?
Thirty minutes, one sitting, in AI Central's version. That covers all three passes for the whole week, not a single message. The number is only credible because of the order: by the time you reach the update, you are restating decisions the plan and the delegations already made.
What do I actually say when I sit down?
Three things, in order. The week's priorities, spoken into a planning doc. Then one brief per handoff, each naming the owner, the deadline, the resource and the escalation route. Then one team update covering status, arrivals and any schedule change. AI Central's examples are all short declarative sentences, which is also what dictation handles most reliably.
Where should I start if I only try one part of this?
Start with the delegation pass. It is the point where, in AI Central's phrase, the thought becomes the brief, and it is where being the bottleneck costs the team the most. A week of properly briefed handoffs removes more back and forth than a tidier plan document ever will.