Loading lesson…
Pipe Stripe, Posthog, and Linear into Claude to draft a credible investor update in under 10 minutes.
If you've raised even a pre-seed check, investors expect monthly updates. Skipping them looks shady. Rushing one at 11pm looks worse.
Investors skim. A tight 'wins / losses / asks' structure beats a three-page essay every time. Claude is good at the structure; you own the asks.
# Investor Update Prompt Draft an investor update for {company}, month of {month}. Inputs: - MRR: {current} (prev: {prev}, Δ: {delta}%) - Cash: {cash}, burn: {burn}/mo, runway: {months} - Shipped: {linear_top_3} - Losses/learnings: {journal_notes} Format: 1. TL;DR (3 bullets) 2. Wins 3. Losses & what we're changing 4. Metrics table 5. Asks (3 specific, warm intros / hires / feedback) Tone: confident, no corporate hedge, honest about losses.Good looks like sending on the 1st of every month, getting at least two useful intros per quarter, and investors saying 'your updates are the clearest ones I read.'
8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-biz2-investor-updates-adults
What is the main idea of "Auto-Generating Monthly Investor Updates From Your Metrics"?
Which concept is most central to "Auto-Generating Monthly Investor Updates From Your Metrics"?
Which use of AI fits this topic best?
What should a careful learner remember about "Never cherry-pick metrics"?
You want to use AI after this lesson. What is the safest next step?
How should AI output about investor relations be treated?
Name one way to verify an AI answer about investor relations.
Which action would help you apply "Auto-Generating Monthly Investor Updates From Your Metrics" responsibly?