How to Humanize an Investor Update After ChatGPT
ChatGPT investor updates hide burn behind adjectives and skip runway math. Lock cash, monthly burn, and months left the way you would say them on a call. Humanize narrative once—not the numbers.
Investor updates are where founders earn trust—or spend it. ChatGPT drafts "strong progress" and "exciting momentum" while avoiding the numbers investors actually open the email for: cash, burn, runway, and what changed since last month.
If you would not say the runway aloud on a partner call, do not publish the AI paragraph that implies it.
Human Writes is the voice pass after burn and runway are locked the way you would say them. You supply figures from finance—not optimism from a language model.
Related: board update script, all-hands talking points, work reports and status updates. Hub: best practices for humanizing AI content.
What investors scan first
| They look for | AI usually hides |
|---|---|
| Cash and months of runway | "Well capitalized" |
| Net burn trend | "Investing in growth" |
| Revenue or usage delta | "Strong engagement" |
| One real risk | Risk in paragraph five |
| Clear ask | "Happy to chat anytime" |
Updates that read like fundraising decks without numbers get archived unread.
Lock burn and runway before ChatGPT
Build a finance fact block from your CFO, bookkeeper, or bank export:
| Row | Example (your truth) | Say-it-aloud version |
|---|---|---|
| Cash | $842k as of Aug 31 | "Eight-forty-two in the bank" |
| Monthly net burn | $118k August | "About one-eighteen net burn" |
| Runway | 7.1 months at current burn | "Seven months at this burn" |
| Revenue / MRR | $42k MRR, +6% MoM | "Forty-two K MRR, up six percent" |
| Headcount | 14 FTE, 2 open roles | Exact counts |
| Win | One customer or ship | Named if public |
| Risk | One yellow item | Owner + date |
| Ask | Intro, hire, bridge | Specific |
Never round runway up to "about a year" unless the math works. [VERIFY WITH FINANCE] beats a hallucinated eighteen months.
Prompt: "Investor update email from this table. Put cash and runway in the first screen. One risk before wins. No new metrics."
Investor update vs board script vs all-hands
| Artifact | Channel | Numbers | Ask |
|---|---|---|---|
| Investor update | Email / portal | Full runway | Intro, hire, note |
| Board script | Live meeting | Curated | Decision |
| All-hands | Company | Selective | Employee action |
Do not paste the investor email into an all-hands without redacting.
Typical investor update skeleton
- TL;DR — runway + one line on delta since last update
- Metrics — cash, burn, revenue, usage (table OK)
- Highlights — one or two wins with proof
- Lowlights — honest risk paragraph
- Product / roadmap — ships next 30–60 days
- Team — hires, departures if material
- Ask — one specific request
| Section | Humanize? | Why |
|---|---|---|
| Dollar amounts, dates | No | Legal and trust |
| Customer names under NDA | Follow counsel | — |
| TL;DR and risk prose | One pass | AI hedges too much |
| Ask paragraph | Light pass | Keep names exact |
Before and after
AI investor update opening:
We are pleased to share continued momentum across the business. The team remains focused on executing our vision and delivering value to customers while maintaining a disciplined approach to growth.
After finance block + one humanize pass:
As of August 31 we have $842k cash—seven months runway at $118k net burn. MRR is $42k (+6% MoM). We missed the enterprise pilot close (risk: single-threaded deal); consumer activation improved after we shipped onboarding v2 Tuesday. Ask: intro to a Head of People who has scaled eng teams from 15→40.
Second version is forwardable without a translation call.
Workflow
- Pull numbers from finance the same day you send.
- Compare to last month's update; note deltas in TL;DR.
- Draft wins and risks from fact block—no invented logos.
- One Human Writes pass on narrative sections.
- Founder re-reads every dollar and month count.
- Send on a consistent cadence (monthly is common).
- Log replies; follow up on asks personally.
For spoken board meetings, see board update scripts. For customer-facing metrics language, see customer QBRs.
What not to do
- Imply runway you have not calculated.
- Hide a layoff or miss in "product updates" section.
- Humanize until burn changes by ten thousand dollars.
- Paste cap table or bank credentials into a consumer chatbot.
- Send the same update to angels and the whole mailing list without redacting.
Bottom line
Investor updates win when burn and runway appear the way you would say them on a call, plus one honest risk and one clear ask. Human Writes polishes prose after finance signs off on the fact block.
Paste stiff TL;DR paragraphs on Human Writes when every dollar matches the spreadsheet you would screen-share.