/pre-call-briefing

The aha: Before: Hilda spent 15 minutes before every Rennie call -- checking Slack for flags, pulling up last month's numbers in Ads Manager, scanning ClickUp for open tasks, and re-reading her last meeting notes to remember what was promised. Now she types /pre-call-briefing rennie and gets a full briefing in 30 seconds. Everything she needs on one page, ready to go.

What you need to know (2 min read)

/pre-call-briefing prepares you for client meetings. You give it a client name, and Claude pulls from six different sources to build a single, scannable brief -- performance data, budget pacing, open tasks, recent meeting notes, active flags, and client contacts.

No more opening five tabs and scrambling to piece together what's happening before a call. One command, one page, everything you need to walk in confident. It works for any active client.

This is the command Miller runs before every Rennie project call. It's the command Simon's team uses before Wesgroup check-ins. If you're talking to a client in the next 10 minutes, this is where you start.

How it works

When you run /pre-call-briefing, Claude pulls from multiple sources at once:

1. Campaign Director brief -- The high-level strategic summary for the client. What's the current focus, what campaigns are in market, any known issues.

1. Campaign Monitor flags -- Active warnings from the automated health checks that run daily. Things like delivery errors, learning phase resets, or campaigns that unexpectedly paused. If something is broken, this is where it shows up.

1. BigQuery performance data -- Two windows: the last 7 days and the last 30 days. Spend, impressions, clicks, conversions, CPL, CTR. You see the short-term trend and the monthly picture side by side.

1. Budget pacing -- Month-to-date spend compared to the approved media plan. Shows whether the client is on track, underspending, or running hot. Flagged if pacing is below 70% or above 130%.

1. ClickUp tasks -- Open tasks assigned to this client. Overdue items get called out so you know what the client might ask about.

1. Fireflies meeting notes -- Notes from recent calls with this client. Key decisions, action items, and anything that was promised. So you don't walk into a meeting having forgotten what you committed to last time.

The output is organized top-to-bottom by what matters most: health and flags first (anything on fire?), then performance trends (how are the numbers?), then tasks and action items (what's outstanding?), then context and contacts (who's on the call and what's their role?).

Try it yourself

1. Open Cowork
2. Type: /pre-call-briefing rennie
3. Wait about 15 seconds -- Claude is pulling data from multiple sources
4. Review the briefing. It includes:

• Account health summary -- any active flags or warnings from Campaign Monitor
• 7-day and 30-day performance trends -- spend, leads, CPL, CTR with direction arrows
• Budget pacing -- spend vs. plan with percentage and status
• Open ClickUp tasks -- what's outstanding for this client, with overdue items highlighted
• Recent meeting notes -- key points from the last Fireflies transcript
• Client contacts -- who to expect on the call and their role

1. Use it right before your next client call

Quick reference

Tips

• Run it before every external client call. It takes 30 seconds and catches things you'd miss. A pacing flag, an overdue task, a promise from the last call you forgot about -- better to know before the client brings it up.
• If the briefing seems thin, the client's context files might need updating. The briefing is only as good as the data behind it. If a client's context files are stale, try running /context-sync first to refresh them.
• Ask follow-up questions after the briefing. Claude remembers the data it just pulled. You can ask things like "What changed since last month?", "What should I flag to the client?", or "Summarize the last three meetings" without running another command.
• Use the short client name. Type rennie, not Rennie Advisors. Use the kebab-case slug: century-group, pier-west, skin-matters.
• Pair it with /campaign-status if you need more detail on specific campaigns. The briefing gives you the big picture. /campaign-status gives you the per-campaign breakdown with delivery status and pacing by campaign.

Related

• Context Files Explained -- The files that power this briefing
• /campaign-status -- Quicker check if you just need campaign status, not a full brief
• /context-sync -- Keep context files updated so briefings stay accurate