How to share an interactive financial model with investors
To share an interactive financial model, prepare clearly named scenarios and export a standalone HTML copy. The recipient can open it in a browser, change assumptions, and explore results without installing spreadsheet software. In Startup Model Builder, the HTML export includes all scenarios; each recipient's changes remain local and do not synchronize with your original workspace.
In this guide
Prepare the version you actually want someone to inspect
Start by naming the base case and each alternative so a recipient can tell what they mean. Base, slower acquisition, and delayed financing are easier to interpret than copy 2 and final final. Review the assumptions behind each case before creating the file.
Check every scenario for information you intend to share. The HTML export contains all of them, including their model inputs. A scenario that is not selected on screen can still travel with the file. If you want a narrower sharing copy, create and review that copy deliberately before export.
Give the accompanying explanation a specific purpose: which scenario to open first, which assumptions matter to the discussion, and what period the forecast covers. You do not need to turn the email into a second article; a clear starting point is enough.
Choose HTML, JSON, or CSV for the job
The three formats serve different purposes in Startup Model Builder. Choose based on what the recipient needs to do, rather than treating every export as a complete copy of the same thing.
| Format | What it carries | Use it for |
|---|---|---|
| HTML | All scenarios, editable controls, and the forecast engine | An interactive model someone can open in a browser |
| JSON | The active model's assumptions | Backup or import into the builder |
| CSV | The selected report | Reviewing report values or preparing presentation tables |
Open your model in Startup Model Builder, review the scenarios, and use Download HTML to create the interactive sharing copy.
Check the downloaded file before sending it
Open the downloaded HTML file itself in a browser. Confirm the model name, scenario names, and key assumptions match the version you intended to export. Switch scenarios and change an input in that copy to confirm the recipient experience makes sense.
The portable file contains the app and forecast engine and is designed to work offline. It does not need a server to calculate the model. A recipient opens the downloaded file in a browser rather than relying on a static attachment preview to run the controls.
If you use a funding amount or an illustrative assumption in a presentation, check the same number in the exported file. This catches a simple but consequential mismatch: revising the model after making the deck without generating a new sharing copy.
- Verify the starting scenario and forecast period.
- Open each included scenario and check its assumptions.
- Change a known driver and confirm the relevant result updates.
- Try the file offline and confirm the controls still work.
- Keep a clearly named copy of exactly what you send.
Explain what happens when the recipient edits it
An investor can explore a different acquisition rate, renewal assumption, or hiring date in their own copy. Those edits do not update your online workspace or another recipient's file. The export is a portable model, not a live shared document.
If you want to discuss the changed assumptions, ask the recipient to identify the scenario and inputs or return a newly downloaded HTML copy. Be explicit about which version you are reviewing. A model filename and a short note about the changes can prevent a discussion about two different forecasts.
Treat the export as an editable copy of the included assumptions. The exported Studio does not provide permissions for selectively locking those inputs. If the recipient only needs report values, send the appropriate CSV instead of the interactive model.
Use the model as supporting material for the pitch
Keep the deck focused on the financial story and use the model for the assumptions behind it. The HTML file can accompany the presentation, but the builder does not automatically create slides or turn the file into a hosted investor portal. The pitch-deck guide suggests what to summarize.
Save a separate JSON backup of important active-model assumptions as you work. The online Studio persists in browser storage, so it is sensible to keep an exported copy before clearing site data or changing computers. Use HTML when you need the complete set of scenarios in one portable file.
After the conversation, update your operating plan deliberately. A recipient's scenario is useful input, but it should not silently replace your base case. Review why the assumptions changed and keep the old version for comparison.
Related questions
Does the recipient need an account?
No. The standalone HTML export can be opened and used in a browser without an account. It carries the model and its calculation code rather than requiring access to your browser workspace.
Will changing my online model update a file I already sent?
No. The file contains the assumptions at the time of export. Generate and send a new copy when you want someone to review a revised model, and identify which version replaces the previous one.