Executive Product Review
Purpose: Give executives a concise view of product health and surface decisions that need their input
How to run this meeting
Lead with business outcomes, not product activity. Executives don't need to know that three features shipped — they need to know what moved because of them. Frame every update as: here's what we expected, here's what happened, here's what it means for the business. This reframing prevents the meeting from becoming a demo or a status theater.
Keep it to 30 minutes. If you can't cover the material in 30 minutes, the material isn't ready. The discipline of brevity forces preparation. Send a pre-read document (1-2 pages) at least 24 hours in advance so executives can come informed rather than spending meeting time on orientation. Reserve the meeting itself for discussion, not delivery.
Focus on decisions, not status updates. Every agenda item should answer one question: "What do you need from the executives in this room?" If the answer is "nothing — this is just FYI," it belongs in the pre-read, not on the agenda. Ruthlessly filter for items that actually require executive judgment, approval, or air cover.
Before the meeting
- Pre-read document distributed at least 24 hours before the meeting
- Pre-read includes: business metrics dashboard, product progress summary, key risks, and proposed decisions with recommended options
- Each proposed decision includes a clear recommendation and the reasoning behind it
- Product leader has aligned with engineering and design leads before the meeting — no surprises
- Facilitator confirms which executives are attending and adjusts depth accordingly
Meeting Details
- Date:
- Facilitator:
- Attendees:
- Duration: 30 minutes (monthly recommended)
Business Metrics
Top-line indicators of product and business health. Executives should have seen these in the pre-read — use this section for discussion of anything unexpected.
| Metric | This Month | Last Month | Target | Status |
|---|---|---|---|---|
| ARR | $4.2M | $3.9M | $4.5M | 🟡 Behind plan |
| New logos | 28 | 31 | 30 | 🟢 On track |
| Net revenue retention | 108% | 105% | 110% | 🟡 Slightly below |
| Churn rate | 2.1% | 1.8% | <2% | 🔴 Above target |
Churn flag: Churn elevated this month due to 3 mid-market customers lost to a competitor. Root cause analysis: all 3 cited lack of Salesforce integration. This is the primary driver of the decision item below.
Product Progress
What shipped, what's in progress, and whether we're on track for the quarter. One paragraph — executives don't need feature-level detail here.
Q1 delivery is 85% on track. The AI meeting summaries feature shipped on schedule and is showing strong early engagement (71% of active teams have used it at least once in the first three weeks). The enterprise SSO feature is two weeks behind due to a vendor API change; revised completion date is April 14. All other Q1 commitments are on track.
Key Risks
Risks that could affect business outcomes. Rate each and be explicit about what would trigger escalation.
| Status | Risk | Business Impact | Mitigation |
|---|---|---|---|
| 🔴 Red | Salesforce integration gap causing churn | Estimated $180K ARR at risk in pipeline | Accelerating integration to Q2; see decision below |
| 🟡 Yellow | Enterprise SSO delayed 2 weeks | 4 deals at risk totaling $280K ACV | Deals have been notified; none have indicated they'll walk |
| 🟢 Green | AI regulatory exposure (EU AI Act) | Low — confirmed limited risk tier | Legal review complete |
Strategic Decisions
Items that require executive input, approval, or awareness. State the decision clearly, provide context, and make a recommendation.
Decision: Accelerate Salesforce integration to Q2 Context: Three recent churns all cited Salesforce integration as the primary reason. Four additional pipeline deals have flagged it as a requirement. Engineering estimates 6 weeks of work. Pulling it into Q2 would require deprioritizing the reporting dashboard feature.
Recommendation: Approve the swap. The $280K pipeline risk and churn signal outweigh the dashboard delay, which has no direct revenue dependency.
Options:
- Approve Q2 Salesforce integration (deprioritize dashboard) — Recommended
- Maintain current roadmap; address Salesforce in Q3
- Explore contractor augmentation to avoid the tradeoff (adds ~$40K cost)
Next Priorities
What the product team is focused on in the coming month. Flags anything that needs executive support or air cover.
- Finalize Q2 roadmap with approved changes and communicate to customers by March 28
- Close enterprise SSO and support the 4 active deals through procurement
- Kick off Salesforce integration discovery and vendor alignment
- Begin Q3 planning cycle — strategy sessions start April 10
Action Items
| Owner | Action | Due Date | Status |
|---|---|---|---|
| @cpo | Communicate Q2 roadmap change to enterprise customers | 2025-03-28 | Open |
| @cto | Confirm engineering capacity for Salesforce acceleration | 2025-03-21 | Open |
| @cro | Brief sales team on SSO timeline for active deals | 2025-03-19 | Open |
Follow-up
The facilitator sends a decision log to all attendees within 2 hours — one paragraph per decision, capturing what was decided and who is accountable. The full meeting notes go to product, engineering, and sales leadership. Any decision that affects customer commitments should be communicated externally before the end of the week.
Skip the template
Let Stoa capture it automatically.
In Stoa, the AI agent listens to your executive product review and captures decisions, drafts artifacts, and tracks open questions in real time — no note-taking required.
Create your first Space — free