Variance analysis
Actuals vs plan, line by line, with the explanation already drafted – and every number traceable to source.
By team · Finance
Variance, forecast, and audit-ready packets.
A co-worker for the work finance does every week – without giving up control of the numbers.
§01 · Weekly work
The work finance already does – every week, every close.
Recurring deliverables where the shape is fixed and the numbers must be defensible. A co-worker handles the assembly; the analyst keeps the judgement.
Forecast review packet
Rolled-up forecast view with the assumptions, drivers, and last-period deltas prepped for the FP&A meeting.
Audit-ready summaries
Every line item tied back to the underlying ledger entry, with the supporting evidence linked.
Month-end close prep
The repeatable checklist of reconciliations, accruals, and review tasks – assembled, flagged, ready for sign-off.
§02 · Co-worker
A co-worker that reads the ledger, drafts, waits for sign-off.
Connects to the source systems finance already runs on. Drafts the work. Nothing leaves the approval gate until a human approves.
RIY-FIN-01
Connected
NetSuite / SAP
BI tool
Sheets
Docs
Finance co-worker
read·draft·approve
Variance brief drafted
Forecast review prepped
Audit packet queued
§03 · Engines
The agent engines doing the work.
For finance, the analysis runs deep, the dashboard tells the story, and the simulation tests the scenario.
Data Analysis Agent
Reads the ledger and BI extracts, runs the variance walk, drafts the explanation – with every number traced to source.
Analytical · Cited
Simulation Agent
Stress-tests the forecast: drivers up 10%, demand softening, FX move. Prepares the "what if" your reviewer will ask about.
Predictive · What-if
Dashboard Agent
Refreshes the forecast and variance dashboards on the rhythm finance already follows – weekly, period-end, board cycle.
Visual · Recurring
§04 · Sample workflow
The monthly variance walk that landed Monday 9am.
A real engagement pattern – what the team asked for, what the co-worker did, what got approved, and what landed before the leadership review.
What was asked
"Get me the monthly variance walk without taking out Tuesday."
A senior FP&A analyst was losing a full Tuesday each close to assembling the variance walk – pulling actuals from NetSuite, plan numbers from the model in Sheets, commentary from the BU leaders' Slack threads, and stitching the narrative.
What the co-worker did
Read the ledger. Drafted the walk. Flagged the lines that moved.
Over the weekend, the co-worker pulled actuals, joined them to the plan, ran the variance at the line-item level, drafted the explanation against the BU commentary it could find, and flagged the four lines that breached the materiality threshold for review.
What got approved
The analyst reviewed Monday morning, corrected one line, approved.
The analyst opened the draft at 8:15am, corrected the commentary on a one-time accrual the model had read as ongoing, approved it. Nothing left the approval gate until the analyst said yes.
What shipped
In the CFO's hands at 9:00am, structured and traceable.
An implementation-led engagement that took four weeks to map and ship – including the security review and the rollback plan. Tuesday is back. The workflow runs every close.
§05 · Get started
Bring the one weekly thing your finance team repeats.
We'll map it with you, identify the minimum context, and ship a working version in 2—4 weeks – your ledger, your tools, your sign-off.