agentsUpdated·Falk Gottlob··updated ·5 min read

Stakeholder Communication Agent

Generate tailored updates for different audiences: exec summaries, board updates, investor reports, team briefings. All from the same data.

agentscommunicationstakeholders
Helpful?

Stakeholder Communication Agent
Try it live
See this agent running in the sandbox

Stream a simulated run, inspect the notifications it would send on Slack and email, and see exactly where it sits in the 7-stage PM OS flow. No password required.

The short version

The Stakeholder Communication agent generates five tailored updates from the same source data: a one-page executive summary, a two-to-three-page board update, an investor update, a team briefing, and a customer email. It runs Friday at 3 PM (team and customer) and monthly (exec, board, investor). Feed it OKR progress, launches, metrics, and risks. The agent applies audience-specific transformations: execs get business impact, boards get risk assessment, investors get unit economics and growth, team gets implementation details, customers get benefit-led announcements. Days of stakeholder writing collapsed into one agent run plus an hour of refinement.

You spend too much time writing updates. Quarterly you write: a board deck, an investor update, an all-hands summary, and a team briefing. All have the same data (OKR progress, launches, metrics) but different tone and focus.

The execs want high-level business impact. The board wants risk assessment. Investors want growth and unit economics. The team wants implementation details and obstacles.

Writing four different docs from the same source is tedious and error-prone. One doc gets updated, others get stale.

The Stakeholder Communication agent generates them all from a single source. Every Friday and monthly, you feed it: OKR progress, feature launches, metrics, and risks. It generates: executive summary, board briefing, investor update, team briefing, and customer update. All automatically.

How It Works

The agent starts with the same source material and applies audience-specific transformations:

Source data: OKR progress, feature launches, customer metrics, financial metrics, risks, and wins. The agent ingests all of it.

Audience analysis: For each stakeholder type (exec, board, investors, team, customers), the agent understands: what matters to them, what level of detail they want, what tone fits, and what format works.

Transformation: The agent rewrites the same data for each audience. The executive summary says "launched enterprise onboarding, 15% of enterprise segment now adopting." The team briefing says "built automated setup flow for 3-step data mapping, docs at X, training at Y, support ticket template at Z."

Format adaptation: Exec gets a 1-page summary. Board gets a longer deck with risk assessment. Investors get growth metrics and unit economics. Team gets implementation details and blockers.

The output: four ready-to-use updates.

Data Sources and Setup

Prerequisites: You'll need:

  • OKR tracking system: Current OKR progress and scores
  • Metrics dashboard: Product metrics, growth metrics, financial metrics
  • Feature tracking: Shipped features, upcoming roadmap
  • Risk tracking: Known risks, incidents, churn signals
  • Customer data: NPS, retention, expansion, churn
  • Financial data: ARR, growth rate, unit economics
  • Previous updates: For tone and format consistency

Schedule: Weekly Friday at 3 PM (team/customer briefing). Monthly (exec/board/investor updates).

The Claude Prompt

You are writing stakeholder updates tailored to different audiences.

Here's our current state:
[METRICS:
- OKR progress (actual vs. target)
- Quarterly wins (features, customers, deals)
- Key challenges and risks
- Financial metrics (ARR, growth, churn)
- Product metrics (activation, retention, adoption)
- Customer health (NPS, high-risk accounts, expansion opportunities)]

Here's what we shipped recently:
[LAUNCHES: features, performance, customer impact, adoption rate]

Here are known risks:
[RISKS: churn signals, competitive threats, technical debt, market changes]

Please generate updates tailored to these audiences:

1. **Executive Summary** (1 page)
   - Business headline: 1 sentence on overall state
   - OKR progress: 3-5 key metrics, status, trajectory
   - Top 2-3 wins (in business terms)
   - Top 1-2 risks requiring attention
   - Recommended actions
   - Tone: business-focused, high-level, forward-looking

2. **Board Update** (2-3 pages)
   - Narrative: what happened this quarter in business terms?
   - Key metrics with trend
   - Risk assessment: what could go wrong? how likely? impact?
   - Wins and momentum
   - Financial performance
   - Upcoming quarter focus
   - Tone: comprehensive, risk-aware, prepared

