How to Share a Financial Model With Investors Securely

Sharing a financial model during a fundraising process is one of the moments where founders lose control without realising it. The wrong file version, an exposed internal scenario or an assumption that contradicts the pitch deck can quietly damage investor confidence before a single question is asked.

TL;DR

• Freeze a review copy before sharing — never send the live working model.
• Write a short assumptions note so investors do not reverse-engineer your logic.
• Reconcile the model to the deck and cap table before any file leaves the company.
• Restrict access to named reviewers, not to open links.
• Log every version sent and keep a record of any corrections made during the raise.

Fundraising moves quickly, but a financial model is a high-stakes document. It encodes your assumptions about revenue, costs, hiring and runway. When it contradicts other materials, or when an investor receives an uncontrolled copy, confidence erodes. This guide explains the practical steps for sharing a model securely — from preparing the file to managing updates when numbers change.

Why financial model sharing goes wrong

Most problems do not come from malicious actors. They come from urgency. A founder sends the working Excel file from their desktop because the investor asked for it that morning. The file includes an internal bear-case scenario, a hidden tab with individual salary data and a set of formulas that reference a revenue definition different from the one in the deck.

The investor does not know which version is current. They can see the hidden sheet. The numbers in the deck do not match the totals in the model.

None of this is intentional. All of it is avoidable.

1. Prepare the review copy

Before sending anything, create a separate review copy that is distinct from the working model.

Remove tabs, scenarios, salary data and supplier costs that are not relevant to the question the investor is trying to answer. If the investor wants to understand your revenue trajectory, they do not need a detailed hiring plan by department. Include it only when asked and only after a deliberate decision.

Protect sheets that contain formulas but not inputs. This prevents accidental edits while keeping the model readable. If you share a PDF for initial review, make clear that an editable version is available under NDA.

2. Write an assumptions note

A financial model without an assumptions note is a puzzle. Investors will make their own assumptions to fill the gaps, and those assumptions may be more pessimistic than yours.

Write a one-page document that covers:

• Revenue recognition basis (booked, billed, collected or ARR)
• The reporting period and the "as of" date
• How headcount costs are calculated
• What the base case and downside case assume
• Any items that are estimates rather than contracted values

This note does not need to be long. It needs to be clear. A reviewer who understands your assumptions can engage with your model. One who does not will challenge every number.

3. Reconcile to other materials

Check every figure that appears in both the model and another document before sharing. A mismatch that an investor catches undermines more than just the number — it raises questions about process discipline.

4. Control who receives it

Different investors should not automatically receive the same level of access. A lead investor at term sheet stage may see a detailed model. An early-stage interested party may see a summary version.

Set access by named recipient rather than shared link. A shared link can be forwarded and cannot be reliably revoked once used. Named access can be tracked and removed if the relationship does not progress.

Before sending, test the access path yourself using a different account. Check that the file opens correctly, that the correct sheets are visible and that no unintended content is accessible. A setting that appears locked from an administrator view can still be open to recipients with direct links inherited from a parent folder.

A platform that combines document hosting with access tracking can simplify this. SendNow supports controlled document sharing with engagement records — useful when you need to see whether a model has actually been reviewed before a follow-up call. Choose any platform after confirming its documented behaviour matches your security and compliance requirements.

Editorial disclosure: SendNow has a commercial relationship with this publication.

5. Run the five-step release process

1. Freeze the review version — save a named copy and lock the working model from further edits until review is complete.
2. Strip unrelated content — remove hidden sheets, internal scenarios and salary data not relevant to the investor's question.
3. Attach the assumptions note — include it in the same folder as the model, not as a separate email attachment.
4. Assign named access — invite specific individuals rather than generating an open link.
5. Log the release — record who received it, what version number it is, the date and any accompanying documents.

Keep this log in a shared register that your finance and legal contacts can see. If you send a correction later, the log tells you who received the original and what they need to be told.

6. A realistic example

