Draft an investor follow-up from the last touchpoint, requested item, new proof, and next ask.
The form starts with an editable founder scenario. Generate the draft as-is, or replace the context with your own thread first.
The follow-ups that work give the investor a concrete reason to re-engage: the thing they asked for, plus one new proof point.
Reference the metric, question or meeting detail they raised. It proves you listened.
A follow-up with fresh news is an update. It gives the investor a reason to move now.
End with a single next step. Let me know your thoughts is not an ask.
The generator turns your structured thread context into an AI draft, checks for unsupported claims and generic phrasing, and rewrites the draft when the review fails.
# core components stage + thread context -> follow-up type asked_for + proof -> one new input ask -> one concrete next step quality review -> pass or rewrite
The output is a first draft, not auto-outreach. You should edit it into your own voice before sending.
RoundOS uses the same structure, but fills context from your real inbox, calendar and notes.
A follow-up without context or proof gives the investor nothing useful to act on.
Long follow-ups get saved for later, which usually means never.
If the next step is not obvious, the investor defaults to inaction.
It is generated from your thread context, then checked for generic investor-email slop before you see it. You still edit the draft before sending.
Most fundraising follow-ups should land around 80-140 words: enough context, one new proof point, and one clear ask.
No. RoundOS drafts from your real context, but every message is reviewed and sent by the founder.