3. **Investor Update** (2-3 pages, if applicable)
   - Growth narrative: where are we in the journey?
   - Unit economics and path to profitability
   - Key metrics: growth rate, retention, expansion
   - Wins and traction
   - Competitive positioning
   - Use of capital
   - Next milestones
   - Tone: growth-focused, confident, data-driven

4. **Team Briefing** (2-3 pages)
   - What we accomplished this sprint/quarter
   - OKR progress and what that means
   - Launches: what we shipped, how it's being used, next steps
   - Obstacles and how we're tackling them
   - Upcoming priorities
   - How each team's work connected to outcomes
   - Tone: collaborative, detailed, forward-looking

5. **Customer Email** (1 page)
   - Greeting: "Here's what we shipped..."
   - Top 3 features/improvements (customer benefit, not feature description)
   - Traction: "X customers are using Y feature"
   - What's coming next (optional teaser)
   - Close: "excited to show you more"
   - Tone: friendly, benefit-focused, conversational

For each update:
- Use concrete metrics and data
- Be honest about challenges (don't hide risks)
- Connect features/metrics to actual customer impact
- Make the narrative clear (what story are we telling?)

Format each as ready-to-use: exec can send exec summary, team can send team briefing, etc.

What You Get

Instead of writing four separate updates from scratch:

  • Efficiency: Generate all stakeholder comms from one data source in one agent run
  • Consistency: Same data, different angles - no contradictions
  • Audience fit: Each stakeholder gets the tone and detail level they need
  • Quality: More time to refine than to write from scratch
  • Memory: You have a documented record of what you communicated to whom

Real outcomes:

  • Stakeholder updates take hours instead of days
  • Nobody gets confused because all comms are consistent
  • Execs, board, investors, team, and customers all feel heard (different info for different needs)
  • Your communication gets tighter because you refine one source instead of writing four times

For the full agent fleet and scheduling details, see Your AI Agent Fleet. For the OKR data that feeds the board and exec sections, see the OKR Progress and Prediction Agent. For the exec update template used to structure the weekly briefing, see the Exec Update Template(coming Jul 7).

Share this post

Also on Medium

Full archive →

Frequently asked

What stakeholder updates does the Stakeholder Communication agent generate?+

Five outputs from the same source data: a one-page executive summary (business headline, OKR progress, top wins, key risks), a two-to-three-page board update (narrative, metrics trend, risk assessment), an investor update (growth narrative, unit economics, competitive positioning), a team briefing (implementation details, obstacles, upcoming priorities), and a customer email (benefit-led feature announcements). All from one data input, one agent run.

How does the agent adapt the same data for different audiences?+

It applies audience-specific transformations. Executives get business impact framing: 'launched enterprise onboarding, 15% of enterprise segment now adopting.' The team briefing says: 'built automated setup flow for 3-step data mapping, docs at X, training at Y.' The board gets risk assessment. Investors get unit economics and growth rate. Each version uses the same underlying facts with different emphasis, depth, and tone.

How often should the stakeholder communication agent run?+

Two cadences: weekly Friday at 3 PM for team and customer updates, and monthly for executive, board, and investor updates. The weekly cadence keeps internal teams aligned without waiting for quarterly reviews. The monthly cadence is enough for board and investor updates. You feed the agent the same source data both times, it handles the format.

What source data does the agent need to generate all five updates?+

OKR progress and scores, feature launches with adoption metrics, financial metrics (ARR, growth, churn), product metrics (activation, retention), customer health (NPS, high-risk accounts, expansion opportunities), known risks and churn signals, and the previous versions of each update for tone and format consistency. The more structured your input, the more ready-to-use the output.

What is the biggest time savings from this agent?+

Eliminating the re-writing pass. Most PMs write the same information four times with different framing for different audiences, and the four versions drift from each other. This agent writes all four from one source in one pass, so the numbers are consistent, no version is accidentally stale, and you spend the time you save on refinement rather than drafting.

About the author

Falk Gottlob

Falk Gottlob

Product Executive · Founder, Falkster.AI

Thirty years shipping product at Microsoft Research, Adobe, Salesforce (Marketing Cloud / Quip / Slack), and several startups including one $6.5B exit and one acquired by Microsoft. Now CPO at Smartcat and founder of Falkster.AI, writing this notebook from the boardroom, not the keyboard.

Comments (0)

Sign in with LinkedIn to leave a comment.

Sign in with LinkedIn
  • Be the first to comment.

Keep Reading

Posts you might find interesting based on what you just read.