To choose a data room for your first raise, check three things: what your investors and your company need it to meet, the sharing work it has to handle and what you're committing to if the raise takes longer than planned. Get written evidence where it matters, then try the recipient's side with test files. If a must-have question is still unanswered, leave it open and hold off on subscribing.
Most first raises start small: a deck and a few good conversations. Then one investor asks for your accounts while another wants to dig into everything. Choosing a tool gets a lot easier when you start from that next review.
Use the free selection worksheet below to keep your requirements, your checks and the open questions in one place. It works whether you're comparing dedicated data rooms or the tools your company already uses.
Work out what the tool has to do
Before you open any trials, ask the people who will sign off on how you share whether they need specific controls, contract terms or independent certification. That could be an investor's security reviewer, whoever makes the call at your company or an advisor handling part of the process.
Sort each requirement into one of three groups:
- Required now: this has to be in place before the review can start.
- Useful now: it would make the review easier, but you have a workable alternative.
- Possible later: come back to it when the process grows or changes.
For example, separate access for two investor teams might be required now. A certain report format might be useful. Room for several deals at once can probably wait. Where each item lands depends on your review.
You don't have to pay for a data room on day one. Venture firm CRV describes simpler sharing setups as an option for early fundraising. That's one investor's practical advice, so check what your own reviewers expect. If your current tool is in the running, the shared-folder decision guide helps you test whether it fits. CRV's fundraising preparation guide.
Ask six questions that change the answer
| Question | What to write down | How to check |
|---|---|---|
| Who needs a different view? | Audiences needing different files, permissions or timing | Try two recipient views with test files |
| What certification is required? | The exact report, certificate, policy or contract answer requested | Get current evidence for this service and ask whoever set the requirement to review it |
| What happens when a file changes? | How a replacement reaches recipients and what happens to old versions | Replace a sample, reopen the recipient view, check the history |
| What will the busy weeks need? | Rooms at once, people preparing files, outside recipients, storage, file sizes | Check trial and paid allowances and how each limit is counted |
| What help is there? | Support channel, hours and any promised response time | Read the terms or ask for it in writing |
| What happens when the raise ends? | Cancellation, ongoing access, getting files back, deletion | Read the terms and try retrieving a small sample |
Write where each answer came from next to the question. "Seen in the trial", "provider documentation" and "waiting to hear back" tell you different things. A polished demo can show you how something works. It can't answer an open contract question.
What does the security evidence actually cover?
The UK's National Cyber Security Center advises weighing a cloud provider's evidence against how sensitive your information is and what service you're buying. Evidence about the hosting platform underneath doesn't, on its own, show how the application provider runs its service. Check the scope, relevance and date with whoever owns that requirement. NCSC guidance on choosing a cloud provider.
Be specific when you ask for independent certification. ISO/IEC 27001 is about an information security management system, so ask which organization and services a certificate covers. SOC reports are audit reports about controls, so ask for the right report and the period it covers. A logo, or a casual claim that a product follows good practice, answers neither question. ISO's ISO/IEC 27001 overview, AICPA's SOC services overview.
Aurora does not currently have a SOC 2 report or ISO/IEC 27001 certification. If either is a must for your process, note that gap before you consider Aurora. Testing how access behaves is still useful, but it can't stand in for missing independent certification. Small raises can involve sensitive information and demanding reviewers too.
Count the review you expect to run
Count the audiences that need their own selection and permissions. Not every investor contact needs a new room. Two people may share one view, while two teams may need different ones. Then picture the busiest realistic moment in the review, and include the people keeping the files up to date.
Say a founder and a colleague are preparing a raise. Two investor teams are reviewing now: one needs a financial pack, the other is ready for a different set of documents. A third investor may start reviewing next month.
| What the example needs | What the founder writes down |
|---|---|
| Two different recipient views now | Test two separately set-up rooms |
| Maybe a third view at the same time later | Confirm the next plan up and its cost before then |
| Both colleagues will maintain documents | Check internal user allowances apart from guest access |
| Files will change during the review | Replace a file and check what recipients see |
| A security requirement isn't confirmed yet | Hold the decision until the right person answers |
This is a planning exercise. It doesn't show that any provider has passed these checks. The founder can accept a limit that works today and write down what would trigger a fresh decision.
Keep preparing documents separate from choosing the tool. Once you've picked how you'll share, the investor follow-up guide helps you turn an investor's questions into a useful pack.
Compare what you're signing up for, and how you'd leave
Ask for the total cost over the period you expect to use the service, plus a longer case. For example, compare a three-month review with a raise that runs twelve months. Write down minimum terms, what's included, any taxes or extra charges and what happens if you need another room or more storage.
An annual price can look cheaper per month while locking you into a bigger commitment. Read the payment and cancellation terms before you treat those numbers as the same thing. Only the person allowed to spend company money should approve a paid change.
Ask what you can get back before and after you cancel or the trial ends. Name the things you'd need: original documents, folder structure, earlier versions or activity records. What's available, and in what format, can vary. Test a small sample and note anything missing. One export may not contain everything.
Access controls can't pull back copies someone has already downloaded. Agree how recipients should handle those copies when the review ends. Your company's own retention and confidentiality obligations still need someone to own them.
Use a trial to answer one real question
Keep the test small enough to finish in a sitting. Pick one question, such as: "Can these two audiences get different selections while both see the current version of a shared document?" Use made-up material and test accounts you control until the service is approved for real files.
In an Aurora trial, a useful first task looks like this:
- Create one library and add a few sample documents.
- Set up two rooms with different selections, with one document in both.
- Check each room as the recipient it's meant for and confirm which files show. Check download permissions separately.
- Replace the shared document in the library, reopen or refresh both recipient views and look at the version history.
- Write down what happened, what's still open and whether someone else needs to review the result.
Access groups can narrow access inside a room when members need different permissions. They can't reveal a document you left out of that room. The short trial above can start with two simple audience selections, and you can add group checks if your review needs them.
Aurora's 30-day trial needs no card and includes one organization, unlimited libraries, two rooms, three internal users, 25 external users and 10 GB of storage. Paid plans come with different allowances, so check the current pricing and allowances before moving from trial to subscription. This task tests a small slice of how the product works. It doesn't assess every security control, export need or contract condition.
Leave with a decision you can explain
Fill in the selection worksheet for each serious candidate. Keep must-have gaps visible, give each open question an owner and write down why your choice fits the next stage of the raise. If your current setup already does the job, keeping it is a perfectly good answer.
To see how Aurora approaches this, look at how its data rooms work. If it makes your shortlist, start a free trial and run the two-audience task above.
Data room selection worksheet
Free to use and adapt. Keep your completed worksheet in your own project files.
Download Worksheet (.md)Use one copy per candidate, including your current file-sharing setup if it's in the running. This worksheet is free, with no sign-up. Keep completed copies private if they hold sensitive requirements or provider details.
Describe the next review
- Process and expected review period:
- Who is filling this in:
- Who approves how you share:
- Who can approve spending on a subscription:
- Audiences needing their own selection or permissions now:
- Extra audiences that might review at the same time:
- People maintaining files, and outside recipients:
- Expected storage and largest sample file:
- Date you want to decide by:
Requirements and evidence
Importance: Required now, Useful now or Possible later. Status: Met, Unresolved or Does not meet. Keep a required item unresolved until the person who decides has enough evidence. A nice feature can't make up for a missing must-have.
| Requirement | Importance | Evidence needed | Evidence found and date | Status | Who decides / next step |
|---|---|---|---|---|---|
| Separate recipient selections and permissions | Recipient-view test | ||||
| Required independent certification | The report or certificate, with scope and period | ||||
| Data location or contract conditions, if required | Written terms or confirmation | ||||
| What happens on replacement and to old versions | Replace a sample and check what recipients see | ||||
| Room, user and storage allowances for busy weeks | Trial and proposed paid-plan terms | ||||
| Support availability | Published terms or written confirmation | ||||
| Getting files back and deletion when the review ends | Terms plus a sample retrieval | ||||
| Anything else this review needs |
Evidence can be a document reference with the passage and scope that matter, or a dated note of what you saw with a sample file. Record who assessed it. Keep provider statements, independent reports and your own trial results labelled as what they are. File sharing working smoothly doesn't tick off a security requirement.
Run one recipient test
- Question the trial has to answer:
- Sample files, and why they're safe to use:
- Audience A should see:
- Audience B should see:
- File both audiences share:
- Download permission you expect for each audience:
- What the recipients actually saw:
- What happened after replacing the shared file and reopening both views:
- What you saw of earlier versions:
- Test date, account types and plan used:
- Anything unresolved, and the next step:
Pick only the checks that answer your question. This rehearses how sharing works and doesn't assess security. If a file shows up where it shouldn't, stop adding real files and sort it out first.
Compare the commitment
Use the provider's actual offer and terms. Fill in both your expected review period and a longer case, and don't compare a monthly equivalent with a total payment as if they were the same.
| Item | Expected review period | Longer case |
|---|---|---|
| Number of months | ||
| Plan and billing frequency | ||
| Minimum commitment and when you pay | ||
| Included rooms / internal users / external users / storage | ||
| Expected extra charges and taxes, if any | ||
| Total expected cost under those terms | ||
| Change that would need a new paid decision | ||
| Who can approve that change |
Don't assume trial allowances carry over to a paid plan. Ask how limits are counted and whether adding capacity changes the commitment. Leave unknown costs blank and flag them to confirm.
Check how you'd leave before subscribing
| What you'd need at exit | Available? | Format or method tested | Deadline or condition | Still to ask |
|---|---|---|---|---|
| Original documents | ||||
| Folder structure | ||||
| Earlier versions, if needed | ||||
| Activity records, if needed | ||||
| Other process records |
- Cancellation steps and when they take effect:
- Access after canceling or after the trial ends:
- Provider's deletion arrangements, and where that's stated:
- Who owns your company's retention decision:
- What to tell recipients who already downloaded copies:
These rows are questions to ask. They don't claim any product offers every export or retention option.
Record the decision
- Candidate and plan:
- Decision: Go ahead / Hold for answers / Keep current setup / Choose another candidate.
- Why it fits the next review:
- Must-have gaps still open:
- Limits you've accepted, and who accepted them:
- What would trigger a new decision:
- Approver and date (fill in only after real approval):
The worked example in the guide uses two investor audiences now and a possible third later. Swap in your own process. No room count, certification requirement or retention period suits everyone.
