# A placement-agent deal pack for introductions and follow-up Canonical: https://opendataroom.com/guides/placement-agent-deal-pack Updated: 2026-10-17 Keep each mandate’s approved materials, version date and follow-up questions together. A distinct recipient connection helps separate requests across concurrent deals. ## How OpenDataRoom helps Market: Placement agents, Fundraisers, Fund managers Keep each mandate’s approved materials, version date and follow-up questions together. Keep source documents organised in drops, like folders, and select named packs for each audience. OpenDataRoom manages access and request records; the recipient uses their own AI for analysis. Current AI tools return extracted text, not complete original files. - [Named recipients and separate packs](/guides/separate-packs-per-audience): Choose who can connect. Prepare separate packs when people are allowed to see different documents. - [MCP request ledger](/guides/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](/guides/time-limited-ai-access): Choose a review window and stop future requests when it ends. Previously retrieved copies cannot be recalled. ### Workflow impact 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. ### Bring these documents - Approved fund overview.pdf - Mandate and disclosure note.docx - Follow-up questions.txt ### Prompt for your own compatible AI Using only this approved pack, keep each mandate’s approved materials, version date and follow-up questions together. Start with this source question: What can this recipient review before a diligence invitation? Cite the file and passage. Distinguish supplied facts, assumptions, missing evidence and contrary evidence. Do not infer human reading or investment intent from request records. Try the fictional source question on this page and check the cited evidence. To use your own documents, check compatibility and join the waiting list; private access is by invitation. ## Frequently asked questions ### 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. ## Fictional example documents These are invented teaching documents, not customer evidence. ### 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. ## A source question What can this recipient review before a diligence invitation? Illustrative answer: 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. ## 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 ledger can support a factual timeline of server requests through a named connection. It does not prove who typed a question, establish a contractual introduction fee or show investment intent. Retain the underlying mandate and correspondence separately. ## Sources and further reading ## Related workflows - https://opendataroom.com/guides/placement-agent-material-approval-index - https://opendataroom.com/guides/conference-fundraising-follow-up - https://opendataroom.com/guides/lp-manager-diligence-pack 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. Admission is by invitation. Join the waiting list: https://opendataroom.com/signup Check compatibility and the separate public service-information sample: https://opendataroom.com/compatibility ## Try the fictional example https://opendataroom.com/example-demo.html?example=placement-agent-deal-pack