We’ve all sat in that one weekly meeting that somehow eats an hour and leaves you with nothing. People read status updates out loud. Half the room sits quietly waiting for the one minute that actually involves them. I used to think long meetings were just a fact of work life.
Then I came across this post from an AI professional who shared a single Claude prompt that cuts a recurring meeting from 60 minutes to 30. No fancy tools. No paid plan. Just a clear, repeatable process. I was genuinely impressed by how simple the creator made it, so I broke the whole thing down for you here.
What you need first
Before any prompting happens, the original poster lays out a quick setup. It’s a one-time thing, and then you’re done forever.
- Record your meetings without an AI bot sitting in the call
- Download Granola.ai, which is free
- Keep it open in the background during your calls
- Open the Claude desktop app, not the browser version
- No Claude Pro plan needed for this workflow
Why it matters: Granola transcribes your Zoom, Teams, or Meet calls silently, so there’s no awkward bot announcing itself. That quiet transcript is the raw material Claude works from later.
The step-by-step the author walks through
What I love about this contributor’s approach is the timing. The whole audit fits inside a 30-minute window, and each step has a clear reason behind it.
- 0 to 5 min, set up the system. Go to Claude, click the ‘+’, open Connectors, and toggle Granola on. That’s the only setup, and you do it once.
- 5 to 10 min, pick one meeting. Not all of them. Just one. The weekly recurring call that always runs long and feels like catch-up. This works on a single recurring call at a time.
- 10 to 15 min, paste one prompt. This is where the magic happens (more on the exact text below).
- 15 to 20 min, make Claude show its work first. You add a line that forces it to pause so you can correct it.
- 20 to 25 min, read what Claude built. A one-page pre-read, a 30-minute agenda, and a pre-work list per person.
- 25 to 30 min, send it and cut the meeting. Drop the pre-read into the calendar invite a day ahead.
The exact prompt to paste
Here’s the core prompt the expert shares. Copy it word for word and swap in your meeting name:
“Audit my recurring meeting [NAME] and cut it from 60 minutes to 30. Pull the last 3 transcripts from Granola, then: list what got repeated in all 3, split it into read-before vs. discuss-live, write a one-page pre-read from the read-before items (status, open threads, numbers, no recap), build a 30-minute agenda from the discuss-live items, list the pre-work each attendee should bring done, and from who actually spoke, tell me who only needs part of the call.”
That single block does a lot of heavy lifting. It finds the repeated filler, separates what people can read on their own from what truly needs a live conversation, and even flags who can skip most of the call.
Make Claude show its work
This is the step I think most people would skip, and it’s the one that keeps you in control. The original poster says to add this line to your prompt:
“Before you write anything, show me the 3 transcripts you’re using and the read vs. discuss split, so I can correct it.”
The reasoning is sharp. Letting the AI run and hoping for the best is useless. Making it pause so you can fix the split before it builds anything is what works. As the creator puts it, you stay in charge, not the AI.
Why the pre-read changes everything
Once Claude builds the materials, half of what you used to say out loud is now on a page. Nobody has to perform a status update live. The author makes one point that stuck with me: paste the pre-read into the calendar invite a day ahead. A pre-read handed out during the meeting is just wasted paper.
Then check Claude’s “who only needs part of the call” list. If half your room is only there for one minute, let them skip the rest. That’s real time given back to your team.
Running the actual meeting
The context is already on paper, so the LinkedIn user suggests starting at the first decision. Hold the time boxes. That discipline is your 30 minutes. No warm-up, no recap, just decisions.
Don’t write the follow-up yourself
After the call, the savvy professional hands the notes back to Claude with this prompt:
“From this transcript, write the action items with owners and deadlines.”
The reason is painfully relatable. “I’ll send notes later” is the email that never actually gets sent. Letting Claude draft it the moment the call ends means it actually goes out.
The pro tip I almost missed
Here’s the part I think makes this a habit instead of a one-off. The creator recommends running the same audit again in a month. Meetings creep back toward 60 minutes the moment you stop watching. So you simply ask Claude what crept back in, and you cut it again.
I find that loop brilliant. It treats meeting bloat as something you manage on a schedule, not a one-time cleanup. With more teams leaning on AI to reclaim focus time, having a repeatable system like this feels like a real edge.
If you run even one recurring meeting that always overstays its welcome, this workflow is worth a try. Go read the full post from the original creator on LinkedIn for the complete walkthrough and give your calendar some breathing room.