SpeakribeDictation for Notion
Notion is where the long-form writing lives: specs, notes, retros, documentation. It is also where pages go to sit half-finished. Speaking a first draft into the page is a much lower bar than typing one.
Why it helps here
The blank Notion page is the problem, not the formatting. Talking through what a document should say is easy; typing that same thing cold is where the afternoon goes, which is why so many pages stop at a title and three bullets.
First drafts get written
The gap between a page that exists and a page that does not is mostly activation energy. Speaking lowers it enough that the draft happens.
Notion's own shortcuts still work
Text arrives as text, so slash commands, markdown shortcuts and blocks behave exactly as they always do.
Nothing is uploaded to transcribe it
Internal planning and unreleased work are transcribed on your Mac, not sent to a service.
Things people say into Notion
- “Here's the summary from today's call: we're moving the launch to March, and marketing owns the announcement.”
- “Draft spec. The goal is to let users export their data as CSV, with a size limit we still need to decide.”
- “Retro notes. What went well: the migration had zero downtime. What didn't: we found out about the schema change on the day.”
- “Meeting agenda for Thursday: budget review, hiring update, and the open question about the contractor.”
Setting up for Notion
Notion is a block editor, and that shapes the whole setup: everything you dictate lands inside whichever block the cursor is in, and structure is something you add afterwards with Notion's own shortcuts.
Start an empty block first
Press Enter to get a fresh block, then dictate into it. Speaking into a block that already has text appends to it, which is usually not what you meant and is tedious to unpick in a long page.
Pick a binding Notion's slash menu won't eat
Notion binds a wide set of chords and opens its slash menu on a bare keystroke. A modifier-only shortcut stays out of both, and avoids the specific annoyance of the slash menu opening halfway through a sentence.
Dictate the prose, then add the structure
Speak the whole paragraph or the whole list as continuous text, then use Notion's markdown shortcuts to turn lines into bullets and headings. This is faster than trying to speak structure, and it is the only thing that works, because spoken formatting commands are typed as words.
Add your workspace vocabulary
Project names, team names, the internal acronyms that fill a company wiki. Add them once in settings; documentation is dense with exactly the proper nouns transcription cannot guess.
One dictation, start to finish
The opening of a retro doc, spoken in about thirty seconds into an empty page. The point is not that it is polished — it is that a page with this on it gets finished, and an empty page does not.
The main thing that went wrong this cycle was that we started building before the API contract was agreed, so we rewrote the client twice. It wasn't anyone's decision exactly, it just happened because the design review slipped a week and nobody wanted to sit idle. What I'd change is that we treat the contract as the gate rather than the design, because the contract is what the two teams actually need from each other.
The main thing that went wrong this cycle was that we started building before the API contract was agreed, so we rewrote the client twice. It wasn't anyone's decision exactly, it just happened because the design review slipped a week and nobody wanted to sit idle. What I'd change is that we treat the contract as the gate rather than the design, because the contract is what the two teams actually need from each other.
- All of this landed in one block, as one paragraph. Splitting it into the three points it contains is a Notion job afterwards — nothing you say produces a new block.
- "API" survived as an acronym rather than becoming "a P I". Well-known acronyms usually do; a three-letter internal one usually does not, until you add it to the custom-words list.
- The hedging stayed in — "wasn't anyone's decision exactly", "it just happened". For a retro that is arguably the useful part, and it is there because nothing is being tidied on the way through.
What it won't do in Notion
No spoken blocks or formatting
Saying "heading two", "bullet point" or "toggle" types those words. Every block-level decision is made afterwards with Notion's own shortcuts, and that is the main adjustment coming from a tool with voice commands.
Everything lands in one block
A four-minute dictation becomes one very long paragraph. That is workable for a first draft and poor for anything structured, so dictate in the chunks you want the page split into.
It won't navigate or search Notion
Opening a page, searching the workspace, moving a block: all still manual. Speakribe fills the block you are already in.
Databases need the field focused
Dictating into a database property works, but only once you have clicked into the field itself. Notion's tables move focus in ways that are easy to lose track of mid-sentence.
Questions people actually ask
- Does Speakribe work inside Notion blocks?
- Yes. It types into the focused block, so it behaves as if you had typed the text yourself.
- Can I create headings and lists by voice?
- Speakribe writes clean prose; it does not issue formatting commands. Use Notion's own markdown shortcuts to structure the text once it is down.
- Does it work in the desktop app and the browser?
- Both, without configuration.
- Can I dictate a whole structured page in one go?
- Not with structure, no. It all arrives as one block of prose and you break it up afterwards. If you want headings and bullets as you speak, that needs spoken formatting commands, which Speakribe deliberately does not have.
- Will it get our internal project names right?
- Not until you tell it. Add them to the custom-words list in settings — a company wiki is unusually dense with invented nouns, so this is worth five minutes before you start.
Speakribe in other apps
Ready to stop typing?
One payment. Every future update included.