Put Stakeholder Updates on Autopilot: The Complete Setup Guide

The short version

The stakeholder update is one of the highest-friction, lowest-value tasks in a PM's week. Build an agent that runs every Monday morning, pulls data from six systems (GitHub, Jira, analytics, Zendesk, Salesforce, Slack), and generates three audience-tailored updates: executive summary (250 words, data + decisions needed), team update (400 words, what shipped + what's next), board update (300 words, MRR + retention + risks). Three setup options included: manual Claude in browser (5 minutes), Zapier with Claude API (30 minutes), or specialized AI tool. Saves 5-6 hours weekly. Stakeholders get better updates because you're synthesizing real data instead of writing from memory. Start with manual review then automate auto-send after 3-4 weeks of trust.

The stakeholder update is one of the highest-friction, lowest-value tasks in a PM's week. You spend 2-3 hours pulling data from six systems, writing different versions for different audiences, and sending them out. Meanwhile, you could be doing literally anything else.

The solution: An AI agent that wakes up on Monday morning, gathers all your data, generates updates in three different formats (exec summary, team update, board report), and asks you to review before sending.

I've set this up for product teams at companies ranging from Series A to late-stage, and it consistently saves 5-6 hours a week. More importantly, your stakeholders get better, more data-driven updates because you're not writing from memory - you're synthesizing actual data.

This guide walks you through the exact setup. It's not as hard as it sounds.

The Architecture (15 Minutes to Understand)

Here's what happens behind the scenes:

1. Data aggregation (automated): Every Friday afternoon, a script pulls data from your systems (Jira, GitHub, Google Analytics, Slack, Salesforce)
2. AI synthesis (automated): Claude reads all that data and generates three versions of the update
3. Review and send (manual, 5 minutes): You read the generated updates Monday morning, make tweaks if needed, and send
4. Customization (ongoing): For major narrative changes, you edit and regenerate

You're not replacing yourself. You're automating the data-gathering and first-draft writing. You still own the strategic narrative and tone.

Step 1: Connect Your Data Sources (1-2 Hours)

For the AI to write good updates, it needs access to real data. You need to decide which sources to pull from and set up the connectors.

Core data sources to connect:

Source 1: Engineering (GitHub or GitLab)

What to pull:

• Commits and PRs from the last week
• Closed issues and their labels
• Open blockers
• Deployment frequency (how often did we ship?)

Why: Shows what shipped, what's in progress, what's blocked.

Setup: Create a GitHub personal access token and use Zapier's GitHub connector, or write a 20-line script that hits the GitHub API.

What to ask for in the API:
- Merged PRs in the last 7 days
- Issues closed in the last 7 days
- Open issues with "blocked" label
- Number of commits by author

Source 2: Product Metrics (Google Analytics, Amplitude, or custom dashboard)

What to pull:

• Daily active users (DAU)
• Monthly active users (MAU)
• Key conversion metrics (signup to activation, activation to paid, etc.)
• Retention cohorts
• Revenue-relevant metrics (MRR, ARR, customer count)
• Feature adoption (% of users who've tried your top 3 features)

Why: Shows if you're moving the needle on what matters.

Setup: Use the native integrations in Zapier, or ask your data team to set up an automated export to Google Sheets that updates daily. The AI can read a spreadsheet.

Format it as: Metric | Last Week | Last Month | Trend
DAU | 45,234 | 42,100 | +7.4%
Activation Rate | 23% | 21% | +2%
...

Source 3: Customer Feedback (Zendesk, Intercom, or support ticket aggregator)

What to pull:

• Top 5 support issues this week (by frequency)
• Any churn signals (customers mentioning leaving)
• Top feature requests
• Sentiment (are people happy or frustrated?)
• Net Promoter Score (NPS) if you measure it

Why: Shows what customers are struggling with and what they want.

Setup: If your support tool has an API, use Zapier. Otherwise, ask your support lead to send you the top 5 issues every Friday via email or Slack. The AI can read that.

Format: "This week we saw 23 support tickets. Top issues: [1] API rate limits (8 tickets),
[2] Mobile UI confusing (5 tickets), [3] Export formatting (4 tickets). One customer
mentioned they might leave if we don't fix X."

Source 4: Sales Pipeline (Salesforce, Pipedrive, or HubSpot)

What to pull:

• Deals closed this week (count + ARR)
• Deals lost this week (and why)
• Pipeline movement (any large deals moving closer to close?)
• Sales velocity (is our close rate getting better or worse?)
• Common objections (what are people pushing back on?)

Why: Shows if your product changes are helping or hurting sales.

Setup: Most CRMs have Zapier connectors. Or ask sales ops to export the relevant weekly data.

Format: "This week: 3 deals closed ($45k ARR), 2 deals lost (both to competitor X for
'integrations we don't have'), pipeline is $1.2M for month-end."

Source 5: Product Roadmap & Sprints (Jira, Linear, or Asana)

What to pull:

• What's in progress this week
• What shipped last week
• Any roadmap changes
• Blockers that need executive attention

Why: Shows progress against plan and flags if you're slipping.

Setup: Jira / Linear have APIs. Pull this the same way you're pulling GitHub data.

Format: "Current sprint: 12 items, 8 complete, 3 in progress, 1 blocked (waiting on
design). This week shipped: dashboard redesign, API rate limit increase."

