Practice tooling · Live · since August 2026
Meeting transcription and diarization.
Every client call becomes a build brief: local transcription with speaker attribution, then a requirements doc, then the plan.
The problem
Requirements arrive in conversation, half-remembered by the time the build starts. Cloud transcription means sending client calls to a third party.
How it works
- Runs entirely on the desk PC: speech-to-text with word timestamps, then speaker attribution by voice embedding. Phone calls use a mode that skips voice-activity detection, which otherwise swallows long stretches.
- The transcript is cleaned, the requirements are distilled into a meeting document, and the document becomes the brief the build is checked against.
// audio never leaves the machine
The result
A dozen client meetings turned into written requirements and into systems on this page. The transcript is the contract.
Related systems
- Live
The second-brain recorder
An Android app that records a conversation and uploads it to a backend on my own PC, where it is transcribed and searchable. Own data, own code, end to end.
How it works - Live
The outreach system
A cold-email and calling machine built the careful way: scripted DNS, verified addresses only, one suppression table, and a human on every send and every dial.
How it works
Your version of this exists.
Different industry, same shape: a repetitive workflow, a fragile spreadsheet, an inbox someone babysits. Tell me what the manual work looks like and I can usually name the first build in one conversation.