Turn analysis findings into an executive summary

Convert raw findings and numbers into a short, decision-ready summary with the answer first, evidence, caveats and next steps.

LLazyPrompt(@lazyprompt)Data & AnalysisSummarizeWorks with any model
No ratings yetSign in to rate
Save 0 Fork Report
Prompt template
Turn my analysis into an executive summary for {{audience}}.

The question I was asked: {{question}}
My findings, numbers, and notes (messy is fine):
{{findings}}

Caveats or limitations I know about: {{caveats}}
Decision or action this should support: {{decision}}

Write the summary as follows:
1. Bottom line: a two-sentence answer to the question, leading with the conclusion and the single most important number. No preamble.
2. Key findings: 3-4 bullets, each beginning with the insight, then the supporting number, then why it matters. Use only numbers I provided; do not invent or round in a misleading way. If I gave inconsistent figures, flag it.
3. Confidence: say how confident we can be (high, medium, low) and why, in one or two sentences, using my caveats.
4. Recommendation: 2-3 concrete actions, in priority order, each with an owner role and expected effect where I gave enough information.
5. What we don't know: up to 3 open questions and how we could close them.
6. Suggested visual: one chart that would make the main finding obvious, with a headline that states the insight.
7. Then a 60-word version suitable for pasting into an email or chat message.

Write plainly, avoid hedging words that say nothing, and keep the whole thing under 350 words excluding the short version.
Example output
**Bottom line**: Monthly churn rose from 2.1% to 3.4% in Q3, and about 70% of the increase came from the legacy Basic plan, especially customers acquired through Q1 discounts. Pro churn did not change (1.2%). **Key findings** - The increase is concentrated, not broad: Basic accounts for roughly 70% of the rise, so a company-wide fix is unnecessary. - Promo-acquired Basic customers are the main group at risk; they joined at a discount and then met the July 1 price increase. - Support contact predicts retention: customers who reached support within 30 days churned at half the rate. This is a correlation; engaged customers may be more likely to ask for help. **Confidence**: Medium. The price increase and the promo cohort overlap in time, so we cannot say which drove the churn. **Recommendation** 1. Proactively contact new Basic customers in their first 30 days (Customer Success). 2. Run a small test of the old price for promo-acquired Basic customers to separate the causes. 3. Hold off on a full rollback until the test reads out. **What we don't know**: how competitors priced in Q3; whether promo customers churn at the same rate before the increase. **Suggested chart**: Line chart of monthly churn by plan, with the July 1 price change marked. Headline: "Basic churn jumped after July; Pro did not move." **60-word version**: Churn rose from 2.1% to 3.4% in Q3, mostly on the Basic plan among customers who joined on discounts. Pro is unchanged. We cannot yet tell whether the price rise or the promo cohort is the cause. Recommend early support outreach and a small price test before rolling anything back.

Why it works

Leading with the answer and forcing a confidence statement makes summaries decision-ready and honest. Paste your real notes unedited; the prompt is designed to restructure them.

Licensed CC0 (public domain) Version 1 · history