Open a specific financing conversation.
Use the progress that matters to that fund and ask for the next discussion, without disguising it as a general newsletter.
Operator · Investor updates
Updates with a reason to reply.
RoundOS prepares a recipient-specific draft from the progress, questions and relationship context already inside your round, then leaves the edit and send decision with you.
One recipient, one relevant update, one concrete ask.
Investor timelineThe reason for writing now
RoundOS
RB
Riley Brooks
Partner · Northline Ventures
Relationship timeline
Returned to the financial model
Named room session · 6m 42s · pages 8–12
Asked for weekly usage and retention
Inbound email · request remains open
Partner call completed
Calendar · 31 minutes · follow-up promised
Opened the room for the first time
Tracked link · pitch deck and model viewed
Round contextDraft · Riley Brooks
RoundOS
RB
Riley BrooksNorthline Ventures · Gmail reply
Round update: usage, design partners and the retention view
Riley, quick update since our call. Weekly active workspaces grew 18%, and we signed three additional design partners. I also added the retention view you asked about to the room.
The same room link has the current model and the supporting cohort view.
Specific askWould you be open to a 20-minute follow-up next week to walk through the retention pattern?
The update, assembled
Every draft starts with the round and its context.
The useful round facts, the recipient’s last question and the source-backed reason for writing arrive beside the draft. You review the argument before you review the prose.
Current round factsRecipient contextFounder-controlled delivery
The broadcast problem
The monthly update became a forwarding ritual.
A generic note asks every investor to care about the same things. It forgets who asked for retention, who offered an introduction and who has gone quiet. The result is informative. It is rarely actionable.
Context assembly
The draft starts from the live round.
Operator can ground the message in current company and round evidence, then connect it to the recipient’s own thread, room activity and open work. It does not need you to paste the fundraising story into another writing tool first.
01
Current progress and proof from the workspace
02
The investor’s actual questions and prior touchpoints
03
The work worth asking them to do now
Recipient-specific drafts
Same progress. Different reason to care.
A lead fund, a helpful angel and a quiet observer should not receive the same opening line with a different first name. RoundOS prepares each draft against that recipient’s actual relationship context.
Lead fund · asked about retentionWalkthrough ask
Angel · offered partner accessIntro ask
Quiet fund · reopened the roomContextual check-in
One useful ask
The update should create a next move.
The draft is not finished when the news is summarized. It is finished when the recipient can understand what changed and what useful action is being asked of them.
Name the person and why the path fits.
The connector sees a forwardable reason, the target and the context needed for a double opt-in request.
Bring the requested proof back to the table.
Point the investor to the current room material they asked for and propose the smallest sensible next meeting.
Round memory
Every update continues the same investor relationship.
The previous email, held meeting, room return, open request and current work stay on the investor timeline. The next draft can continue that history instead of recreating it from old threads.
Retention asked → model reopened → update prepared
The sequence is preserved as evidence. It explains both the timing of the message and the ask inside it.
Questions
Investor updates, answered.
01How does RoundOS decide what belongs in the draft?
Operator uses current workspace evidence and the recipient’s own relationship context, then prepares a draft when there is a useful move worth making now.
02Can different investors get different versions?
Yes. Each recipient is a separate draft with its own target, evidence, timing and ask. The product avoids duplicating work when those are materially the same.
03Can I edit the message before it goes out?
Yes. Drafts can be reviewed and edited. A message is not marked sent unless the delivery flow succeeds.
04Does it reply in the existing Gmail thread?
When the recipient’s real Gmail thread is known with confidence, the draft can continue it. If that context is uncertain, RoundOS prepares a new thread rather than guessing.
05Is this only for monthly updates?
No. The same workflow can support a milestone, a diligence response, a bridge conversation or a targeted check-in whenever current evidence creates a useful reason to write.
Send what matters
Turn current progress into the next conversation.
Connect the round and review the next recipient-specific draft while the context is still current.
Evidence attached. Founder reviewed. Delivered through Gmail.