
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.
Also on Medium
Full archive →AI Agents and the Future of Work: A Pixar-Inspired Journey
What product managers can learn about AI agents from how Pixar runs a film team.
Many AI Agents Are Actually Workflows or Automations in Disguise
How to tell agents from workflows from cron jobs, and why it matters for what you ship.