A SaaS company at Series A is preparing for investor due diligence. Their working model has five scenarios, a tab with individual employee salaries and three historical periods.

For the investor review, they create a copy with one scenario (base case only), remove the salary tab and limit the history to 24 months. They write a one-page assumptions note that defines MRR, explains the churn calculation and identifies the reporting period.

They upload both files to a named folder in their data room, assign access to two people at the lead fund and one external adviser. They run a test using a personal email address to confirm the files are readable and the assumptions note is visible.

Three weeks later, the investor asks about the downside case. The team prepares a second controlled version — with the downside scenario only — records it as version 2 in the log and sends it to the same three recipients. The original base-case copy remains on record and is not replaced.

7. Managing updates during the raise

Fundraising processes often span two or three months. Numbers change. Forecast assumptions get refined. A new month closes.

Decide in advance how you will handle updates:

• Which items will refresh at each month end (actuals, cash position)
• Which items will only change after explicit approval (revenue recognition method, scenario definitions)
• Which items will not change during the current raise (base case inputs, cap table entries)

When you publish an update, name it clearly with a version number and date. Send a brief note to existing reviewers identifying what changed and why. Do not silently replace a file and expect investors to notice.

If a correction affects a figure already cited in a written Q&A response, update the Q&A log and tell the recipient. A disclosed correction is far less damaging than an undisclosed one discovered during closing.

8. Common mistakes

• Sending the master file. Create a review copy. Never share the file that is actively being edited.
• Unlabelled scenarios. If your model has multiple tabs, investors will read all of them. Label each one clearly or remove the ones not relevant to the review.
• Mismatched numbers. If the deck says £4.2m ARR and the model shows £4.1m, explain the difference in the assumptions note. Do not leave it for the investor to ask.
• No version control. If you have sent multiple versions without tracking them, you cannot tell an investor which is current. Start a log even if it is a simple spreadsheet.
• Ignoring download activity. If a model is downloaded multiple times by multiple accounts, investigate before assuming it is routine. A forwarded file can reach unintended recipients.

9. Final pre-release checklist

• Review copy is saved separately from the working model
• Hidden sheets, salary data and unrelated scenarios are removed
• Assumptions note is attached with clear definitions and reporting period
• All figures reconcile to the investor deck and cap table
• Access is set to named recipients — no open links
• A test access check was completed using a separate account
• The release is logged with version number, date and recipient list
• A process exists for handling corrections and version updates

Frequently asked questions### Should I send an editable financial model or a PDF?

Start with a PDF for initial review. Share an editable version only when the investor is in active diligence and has signed an NDA. Clearly label which version of the model the PDF was generated from.

How do I handle it if the investor asks for a scenario I have not prepared?+

Treat it as a new scoping decision. Prepare the scenario under your normal internal review process, not under time pressure. Record the request, the date and the version you eventually share.

The investor has already downloaded the file. Can I revoke access?+

Revoking platform access prevents future downloads but cannot recover a file already downloaded. This is why the release decision matters — once a file is out, assume it will be retained. Only share what you are comfortable with the investor keeping.

How do I prevent the model from being shared internally at the fund?+

You cannot prevent internal sharing at a fund once a file is downloaded. Address this through the NDA, through access controls that limit what is initially shared, and by building a relationship where sensitive information is handled professionally.

Do I need legal review before sharing the financial model?+

Get legal input on the NDA and on any forward-looking statements before the first external share. Your legal adviser can also flag whether your model contains information that has specific disclosure obligations in your jurisdiction.

Final takeaway

Sharing a financial model with investors securely is primarily a discipline problem, not a technology problem. The habits that matter are: preparing a clean review copy, writing clear assumptions, reconciling to other materials, controlling access deliberately and logging every release. Technology can support all of these steps, but it cannot substitute for the decisions that precede them.

Related articles

• How to Share SaaS Metrics With Investors
• How to Run a Data Room for a Rolling Close
• Fundraising Data Room File Naming Guide