You're on a sales call explaining your product. it sounds perfect. You hang up and draft the follow-up email. Read it back. it feels like you. Hit send. Twenty minutes later you're re-reading your own words thinking "that's not right" and you're three drafts in when you remember: Wispr Flow. Costs $14/month. Only works on Mac. So you're back to typing.
The Mac Problem
Every premium voice tool launches on Mac first. Wispr Flow, Otter.ai's pro tier, the newer ones. Probably smart business. San Francisco design partners. Mac-first dev culture. The economics probably work out. But if you're on Windows, the message gets through loud and clear: we didn't build this for you.
Windows has around 75% of the PC market globally. But listen to software company roadmaps and you'd think it was 2%. The pattern is predictable. Launch on Mac. Get some runway with the early-adopter crowd. Build social proof. Then maybe, eventually, think about Windows. By that time, everyone's already locked in with the Mac version and the network effect does the work for you.
Kristian bootstrapped a SaaS on Windows. Not by choice, necessarily. That's what the dev machine was when he started. His Thursday mornings were for distribution batch work: drafting cold emails and social posts for the week. It's not glamorous. It's the work that moves the needle.
Every design-partner email was a negotiation with himself. First draft felt too friendly. Second draft sounded stiff. Third draft was okay, ship it. Always a drag. Always three rewrites. Not because he's a perfectionist. Because typing makes you self-edit in real time. Your brain is already two sentences ahead when you're speaking. But Wispr didn't exist for him. So he typed.
Where Voice Actually Wins
The first draft gets faster. That matters more than polish on draft three.
Most people think voice writing is about input speed, like dictating instead of typing saves 30% on time. That's not actually the gain.
Kristian's bottleneck wasn't typing speed. He can type. It was the gap between how clear something sounds when you say it and how muddled it looks when you type it. There's a moment on every sales call where you explain something beautifully. You're in flow. You're not reading notes. You're just talking. Then you hang up and try to write it down and it's gone. You're back in your head. Second-guessing every word choice. Is this casual? Too formal? Do they think I'm pitching or sharing context?
When he tried voice, something shifted. He talked like he was on a call explaining to a friend. Output was rough. Extra words. Thinking-out-loud cadence. But the intent? There. The clarity was there. Then polish in 20 seconds instead of 10 minutes.
For someone who bills Thursday mornings by the minute, that 10-minute delta adds up. He was losing half an hour a week to re-drafting emails that had already been written five times. Five times. The same idea, re-explained, because the first four versions didn't feel right.
That's a lot of wasted Thursday mornings.
What Actually Happens
You start writing colder, rougher first drafts because you know you can polish fast. More first takes. Fewer re-writes.
Thursday batch that used to take 60 minutes now takes around 40.
Doesn't sound like much until you multiply. That's 20 minutes a week times 50 weeks a year. 1000 minutes. 16-17 hours a year spent re-writing the same ideas. For a solo founder, that's real money.
But here's the thing: Recitey runs on Windows. In Slack. Email. Your browser. Inline. No new app. No new login. No tab-switching tax. Runs on your device with zero variable cost. You speak, it cleans it up into a sentence that sounds like you in under two seconds, and you keep working.
The speed-vs-polish trade-off flips. Polish becomes the final move, not the default. You learn to write faster because you know cleanup is fast. You stop waiting for perfect. You ship rough ideas because there's no friction to clean them up.
For distribution work, that's the whole game. Cold emails. Social posts. Slack messages to investors. GitHub issues explaining a bug. None of this needs to be polished the first time. It needs to exist. To move. To get out of your head and in front of the person who needs to read it.
The Tradeoff
You can't voice-code. Can't voice-write a SQL query. Can't dictate a design spec. These are real limitations.
But look at what you're actually doing during your distribution batch. You're not building. You're explaining. Pitching. Asking context questions. Narrating what happened on a support call. These are voice-first tasks. Voice is the natural medium. Typing is the constraint.
Windows users have been waiting for someone to acknowledge that simple fact. Wispr decided Mac was the market. That's fine. They probably have good reasons. But it left an entire platform without a tool that actually worked in their workflow.
That gap is what Recitey was built to close.