Partner · Bessemer Venture Partners
Is the retention line based on logo retention or net revenue retention? The assumption on page 12 looks stronger than the cohort table in the appendix.

Series A adds deeper requests, more stakeholders and weeks of parallel work. Keep the room, the investor state and the follow-through in one system.
Associates run a first pass, partners build conviction, finance checks assumptions and counsel examines the contracts. The room has to distinguish their access and activity without fracturing the story into separate sends.
Keep the deck, cap table, financials, contracts and product evidence in the same ordered room. Update a material once and the existing room links lead reviewers to the current version.

Create room-local access groups such as associate review, partner review and counsel. The names are yours; the access boundary is enforced by the room.
Partner · Bessemer Venture Partners
Is the retention line based on logo retention or net revenue retention? The assumption on page 12 looks stronger than the cohort table in the appendix.
Founder · RoundOS
Net revenue retention. I added the cohort reconciliation below the assumption and linked the source export in the appendix.
A viewer can ask from a material or a rendered page. The founder sees the source context, answers the thread and chooses whether the response belongs to that thread, the originating group or the room.

A room open is not the same as a partner returning to the model. Keep viewers, sessions, pages seen, longest attention and return visits separate, so the process does not collapse into one blended engagement number.
Read the activity at the individual, session and material level. Page detail appears for page-rendered materials, while every supported material still keeps its viewer and session history.
Prepare positioning before outreach.
No next action set.
Nudge connector for status.
Wait two days, then follow up.
Ask about partner walkthrough.
Next action generated from call.
Send customer proof packet.
Weekly usage view prepared.
Room activity, replies, meetings, waiting state and open work remain attached to the investor opportunity. The team can inspect the same evidence without reconstructing it in another status tracker.
Institutional depth should add evidence, not multiply versions of the truth.
Use room-local groups for recurring stakeholder patterns and explicit exceptions where needed.
Material and page context prevent the same diligence question from being answered twice.
An associate session and a partner return are separate signals inside the same fund.
Existing links continue into the current material and preserve the version history.
It is the same product with more structure: deeper sections, room-local access groups, more named stakeholders, heavier use of Q&A and version history, and a shared operating state around the room.
Yes. Set group access, apply individual exceptions, protect entry with the gates the process needs and revoke a link when the conversation ends.
No. They are examples of access-group names a team may create for its own process. The room enforces the permissions assigned to the group.
It keeps diligence questions tied to the room, material or rendered page that created them. Scheduling and relationship conversations can continue through the connected tools the team already uses.
Each stakeholder can receive a named link, so their sessions remain separate while still belonging to the same investor opportunity.

One structured room, named stakeholder context and a shared next move across the team.