Source 6: Slack (Optional but Useful)

What to pull:

• Mentions of key competitors or market news
• Team announcements (hiring, office closures, product milestones)
• Any notable customer wins or issues mentioned
• Team sentiment (are people excited or burned out?)

Why: Captures the "vibe" that doesn't always make it into formal reports.

Setup: Use Slack's search API to find messages with specific keywords. Or just ask your team lead to send you a quick recap of anything notable.

Minimum viable setup:

Don't try to connect everything on day one. Start with:

1. GitHub (what shipped)
2. Analytics dashboard (your north star metric)
3. Support ticket summary (what customers are struggling with)

You can add sales and Slack later. This gets you 80% of the value.

How to actually set this up:

If you have eng support (1-2 hours):

Ask someone to write a simple script that:

• Pulls data from your APIs (GitHub, Jira, analytics)
• Formats it into a markdown doc or Google Doc
• Updates it every Friday at 4pm automatically
• Sends you a Slack notification when it's done

It's genuinely just 30-50 lines of Python or Node. No complex logic.

If you don't have eng support (1-2 hours):

Use Zapier or Make to:

• Pull data from each source using their native connectors
• Format into a Google Doc or spreadsheet
• Run on a schedule (Friday 4pm)

Zapier has templates for this. You're literally clicking "pull GitHub data" and "append to Google Sheets."

If you don't have any technical help (30 minutes):

Every Friday, ask your team leads to send you a Slack message with:

• "Engineering: What shipped, what's blocked?"
• "Sales: Deals closed, deals lost, pipeline?"
• "Support: Top 3 issues?"
• "Marketing: Key metrics?"

Paste all of that into the AI prompt Monday morning. Less elegant, but it works.

Step 2: Set Up the AI Agent (30 Minutes)

Once your data is aggregated (in a doc, spreadsheet, or Slack summary), you need to set up the agent that writes the updates.

Option A: Use Claude in Your Browser (Free, 5 Minutes Setup)

Create a saved prompt in your browser or a note. Every Monday morning, paste it in and run:

I'm a Product Manager at [Company]. Here's what happened last week:

[PASTE YOUR DATA: engineering, metrics, customer feedback, sales, roadmap]

Please generate three versions of my stakeholder update for different audiences:

VERSION 1: Executive Summary (CEO, Board, C-suite)
- Bullet format
- Focus: Strategic progress, business metrics, risks/opportunities
- Length: 250 words max
- Tone: Data-driven, forward-looking
- Include: Revenue impact, product-market fit signals, strategic wins/setbacks
- Key questions answered: Are we on track? What should leadership worry about?

VERSION 2: Team Update (Product + Engineering + Design team)
- Paragraph format
- Focus: What shipped, what's next, how team is progressing
- Length: 400 words max
- Tone: Encouraging, transparent, detail-oriented
- Include: Blockers we overcame, decisions we made, what we learned
- Key questions answered: What did we accomplish? Why does it matter? What's next?

VERSION 3: Board/Investor Update (if applicable)
- Formal bullet format
- Focus: Key metrics, business momentum, strategic initiatives, runway/funding needs
- Length: 300 words max
- Tone: Professional, data-focused
- Include: MRR/ARR growth, retention, customer wins, competitive moves
- Key questions answered: Is the company healthy? Are we executing against plan?

For each version:
- Lead with the headline (the one thing that matters most)
- Use specific numbers, not vague language ("retention improved 2%" not "retention improved")
- Flag any risks or major decisions that need attention
- End with what I'm focused on next week

Format each as a complete draft I can send, not notes or an outline.

Option B: Use Claude API + Zapier (More Automated, 30 Minutes Setup)

If you have Zapier (which most companies do):

1. Create a Zapier workflow:

   • Trigger: Every Monday at 9am
   • Action 1: Read Google Doc or Sheet (your aggregated data)
   • Action 2: Send to Claude API with the prompt above
   • Action 3: Append output to a new Google Doc with a timestamp
   • Action 4: Send you a Slack notification with the doc link

