Last year I realized something a little embarrassing.
I had a Lindy notetaker joining my calls. I had transcripts being saved to Google Drive. I had this whole system set up to capture everything.
And I was reading maybe 5% of it.
Somewhere in that other 95% was a comment a client made in passing that I should have followed up on. A recurring blocker that came up three times in a month. A contradiction between what two different advisors told me in separate meetings that I never noticed because I was reading one transcript at a time.
So I built something to fix it.
The Weekly Synthesizer Agent
Every Sunday night, an agent runs through all my meeting transcripts from the past seven days. Sometimes that’s 8 meetings. Sometimes 15. It doesn’t matter — it reads everything, synthesizes it into a Google Doc, and drops the doc in my inbox before I wake up Monday morning.
Here’s what the document includes:
- Executive summary — a paragraph or two overview of what the week was actually about, not just what was scheduled
- Recurring themes — topics that came up across multiple conversations (if something showed up in 4 different meetings, I want to know)
- Key decisions made — things I committed to or agreed on
- Blockers and open questions — things that haven’t been resolved
- Books, tools, and resources mentioned — across all calls, so I don’t miss the thing someone recommended in passing
- Relationship signals — who I said I’d follow up with, or who seems like they need a check-in
That last category has probably been the most useful for me practically. I miss follow-ups all the time. Now my agent flags them automatically.
The Contradiction Feature
But here’s the part I didn’t expect to be so valuable.
Contradictions.
Last month, two people told me completely different things about AI-generated content. One person said AI clones and AI-generated content are the future of personal branding. Another person, in a completely different call a few days later, said authenticity is the only thing that builds real trust and that AI-generated content is destroying it.
Neither of them knew the other had said the opposite thing.
But my agent caught both. It flagged them as a contradiction. And suddenly I had a genuinely interesting question to sit with: which one is right? Are both right in different contexts? Is there a third answer?
You can’t get that by reading one transcript. You can only see contradictions when something is holding all the conversations at once.
This is what I mean by transcript-first thinking. Your meetings are already producing data — real conversations, real opinions, real signals. The question is whether you’re capturing it in a way that lets you use it.
The Context Profile That Makes It Work
There’s a second piece to this that took me a while to figure out.
The synthesizer is only as useful as the context you give it. If the agent doesn’t know who I am, what my businesses are, or what I care about, it can’t tell the difference between a minor comment and something worth flagging.
So I built what I call a context profile.
It’s a single Google Doc that I load into every agent I build. It has my name, my values, my business goals, my working style, my communication preferences, my current projects. I used ChatGPT to help me write it. I basically had a conversation with ChatGPT about myself and asked it to summarize everything into a structured document.
The funny part is that ChatGPT wrote a better summary of me than I would have written myself. It asked follow-up questions. It noticed patterns I hadn’t spelled out. And when I loaded that document into Lindy, the agents immediately got better. They stopped giving me generic output and started giving me relevant output.
Think of it like the difference between asking a new consultant to help you and asking one who’s worked with you for six months. The work is technically the same. But the consultant who knows your business gives you something you can actually use.
This is the Centralized Context principle in practice. Instead of explaining yourself every time you open a new AI session, you build one document that travels with every agent you deploy. One source of truth. Agents stop asking you the same questions. Output gets more personalized. Everything gets faster.
How to Build Your Own
If you want to try this, here’s the rough structure:
Step 1: Get your transcripts somewhere readable
You need your meeting transcripts stored somewhere an AI can access them. Google Drive works well. The key is saving them as plain text files — not PDFs, not formatted docs. Just text.
Step 2: Build your context profile
Open ChatGPT and have a conversation about yourself. Tell it your name, your businesses, your goals, your communication style. Then ask it to summarize everything into a structured document. Review it, fill in gaps, save it to Google Drive.
Step 3: Build the synthesizer in Lindy
The trigger is time-based — every Sunday at 9pm, for example. The action is: load the context profile, read all transcripts from the past 7 days, generate a structured summary, write it to a new Google Doc, and share it to your email.
The whole thing took me about two hours to build the first time. And the output on week one was immediately useful.
Why This Matters
There’s a concept in productivity called real vs fake work. Reading through individual transcripts one by one looking for insights is real work — it takes time and attention. But having an agent do the first pass so you can focus on the thinking? That’s leverage.
The synthesizer doesn’t replace your judgment. You still have to decide what the contradictions mean. You still have to choose which follow-ups to actually send. But it surfaces the raw material so you’re making decisions with better information.
Your meetings are already happening. The data is already there. The question is just whether you’re letting it work for you.
Want to learn how to build AI agents like this? Check out our Productivity Academy for frameworks on AI-powered productivity systems.
