Features

Nine parts that only make sense together

Zephyr is an operational memory and execution system, not a chatbot with a task list bolted on. Each piece below is useful alone — together they're the reason work stops disappearing.

Capture

A voice note, a scanned form, a PDF, a photo of a whiteboard or a line of text you type at a red light. One pipeline takes all of it.

Read more

Actions & priorities

Not a checkbox. An action with an owner, a due date, a priority, the context it came from and an activity trail that cannot be quietly edited.

Read more

Waiting & follow-ups

Mark an action as waiting on someone and Zephyr keeps the clock. When the follow-up date passes, it drafts the nudge and asks you first.

Read more

Daily brief

Overdue, due today, blocked, waiting, at risk — assembled from structured queries against your own records, then written up short enough to read.

Read more

Ask your work

"What am I waiting for?" "What did I promise Sarah?" The assistant answers by querying your data with tools — or says it has nothing recorded.

Read more

Meetings & decisions

Record the meeting, review what Zephyr found: decisions, actions, owners, deadlines and risks. Create all, edit, or discard.

Read more

People & relationships

A running balance of every working relationship — what they owe you, what you owe them, how long it has been quiet. Derived from your work, not a CRM to maintain.

Read more

Integrations

Gmail, Outlook, Google Calendar and Slack. Reads widely enough to find a commitment, and holds no scope that would let it send anything.

Read more

Sharing

Share one action with one address. No seat, no workspace to join, and a grant that widens what they can read by exactly one row.

Read more
The rule underneath

One constraint the whole product is built around

Zephyr proposes. You decide. That order never reverses, in any feature, on any plan.

Why an approval step, and not more automation?

Because the cost of a wrong autonomous action in operations work is not a bad paragraph — it's an email to a client that shouldn't have gone, a cancelled shift, a commitment nobody made. The value of an assistant here comes from noticing, not from acting alone.

So every extraction is measured against a floor it has to clear, every suggestion is a proposal, and no external communication leaves the app without a human tapping approve. That's a product decision, and it's enforced in the backend rather than requested in a prompt.

  • Confidence on every extraction. At or above 0.90 it's preselected; 0.70–0.89 is suggested; 0.50–0.69 is shown as a possible reading; below that it isn't surfaced at all.
  • Nothing persists as fact until you approve. Approval is what creates the records — and it writes an audit event at the same time.
  • No external tools in the assistant. It can read your work and, with confirmation, write to it. It cannot email anyone.
  • Captured content is data, never instructions. Text that says "ignore previous instructions" is treated as content, and the eval suite tests exactly that.

Ready to see it on your own work?

Zephyr is in development for iOS and Android. Join the early access list.