Where these 4 reports land
Build it3
Scope it1
Keep it0
Category report
Voice Dictation
4 products ranked by how much of their useful core an AI coding agent can reproduce: 3 strong builds, 1 scoped build, and 0 weak replacements.
How the score breaks down here
- Interface
- 72
- Core workflow
- 82
- Data access
- 76
- Operations
- 63
- Trust & safety
- 76
76/100 average buildability
Why people keep paying here
- execution polish4 of 4 reports
The last 20 percent is sync, migration fidelity, speed, and edge cases.
- integrations1 of 4 reports
Connectors, OAuth flows, and vendor API changes require constant upkeep.
- proprietary models1 of 4 reports
Model quality and inference operations are part of the product.
The typical achievable core in this category: transcribe speech locally and paste formatted text anywhere.
Build it
Superwhisper
A push-to-talk recorder that transcribes and pastes text into the active app is very buildable for one person, especially on macOS.
Build it
MacWhisper
MacWhisper's solo core is compact: build a private local transcription pipeline that accepts an audio file, transcribes it, creates structured notes, and exports Markdown. A competent builder can reach a useful personal version, while the paid product mainly wins on capture, integrations, reliability.
Build it
Wispr Flow
Hotkey → record → Whisper → paste at cursor. One of the most-cloned apps of the trend for a reason.
Scope it
Superscribe
The desktop dictation half is a solved one-sitting build with complete open-source clones to fork. The hero product is not that: live-transcribing calls on your existing iPhone number takes carrier call forwarding, a pooled Twilio number, a CallKit/PushKit softphone, and a dual-track media-stream pipeline that can only be debugged against live phone calls. And a clone gets you a transcript file, not the workspace around it: roughly 45k lines of API and web app that embed every recording, time block, and project (with synced GitHub repo context), auto-file notes and billable time to the right client, and expose it all as reports, semantic search, a public API, and an MCP server. Each piece is a documented recipe; shipping all of them integrated is the substantially larger part even before telephony.