When an investor asks for more detail, send a short answer to each question, the current document behind it and a plain note about anything you're still checking. First agree who will read the material and what decision it has to support. That keeps the preparation to a list your team can actually finish.
This usually happens right after a pitch that went well. One person asks for retention figures, another wants the forecast, someone else would like to speak to a customer. Your files probably hold all three answers, mixed in with personal information, half-finished assumptions and internal discussion. Sending the nearest folder is quicker, and it's also how the wrong file goes out.
Ask what the next review needs
Before you build a pack, find out which questions need answers, who will review them and by when. A short message does it:
To prepare the follow-up, could you confirm the questions you'd like the material to answer and who will review it? I'll then point you to the documents that answer them and flag anything still being checked.
How much to send varies. Y Combinator's seed fundraising guide recommends keeping early preparation in proportion and having a clear summary and deck. OpenVC's data-room guide separates an initial investment review from deeper diligence. A stage label still won't tell you what to disclose, so agree the scope for your own conversation.
If one approved document answers the request and the way you already share files suits the recipients, use it. Separate rooms start to help when several investors need different collections, permissions or updates.
Match each question to evidence
Start a simple request log. Put the investor's question in the first column, then find the smallest set of documents that answers it accurately. Keep the context, caveats and unfavorable findings that belong with the answer.
| Investor question | What might answer it | Check before sharing |
|---|---|---|
| Are customers still using the product? | A dated retention summary with definitions and the period covered | Who's included, exclusions and gaps; whether names or individual records are needed |
| What assumptions drive the forecast? | The current forecast and a short assumptions note | Actuals kept apart from projections; the version; whether they need the workbook |
| Can we speak to a customer? | A proposed reference and the topics they can cover | The customer's permission and an agreed introduction before you pass on contact details |
| How is the company owned? | A current ownership summary, with supporting records if asked | Accuracy and scope, checked by your finance or legal lead |
| What supports this technical claim? | Test results or technical documentation | Test conditions and limits explained; sensitive details reviewed with their owner |
These are possible answers to specific questions, and your company may need different evidence. If you're pre-revenue, describe the evidence you have and its limits plainly.
Give each request an owner and a status: ready to share, needs clarification, being checked or awaiting permission. If the requested document doesn't exist, say so and agree what would answer the question. An empty folder leaves the investor guessing.
Work through a three-question follow-up
A small software company is preparing for a seed round. After a product discussion, an investor asks for retention evidence, the hiring assumptions behind the forecast and a customer reference.
The founder and operations lead take the requests one at a time:
- Retention: The operations lead prepares a summary by customer start month. It states the reporting period, how an active customer is defined and which accounts are left out. They check it against the source before approving it. The first question can be answered without a list of individual customer contacts.
- Hiring assumptions: The finance lead confirms the current forecast and explains when proposed roles enter the model. Before sharing the workbook, they check hidden sheets, comments and links to internal files. The assumptions note separates planned hires from existing commitments.
- Customer reference: The founder asks the customer whether they're willing to take part. The request log says "Awaiting permission" and names who is following up. It stays open until the introduction is agreed or the investor accepts another way to review the evidence.
The follow-up that goes out has two approved answers and a clear status for the third. The investor knows what's available now and when to expect the rest. The team is left with three small tasks, each with a name next to it.
Make the pack easy to read
Add a short contents note that links each question to its file. A reviewer should see why a document is there before opening it. Give the reporting period or version, and mention any limit that changes how the document should be read.
For example:
Retention: the customer-retention summary covers the period we discussed and includes its definitions. Hiring: the current forecast comes with the assumptions note. Customer reference: we're asking for permission now and will update you on the agreed date.
Open the copies you're actually sharing. A filename can look right while the workbook still holds an old scenario, or an attachment carries unrelated correspondence. Check that the note, the document and the claims in your current pitch all say the same thing.
For formal diligence, work from the investor's request list and advice on your transaction. Cooley GO's sample VC diligence list is framed as preparation before a financing closes. It can help you organize records, but it can't tell you which documents your transaction needs or when to disclose them. Settle legal and confidentiality questions, including any required disclosures, with your advisor.
Keep a second investor's review separate
Next week another investor may ask something different. Log their requests separately, but keep one approved source for each shared document. If the forecast changes, that change needs a clear owner, version and explanation everywhere the forecast is used.
Before you replace shared material, check what changed and who it affects. A revised model may mean the pitch or the assumptions note needs correcting too. Tell recipients which document changed and what to look at again. Downloaded copies stay as they were, so point people to the current shared version.
Decide download access request by request. One reviewer may need the workbook for analysis, while another request can be answered by viewing. View-only access can't prevent every kind of copying, such as screenshots or photos of the screen. Withdrawing access can't retrieve a file that has already been downloaded.
Set it up in Aurora
Keep the approved fundraising files once in a library. Create a room for each investor audience and pick the files that audience should get. Keep your request log as a separate team document.
If people within one investor team need different access, create access groups for them and adjust individual permissions where needed. A group can only see documents already in its room. Set viewing and downloading to match the review you agreed.
When you have an approved revision, replace the file in the library. Rooms sharing that document show the current version when participants reopen or refresh, and earlier versions stay in the library's history. Look at the sharing settings again whenever the document or the audience changes.
Prepare one follow-up today
Take the next real question in your inbox and put it in the free worksheet below: the answer, supporting file, recipient, approver and next action. Send it to the colleague preparing the evidence. You're ready to reply when every request has either an approved answer or a named next step.
To try the sharing setup, take the product tour or start a 30-day free trial. Use harmless sample files to create one library and two investor rooms. Give each room a different selection, then check what each recipient can see. The trial includes one organization, unlimited libraries, two rooms, three internal users, 25 external users and 10 GB of storage, with no card required.
Before you send invitations, run through the external sharing checklist. If figures change during the review, read how to keep shared documents current.
Investor follow-up worksheet
Free to use and adapt. Keep your completed worksheet in your own project files.
Download Worksheet (.md)Use one copy per investor review. Fill the first row with a real question, then ask the person who owns the evidence to check it. Keep this working copy inside your team, and write a separate contents note for the investor from the approved answers.
Agree the review
- Company or project:
- Investor and named recipients:
- Decision or next meeting this supports:
- Questions received on:
- Agreed response date:
- Person coordinating the response:
- Person approving what gets shared:
Connect questions to files
| Request ID and question | Answer and supporting file | Period or version | Owner and approver | Recipient and view or download | Status and next action |
|---|---|---|---|---|---|
| R1: Enter the investor's exact question | Add the answer, file location and any limits that matter | Add the reporting period or version | Name both people if different | Note who receives this answer and how | Note status, person and agreed date |
| R2: | |||||
| R3: |
Possible statuses: ready to share, needs clarification, being checked, awaiting permission, shared or further question. A missing document needs an explanation and an agreed response. "Shared" means the material was sent or made available. It doesn't mean the investor accepted the answer.
Worked row (example)
| Field | Example entry |
|---|---|
| Question | Which customers kept using the product during the period discussed? |
| Supporting file | Customer-retention summary, with the period, definitions and exclusions written into the file |
| Owner | Operations lead |
| Approver | Founder handling the investor response |
| Sharing decision | Named investor team; check whether a summary answers the question before sharing underlying records |
| Status | Being checked; operations lead to reconcile the summary with source records by the agreed date |
Check before sharing
- Check that the answer addresses the request and keeps its context, limits and unfavorable findings.
- Open the actual files. Check reporting periods, definitions, hidden sheets, comments, attachments and internal links.
- Confirm the recipients, who can approve sharing, and any customer permission or advisor review needed.
- Note the approved file and version, then check its room selection and viewing or downloading permissions.
- Tell the recipient what's ready and give a clear next step for each open request.
Write the contents note
For [question], see [file and reporting period/version]. It covers [scope] with [important limitation]. [Open item] is being checked by [responsible person], with an update due [agreed date]. Please confirm whether this answers the question or which further detail is needed.
When something changes
Note the replacement version, what changed, who owns the source and which recipients are affected. Check whether the pitch, forecast or other supporting files also need correcting. Update the approved source, review access and send the explanation through the agreed channel. Track any follow-up you need separately from file activity.
This worksheet organizes the response. The transaction team and its advisors decide required disclosures and confidentiality arrangements. Changing room access can't recall copies that were already downloaded.
