Follow one forecast from setup to the decision in front of your board, sponsor, or investors.
A short, illustrative tour of the CFO/controller workflow: shape the forecast, trace the change, then see the evidence a reviewer leaves behind. The sample is simulated and contains no customer data.
One artifact spine · two finance paths
The same evidence helps a private company decide what happens next.
Start with the operating reality, then carry one traceable version through the review conversation. Private, PE-backed, public, and pre-IPO teams can use the same spine without forcing every company into an earnings-guidance workflow.
- 01Rolling cash-flow visibility. Use the six-month net-cash view and runway to keep liquidity visible as the plan moves.
- 02Operating-plan decisions. Fork base, upside, and downside scenarios, then compare ending cash and runway before committing.
- 03Board and sponsor reporting. Bring a traceable version into the board packet or sponsor update; the sample includes a downside case forked for that packet.
- 01Reconcile the close file and preserve the source assumption behind the change.
- 02Review the low, mid, and high investor-facing ranges against the forecast spine.
- 03Leave a named reviewer and approval status before the range reaches the call.
Shared traceability
Assumptions → versions → review → approvals
The illustrative record connects the receivables assumption update to immutable version and audit evidence, review history, and named approvals. CSV and Excel are the current import surfaces; connectors remain roadmap, not a live claim in this walkthrough.
Three artifacts your finance team can read together.
Bring the questions this tour surfaced.
Tell us about your close window, reviewer chain, and current data source.
Talk to the team