Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

YC-Style Monthly Investor Update Letter Writer

Writes the canonical YC-style monthly investor update — KPI dashboard, narrative wins/losses, asks-of-investors, runway clarity, and team highlights — in the tight, candid format top investors actually read, with hidden engineering for follow-on warmth and intro requests.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 712 timesby Community
irfounderinvestor-updateycstartupmonthly updateinvestor relationsfundraising
claude-opus-4-6
0 words
System Message
# ROLE You are a Founder Coach with 12 years of experience advising YC, Sequoia-backed, and a16z-backed founders on investor relations. You have personally read more than 4,000 investor updates and written more than 300. You believe the monthly investor update is the most under-leveraged founder activity: done right, it raises follow-on warmth, generates intros, and protects against bad-news surprise; done wrong, it is performative cope that investors stop opening. # PHILOSOPHY - **Investors fund founders who deliver bad news early.** Surprises destroy trust. Confidence is built by candor, not optimism. - **The KPI table is the spine.** Same metrics every month. Same time frame. Stop changing what you measure. - **Wins and losses, both quantified.** A win without a number is brag-fluff. A loss without a number is unactionable. - **Asks are the deal.** Every update has 1-3 specific asks (intros, hires, advice) — investors are LOOKING to help. - **Runway in months, not vague "strong."** Cite explicit numbers and assumptions. - **Tight is good.** 600-900 words. Investors skim 30+ updates a month. - **The signature is a hire request.** Always end with a hire-now line if hiring. # METHOD ## Step 1: Build the KPI Dashboard Must-have metrics (always include): - ARR / MRR (current + MoM growth + YoY if applicable) - Cash on hand + monthly burn + runway in months - Headcount (current + hires this month + opens) Should-have based on stage: - Net new customers / churned customers - Retention (logo, NRR if SaaS) - North-star metric specific to business Format: small table, MoM and YoY columns when relevant, RED/GREEN signal. ## Step 2: Narrative — Wins (3-5 max) For each win: - 1 sentence what happened - 1 sentence quantified impact - 1 sentence what you learned ## Step 3: Narrative — Losses & Lowlights (2-4 max) Do NOT skip. Do NOT euphemize. Do NOT spin. Each loss: - What happened (1 sentence) - Quantified impact (1 sentence) - What you're doing about it (1 sentence) - What signal it's giving the company (1 sentence) If there are no real losses to report, you are not running fast enough — call it out. ## Step 4: Strategic Updates (1-2 paragraphs) - Pivot, repositioning, or expansion under consideration - Customer / market signals shaping the next quarter ## Step 5: Team - Hires made this month (named, role) - Departures (named, role, reason — be honest) - Open roles ## Step 6: Asks (1-3 specific, named) - Intro requests (named investor / customer / talent) - Hire help (specific role, specific source needed) - Advice (specific question) Asks must be: - Specific (not "we're always looking for great engineers") - Actionable (the investor knows what to do) - Easy to fulfill (one click for them, big win for you) ## Step 7: One-Liner P.S. A single line at the bottom: thanks for support, hire-now signal, link to recent press, or a personal moment of gratitude. # OUTPUT CONTRACT ## Subject Line (≤ 60 chars, includes month + 1 KPI signal) ## Greeting (1 line) ## TL;DR (3 sentences max) ## KPI Dashboard (table) ## Wins ## Losses & Lowlights ## Strategic Updates ## Team ## Asks (numbered, 1-3) ## Sign-off + P.S. # CONSTRAINTS - DO NOT exceed 900 words. - DO NOT skip the Losses section. Empty losses = founder not being honest. - DO NOT use vague language: "strong," "great," "on track" without numbers. - DO NOT include vanity metrics ("users signed up") without conversion to value. - DO use small specific asks; vague asks get vague responses. - DO write in first person plural ("we" not "the company"). - IF runway < 9 months, lead with that fact. - ALWAYS include a P.S. line.
User Message
Write a monthly investor update letter for the following. **Company name & stage**: {&{COMPANY_AND_STAGE}} **Month being reported**: {&{REPORTING_MONTH}} **Founder name & role**: {&{FOUNDER_INFO}} **KPI numbers (with MoM)**: {&{KPI_DATA}} **Cash, burn, runway**: {&{CASH_DATA}} **Headcount & hiring**: {&{HEADCOUNT_DATA}} **Wins this month**: {&{WINS}} **Losses & challenges this month**: {&{LOSSES}} **Strategic updates / shifts**: {&{STRATEGIC_UPDATES}} **Specific asks (intros, hires, advice)**: {&{ASKS}} **Investor list character** (formal / casual / mixed): {&{INVESTOR_TONE}} Produce the full investor update per your output contract.

About this prompt

## Why founder updates fail Most founder investor updates are one of two things: a victory lap (everything is great, we're crushing it!) or a confessional (here's everything wrong, please help). Investors stop opening both. The first is performative; the second is exhausting. The format that actually works — the one used by every YC alum who has raised a follow-on without effort — is candid, tight, structured, and ends with specific asks. ## What this prompt does differently It enforces the **canonical YC investor-update structure**: KPI dashboard with consistent metrics MoM, 3-5 quantified wins, 2-4 honest losses (NOT euphemized), strategic updates, team changes, and 1-3 specific asks (intros, hires, advice). Every section is calibrated for the investor reader who skims 30+ updates a month. The killer feature is the **Losses & Lowlights** section. The prompt refuses to let founders skip it. "If you have no real losses, you're not running fast enough" — that's the principle. Investors trust founders who deliver bad news early; they discount founders who only report wins. ## The asks engineering Most founder asks are vague ("we're always hiring engineers" or "if you know any customers..."). Investors can't act on these. The prompt forces 1-3 specific, named, actionable asks — "Intro to Sarah Lee at Acme Co re: their data team's tooling needs" or "Looking for a senior backend engineer with payments experience; warm intro to anyone at Stripe." These asks generate 5-10x more investor activity. ## Pro tips - Send on the same day each month — investors learn to expect it - Keep the KPI table identical month over month; switching metrics signals you're hiding something - Always include the P.S. — that's what gets read first when forwarded - Use short subject lines that include a KPI signal: "NewCo April update — $1.2M MRR (+11%)" ## Who should use this - Pre-seed through Series C founders sending monthly updates - Founder chiefs of staff drafting on behalf of CEO - Investors writing portfolio LP updates - Operators preparing to fundraise next quarter (start the cadence 4 months ahead)

When to use this prompt

  • check_circleMonthly investor updates for pre-seed through Series C founders
  • check_circleDrafting on behalf of the CEO when chief of staff owns IR cadence
  • check_circleEstablishing investor-update cadence 4 months before next fundraise

Example output

smart_toySample response
A 600-900 word email with KPI-signal subject line, TL;DR, MoM KPI dashboard, 3-5 quantified wins, 2-4 honest losses, strategic updates, team section, 1-3 specific named asks, and P.S. line.
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.