Founder note: what Zahvox is and is not

Why this note exists

Most product sites overpromise. They talk about tomorrow like it is today. Zahvox is early, and the line between shipped and unshipped matters. This note draws that line so nobody has to guess.

I am Hussain Jatoi. Full background is on the founder page. Zahvox is being built to help people who think faster than they type. That is the whole scope.

What Zahvox is today

• A free web voice-to-text experience at /tool.
• Live transcript in browsers that support speech recognition.
• Editable transcript so you can clean before copying.
• Copy and download as .txt.
• A suite of small free utilities: voice notes cleaner, email draft generator, meeting notes formatter, word counter, character counter, reading time calculator, typing speed calculator.
• Auto-restart behavior for supported browser speech sessions, so you do not lose the middle of a long thought.
• No signup. No download. No paywall.

What is in development

• Browser extension.
• Text injection into input fields.
• Professional toggle.
• Basic formatting.
• AI cleanup for rambly voice notes.
• Improved microphone handling.

What is planned

• Desktop app.
• Mobile app.
• Plugins for the tools where people already write.
• Login and account system.
• Saved history and search.
• Personas — saved voice and tone.
• Writing modes: email, meeting notes, posts, replies, drafts.
• Templates.
• Team workflows.
• Paid plans: Writer, Pro, and team pricing.

What Zahvox is not

Product truth table

How we decide what to ship

• 1Does it remove friction from voice-to-writing?

  If it makes the loop faster or cleaner for someone already using the free tool, it moves up the list.

• 2Does it fit the scope?

  If it drifts into meeting transcription, general AI writing, or translation, it moves off the roadmap.

• 3Can we ship it honestly?

  If we can't describe it truthfully in one sentence today, it stays in development until we can.

This is how the roadmap stays honest. If a feature is not on the roadmap, it is not being built. If it is on the roadmap under Planned, it is not shipped. If it is under Available now, you can use it at /tool today.

— Hussain

Why Zahvox exists

I built the first version of Zahvox because I kept losing hours to a stupid problem: I knew what I wanted to write, and I could not get it out of my head fast enough. Typing was the bottleneck. Every founder update, every client reply, every content outline sat in my head longer than it should have because the keyboard was slower than the thought.

The tools I tried either transcribed meetings I did not need to record, or dropped words into a field with no way to shape them into a real message. Nothing was built for the loop of speak, review, shape, use. So I started building that loop. That is Zahvox.

The problem Zahvox is solving

Not "writing faster". Not "AI writing". Not "voice everywhere". The specific problem is the gap between how fast you can think about a message and how fast you can get a usable version of it out of your head. Everything on the roadmap traces back to that one problem. If a feature does not shorten that gap, it does not ship.

How to use Zahvox today

1. Open /tool. No signup. No download.
2. Give microphone permission once.
3. Speak the rough version of a message you actually need to send.
4. Clean the transcript in the editor. Fix filler and names.
5. Copy the text and paste it into your email, Slack, Notion, or doc.
6. Send it.

That is the whole product loop today. Everything else is either supporting utility under /free-tools or roadmap work.

Expectations you should not have yet

• Do not expect a downloadable extension. It is in development.
• Do not expect AI cleanup to auto-format your notes. It is in development.
• Do not expect text to appear inside your other apps automatically. Text injection is in development.
• Do not expect a desktop or mobile app. Both are planned, not built.
• Do not expect saved history or accounts today. Planned.
• Do not expect meeting transcription. Not planned.

Who Zahvox is for

• Founders writing the same reply patterns weekly.
• Freelancers writing proposals and client updates between billable work.
• Creators drafting posts and outlines while ideas are fresh.
• Non-native English speakers who think in one language and type slowly in another.
• People who hate typing, type slowly, or deal with typing fatigue.
• Operators who write a lot of short internal updates.

Who Zahvox is not for, yet

• Teams that need shared voice-to-writing workflows. That is planned, not built.
• Enterprises with strict compliance needs. Not the current audience.
• Anyone whose main need is meeting recording. Wrong tool.
• Anyone who needs system-wide dictation into every app today. Text injection is in development.

Why product truth matters

The fastest way to lose trust with an early user is to imply a feature is shipped when it is not. Once that trust breaks, everything else on the site is suspect. So the rule is simple. If it is live at /tool, it is on the "Available" list. If it is being built now, it is on the "In development" list. If it is on the plan but not started, it is "Planned". If it is none of those, we do not talk about it as if it is coming.

This has a cost. It means the site looks smaller than a competitor that overpromises. That is fine. The users I want to build for value the truth more than the surface area.

The roadmap, without overpromising

The roadmap page is the honest source. It has three columns: Available, In development, Planned. Available is what you can use today. In development means we are actively building it. Planned means we have decided to build it, but work has not started. Dates are not shown because early roadmaps that publish dates lie.

If a feature moves from Planned to In development, that is meaningful. If it moves from In development to Available, that means it is on the site and safe to use. Nothing else on Zahvox is real until it lands in Available.

Scope discipline as a feature

Every early product gets pulled in directions its team did not plan for. Someone asks for a meeting bot. Someone asks for translation. Someone asks for a general-purpose AI writer. Each request is reasonable on its own. Saying yes to all of them turns a focused product into a slower, worse version of five other tools. Zahvox will keep saying no to work that sits outside voice-to-writing, even when the asks come from users I respect. This is not stubbornness. It is the only way an early product can ship anything good. The tools that end up mattering are the ones that stay narrow long enough to actually be great at the narrow thing.

What a good Zahvox week looks like for a user

Somebody who is getting value out of Zahvox today probably runs the loop three or four times a week. Weekly update on Monday. Client reply on Tuesday. Content outline on Wednesday. Follow-up email on Friday. Nothing dramatic. No transformed workflow. Just four messages that would have taken longer to type from scratch and that now get finished in two-minute passes instead. That is the honest bar. If Zahvox saves you those minutes on those messages, it is doing its job. If it does not, tell me and I will fix the part that is failing.

What we will not do to grow

A few things I have decided against, on the record: no fake team page, no invented case studies, no "trusted by" logo wall that is actually a scrape of press mentions, no accuracy percentages we cannot back up on any real workload, no compliance badges we do not carry, no dark-pattern paywalls that trap free users, no auto-billing surprises, no forced signup for the core free tool. If Zahvox ever adds accounts, the free tool at /tool will still work without one.

If you are one of the first users

Right now, being a Zahvox user means being early. Rough edges exist. Some flows break in specific browsers. The set of surfaces is small. If you are here anyway, thank you. The reason to be here is that the loop already works for the narrow job it was built for, and it will keep getting better. If it breaks on a real task you were trying to finish, that is the most important thing I can hear about. Ping me at /contact or read the wider plan on the roadmap. This note will get updated as the product changes.

How this note gets updated

This page is not a launch announcement. It is the current status of the product. When a feature moves from In development to Available, this page changes on the same day. When something on the Planned list gets cut, this page changes on the same day. If you ever land here and something feels stale, that is a bug worth flagging. The value of a product truth note comes from being true right now, not from being true on the day it was first published.

Bookmark /roadmap if you want the widest view of what is coming. Bookmark this note if you want the honest boundaries. Between the two, there should be no daylight between what Zahvox says it is and what Zahvox actually is.