Six meetings today, and forty emails that arrived between them

The calendar has back-to-back thirty-minute blocks from nine to four, and the inbox does not pause for any of them. By the time the second meeting lets out there are already forty unread messages, most needing a decision rather than an essay, and the four minutes before the third meeting starts is the only time available to clear any of them. Typing forty short, specific replies in four minutes does not happen. Saying them does.

Clearing the overnight inbox in the gap before the first call

The overnight batch is mostly things that need one sentence, not a paragraph — an approval, a date change, a polite no. The instinct under time pressure is to shorten the reply to something curt enough to type fast, which reads worse than the sender deserves. Saying the actual sentence, at the length the answer actually needs, takes about the same time as typing three words badly.

Holding the key and speaking lands the reply in whatever field has focus — through the accessibility API where the mail client supports it, a synthetic paste otherwise, clipboard restored either way. Nothing about the sentence gets tightened or reworded afterward; it is typed as said, the same as if it had been typed by hand.

Forwarding with the two lines a bare forward leaves out

A bare forward — the message, an arrow, no comment — makes the recipient reconstruct why it landed in their inbox. Dictating the missing context while the reasoning is still fresh, rather than typing it later from memory, is the difference between a forward someone can act on immediately and one that comes back with a clarifying question.

A handoff to a chief of staff, between two meetings

Walking from one conference room to the next is a minute, maybe two — not enough time to sit down and type a handoff note, but enough to say one. A voice memo dictated straight into the note-taking app the chief of staff already checks travels the specific detail a rushed typed line usually drops: what was already decided, what still needs a follow-up, and by when.

Turning a call straight into a written recap, before the next one starts

A call ends with three decisions and one open question, and the two minutes before the next meeting starts are the only reliable window to get a recap out before the details soften into a vaguer memory of what was actually agreed. Typing that recap from notes taken during the call means reading handwriting or shorthand back under time pressure; dictating it straight from what's still fresh gets the three decisions down in the order they were made, not the order they're remembered in an hour later.

Declining and rescheduling without turning it into a second meeting

A scheduling request that would normally need a short back-and-forth — three emails to find a time that works across two time zones — often just needs one clear counteroffer sent immediately instead of a vague "let me check my calendar" that starts the back-and-forth anyway. Saying the actual constraint and the actual alternative, rather than typing a placeholder reply to buy time, tends to close the loop in one message instead of four.

A morning of replies, kept in the order they were actually sent

Every one of those rows exists because the reply was written to local history the moment the key came up, before the transcription engine was asked anything. A dropped Wi-Fi connection between meeting rooms, a laptop that goes to sleep, or a call that interrupts mid-sentence costs, at worst, a paste back in — not a reply retyped from memory once the next meeting finally ends.

What this isn't: a tool that decides what to say

Worth stating directly, because the search that leads here sometimes wants something else. There is no drafting assistant here, no summarizer that condenses a long thread into a decision, and no tone control that softens a blunt no into something more diplomatic. Every word in every reply above was decided by the person saying it; the only thing that changed was how the sentence got from a decision into typed text. That is a real limit for anyone hoping a held key will also choose the words, and it is the same fact that makes the sent reply trustworthy — nothing between the decision and the inbox has an opinion about how it should have been phrased.

Names that get typed wrong get said wrong too, until they're taught once

A board member, three portfolio company names, and an outside counsel's surname that autocorrect has never once gotten right — all typed dozens of times a week, and all worth entering into the dictionary once rather than fixed by hand every time they come out garbled. Entries are used twice, as a hint before the audio is processed and again as a check over the transcript afterward, on exact word boundaries. They are not inferred from a previous email or picked up automatically the first time a name is said; every one is typed in by hand, once, and then correct in every reply after that.

A reply read back before it goes to the board

A dictated line to the board or to outside counsel gets the same glance a typed one would before it's sent — a misheard company name or a garbled date sits in the transcript with exactly the same confidence as a correct one, and only a second look catches it. That check costs a second or two against a sentence that took five to say, and it matters more on the messages that go to people who do not get a second chance to ask what was meant.

What still gets typed, filed and delegated

