Verified against Claude · 2026-08-07
Write a monthly investor update that gets replies, not silence
Turns raw metrics and notes into a concise investor update — headline numbers first, honest lowlights included, and asks specific enough to actually act on within seconds of opening the email.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are drafting a monthly investor update in the format investors actually read to the end — headline numbers first, honest lowlights included, specific asks only.
CONTEXT
Company: Triagely
Period: July 2026
Key metrics, with trend vs. last period: MRR $58k (up 9% MoM), 9 paying clinics (up from 7), churn: 0
Highlights: Signed our first multi-clinic regional group (5 locations); average wait-to-be-seen down to 19min from 41min at flagship pilot
Lowlights or challenges: Onboarding the 5-location group is taking 3x longer than expected due to their legacy EHR export format
Specific asks, if any: An intro to anyone who has sold into a regional urgent care group with 20+ locations before
HEADLINE METRICS
Open with a one-line list of the 1-2 headline metrics from MRR $58k (up 9% MoM), 9 paying clinics (up from 7), churn: 0, stated as numbers with trend (e.g. "MRR: $58k, up 9% MoM"). No adjective may substitute for a number that already exists in the input.
HIGHLIGHTS
Write Highlights as specific, verifiable facts from Signed our first multi-clinic regional group (5 locations); average wait-to-be-seen down to 19min from 41min at flagship pilot — cut anything that's just momentum language ("strong month," "great traction") without a concrete fact backing it up. A highlight without a fact attached is a claim, not evidence.
LOWLIGHTS
Write Lowlights/Challenges honestly from Onboarding the 5-location group is taking 3x longer than expected due to their legacy EHR export format. Do not soften a real problem into something that reads like a highlight, and do not omit this section even if it feels uncomfortable to send — an update with no lowlights ever is a specific pattern investors recognize, and not a flattering one.
ASKS
If An intro to anyone who has sold into a regional urgent care group with 20+ locations before is given, write each ask as one sentence naming exactly who or what is needed and by when. Rewrite a vague ask like "any intros welcome" into something answerable in under a minute, or drop it entirely if it truly can't be made specific.
OUTPUT FORMAT
Ready-to-send email. Headline metrics as a one-line list at the very top, then Highlights, Lowlights, and Asks as short sections, under 300 words total.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
This follows the widely-used YC-style investor update format, built around the fact that investors skim dozens of these emails and decide in seconds whether to read past the first line — a headline metric with trend gives them that decision instantly, where a narrative opener makes them dig for it before they know if it's worth the time. Including real lowlights is a trust signal, not a weakness: investors who've watched many portfolio companies pattern-match 'no bad news, ever' as a red flag, since it usually means the founder either isn't tracking problems closely enough to notice them or isn't disclosing the ones they do notice — and both are worse signals than the problem itself would be. A specific, dated ask is what actually converts a skimmed email into a reply — a vague ask like 'any intros welcome' asks the reader to do the work of figuring out what to do with it, and that extra step is exactly where most asks quietly die unanswered in an inbox instead of getting forwarded to the one contact who could actually help. Capping the whole email under 300 words is also load-bearing rather than a style preference: an investor reading a fund's worth of monthly updates back to back has a real, finite budget of attention per company, and an update that respects that budget gets read fully far more often than a longer, more thorough one that gets skimmed for the first paragraph and abandoned.
What you get back
Subject: Triagely — July 2026 update MRR: $58k, up 9% MoM. Paying clinics: 9, up from 7. Churn: 0. Highlights: Signed our first multi-location regional group (5 clinics at once). Cut average wait-to-be-seen at our flagship pilot from 41min to 19min. Lowlights: Onboarding the 5-location group is running 3x slower than planned — their legacy EHR export format needs a custom mapping we're building now. Ask: Would love an intro to anyone who's sold software into a 20+ location regional urgent care group before — happy to send a one-pager. Thanks for the continued support.
Verified against
Claude Sonnet 5 · 2026-08-07
ChatGPT GPT-5.1 · 2026-08-04
Changelog
- 2026-08-07 — Initial publish, verified against Claude Sonnet 5 and ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE
