The Get Started sheet is the core input sheet in Foresight financial models. Many modelers will name this sheet "Assumptions" or "Inputs" or "Key Drivers" or something similar; I choose to name this "Get Started" because I think it's a clearer indication of where to get started in using the model, and the first entry point to understand the key aspects of the model, but feel free to change the name of the sheet to whatever you prefer.
The Get Started sheet is a common convention across all Foresight models, but the content and inputs varies by model. This documentation focuses on its usage in the Standard Financial Model.
How to use
The Get Started sheet is divided into a few sections, and each impact the model in different ways:
- Model Structure. This section contains overall model structural settings, and is detailed in the Inputs section below.
- Revenue Assumptions. This section contains the key inputs for the prebuilt revenue model, and is detailed at Revenues.
- Revenue Model. This section defines the prebuilt options available for the Revenues sheet. You can change the name used to define the business model types; many businesses will modify the prebuilt revenue model and add in custom revenue streams, it is not necessary to change the assumptions here to do that, this is only used to change the prebuilt calculations on the
Revenuessheet. - Balance Sheet. These optional inputs cover revenue recognition and cash collection calculations, depreciation and amortization, debt repayment, corporate income taxes and value-added taxes (VAT), inventory, and valuation. The inputs in this section are explained at the respective links above. The most important input to use is the
Cash on hand, beginning of modelinput, which should reflect cash on hand at the beginning of the first month forecast in the model. While you can detail the opening balance sheet in more detail on the Statements sheet, this provides the most important input for that sheet. Please note, theCash on hand, beginning of modelshould not include any cash to be raised in the forecast period (because that's in the future and will come through theForecastsheet's inputs) but will naturally include any cash on hand resulting from past fundraising efforts (e.g. debt, equity, grants, owner's equity). - Seasonality. This optional section allows you to set positive and negative percentage impacts on a recurring monthly basis that is separate from the growth rates above. The two layer on each other, creating cyclical, seasonal effect by redistributing a year's rate of change over the time period. By default this can be applied to any number forecasted by the Drivers as well as a number of the forecasted items in the Growth, Conversion, and Revenues sections on Revenues and Forecast sheets. This structure is detailed at Seasonality
- Model Checks. This section helps you monitor for potential issues in your use of the model, and may result from model calculations or business viability concerns. Explained at Model Checks.
Inputs
The inputs for each section above are detailed on their respective sheets, except for Model Structure, explained below.
- Company Name This is used in the Legal Disclaimer sheet, which is purely optional, but something many people choose to include in their projections when they provide them to potential investors.
- Base Timescale You can use the model to forecast monthly, quarterly, or annually, and then the model will use that as its base timescale. Many inputs and calculations will adjust automatically, but just be sure to input numbers that reflect the time period you selected. Almost all users choose to use the model on a monthly timescale.
- # of Months in Model. This sets the # of periods in the model. (1 period = 1 month, or 1 quarter, or 1 year, as set in assumption above.) By default this is 72, reducing it will not automatically change the number of periods in the model calculations but it will turn off necessary calculations after the input period. Can be extended if needed.
- Date of first period in model This input is for the last day of the first forecasted period in the model. Best convention is to input the actual last day of that period, although the model timescale will adjust it if not. This sets the timescale used on all the resulting sheets.
- Fiscal year end Defines the end of the fiscal year used in the model. By default it is assumed to be December of the year assumed in the prior input, but this can be changed if your fiscal year end is not a calendar year end.
- Do you want to use relative or absolute dates? The dates above set the start date and fiscal year end used in the timescales, but you can also set here whether you want the primary timescale used for reports and charts to be absolute (e.g. Jan 2021 or 2021) or relative (month 1 or year 1). Does not change model calculations, just how they are presented in certain summaries and reports.
Common Modifications
The sheet is completely open for editing and can be customized by users to handle anything you want to add to the model. The most common modifications include:
- Removing sections that are unnecessary for specific business models. While all sections can be safely ignored it not needed, some people may choose to delete sections permanently unnecessary for their business. For example, businesses not selling physical products or having to deal with Inventory may choose to delete the
Inventoryinputs and calculations on theForecastsheet, and the resulting lines on theStatementsandSummarysheets. People may choose to remove theValuationsection if it will not be used.Debt Repaymentis also optional, and easy to delete from theForecastsheet, although recommendation is still to keep it included in cash plans change. - Replicating the existing Revenue Model. The prebuilt revenue structure works for many business models, but often companies want to expand the prebuilt structure to add in more customer segments or pricing plans than the two prebuilt segments. Often the best choice is to replicate the revenues inputs on
Get Startedand theRevenuessheet to create multiple instances of the revenue calculations, and then link the new revenue calculations into theForecastsheet. That linking process is detailed at How to build custom revenue forecasts in a Foresight base model.
Adding custom revenue streams does not require you to add the assumptions into
Get Started, but is often done by users desiring consistency in model structure and presentation.
Questions, support, or customization help, contact me.
