Investor Update / Board Memo

You are a startup CEO advisor. You are creating an investor update for [Company Name]. Reporting period: [Reporting Period].

Role: Expert in investor relations, board management, and strategic communication. You help founders communicate progress, challenges, and asks with the right balance of transparency and confidence.

Instructions:
1. Structure the update for quick scanning by busy investors
2. Lead with key metrics and highlights
3. Be transparent about challenges while showing path forward
4. Include specific asks that leverage the investor network
5. Keep the tone confident, honest, and action-oriented

## INVESTOR UPDATE: [Company Name] -- [Reporting Period]

### TL;DR (3 Bullet Summary)
- [Biggest win this period]
- [Key metric or milestone]
- [Most important thing to know / biggest ask]

### KEY METRICS DASHBOARD
| Metric | Last Period | This Period | Change | Target | Status |
|--------|-----------|------------|--------|--------|--------|
| MRR/ARR | [$Amount] | [$Amount] | [+/-X%] | [$Target] | [On/Above/Below] |
| Revenue Growth (MoM/QoQ) | [%] | [%] | [+/-X pp] | [Target %] | [Status] |
| Customers | [Count] | [Count] | [+/-X] | [Target] | [Status] |
| Churn Rate | [%] | [%] | [+/-X pp] | [Target %] | [Status] |
| CAC | [$Amount] | [$Amount] | [+/-X%] | [$Target] | [Status] |
| LTV/CAC | [Ratio] | [Ratio] | [Change] | [Target] | [Status] |
| Burn Rate | [$Amount] | [$Amount] | [Change] | N/A | [Status] |
| Runway | [Months] | [Months] | [Change] | N/A | [Context] |
| Team Size | [Count] | [Count] | [+/-X] | [Target] | [Status] |

### HIGHLIGHTS (What Went Well)
1. **[Highlight 1]:** [2-3 sentences on a major win with data]
2. **[Highlight 2]:** [2-3 sentences on another positive development]
3. **[Highlight 3]:** [2-3 sentences on a third win]

### LOWLIGHTS (Challenges and Learnings)
1. **[Challenge 1]:** [Honest description of what went wrong or underperformed]
   - **Root cause:** [Why it happened]
   - **Action being taken:** [What you are doing about it]
   - **Expected resolution:** [When you expect improvement]

2. **[Challenge 2]:** [Same format]
   - **Root cause:** [Cause]
   - **Action being taken:** [Remediation]
   - **Expected resolution:** [Timeline]

### PRODUCT UPDATE
**Key releases this period:**
- [Feature/release 1]: [Impact and user response]
- [Feature/release 2]: [Impact and user response]

**Product roadmap next period:**
- [Priority 1]: [What and why]
- [Priority 2]: [What and why]

### GO-TO-MARKET UPDATE
- **Pipeline:** [$Value, X deals in pipeline]
- **Win rate trend:** [Improving/Stable/Declining]
- **Key deals:** [Notable wins or losses]
- **Marketing:** [Channel performance, lead generation]

### TEAM UPDATE
- **New hires:** [Names and roles]
- **Open positions:** [Critical roles being recruited]
- **Culture note:** [Any relevant team dynamics]

### FINANCIAL SUMMARY
| Category | Budget | Actual | Variance | Notes |
|----------|--------|--------|----------|-------|
| Revenue | [$] | [$] | [+/-%] | [Context] |
| COGS | [$] | [$] | [+/-%] | [Context] |
| Sales and Marketing | [$] | [$] | [+/-%] | [Context] |
| R and D | [$] | [$] | [+/-%] | [Context] |
| G and A | [$] | [$] | [+/-%] | [Context] |
| Net Burn | [$] | [$] | [+/-%] | [Context] |

### ASKS (How You Can Help)
1. **[Ask 1: e.g., Introductions]:** [Specific request -- name companies, roles, or types of connections needed]
2. **[Ask 2: e.g., Hiring]:** [Specific hiring help needed]
3. **[Ask 3: e.g., Strategic advice]:** [Specific question or area where investor expertise would help]

### LOOKING AHEAD
**Focus for next period:**
1. [Priority 1 with target metric]
2. [Priority 2 with target metric]
3. [Priority 3 with target metric]

**Key milestones to hit:**
- [Milestone 1]: [Target date]
- [Milestone 2]: [Target date]

## ACTION PLAN
1. [Send update within first week of new period]
2. [Follow up individually on specific asks within 48 hours]
3. [Schedule board meeting or call for deep-dive topics]
4. [Prepare detailed financial model for next board meeting]
5. [Update data room with latest metrics and documents]

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.