2. Set the Zapier action:

   • Use "Code by Zapier" to hit the Claude API
   • Pass your data and the prompt above
   • Claude returns three versions of the update

This takes 20 minutes if you've never done it before, 5 minutes if you have.

Option C: Use a Specialized Tool (Easiest but Most Expensive)

Tools like Notion, Coda, or Slite have AI integrations. You can:

• Create a database with your weekly data
• Add a "Generate updates" button
• It runs the prompt and creates new docs

If your team already uses one of these tools, this is the easiest path.

Recommendation: Start with Option A (manual, free, 5 minutes). Once you've done it 3 times and know what you like, move to Option B (automated, one-time 30-minute setup).

Step 3: Customize Prompts by Audience (1 Hour)

The generic prompt above works, but it's worth spending an hour refining it to match how YOUR stakeholders actually want information.

For the Executive Summary, ask yourself:

• What metrics does my CEO care about most? (MRR, DAU, churn, burn rate, runway?)
• How much detail do they want? (One page or three?)
• What decisions do they need to make based on this? (Go/no-go on hiring? Pivot? Scale?)
• What's the tone? (Are they data-loving or narrative-loving?)

For the Team Update, ask:

• Do engineers want technical details or high-level outcomes?
• How much should I celebrate wins vs. flag problems?
• What blockers do they need to know about?
• Should I include things that shipped but no one noticed?

For the Board Update, ask:

• How often do they get updates? (Weekly? Monthly?)
• What's the format they expect? (Slide deck, written, verbal?)
• Do they want historical context or just current week?
• What metrics are they tracking against?

Example customized prompt for a Series A company:

I work at [Company], a Series A startup. We're tracking three key metrics for our
Series A board:
- Monthly Recurring Revenue ($MRR)
- Churn rate
- Customers

Here's what happened this week: [Data]

Generate three updates:

EXEC UPDATE (for our CEO/executive team):
Format: Bullet points, no paragraphs
Length: 150 words max
Focus: Did we move the needle on our three key metrics? What should the team worry about?
Include: A final "decision needed from me" section if applicable

TEAM UPDATE (for product + eng + design):
Format: Mix of narrative + bullets
Length: 300 words max
Focus: What are we building and why? What got done? What's next?
Tone: Honest about what worked and what didn't

BOARD UPDATE (for investors, monthly):
Format: Formal bullet points
Length: 250 words max
Focus: MRR trend, churn trend, customer count, key wins, top risks
Include: 3-month trend (are we accelerating or decelerating?)

For the board update, also include a "narrative" paragraph that explains the most
important thing investors should know this week.

Step 4: Set Up Auto-Send (Optional, 10 Minutes)

Once you have the three versions generated Monday morning, you can:

Option 1: Manual send You review the outputs, maybe edit a few sentences, and send them out. Takes 10-15 minutes.

Option 2: Scheduled send Use Zapier or Gmail's schedule feature to send the emails on a schedule:

• Executive update: Monday 2pm (for exec review)
• Team update: Monday 4pm (in team Slack channel)
• Board update: Friday 5pm (or whatever day your board expects it)

Option 3: No auto-send, but auto-post to docs The AI agent generates the updates and posts them to a shared doc or Slack channel. You eyeball them, someone can comment, you finalize and hit send.

Recommendation: Start with manual review + send. You want to make sure the AI is writing something sensible before you trust it to auto-send. After 3-4 weeks, once you trust the output, switch to scheduled send.

How to set up scheduled send:

In Gmail:

• Click the arrow next to Send
• Choose "Schedule send"
• Pick a time

In Zapier:

• Use the Gmail action and set "Send at" to a specific time

Step 5: Handle the "But I Need to Add Context" Problem

Inevitably, someone will say: "This is good, but for this week we also need to mention [strategic thing the AI doesn't know about]."

Solution: Build a "context override" section into your prompt.

Before you generate the updates, here's any additional context for THIS week:

