Voice
Hit record on the way out of a meeting or between appointments. The audio is stored as the original record of what was said.
Everything you're handed, in one place
Voice, scan, file, note or shared content. One pipeline stores the original, reads it, and proposes what it means — and the original stays attached to whatever it produced.
On screen
What Zephyr hands back
You record forty seconds on the way to the car. This is the review screen you get: the transcript, what it thinks the actions are, what it was unsure about, and nothing saved until you say so.
Zephyr tells you what it was unsure about rather than scoring itself. A reading it is confident in arrives ticked; one it is not names the field to check — the owner, the date, the wording — and waits unticked. Below its floor it says it does not know rather than guessing at a date.
CAPTURE · REVIEW
“Right, so Sarah still owes us the Thursday rota — chase her
tomorrow. And I said I'd send the revised quote to Maple Court by
Friday, that one's firm.”
2 actions found · voice, 41 seconds
Chase Sarah for the Thursday rota
Ready to review
Send revised quote to Maple Court
Due date needs review
Save both
Edit
Discard
60%
of a knowledge worker's time goes on coordination — searching,
chasing, retyping — rather than the work they were hired for.
Capture is where that starts.
Asana, Anatomy of Work Index 2021, 13,123 knowledge workers
The pipeline
Five ways in, one way through
Whatever the input is, it takes the same path: store the original, read it, classify it, pull out the entities, identify the actions, judge how sure it is, propose — and wait for you.
Scan
Photograph a form, a signed page, a whiteboard or a printed schedule. The image is kept as the source of truth behind whatever gets extracted.
File
A PDF quote, a spreadsheet, a contract. Attach it and it becomes searchable context attached to the work it produced.
Note
Type or paste. The fastest capture there is, and the one most people use twenty times a day.
Shared content
Forwarded emails and shared text arrive as captures like anything else, so the thread stops living only in your inbox.
Everything, one queue
Captures have states — pending, processing, processed, failed — so you can always see what Zephyr has and hasn't read yet.
What survives
The original is never thrown away
A capture is not consumed by the extraction. The recording, the photo, the file and the text you typed all stay attached to the actions they produced, which means every action can answer the question "where did this come from?" months later.
That matters more than it sounds. Most task apps lose provenance at the moment of entry — someone retypes "chase the vendor" and the original message is gone. Zephyr keeps the chain intact.
- Capture history. Every input you've ever sent in, with its processing state and what it produced.
- Full-text search. Postgres full-text search across actions, captures, meetings, decisions, people and projects — always scoped to your workspace.
- Offline queueing. A quick note taken without signal is stored locally and syncs when you're back.
- Delete means delete. Removing a capture removes the stored original, not just the row that points at it.
Honest about what's not finished.
Server-side transcription for voice and OCR for images and PDFs are the
remaining pieces of this pipeline. Until they ship, a voice or scan
capture stores the original and asks you to type the gist so extraction
has something to read. The model routing for transcription is already in
place — see the roadmap.
On the phone
Four ways in, one button
Voice, scan, file or note. The capture sheet is one screen with one primary action, because the moment you need it you are walking to a car or standing in a corridor.
Whatever you hand it, the original is stored and stays attached to whatever it produced.
See it on your own work.
Zephyr is in development for iOS and Android. Join the early access list.