Compress a stack of research notes into an executive briefing an exec will actually read to the end

Compress the research notes below into an executive briefing for someone who has five minutes and needs to leave with a clear takeaway, not a chronological account of how the research unfolded.

RAW RESEARCH NOTES
Competitor A raised prices 15% last quarter with no visible churn spike. Competitor B tried the same and lost 8% of accounts within two months. Our support ticket volume correlates more with feature gaps than price in exit surveys.

WHO IS READING THIS
The VP of Product, who is under pressure from the board to show a credible path to margin improvement this quarter.

DECISION AT STAKE
Whether to raise prices 10% across the board next quarter.

MY OWN RECOMMENDATION (if I have one)
I'm currently leaning toward raising prices but only for new customers, not existing ones.

Open with the bottom line, not the background — the first two sentences should state what this means for Whether to raise prices 10% across the board next quarter., before any explanation of methodology or process. Do not lead with "we conducted research into X"; lead with what was found and what it implies. Reorganize the notes by decision relevance, not by the order I researched them in — group findings under what supports the decision, what argues against it, and what's still uncertain, since a chronological recap is the format research notes naturally come in but never the format a time-pressed reader needs. Cut anything from the notes that's interesting but doesn't bear on Whether to raise prices 10% across the board next quarter. — a briefing is not obligated to use everything I gathered.

If I gave you my own recommendation, state clearly whether the compressed evidence actually supports it, partially supports it, or points a different direction — do not silently reshape the evidence to flatter a recommendation I've already committed to; an executive briefing that quietly confirms whatever the requester already believed is worse than no briefing at all.

Push any supporting detail an exec might ask about in the room — the numbers behind a claim, a caveat, a source note — into a labeled appendix rather than the main body, so the main body stays skimmable in under a minute while the detail is still one scroll away if someone asks a follow-up.

OUTPUT FORMAT
1. Bottom line (2-3 sentences).
2. Supports / against / uncertain, as short bullets.
3. Recommendation verdict, if one was given.
4. Appendix: detail bullets, clearly separated from the main body.