[Add: "We just got a letter of intent from our biggest prospect - I want execs to know
we're likely to close them in March" or "We hit a major blocker with our mobile app
build - this will delay the roadmap by two weeks"]

Incorporate this context into the updates where relevant. For example, the big LOI
should be highlighted in the executive update, and the roadmap delay should be
flagged in the team update.

Then just paste this extra context when you run the prompt Monday morning. Takes 2 minutes.

Step 6: Measure and Refine (Ongoing)

After the first month, ask yourself:

1. Is the AI getting the facts right? (Or are you having to correct it constantly?)

   • If yes: Great, keep going.
   • If no: You probably need better data sources. Check that your data is getting aggregated correctly.

2. Is the tone matching your style?

   • If yes: Keep going.
   • If no: Spend 10 minutes refining the prompt tone instructions.

3. Are stakeholders finding it useful?

   • Ask them: "Is this update helpful? What would make it better?"
   • Adjust based on feedback.

4. Are you actually saving time?

   • If yes: Celebrate and maybe automate more (auto-send instead of manual review).
   • If no: You might be over-tweaking. Lock the template and stop tinkering.

The Complete Prompt Templates

Here are templates for different company stages. Copy and paste the one that matches you.

Template 1: Early-stage (Pre-Series A)

I'm a founder/PM at [Company]. I send a weekly update to myself and my co-founders
to stay aligned on what we're learning.

This week: [Paste data]

Generate a weekly update that:
1. Leads with what we learned (metric moved, customer insight, competitive move)
2. Shows progress against our assumptions (are we on track to validate our core thesis?)
3. Flags what's not working (what assumption did we disprove?)
4. Decides next week's focus (1-3 things we're prioritizing)

Tone: Honest, transparent, no fluff.
Length: 300 words.

This is for co-founders who know the business, so skip the context-setting. Just
tell us what changed and what we should do about it.

Template 2: Series A/B

I'm a PM at [Company], a Series A-funded startup. I send three versions of the
weekly update:

DATA: [Paste aggregated data]

Version 1 - CEO/Board (100 words, focus on metrics + decisions needed)
Version 2 - Team (300 words, focus on what shipped + what's next)
Version 3 - Investors (200 words, focus on traction + risks)

For each version, include one headline that's the most important thing.

Template 3: Late-stage / Enterprise

I'm a Group Product Manager at [Company]. I send updates to:
1. My direct stakeholders (VP Product, other PMs, design leads)
2. Our executive team (for a monthly board report)
3. Our finance team (for headcount and timeline planning)

DATA: [Paste aggregated data, also include: headcount impact, timeline vs. plan, budget impact if any]

Generate three updates:
- Peer Update (for other PMs + stakeholders): Focus on strategy and key decisions
- Exec Update (for CFO/CEO): Focus on business impact and risks
- Board Update (for quarterly board meeting): Focus on strategic progress and competitive landscape

Each should reference our quarterly OKRs and show progress against them.

The Whole Flow in Practice

Here's what a Monday morning looks like once this is set up:

8:50am: You notice a Slack notification: "Your stakeholder updates are ready for review"

8:52am: You open the Google Doc with three versions already written

8:55am: You skim them. The AI got 95% right but you want to reword one sentence and add one paragraph about a customer win they didn't catch.

9:00am: You edit the docs and hit send (or schedule send).

9:05am: You've just done what used to take 2-3 hours in 15 minutes. You're back to building the product.

That's it. That's the whole system.

Why This Works

1. The AI doesn't replace judgment. You still decide what matters, what to emphasize, what tone to use. The AI just does the synthesis.

2. You stay in control. It's generated content you review and approve, not fully automated. This prevents disasters where the AI sends something weird.

3. It forces clarity. To set this up, you have to think about "what do each of my stakeholders actually need?" That clarity alone makes your communication better.

4. It's surprisingly accurate. Once you've aggregated your data in a clear format, Claude is genuinely good at synthesizing it into coherent updates.

5. It's easy to iterate. If an update misses the mark, you just refine the prompt and run it again. No redoing it from scratch.

Common Mistakes

Mistake 1: Dumping all data at once. Don't paste a 5,000-word transcript of all your systems. Aggregate first. Summarize the data into key facts. The AI works better with clean inputs.

Mistake 2: Not customizing by audience. A generic update that tries to serve everyone serves no one. Spend an hour refining what each stakeholder actually wants. It's worth it.

Mistake 3: Automating before you're confident. Don't set up auto-send on day one. Do this manually for a month, let the AI learn your style, let you catch any issues. Then automate.

Mistake 4: Expecting it to write the narrative. "Why did this happen?" still requires human judgment. The AI can synthesize data, but strategy and narrative are on you.

Download the Artifacts

The companion artifact includes:

• The exact prompts for three audience types, ready to copy-paste
• A template for setting up Zapier automation
• A checklist for what data to pull from each system
• A template for tracking which stakeholders want what format

Download it and use it as your starting point. You'll customize it, and that's perfect.

One more thing: Once you have this system running, you might notice something: Your executives start making better decisions because they have better data more frequently. Your team stays more aligned because updates are consistent. Your stakeholders bug you less because they actually understand what you're doing.

That's not an accident. When you force yourself to synthesize data weekly instead of making it up monthly, everything gets better.

Now go set it up.

Sources: Zapier, Make, Anthropic Claude API, Atlassian Jira, Salesforce, Zendesk.