
CFOs, Founders & Finance Teams
See how your plan holds up before you commit.
Forecast from your actuals. Compare hiring, pricing, and slower-growth scenarios to see their effect on earnings, cash, and runway.
A hiring plan. A price increase. A slower quarter. Understand what each would mean for the business.
Explore an example
See the impact before you decide.
Raise prices. Plan your next hires. Switch scenarios and see what changes in revenue, EBITDA, and cash.
Explore the sample data, inspect assumptions, and compare the scenarios side by side.
Loading interactive scenarios…
CFOs, Founders & Finance Teams
What does your plan depend on?
- 01
Start from actual performance
Reconcile actuals, explain recent movements, and build a monthly forecast with explicit growth, cost, and cash-timing assumptions.
- 02
Try the alternatives
Change hiring dates, prices, or growth assumptions. Compare each scenario with the same base forecast.
- 03
Examine the downside
Model slower sales or higher costs. See their effect on earnings and when cash falls below your chosen threshold.
- 04
Understand the difference
Follow each scenario’s results back to the changed assumptions and underlying data.
- 05
Bring the trade-offs into review
Compare scenarios in charts and editable workbooks, with saved versions your team can revisit.
Example workflow
If growth slows, can we still afford the hires?
- 01
Ground the forecast
Start with actuals, opening cash, payment timing, and the planned payroll.
- 02
Change the conditions
Reduce the revenue-growth assumption and compare the planned hires with a later start.
- 03
Find the constraint
Compare monthly earnings, cash balances, and runway across the hiring options.
- 04
Review the choice
Bring the comparison and its assumptions into the management discussion.
For review
The hiring options, their effect on cash, and the assumptions each depends on.
Every team, every engagement.
Client datastays under control.
Ask about securityYou’re working with client ledgers and confidential data rooms. SecondState keeps each engagement separate, every change reviewable, and every answer traceable.

EU or US hosting
Your data stays in the region you choose. The two deployments are separate, and nothing is copied between them.
One project per engagement
Files and analysis are scoped to a project. Nothing is visible outside it unless you share it.
Every figure traced
Answers link to the rows and pages behind them, so a reviewer can check any number.
Nothing changes without you
Data transformations are validated and shown to you before they’re used. Destructive actions need approval.
Full revision history
Workbooks keep every revision. Inspect what changed or restore an earlier version.
Activity on record
Project activity and agent work are logged, so you can see who did what and when.