# Prepare a conference fundraising pack for mobile follow-up Canonical: https://opendataroom.com/guides/conference-fundraising-follow-up Updated: 2026-10-17 Prepare a small approved pack before the meeting so follow-up does not depend on finding attachments on your phone. Share the invitation privately with the intended email recipient. ## How OpenDataRoom helps Market: Fundraisers, Placement agents, Accelerators, Investors Prepare a small approved pack before the meeting so follow-up does not depend on finding attachments on your phone. 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 meeting follow-up brief backed by prepared research. Keep the selected evidence available through one authorised connection instead of assembling another set of attachments for each question. ### Bring these documents - Meeting brief.pdf - Approved talking points.docx - Follow-up evidence requests.txt ### Prompt for your own compatible AI Using only this approved pack, prepare a small approved pack before the meeting so follow-up does not depend on finding attachments on your phone. Start with this source question: What evidence is needed for the next conversation? 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. Check the AI response against the originals, then use the reviewed result in your own meeting, report or handover. ## Frequently asked questions ### What would this change in my workflow? A meeting follow-up brief backed by prepared research. Keep the selected evidence available through one authorised connection instead of assembling another set of attachments for each question. The practical task is to prepare a small approved pack before the meeting so follow-up does not depend on finding attachments on your phone. ### Which documents should I include? For the example on this page, start with Meeting brief.pdf, Approved talking points.docx, Follow-up evidence requests.txt. Use the approved versions relevant to the task and include source dates, definitions and any known gaps. Review the prepared text and disclosure scope before sharing. The fictional examples illustrate the structure; OpenDataRoom does not supply or verify your underlying research. ### Can the ledger tell me whether an investor intends to proceed? It can show the tool requests received through an authorised connection, the source references requested and the response preparation outcomes. Those records can inform a useful clarification or follow-up. They do not prove that the investor personally read a result, that an AI relied on it, or that an investment decision was made. An AI app may issue several requests automatically. ### 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. ### Meeting brief.pdf Fictional conference introduction covers one strategy and the team’s stated responsibilities. ### Approved talking points.docx Example talking points distinguish target outcomes from historical results. No guaranteed returns are stated. ### Follow-up evidence requests.txt Requested after the meeting: dated strategy evidence and an explanation of capacity assumptions. ## A source question What evidence is needed for the next conversation? Illustrative answer: The example follow-up asks for dated strategy evidence and capacity assumptions. Talking points alone do not establish performance. A shared invitation still requires the intended recipient’s verification. QR requests and sender-approval enhancements are separate release work; do not assume a public code grants access. ## Sources and further reading ## Related workflows - https://opendataroom.com/guides/placement-agent-deal-pack - https://opendataroom.com/guides/accelerator-demo-day-pack 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=conference-fundraising-follow-up