Generate a document with these sections:
1. Executive Summary (3 sentences max)
2. Problem Definition (what's broken, who's affected)
3. Proposed Solutions (table: option, cost, timeline, risk)
4. Recommendation (which option and why)
5. Next Steps (numbered action items with owners)

Write this as an internal memo for our engineering team.
Tone: technical, direct, no marketing language.
Assume the reader knows our tech stack.

Keep the total document under 500 words.
Each section should be 2-3 sentences maximum.
Use bullet points over paragraphs.

Use markdown tables for any comparisons.
Bold key terms on first use.
Include a TL;DR at the top (one sentence).
Number all recommendations.

Format this as a monthly investor update email:
- Opening: one sentence on overall status
- Metrics table: MRR, DAU, burn rate, runway
- Top 3 highlights (one sentence each)
- One challenge and how we're addressing it
- One ask (if any)
- Close: one-line forward-looking statement
Keep it under 300 words. Tone: confident, transparent, concise.

Generate a PRD with:
- Feature name and one-line description
- User stories (as a [user], I want [action], so that [benefit])
- Acceptance criteria (given/when/then format)
- Technical constraints
- Out of scope (explicit exclusions)
- Success metrics (how we measure this worked)

Summarize this conversation as a weekly standup:
- What we accomplished (bullet points)
- What's blocked (with blocker owner)
- What's planned next week
- Decisions made (if any)
- Risks raised (if any)
Format for Slack: use emoji bullets, keep it under 200 words.

Create a competitive battle card:
- Our strengths vs [Competitor] (3-5 bullets)
- Their strengths vs us (honest assessment)
- Common objections and responses (table)
- Win themes (what to emphasize in pitch)
- Landmines (what NOT to discuss without prep)
Audience: sales team. Direct, actionable.

Prepare board meeting talking points:
- 3 key messages we want the board to leave with
- Supporting data for each message
- Anticipated tough questions and prepared responses
- Decision items requiring board input
- Framing for each decision (our recommendation + why)