OpenDataRoomYour files, put to work
A placement-agent deal pack for introductions and follow-up
Keep each mandate’s approved materials, version date and follow-up questions together.
A distinct recipient connection helps separate requests across concurrent deals.
Updated 17 October 2026 · OpenDataRoom · Fictional worked example
Your workflow at a glance
- Who it’s for
- Placement agents, Fundraisers, Fund managers
- The task
- Keep each mandate’s approved materials, version date and follow-up questions together
- Bring these materials
- Approved fund overview.pdfMandate and disclosure note.docxFollow-up questions.txt
A fictional situation Fictional example: Brook Fund overview, approved for this demonstration introduction. A target fund size is described, not a completed raise.
How OpenDataRoom helps
The difference in your workflow
A mandate-specific investor handover and follow-up list. Keep the selected evidence available through one authorised connection instead of assembling another set of attachments for each question.
Keep the source documents organised in a drop, like a folder. Create named packs for different audiences, approve their access and let each recipient use their own AI. OpenDataRoom manages access and request records; the recipient’s AI performs the analysis.
- Named recipients and separate packs ↗
Choose who can connect. Prepare separate packs when people are allowed to see different documents.
- MCP request ledger ↗
Review requests received through an authorised connection and what the service prepared, without claiming visibility into the full conversation.
- Access deadlines and revocation ↗
Choose a review window and stop future requests when it ends. Previously retrieved copies cannot be recalled.
A fictional example, shown one step at a time. No files are uploaded and no email or AI call is made.
01Choose the useful files
Start with the evidence for this question.
Prepare the approved versions of Approved fund overview.pdf, Mandate and disclosure note.docx, Follow-up questions.txt. Check the readable text and leave unrelated material out.
Selected for this example · 3 documents
02Choose who gets access
Your pack. Your permission.
Use it with your own AI or invite a named recipient. Set a useful deadline. If people may see different documents, prepare separate packs.
- Recipient
- alex@example.com
- Example access window
- 24 hours
- Scope
- Only this selected pack
Verify email · approve access
Illustrative settings. No invitation is sent.
03Connect the recipient’s AI
Connect once. Choose approved packs.
Add OpenDataRoom in a compatible AI app’s connector settings and complete authorisation. A reusable connection lists only the packs you explicitly approve. Sending a URL into ordinary chat does not install the connection.
Example connection address
https://example.invalid/mcp/your-pack- Open connector settings.
- Add the real address from your pack.
- Complete authorisation.
The address shown here is deliberately inactive.
04Ask the question
Let the source material do useful work.
The recipient decides what to ask. Their AI can list, search and read the approved text; OpenDataRoom supplies access, not the AI model. The current tools return extracted text, not complete original files. Check the preparation report for material they cannot represent.
What can this recipient review before a diligence invitation?
Your ready-to-use prompt
05Check the answer
An answer you can trace back.
Ask for the source file and passage. Compare the result with the originals and keep assumptions or missing evidence visible.
Only the approved overview and strategy material in this example. Negotiated terms and investor identities are excluded. The target size is not evidence of capital raised.
Open the source. Check the wording, date and conditions.
06See what was requested
A clearer handover and follow-up.
Review the requests received through the authorised connection. Investigate gaps, offer a clarification or end future access when the task is finished.
The record shows requests and prepared responses. It does not show the full chat or prove someone read an answer.
Look inside the example Fictional
These are invented teaching documents. The example demonstrates a workflow, not customer evidence or a verified outcome.
Read the 3 example sources
Approved fund overview.pdf
Fictional Brook Fund overview, approved for this demonstration introduction. A target fund size is described, not a completed raise.
Mandate and disclosure note.docx
Example sharing scope: approved overview and strategy summary only. Negotiated terms and investor identities are excluded.
Follow-up questions.txt
Questions outstanding: strategy capacity, team responsibilities and evidence supporting the track-record presentation.
More context for this workflow
Keep mandates separate when documents arrive on your phone
Save the authorised WhatsApp or email attachment to Files or Downloads first. Name the drop for the mandate and date; check the disclosure note before selecting the introduction pack. There is no direct chat or mailbox ingestion.
Keep your working notes private while you prepare an introduction
Store meeting notes, contact preferences, mandate criteria and your own deal analysis as supported files in a private drop. Create a working pack for your own AI with only the notes needed for that task. Ask it to compare a deal against recorded criteria, cite the notes and flag missing or outdated information. OpenDataRoom supplies the selected material; your chosen AI performs the comparison. Review its conclusions yourself. Create a separate investor-facing pack that excludes internal thinking and contact lists. Approving your own AI does not approve other recipients. Hosted AI access requires a separately approved copy our service can decrypt; the AI provider receives retrieved content. Use only contact information you are authorised to hold and share.
The useful detail
Questions about this workflow
What to prepare, how access works and what to expect from the result.
Does a request prove my introduction earned a fee?
No. Keep the mandate and correspondence separately. The ledger can support a timeline of server-visible requests, but cannot establish causation, contractual entitlement or investment intent.
Should I share negotiated terms with every introduction?
No. The fictional disclosure note excludes negotiated terms and investor identities. Prepare a further diligence pack only after the responsible person approves that audience.
Can I use my own notes to compare contacts with deals without sharing those notes with investors?
Yes. Keep your notes in a private drop and select them for a working pack approved for your own AI. Ask for comparisons based on recorded criteria, with citations and uncertainties. Create a separate recipient pack containing only approved deal materials; exclude your contact list, private assessments and negotiation notes. Check the file selection before approving access. This is a document-supported workflow with your chosen AI, not an automated CRM, suitability assessment or outreach service.
How does the recipient connect, and who gets access?
Choose your own AI or invite the intended email recipient. For a private invitation, the recipient verifies the authorised email and completes the required approval flow, then adds the connection in a compatible AI app’s settings. Forwarding an invitation alone does not authorise a different email. Permission covers the selected pack; create separate packs when audiences may see different documents.
Can I keep the files and end someone’s access?
Your wallet contains source drops, like folders. Each named pack shares selected files or passages from one drop. The source drop and its access packs have separate deadlines. You can keep the source until its displayed retention deadline while ending a recipient’s future access. Choose a sharing window, revoke it earlier when needed, and approve an extension deliberately. Expiry cannot recall material that an AI app or recipient has already retrieved.
What happens when I update or remove a file?
After you review and accept a drop update, fresh authorised requests receive the current versions of files already selected for their packs. This does not force an AI to fetch the files again or refresh its existing chat context. New files do not join those packs automatically. Review changed selected passages explicitly. Removing a file or its permission stops future retrieval, and access-change notices are queued for affected recipients. Provider acceptance is not proof of inbox delivery. This cannot erase content already retrieved.
What if my files or AI app are not supported?
Check the compatibility guide and try the public service-information sample first. An app must support the required MCP connection and authorisation; pasting a URL into ordinary chat does not install it. Use supported text-based files and inspect the preparation report. Originals are retained in encrypted storage, but the current AI tools return extracted text, not complete original files. Charts, images and layout are not faithfully delivered by those tools. Image-only scans and standalone images are refused; no OCR, audio transcription or spreadsheet recalculation is provided. Current pilot limits are listed on the pricing page.
What information is recorded about use of the pack?
The ledger records requests received by the service, authorised connection references, requested source information and preparation outcomes. Recipients can also deliberately submit a request, comment or note after approving the exact text. The owner sees that message, the verified connection identity and time in Recipient inbox for up to 90 days, unless deleted sooner. Received does not mean read or answered; no agent or automatic research is started. It does not record the entire AI conversation. Search text is supplied by the AI and may differ from the human question. An AI can reuse retrieved material without making another request. Literal search can miss relevant material; neither a search nor a file request proves that the AI reviewed the entire pack. Owners can investigate no-match searches before deciding whether to clarify wording, repair extraction or add information. A no-match result alone is not proof that a document is missing.
Who can read my files in the hosted connection?
Private-library file names and contents are encrypted in the browser with your wallet key. A hosted AI connection uses a separate access copy that you approve and that the service can decrypt for authorised retrieval. The receiving AI gets the content it retrieves and applies its own data policies. An optional desktop connector can decrypt locally, but it requires installation and is not a universal mobile connection. Review the security and compatibility pages before choosing a route.
Now it’s your turn
Try the whole journey.
Keep mandates separate when documents arrive on your phone. Start with the fictional documents on this page; no login is needed. For a real AI connection, try the separate public service-information sample before requesting private access.
Choose the example files and move through the connection, question, answer and ledger. The tour advances every four seconds; tap a step or Pause to take over.
No real upload, email or AI call is made. The connection in this fictional demo is inactive.
The six static steps and example sources above remain available if the interactive tour cannot load.