Three channels, one place
I've written about how everything I say ends up as text. I've written about why your meeting summary is worthless. But I haven't written about the practical question that determines whether any of it actually works: how do you capture everything?
The answer isn't a single tool. It's three channels that all land in the same place.
Online meetings
Most meetings today happen in Teams, Zoom, Meet. Teams has transcription built in -- you can copy the text directly after the meeting. It works. There's a bit of manual effort, a bit of copy-paste, but it's entirely viable.
For those who want something more streamlined, there's Fireflies. It joins your meetings, records them, transcribes them. And the important part: it has an API. I pull all my Fireflies transcripts centrally every fifteen minutes. Automatically. No manual step. The meeting ends, and within a quarter of an hour the transcript is ready to be processed.
It's not magic. It's an integration and a scheduled call. But it eliminates the friction that makes people stop capturing their meetings after the first week.
In-person meetings
Not every conversation happens in front of a screen. Client meetings, workshops, lunches where the important things are said between courses -- those need to be captured too.
I use record-me on my iPhone or iPad. Every in-person meeting gets recorded. The audio file is then passed through the same pipeline as my Fireflies meetings. Same place, same processing, same chain afterward. It doesn't matter whether the meeting happened in Teams or in a conference room -- the transcript ends up in the same spot.
Newer versions of iOS include Apple Intelligence, which lets you copy text directly from a recording. That simplifies things further. But the principle is the same: in-person conversations can't be treated differently than digital ones. If you only capture online meetings, you're losing half of what's actually said.
Phone calls
The third channel most people miss entirely. Inbound and outbound calls -- the ones that often contain the fastest decisions, the most unfiltered information, the things people say on the phone that they would never have written in an email.
I use Sonetel as my phone service, where I also work. They have a call recording feature and an API for retrieving the audio files. Same principle as Fireflies -- automatic retrieval, centrally stored, ready for transcription.
It's the channel people forget most often. And it's the channel where the most valuable information tends to live, precisely because phone calls are spontaneous, unprepared, honest.
The convergence point
Three channels. One place.
Online meetings via Fireflies. In-person meetings via record-me. Phone calls via Sonetel. Everything lands in the same pipeline. Everything becomes transcripts. Everything becomes searchable, structured text.
It's not three separate systems. It's three inputs into the same system. And that's the point -- it doesn't matter where the conversation happens. It gets captured. It gets processed. It doesn't disappear.
Then the chain takes over. Preparation for the next meeting based on what was said in the last one. Summaries, decisions, follow-ups. Project tracking if needed. Daily overview. All the things I've described in the other articles -- but it starts here. With the audio actually being captured, regardless of channel.
But not everything may land anywhere
This is the part I left out when I first described the pipeline, and it matters more than the pipeline does.
Three channels land in one place. But which place is permitted is not a question with one answer. It depends on what the conversation was.
A voice note I record for myself carries essentially no requirements. An internal check-in carries few. A client meeting where someone commits to something starts to become contractually relevant. A salary review, a board meeting, a medical consultation -- those carry requirements that are not negotiable, and they apply from the moment recording starts.
The point is not to be afraid. The point is that the requirement is a property of the material, not a setting in the system. You do not build "a secure pipeline" and call it done. Turn the requirements up to the strictest level and everything becomes so cumbersome that you stop capturing. Turn them down to the most convenient level and sooner or later the wrong thing ends up in the wrong place.
And one thing that is nearly always merged but is two separate questions:
- Where is the material stored?
- Where is it processed?
Swedish storage with American processing answers one and not the other. Conversely, a model of Chinese origin can be entirely unproblematic if the weights run on your own hardware and nothing leaves your network. Processing is what decides, not the flag on the vendor.
For my own part, I experiment. Most of what I capture carries no particular requirements, and then I use whatever is smoothest. But the day the material does carry a requirement, the chain has to be able to answer it -- and that answer cannot be constructed after the fact.
Which leads to the only practical rule I have: decide when you record, not afterwards. The person who was in the meeting knows what the meeting was. Nobody knows that three months later when the file is sitting among a thousand others.
The only thing required
The infrastructure isn't complicated. It isn't expensive. Fireflies has reasonable plans. Sonetel too. record-me is a tool I built myself, but there are alternatives.
What it takes is the decision to actually do it. To commit to the idea that no conversation is too unimportant to capture. To stop treating in-person meetings and phone calls as exceptions to the system.
Most people who say they work with AI-assisted workflows capture their Teams meetings and nothing else. That's one third of the picture. The rest disappears.
Nothing needs to disappear. The infrastructure exists. The channels exist. What is missing is the habit -- and the habit of asking what the material actually is, at the same moment you hit record.