Dictation replaces typing the words of a reply — it doesn't touch the rest of an inbox. Filing a thread into the right folder, flagging a message for later, attaching a document, or actually deciding who on the team should own a task are all exactly as manual as they were before. What changes is the sentence itself: the one part of answering forty emails that used to cost real minutes regardless of how clear the decision already was in the sender's own head before they opened the reply box.

A quarter's worth of decisive replies, not one day's

A single day like this one doesn't look dramatically different from a day spent typing the same forty replies — a few minutes saved here and there, easy to dismiss as marginal if it's the only thing measured. What shows up over a quarter is different: fewer threads that stall because a one-line answer got postponed past the point where a two-word reply would have closed it, and fewer forwards that come back with a clarifying question because the two sentences of context that answer it were said instead of skipped to save time. None of that is visible in any single reply above. It's visible in how few of them a chief of staff or an assistant ever has to follow up on.

A commute, an airport gate, and a desktop back at the office

A licence covers three devices, which for most executive schedules means an office desktop, a travel laptop, and sometimes a home machine — each installed separately, with no account tying them together. A reply dictated from a gate at the airport does not appear on the office desktop the next morning; whatever the reply was sent through — email, a shared doc, a calendar invite — is what actually carries it between machines, the same as it always did.

What a held key doesn't do for a schedule this tight

There is no phone version of this. It runs on a Mac, full stop, which means the inbox triage that happens from a phone at a gate or in a cab still gets typed the old way. Wispr Flow runs on Mac, Windows, iPhone and Android at $15 a user a month ($12 a month billed annually — $180 or $144 a year, checked against its own pricing page today) and also advertises a vocabulary that learns names and jargon automatically rather than needing each one typed in by hand — a real advantage for a schedule that spends as much time on a phone as at a desk, and worth reading honestly rather than treated as a gap this app closes.

Apple's own Dictation is already free on every Mac and types into the same mail client. What a dedicated held key adds across a day with this many short, decisive replies is a start that fires the instant the key goes down, both the raw and the cleaned-up transcript kept side by side, and filler removal that stays off unless it's turned on — none of which shows up on any single reply, only across a full day of them.

A calendar that's mostly meetings still leaves inbox time somewhere

Some days are wall-to-wall with almost no gaps; most have a handful of two- or three-minute openings scattered between calls, plus a longer stretch at the end of the day for anything that piled up. The short gaps are where one-line decisions get cleared — approvals, declines, quick handoffs. The longer stretch at day's end is closer to the meeting follow-up case, where a reply runs several sentences and deserves a proper read-back before it goes out, not a rushed one between calls.

A reply that goes to an assistant instead of straight out

Not every dictated line is meant to be sent as-is. Some are notes for an assistant to turn into a properly formatted email, or a rough answer meant to be checked against a fact an assistant already has on hand — a contract date, a traveling colleague's actual time zone, a figure from a deck nobody has open in the moment. Dictating the rough version and handing it off is still faster than typing the same rough version, and it changes nothing about how the final email actually gets reviewed and sent; the assistant's judgment about what's ready to go out is still exactly where it was, unaffected by how the rough draft reached them.

What it costs against a calendar like this

$19 once, three devices per licence, macOS 13 Ventura or later, Apple Silicon or Intel. The thirty-day trial runs everything, no card and no account — long enough to carry a genuinely packed week through it and see whether the four-minute gaps between meetings actually get an inbox cleared. Start the trial against a real week of back-to-back calls, not a quiet afternoon chosen because it would go well. Anyone weighing a per-seat cost against a team's assistants and executives, where headcount shifts through the year, is better served reading the case against an ongoing monthly subscription directly.

What a day like this actually adds up to

No single reply above reads as dramatically better written than a typed one would have been — the approval, the forward with context, the handoff note. What changes across a full day of six meetings and forty emails is how many of those replies get the two extra sentences of context that make them useful to the person receiving them, instead of the clipped one-word answer that typing under time pressure tends to produce. Across a week, that is the difference between a chief of staff who has to ask a follow-up question on half of what gets forwarded to them, and one who doesn't. Dictating email more broadly covers the same mechanism without one calendar's six meetings attached to it, and a recruiter's version of the same held-key habit applies it to a different kind of high-volume, short-message day.