Turn Raw Findings Into a Pyramid-Principle Executive Summary

<task>Write an executive summary of our consulting engagement findings for the client's C-suite.</task>
<context>
Project: [e.g., Customer retention diagnostic for a B2B SaaS company]
Duration: [e.g., 6 weeks]
Key findings:
- [e.g., 62% of churn occurs within the first 90 days — onboarding is the primary driver]
- [e.g., Customers who complete all 5 onboarding milestones have 3x higher retention than those who complete fewer than 3]
- [e.g., Customer success team is reactive — 80% of touchpoints are triggered by customer complaints, not proactive outreach]
- [e.g., No formal health scoring exists — at-risk accounts are identified by gut feel, not data]
- [e.g., Competitor benchmarking shows top performers assign dedicated CSMs to accounts >$50K ARR]
Recommendations: [e.g., Redesign onboarding to a milestone-based program, implement a customer health score, restructure CS team from pooled to dedicated model for top-tier accounts]
Expected impact: [e.g., Reduce first-90-day churn by 40-50%, representing $2.1M in preserved ARR annually]
Audience: [e.g., CEO and VP Customer Success]
</context>
<instructions>
- Follow the pyramid principle: lead with the core recommendation, then supporting evidence
- First paragraph: the headline finding and what to do about it (this is what gets read)
- Second paragraph: 3-4 key findings with specific data points that support the recommendation
- Third paragraph: recommended actions with expected impact and timeline
- Final paragraph: clear next steps and what you need from the client to move forward
- Write for a CEO who has exactly 3 minutes before a board meeting
- Every sentence should earn its place — if it does not inform a decision, cut it
</instructions>
<avoid>
- Restating the project scope or methodology — they hired us, they know what we did
- Hedging language: "we believe," "it appears," "it seems likely"
- More than 4-5 key findings — prioritize ruthlessly
- Recommendations without expected impact quantified
</avoid>