Skip to content

For CFO & finance teams

The deliverable is the explanation.

The gap between the numbers and the story costs credibility.

Request a demoSee the FP&A studio
  • The pack is finished the night before the meeting, every month
  • Variance commentary is written by whoever has time, not whoever owns the line
  • Last month's explanation is not visible while writing this month's
  • The forecast is a spreadsheet only one person can safely open

Symptoms

Signs the monthly loop is broken

  • The pack is finished the night before the meeting, every month
  • Variance commentary is written by whoever has time, not whoever owns the line
  • Last month's explanation is not visible while writing this month's
  • The forecast is a spreadsheet only one person can safely open
  • Nobody can reproduce how the last forecast reached its number

The playbook

Four months to a loop that runs itself

  1. Get actuals in as cited spreads

    Whether they come from the ledger export or a subsidiary's PDF, land them as spreads with sources. One truth for the month, traceable.

  2. Set the threshold, honestly

    Decide what a material variance is — and then only explain those. A pack that explains everything explains nothing.

  3. Put the note on the line, and give it an owner

    The person who owns the budget line writes the driver note. When the figures later move, the note flags itself as possibly stale instead of silently misleading the next reader.

  4. Make the forecast reproducible

    State the assumptions as assumptions. A scenario anyone can re-run is worth more than a precise one nobody can audit.

What you use

The surfaces an in-house team lives in

  • Budgets, isolated

    Plan data kept structurally apart from actuals, so a budget can never be analysed as though it happened.

  • Threshold variance

    Only the lines outside your band ask for an explanation. The pack gets shorter and more useful.

  • Driver notes that age visibly

    Notes carry an author and a date, and flag drift when the underlying figures change after they were written.

  • Rolling forecast

    Scenarios built from stated assumptions, comparable months later because the assumptions are recorded.

  • Ratios on the same data

    Liquidity, leverage and efficiency computed from the same spreads the pack is built on.

  • A weekly rhythm underneath

    Between closes, actions with owners keep the follow-ups from becoming next month's surprises.

What good looks like

Four closes in

The meeting starts from the variance list rather than from a page-turn through the whole pack.

Every line outside the band has a name and a sentence next to it, written by the person accountable for it, before the meeting.

  • The pack assembles from the record, not from a night of copying
  • Last month's story is visible while writing this month's
  • The forecast can be re-run by someone else
  • Group companies can each hold their own workspace under one deployment
FP&A · Budget vs actual · Tir
  • Revenue180,000196,400+9.1%
  • Gross margin34.0%35.3%+1.3 pp
  • Payroll42,00047,800+13.8%
  • Marketing12,0008,900−25.8%
Variances outside the threshold ask for a driver note.

For finance teams

  • Does this replace our ERP?
    No. It sits above the ledger: actuals come in as spreads, the analysis and the narrative live here, and the versioned API lets your other systems read the same figures.
  • We have several subsidiaries. How does that work?
    Each entity can be its own workspace on one deployment — separate data boundaries, seats and catalogues — or several entities can live as clients inside a group workspace. Both patterns are in use.

Bring your hardest engagement to the demo

We will walk your own workflow, not a scripted one — and tell you plainly where the platform does not fit yet.

Request a demoSee pricing