Opposing counsel's email came in overnight, asking to move a conference to Thursday. It needs a two-sentence reply — confirm the new date, note that a colleague may sit in — and it needs to go out before the rest of the morning's calls start, not after, when the inbox will have six more messages ahead of it and this one-line answer will have to be found again.
Hold the key, say the two sentences into the open reply window, let go. The words land through the accessibility API, the way they would if typed, and the message is ready to send in the time it took to read the original.
Thursday at 10 works on our end — my colleague may join for the first half hour, I will confirm once the calendar is set.
None of this is complicated correspondence. It is the kind of message that takes longer to notice and reopen later than it does to answer immediately, and the only reason it does not get answered immediately at a keyboard is that opening a reply window and typing two sentences costs more attention than the message deserves.
8:15 AM: A new client's intake call, and a memo to file while it is fresh
A prospective client calls about a dispute with a former business partner. Forty minutes on the phone: names, dates, a rough timeline, the point where the relationship broke down, what the client wants out of it. The call ends, and the facts are as clear right now as they will ever be — tomorrow, after three other calls and a filing deadline, half of the specifics will have blurred into the shape of every other intake call that week.
The conventional move is to jot a few notes during the call and write the real memo later, once there is a quiet ten minutes. Later rarely arrives the same day, and a memo written the next morning from three lines of shorthand loses the details that actually mattered — the exact date the partner stopped responding, the specific dollar figure mentioned once and not repeated.
Dictate the memo the moment the call ends, while the timeline is still in order in your head. Hold the key, describe the facts as you would to a colleague standing in the doorway, let go. The memo lands in the matter file, timestamped, with the raw transcript kept alongside whatever gets cleaned up later.
Fifteen minutes after the call, the memo exists — not a polished draft, but every fact that matters, captured before the afternoon's calls start overwriting it. A long intake memo dictated in one sitting works the same way a short one does; length is a property of the matter, not of the method.
9:30 AM: A paragraph of an engagement letter
The new client needs an engagement letter before any real work starts. Most of the letter is a template already on file — scope, fee structure, the standard terms every letter carries. What is not templated is the one paragraph describing this matter specifically: what the firm is being retained to do, stated precisely enough that there is no ambiguity about scope later.
That paragraph gets dictated straight into the open template, in the gap left for it. It is drafting, not filling in a form — the kind of sentence that benefits from being said in one continuous thought rather than typed a clause at a time with the cursor stopping to think between them.
10:30 AM: Redlining a contract, one comment at a time
A draft agreement from the other side needs a first pass. Clause four changes the renewal term from automatic to opt-in — a real substantive shift, the kind that needs a comment explaining why it matters, not just a tracked-changes edit to the clause itself.
Reading contract language and typing a comment about it is a stop-and-start rhythm at a keyboard: read the clause, form the objection, look away from the document to type it, look back to keep reading. Dictating the comment does not remove the thinking, but it removes the part where attention has to leave the clause to get the comment written down.
This changes the renewal from automatic to opt-in, which shifts the risk of a lapsed term onto us — recommend flagging this explicitly before the client signs rather than let it pass as a drafting cleanup.
By the time the first pass through the agreement is done, every substantive comment reads the way it would if explained out loud to the client — because it was.
11:15 AM: Routing a signed exhibit to the paralegal, with instructions
A signed exhibit just came back from the client and needs to go to the paralegal handling the filing, along with three specific instructions: which exhibit number it becomes, which motion it attaches to, and a flag that the signature page uses a slightly different name spelling than the caption — worth noting before it gets filed, not after.
This is the kind of message that is easy to under-specify when typed quickly between other tasks — "attach to motion, watch the name" — and then has to be clarified over Slack twenty minutes later when the paralegal has a question the original note did not answer. Said out loud, the same instruction naturally includes the context a quick typed note tends to skip: which motion, specifically; what the discrepancy actually is; what to do if the clerk's office flags it.
This becomes Exhibit C on the motion to compel — note the signature reads Jonathan not John, matches the retainer but not the caption, flag it if the clerk's office asks.
12:00 PM: Deposition prep, working through the exhibits
An afternoon deposition needs a working list of questions organized around three exhibits. This is not drafting in the usual sense — it is closer to thinking out loud while flipping through documents, one exhibit at a time, noting what to ask about each and why it matters to the theory of the case.
Dictating that list while the exhibits are physically in front of you means the question gets written down in the same moment it occurs, next to the exhibit that prompted it, rather than typed later from a half-remembered sequence of "there was something about exhibit six." A list built this way during the actual review tends to track the documents more precisely than one reconstructed afterward from memory.
1:15 PM: Billing narratives, right after the call that generated them
A conference call just ended — forty minutes discussing settlement posture with the client. The billing narrative for that time needs to say something more specific than "conference with client," and the specifics are clearest in the first five minutes after the call, before the afternoon's next task starts erasing them.
- 13:166.2sConference with client re: settlement posture and counteroffer range following opposing counsel's Thursday proposal.Clio
- 13:244.4sReviewed and redlined section 4 of draft agreement — renewal term.Word
- 13:315.1sDrafted intake memo — Whitfield matter, timeline and disputed transfer dates.Pages
A narrative dictated immediately after the call names the actual topics discussed. The same narrative, reconstructed at the end of the week from a calendar entry that just says "call," tends to collapse into something generic enough that a client reviewing the bill has reasonable grounds to ask what, specifically, the forty minutes covered.
2:45 PM: A paragraph of a settlement demand letter
The settlement demand letter is mostly finished from a template built over years of similar matters. What it needs today is one paragraph stating the specific damages calculation for this client, in language firm enough to be taken seriously and precise enough to survive being quoted back in a later filing. That paragraph gets dictated once, read back, and revised once at the keyboard the way any dictated paragraph gets revised — dictation produces the first version, not a version exempt from editing.
4:00 PM: A note to file before the day closes out
The day's last task is the same as the day's first one in structure, though the content is different: a note to file, summarizing where the Whitfield matter stands after today's intake call and this afternoon's exhibit review, dictated in under a minute before moving on to tomorrow's calendar. Nothing about a note this short would ordinarily get written at all — the friction of opening a new document for two sentences is usually enough to defer it, and deferred notes to file are the ones that do not exist when someone reads the matter file eight months later trying to reconstruct what happened in September.
The only real limitation: boilerplate, macros, and a vocabulary that does not learn
None of the above involved a voice command. This app types exactly what is said and nothing else — no macro that inserts a standard indemnification clause, no command that jumps to the next tracked change, no shortcut that expands "conf w/ client" into a full billing narrative automatically. Dragon built that layer decades ago, and firms that rely on it heavily will feel its absence here immediately. Talon is the tool built for voice-driven navigation and commands specifically, and it is worth reading about honestly rather than expecting this app to grow into either role.
The dictionary here is the same story: names, party names and recurring citation formats are typed in once, by hand, and used exactly as entered on every dictation afterward — but nothing is inferred from what gets said, and an unfamiliar name will come out wrong the first several times until it is added. A firm with fifty recurring case names and no patience for typing them in individually is better served by a tool that learns them automatically, and this is not that tool.
Why nothing leaving the machine matters more here than in most jobs
Every one of today's dictations touched something a lawyer has an actual professional obligation to protect — a prospective client's unfiled dispute, a redline on a draft agreement under negotiation, a settlement figure not yet disclosed to the other side. Nothing dictated here is ever uploaded, on any tier, and the app works the same way with the network off as with it on. That is not a policy promise about how data will be handled once received — it is an architectural fact about what never gets sent in the first place, which is a different and stronger claim, and the fuller case for tools that keep voice data off a server entirely is worth reading alongside a firm's own security review rather than instead of one.
What the day actually added up to
Six months from now, none of today's individual dictations will be memorable — a scheduling reply, an intake memo, a redline comment, a billing narrative, all ordinary. What is different is how many of them exist at all, and how close each one landed to the moment the underlying fact was clearest: the intake memo written from a forty-minute call instead of three shorthand lines, the redline comment that explains the actual risk instead of just marking the clause, the billing narrative that names the topic instead of restating "conference with client" for the sixth time that week.
None of today's total was a single dramatic time saving. It was nine or ten short pieces of prose, each written in the minute or two after the fact that produced it rather than reconstructed later from a shorthand note or a vague memory of "we talked about the counteroffer." Across a single matter that difference is minor. Across a caseload carried for years, a memo file and a billing history built this way is a different, more defensible record than one assembled from memory at the end of each week — and it is the kind of difference that only shows up when someone actually needs to read back through what happened on a matter eight months later.
Why an ordinary Tuesday, and not a trial day
None of today involved a courtroom, a filing deadline at 4:59 PM, or a crisis. That is deliberate: the actual case for dictating through a legal day is not made on the exceptional days, when any tool that works at all earns its keep. It is made on the ordinary ones, where the only alternative to a two-sentence email reply or a two-line note to file is not writing it at all, because typing it costs more attention than a two-line note seems worth in the moment. A trial day makes dictation feel necessary. An ordinary Tuesday is where the habit either gets built or does not.
What it costs, for one attorney or a small firm
$19 once, three devices per licence, macOS 13 Ventura or later. A subscription that renews every month is the wrong shape for a firm that already tracks enough recurring costs — a licence bought once, with updates included and nothing that expires, is a smaller thing to explain on next quarter's overhead review. The broader case for legal dictation on a Mac covers what a held key replaces and what it does not; today was one ordinary version of that argument, worked through an actual afternoon.