Chloe Adams·
My research became a board-ready report with BLUF structure and evidence-strength tags on every finding
Transform research materials into publication-ready executive reports with structured narrative, evidence hierarchy, and recommendations.
Executive Research Report Architect
You are an executive research director who produces board-level reports. Transform my research into a polished, publication-ready report.\n\nREPORT TOPIC: {{report_topic}}\nAUDIENCE: {{target_audience — e.g., 'Board of Directors', 'VP of Product', 'Investment Committee'}}\nPURPOSE: {{purpose — e.g., 'Decision support', 'Status update', 'Strategic planning', 'Due diligence'}}\nPAGE TARGET: {{page_count}} pages\nTONE: {{tone — e.g., 'Authoritative', 'Balanced', 'Urgent', 'Academic'}}\n\nRESEARCH MATERIALS (paste notes, articles, data, interview summaries, or provide links):\n{{research_materials}}\n\nOUTPUT STRUCTURE:\n\n1. TITLE PAGE SUGGESTION\n- 3 options for compelling titles + subtitles\n\n2. EXECUTIVE SUMMARY (1 page max)\n- Context (2 sentences)\n- Key Findings (4-6 bullets with evidence strength indicators)\n- Recommendations (3 prioritized actions)\n- Risk Alert (if any critical issue requires immediate attention)\n\n3. METHODOLOGY\n- Research approach summary\n- Sources consulted (count and type)\n- Limitations and caveats (be transparent)\n\n4. FINDINGS (main body)\n- Organized by theme (not by source)\n- Each finding follows: Assertion → Evidence → Implication structure\n- Use subheadings, bullet points, and highlighted quotes from sources\n- Mark evidence quality: [Strong] [Moderate] [Emerging] [Anecdotal]\n\n5. ANALYSIS & INTERPRETATION\n- Pattern recognition across sources\n- Contradictions or gaps in the evidence\n- Causal analysis (not just correlation)\n\n6. RECOMMENDATIONS\n- Each recommendation: Action + Owner-type + Timeline + Expected Outcome + Risk\n- Organized by priority (Must Do / Should Do / Could Do)\n\n7. APPENDIX OUTLINE\n- Suggested supporting materials (data tables, source list, glossary)\n\nWRITING RULES:\n- Open with the conclusion (BLUF: Bottom Line Up Front)\n- One idea per paragraph\n- Active voice, no passive constructions\n- Every claim must trace to a source or be flagged as [Analyst Inference]\n- Use 'however' not 'but' for contrast; 'therefore' not 'so' for conclusions\n- No filler phrases ('It is interesting to note that...', 'As we can see...')
Ergebnisse
# Customer Retention Strategy: Findings & Recommendations
**Audience:** VP of Product. **Purpose:** Decision support. **Target:** 4 pages. **Tone:** Balanced.
## 1. Title options
1. *"The Leaky Bucket: Why 6% of Customers Leave Monthly — and the Three Fixes That Stop It"*
2. *"Retention Before Growth: A Data-Backed Case for Pausing Acquisition Spend"*
3. *"From Churn to Compounding: Closing the Retention Gap in Q3"*
## 2. Executive Summary
Monthly churn (5.8%) is eroding growth faster than acquisition replaces it. Three interventions can cut it below 4% within a quarter.
- Onboarding completion correlates with 3× higher 6-month retention [Strong]
- 70% of churned users never adopted the core "linking" feature [Strong]
- Support-ticket volume predicts churn 30 days out [Moderate]
- Enterprise accounts churn half as often but are under-targeted [Moderate]
- **Risk Alert:** at current churn, net-new growth turns negative by Q4 if acquisition dips.
## 3. Methodology
Analyzed 18 months of product + billing data (45k user-months), 12 churned-customer interviews, and 3 industry benchmarks. **Limitation:** interview sample skews toward self-serve; enterprise voice underrepresented.
## 4. Findings
**Onboarding is the retention lever.** *Assertion:* completion drives retention. *Evidence:* completers retain at 78% vs 26% [Strong]. *Implication:* fixing onboarding beats any acquisition tactic.
**Feature adoption is the leading indicator.** Users who adopt linking in week 1 churn 60% less [Strong]. *Implication:* drive one activation moment fast.
**Support load signals exit.** 3+ tickets in 30 days → 2.4× churn odds [Moderate]. *Implication:* proactive outreach on ticket spikes.
## 5. Analysis & Interpretation
Across sources the pattern is consistent: churn is an *activation* problem, not a *feature-gap* problem [Analyst Inference]. The contradiction worth noting — interviews cite "price," but usage data shows price-sensitive churners were also low-activation, so price is likely a rationalization, not the cause.
## 6. Recommendations
| Priority | Action | Owner-type | Timeline | Outcome | Risk |
|----------|--------|-----------|----------|---------|------|
| Must Do | Redesign onboarding to force first "link" | Product | 0–30 days | Churn −1.5pt | Friction if over-gated |
| Must Do | Ticket-spike retention outreach | CS | 1–3 mo | Churn −0.8pt | CS capacity |
| Should Do | Enterprise expansion focus | Sales | 3–6 mo | Higher LTV | Longer cycle |
| Could Do | Win-back campaign | Marketing | 3–6 mo | Recover 5% | Low ROI |
## 7. Appendix outline
Retention cohort tables, interview transcript summaries, benchmark sources, glossary.
Modell: Claude Sonnet 4
49 Likes11 SavesScore: 39
4 Kommentare
Maya Patel·
The time-block table is so much better than my color-coded chaos.
Leon Wirth·
This is the calm Monday I've been chasing. Thank you.
Ethan Reed·
My standups got shorter and clearer overnight.
Noah Steiner·
This is the first weekly review template that actually stuck.