Resonant

Resonant + Notion

The blank page
isn't the problem.
The keyboard is.

You already know what the doc should say. You explained it in the meeting, on the call, to your teammate. The written version is the same thinking — it just needs to exist. Resonant closes that gap.

Press a hotkey in any Notion page. Speak your thoughts. Structured, clean text appears where your cursor was. All on-device.

The friction

Notion is where docs
go to be written “later.”

You leave the meeting knowing exactly what the page should say. You open Notion. The cursor blinks. And suddenly, typing it all out feels like work — because it is. Translating coherent verbal thinking into typed text is the slowest part of knowledge work.

So the doc gets written later. Or it gets written shorter. Or it gets replaced by a Slack message that captures 40% of the thinking and none of the structure.

The verbal version was better. It just didn't make it to the page.

What lands in Notion

Speak it rough.
Notion gets it clean.

Meeting notesRight after a product review
You said

ok so the big takeaway from the review was that the onboarding flow is too long, users are dropping off at step three which is the team invite screen, the hypothesis is that asking for team size and role information before they've seen any value is too much friction, so we're going to test a version where we skip straight to the workspace and ask for team details later through a prompt

Resonant delivered

Key takeaway: the onboarding flow is too long. Users drop off at step 3 (team invite screen). Hypothesis: asking for team size and role information before users see any value creates too much friction. Next step: test a version that skips to the workspace immediately and prompts for team details after first value moment.

Product specFirst draft of a feature brief
You said

the saved filters feature is for power users who apply the same filter combinations every day, like three or four filters with specific date ranges and categories, they should be able to save a set with a name load it from a dropdown and delete ones they don't use, store it server side not local storage because they switch machines, keep the UI minimal just a save icon and a dropdown

Resonant delivered

Saved Filters — Feature Brief Target user: Power users who apply complex filter combinations (3-4 filters with date ranges + categories) daily. Core behavior: Save filter sets with a name. Load from dropdown. Delete unused sets. Storage: Server-side (users switch between machines). UI constraint: Minimal — save icon next to filter bar + dropdown for loading. No new pages or modals.

Weekly updateFriday afternoon status
You said

this week we shipped the notification preferences page, the API rate limiting is in code review should merge Monday, the onboarding experiment is running with about sixty percent of new signups, early results look positive but we need another week of data, blockers are the SSO integration which is waiting on the security review

Resonant delivered

Weekly Update Shipped: Notification preferences page (live). In review: API rate limiting — should merge Monday. Running: Onboarding experiment (60% of new signups). Early results positive, need one more week of data. Blocked: SSO integration — waiting on security review.

Every doc type

From first draft
to structured output.

Meeting notes

Dictate the takeaways right after the call, while the thinking is still fresh. Resonant structures them. You edit — you don't reconstruct.

Product specs

Speak the feature intent, the constraints, the user story. The verbal version is almost always sharper than the one you'd type cold.

Weekly updates

The most dreaded recurring writing task. Speak the status of each workstream in two minutes. Structured output. Done.

Design rationale

The reasoning behind a design decision exists in your head before any doc. Capture it while it's warm — not after it's cooled into bullet points.

Project briefs

Scope, goals, non-goals, timeline. Say it the way you'd explain it to someone joining the project. Resonant formats it for the wiki.

Retrospectives

What worked, what didn't, what to change. Speak the honest version — the one you'd say in the room, not the careful one you'd type in front of everyone.

How it works

Inside Notion. Not next to it.

01

Click into the page

Put your cursor where you want text to appear — a new line, a section, a comment. Any Notion text field.

02

Press the hotkey. Speak.

Say everything the section needs. Thinking out loud is fine — Resonant handles cleanup. Filler words, restarts, tangents — all removed.

03

Structured text lands

Clean prose with proper structure. Headings, bullet points, and formatting inferred from your speech patterns. Edit the output, not a blank page.

Privacy

Your docs. Your device.

Resonant processes audio on your Mac. Your voice — including the messy draft, the unfinished thought, the version before cleanup — never leaves your device.

Only the final text reaches Notion, through Notion's normal input channels. Exactly as if you'd typed it.

Free. Local. Works in any Notion page.

Stop staring at
the blank page.

Speak the doc. Resonant writes it. No subscription, no cloud, no translation tax.

Requires macOS 14+ · Apple Silicon