Weekly Executive Report Agent

Agent Name: Weekly Executive Report Agent Role: Executive-level weekly briefing generator Frequency: Every Monday at 7:00 AM Output Channel: Slack (executive channel) + Email Run Time: ~20 minutes

---

PURPOSE

Your leadership meeting is in 30 minutes. Your CEO walks in and asks: "What's our product health? What are we shipping this month? What's at risk?" You need a 5-minute answer that covers strategy, execution, risk, and metrics. That's what this agent does.

The Weekly Executive Report Agent consolidates all critical product data from the previous week into a single, shareable executive brief. It aggregates outputs from your daily and weekly agents, adds strategic context, and produces a narrative that leadership can consume in under 3 minutes.

This agent is your "what's happening in product" dashboard for people who don't have time to dig into details but need to know what matters.

---

DATA SOURCES

1. All Daily/Weekly Agent Outputs

Source: Slack, Email, Notion Query:

• Retrieve outputs from: Daily Focus agent, Daily Health Check agent, Weekly Ops Digest agent, Product Health Dashboard agent
• Extract key metrics, risks, wins, operational trends
• Date filter: Last 7 days

2. Roadmap Status (Jira, Asana, Linear)

Query:

• Filter: Current release month + Q-level roadmap
• Extract: Feature status (on track / at risk / blocked), ARR impact per feature, customer commitments, shipping dates
• Trending: Week-over-week status changes

3. Key Business Metrics (Amplitude, Mixpanel, Data Warehouse)

Query:

• Revenue/ARR (trend, MoM), Activation rate, Retention rate, Churn risk signal, NPS/CSAT, Usage growth
• Extract: Absolute numbers + trend indicators (up/flat/down)

4. Customer Health Data (HubSpot, Vitally, CSV export)

Query:

• New at-risk accounts (from Health Check agent), Recent escalations, High-value customer signals
• Filter: Accounts >$50K ARR or new churn flags
• Extract: Account name, reason for risk, action needed

5. Engineering Velocity & Deployment Data (GitHub, Engineering dashboard)

Query:

• PRs merged this week, Deployment frequency, Build health (pass rate), Critical bugs resolved
• Extract: Velocity trend (up/flat/down), any blockers

---

REPORT STRUCTURE

1. EXECUTIVE SUMMARY (5-Sentence Narrative)

A single paragraph that tells the story: What happened this week, what's on track, what's at risk, and what needs attention. Written for someone who reads 50 briefings a week.

Format:

[Week of MMM DD]: Product shipped [feature], delivered [metric result], and identified [1-2 key risks].
Status: [execution assessment]. Leadership decision needed on: [1-2 items].

2. KEY WINS THIS WEEK

The 3-5 things that went well. Not everything, just the ones leadership cares about.

Format (Bulleted):

• [Feature shipped / metric achieved / customer outcome]: [Brief explanation + impact]. [$ARR impact if applicable]
• [Efficiency gain / operational win]: [Explanation]. [Time saved or risk reduced]

3. TOP 3 RISKS (Prioritized)

What could go wrong. Ranked by impact (revenue risk first, then execution risk, then operational risk).

Format:

Risk	Impact	Owner	Action	ETA
[Risk name]	[ARR at risk / customer impact]	[PM/Eng lead]	[Mitigation step]	[When resolved]

4. ROADMAP HEALTH SNAPSHOT

One-line health assessment + breakdown by status.

Format:

Roadmap Health: 15 features on track (75%), 4 at risk (20%), 1 blocked (5%)

On Track (75%):
- [Feature 1] | [ARR] | Ships [date]
- [Feature 2] | [ARR] | Ships [date]

At Risk (20%):
- [Feature 3] | [ARR] | Issue: [blocker]. ETA revised to [new date]

Blocked (5%):
- [Feature 4] | Waiting on [dependency]. Impact: [customer impact]

5. METRICS SNAPSHOT (Weekly Trend)

The numbers leadership watches.

Format:

Revenue & Growth:
- ARR: $[X] (↑ $XXK vs. last week) | MoM: ↑ 2.3%
- New ARR: $[X] | Expansion ARR: $[X]
- Activation Rate: [X]% (target: [Y]%)

Retention & Health:
- Retention Rate: [X]% (target: [Y]%)
- Churn Risk (new): [N] accounts | At-risk ARR: $XXK
- NPS: [X] | CSAT: [Y]%

Product:
- Usage Growth: ↑ [X]% WoW | DAU: [X] | Session length: ↑ [X]%
- Feature Adoption: [Top 3 features by adoption %]

6. CUSTOMER HEALTH & ESCALATIONS

