Threads and delivery
Imports investor correspondence, preserves source context and can deliver founder-reviewed email drafts as replies or new threads.
Connect Gmail, Google Calendar and Granola to the native RoundOS Data Room. Correspondence, meetings, notes and room activity become one current evidence trail.
Named room session · pages 8–12
30 minutes · Riley Brooks and Alex Morgan
Reply context attached to Northline opportunity
Usage durability and repeatable acquisition
Include model attention, retention question and the latest meeting note.
The round does not happen inside one app. RoundOS keeps each source distinct, preserves its evidence and joins it at the investor, opportunity and work-item level.
Imports investor correspondence, preserves source context and can deliver founder-reviewed email drafts as replies or new threads.
Imports events as fundraising context and can prepare reviewed calendar drafts when a concrete time and attendee exist.
Brings call notes into workspace memory so decisions, asks and relationship changes do not disappear after the meeting.
Named sessions, page attention and return visits already live in RoundOS. No connector or export sits between the signal and the round.
Named room session · pages 8–12
30 minutes · Riley Brooks and Alex Morgan
Reply context attached to Northline opportunity
Usage durability and repeatable acquisition
Include model attention, retention question and the latest meeting note.
A room session remains a room session. A Gmail reply remains a thread. A Granola note remains a meeting note. RoundOS combines the context without erasing provenance.

RoundOS turns imported correspondence into relationship evidence. When Operator prepares a message, it can use the recipient’s actual thread context and reply there only when the delivery match is confident.
Inbound questions become touchpoints and evidence
Drafts keep source context separate from delivery intent
Founder review remains between preparation and send
A scheduled meeting and its notes solve different parts of the same problem. RoundOS uses both as evidence for what the founder should do next.
Events identify the meeting, its attendees and timing. They can surface prep work before the call and make follow-up actionable after the event passes.
Imported notes preserve questions, commitments, diligence steps and stage evidence from the conversation, without asking the founder to rewrite the call into the CRM.

The room is part of RoundOS. Named opens, page attention and return sessions enter the same round context directly, so Operator can use the original signal, not a delayed dashboard export.
The room event stays attached to the investor, the relevant material and the next move it helps justify.
An investor returns to the model, a partner meeting lands on Thursday, and the last note identifies the unresolved retention question. RoundOS can assemble those facts into one prep brief or draft instead of three disconnected notifications.
Room return adds attention evidence
Calendar adds the meeting deadline
Meeting note supplies the decision focus
Operator prepares the useful move with all three attached

Connect Google for Gmail and Calendar, connect Granola for meeting notes, and create or attach the Data Room already inside RoundOS.
Gmail, Google Calendar and Granola. RoundOS Data Room activity is native to the product and does not require a separate connection.
Yes. The Google connection supports Gmail, Calendar or both, so you can add the sources that fit the workspace.
No. Operator can prepare a useful draft, but delivery is a separate action. The message is only marked sent after the delivery flow succeeds.
Calendar provides attendee and timing context. Granola contributes the substance of the meeting: questions, decisions, commitments and follow-up evidence.
RoundOS tracks connector state and can flag sources that need reauthorization before new activity can be monitored again.

Bring email, meetings, notes and native Data Room activity into the same current round.