Some calls you plan for. Some come out of nowhere.
This one caught me away from my desk. A developer asking detailed questions about an industrial park property. No notebook. No screen. Just me and a phone call full of specifics. Land size. Use case. The little tangents that usually disappear the second you hang up.
There is always that split second where you know you are going to forget something important. Then I remembered I had a recorder on me. I hit record and let the conversation flow. Everything captured.
When the call ended, I dropped the transcription into an AI thread I had already loaded with everything about the property. The specs, the PDFs, the video tours, the templates. All organized and ready. Then I told it, here is the transcription, pull the details, combine it with what you know about this property, and draft the follow-up. Five minutes later I had a detailed, personal email that referenced the specific things we talked about and lined up the next steps.
What used to take thirty or forty-five minutes of remembering, drafting, and hunting down attachments became five minutes of refinement.
Now think about what that means for a business that lives on follow-up. Most deals are not lost on the call. They are lost in the hours and days after, when the follow-up is late, generic, or never comes because everyone got busy. The speed and the specifics are what make a prospect feel remembered instead of processed. And the specifics are exactly what your team forgets first.
You do not need my exact setup to use this. The pattern is what matters. Capture the conversation instead of trusting your memory. Give AI the context it needs about your product or service ahead of time, so it is not starting cold. Then let it turn the raw call into a follow-up you only have to refine, not write from scratch.
Do that, and every person on your team sends follow-ups like your best closer, on the same day, every time. That is a real edge, and most of your competitors are still telling themselves they will get to it tomorrow.
Originally published in Daniel Rivera's newsletter, Between Meetings & Meals, on Substack and at danielgrivera.com.