Worksheets

Worksheets is a new feature in Flightpath, currently in available in public beta. You can access it at yourcompanydomain.flightpathfinance.com/worksheets

Usage - Forecasting

Worksheets are best used for creating custom forecasts and metrics. 

Example

Forecasting Software Expenses

The goal here is to forecast your software spend as a function of your employees. The larger your team, the more you pay for their software and tools. 

1. Start by creating a New Worksheet, and give your worksheet a name. Here we go with "Software Forecast"

2. Click on New Metric, and select Forecast (all scenarios) from the sidebar on the right

2. Give your metric a name, and click on the tab Actuals from the top right.

3. From Type of Actuals, select Reference another account. Pick Software & Tools - G&A as your reference . This is the software spend from your Profit and Loss.

4. Click Add Reference, and select Employees (All Teams)

5. Click Add Metric and name it "Software Spend per Employee."

6. Select the Actuals tab and select Formula radio button. We now want to enter a formula to calculate the software spend per employee, so we know 
which number we can use once we begin to forecast the future.

7. You can reference any other row visible on the worksheet by typing a curly bracket or { in the formula bar. Here, we want to divide the Software - G&A by the
number of employees.  

8. Now, we can see that the software spend per employee ranges from 246 in January to 397 in September. Let's use six month average to forecast
the future. Switch over to Forecast tab, and enter a formula mean({software_spend_per_employee,-6,-1})

The formula mean is just another way of saying average, and the -6 and -1 denote that we are interested in a rolling time period from six months ago to last month.
Like this:

9. Finally, to get to our software spending forecast, we need to multiply the number of employees by the newly calculated six month average spend per employee.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us