New risks + what you're doing about them.

Format:

New At-Risk Accounts (This Week): [N]
- [Customer Name] | [ARR] | Reason: [Churn signal]. Action: [Owner] calling on [date].

Active Escalations:
- [Escalation title] | Severity: [Critical/High] | Owner: [Name] | Next update: [Date]

7. RESOURCE ALLOCATION CONCERNS

Are teams blocked? Understaffed? Overcommitted?

Format:

Staffing:
- [Team name]: [Concern, e.g., "QA 2 weeks behind on test coverage for release"]
- [Team name]: [Concern, e.g., "Design blocked waiting for API specs from eng"]

Capacity:
- [Team name]: On track for [N] commits this month
- [Team name]: Carrying [N] bugs in to next sprint (trend: ↑/→/↓)

8. DECISIONS NEEDED FROM LEADERSHIP

The asks. Be specific about what decision, who's deciding, and what the deadline is.

Format:

1. **[Decision Title]**: Scope [Feature X] down from [original scope] to [revised scope]?
   - Rationale: [Why this is needed]
   - Impact: [If you say no, what happens?]
   - Decision Owner: [CEO/Chief Product Officer]
   - Deadline: [Date]

2. **[Decision Title]**: Accelerate launch of [Feature] to [earlier date] despite [constraint]?
   - Rationale: [Customer commitment / revenue opportunity / competitive]
   - Resource Ask: [What it costs to accelerate]
   - Decision Owner: [CEO/CRO]
   - Deadline: [Date]

9. WEEK AHEAD PREVIEW

What's coming next week that leadership should know about.

Format:

- Monday: Release readiness verification for [release name]
- Wednesday: Competitive landscape deep dive
- Friday: All-hands product update (including [key announcement])

---

HOW TO SET IT UP

Step 1: Create Slack Integration

• Connect your product alerts channel
• Create a dedicated #executive-reports channel if you don't have one
• Give the agent read access to all daily/weekly agent outputs

Step 2: Connect Data Sources

• Roadmap: Grant read access to Jira/Asana (via API token or Zapier)
• Metrics: Connect to your product analytics (Amplitude/Mixpanel API) and data warehouse
• Customer Health: Connect to HubSpot/Vitally (CRM export)
• Velocity: Connect to GitHub API for PR/deployment data

Step 3: Define Leadership

• Specify who receives the report (email list or Slack mentions)
• Define decision owners (CEO, CPO, CRO, CFO, etc.)
• Set escalation rules (if X metric drops Y%, notify Z)

Step 4: Customize Report Sections

• Decide what metrics matter most to your CEO
• Define "at risk" thresholds (e.g., feature >2 weeks behind = at risk)
• Define ARR impact tiers for risk prioritization

Step 5: Schedule

• Set to run every Monday at 7:00 AM (1 hour before your executive sync)
• Set timezone to match your leadership's location
• Test with mock data first

---

SAMPLE PROMPT (Customizable)

You are an executive product analyst. Your job is to produce a 5-minute weekly executive brief from product data.

DATA INPUTS:
- Daily focus report from [date]
- Health check report from [date]
- Weekly ops digest from [date]
- Product dashboard from [date]
- Current roadmap status
- Key metrics from [analytics tool]

INSTRUCTIONS:
1. Write a 5-sentence executive summary covering: what shipped, what's at risk, what needs leadership decision
2. List 3-5 key wins with ARR impact where applicable
3. Identify top 3 risks ranked by business impact (revenue first)
4. Summarize roadmap health: % on track / at risk / blocked. List featured by status.
5. Pull key metrics (ARR, activation, retention, churn, NPS, usage growth)
6. Highlight new at-risk customers from health check data
7. List any resource allocation blockers
8. Identify 1-3 decisions needed from leadership (with impact if not decided)
9. Add week-ahead preview

TONE: Professional, concise, data-driven. Assume the reader has 3 minutes.
OUTPUT: Markdown formatted for Slack and email.

---

FREQUENCY & TIMING

• Frequency: Every Monday
• Time: 7:00 AM (adjust to 1 hour before your executive sync)
• Runtime: ~20 minutes
• Timezone: Your company's headquarters timezone

---

WHAT SUCCESS LOOKS LIKE

✓ Your CEO reads it in 3 minutes and has full product context before the leadership meeting ✓ One-pagers disappear because this report covers the same ground ✓ Decision cycles accelerate (you're asking for decisions explicitly, not hoping leadership notices) ✓ No "surprises" in executive syncs, risks and wins are known in advance ✓ Non-product leaders can answer "What's happening in product?" because they read your report