How is your team actually using recordings beyond meeting notes?
a16z published a piece last week arguing that everything at work is being recorded, and that companies who build AI on top of that context layer will win.
Compelling thesis. But it mostly frames recordings as a memory and retrieval problem. I think the more interesting question is what people are actually doing with them beyond transcripts, summaries, and action items.
I've seen teams use recordings for onboarding, async decision reviews, even as a source of truth when things go sideways. But I'm curious what's happening in practice.
A few things I'd love to discuss with the community:
— How are you using recordings beyond just capturing notes?
— Have recordings changed how your team makes decisions or shares context?
— And the part the a16z piece barely touched: how do you handle the fact that recordings are sensitive? Board prep, HR calls, strategy debates — who in your org is actually allowed to see what?
Would love to hear what's working, what's broken, and what you wish existed.
Replies
For me, recordings have become much more than meeting notes. I use them to revisit decisions, catch missed details, and improve follow-through on action items.
@new_user___0932026a86e905cf4b2b7f7 I've found recordings especially useful for onboarding and training. Instead of repeating the same explanations, I can share relevant recordings and let people learn at their own pace while keeping context intact.
@new_user___0932026a86e905cf4b2b7f7 @bartosz__strickland I think it might be interesting to convert those training purpose recordings into something interactive.
One expected use case has been settling "I thought we agreed on X" debates.
@grace_mitchell5 This is the true dilemma! People always forget what they agreed or disagreed on. I used to work with someone who always forgets what he said yesterday.
The privacy ques is the one I keep coming back to. The more useful recordings become, the more sensitive they become.
@logan_pierce2 Agreed. There is a clear need for robust access control and guardrails. One idea is a recording tool knows what to record and what not to record.
Retime
One pattern I've seen work is treating the recording as evidence, not as the artifact people operate from. After the call, the useful output is usually a small decision log: what changed, who owns the next step, what date matters, and which part of the recording supports it.
That also helps with the sensitivity problem. Most teammates do not need the whole recording forever. They need the decision, the follow-up, and a path back to the source if something is disputed. For board/HR/strategy conversations, I would rather see tools create role-scoped excerpts or decision records than dump every transcript into a searchable company brain.
@hadifarnoud Evidence is a good call. For role-scoped excerpts, the key question is how much tolerance users have when the model misses some relevant excerpts when transcript is not saved.
Receiptor AI
Super interesting topic! Depending on the meeting type, I've built different systems:
For Internal Meeting:
- Use previous meeting transcripts (+ other elements like Linear activity, Slack messages, etc.) to prepare the agenda for the next meeting, make sure we're on track and don't miss any topics
- Team Operational Dashboard: easy review of what each of us have been working on, and our top priorities
For Leads/Partners meeting:
- Sales Pipeline management (add context, challenges, needs)
- Follow-up reminders & Automatic Draft (knowing the context)
For Customers
- Collect Feature Requests & Feed the roadmap
- Customer Support & Tickets management
- Automatic enrichment in HubSpot
- Voice of Customers Analysis: their pain, blockers, what they like in the product, wow moment, etc.
@luigi_receiptorai Wow, you're really getting a lot of value out of meeting notes across different departments. Are you also building a way to share that context across your team?