Six systems.
One operating model.
Nash is not a chatbot layered over a planning tool. It is six systems sharing one model, one set of dimensions and one audit trail.
Six systems.
One operating model.
Decision System
Understands the business — P&L, Balance Sheet, Cash Flow as one model with variance, drivers, and drill-down to source of truth.
Continuous Planning
Keeps it current — driver-based planning, scenarios, what-ifs and continuous recomputation across the model.
Agentic Execution
Turns intent into action. Ask in plain English; the system plans and drafts, and you confirm and commit.
Audit & Control
Every figure saved is recorded — attributed to its user, with before/after kept on most committed drafts, and role-based control.
Data Foundation
Holds it together — multi-entity, multi-currency, shared dimensions, consistent computation everywhere.
Integrations
Connects Nash to your data — APIs, SFTP, CSV, Excel, validated on every run with full run history.
Together, these systems operate as one — multi-entity, continuously computed, every saved figure recorded. No handoffs. No sync issues. No rebuilds.
Try with your dataHow they fit
Six systems, one write path.
The Decision System holds P&L, Balance Sheet and Cash Flow as one model rather than three reports, so asking why a line moved returns an answer that traces to the transactions that moved it. Continuous Planning keeps that model current — change a headcount assumption and runway, burn and EBITDA update without a rebuild.
Agentic Execution turns intent into action, but it works through the same write path a person does. There is no side channel and no unlogged edit: whatever the agent does is staged, shown, and only then committed.
Audit & Control is what makes that safe to run. Most edits committed from a draft card store their before value, after value, actor and timestamp, grid saves and bulk loads are recorded per save, and nothing the agent proposes reaches the model until a user confirms it.
Underneath, the Data Foundation is multi-entity and multi-currency by construction, so an entity view and a consolidated view are two reads of the same numbers rather than two builds. Integrations connect it to your sources — REST, SFTP, CSV and Excel — validated on every run, with full run history so a bad load is visible before it reaches a report.
FAQ
About the agent
Can the AI change my numbers without me knowing?▾
No. Agent-initiated changes are staged as draft cards, shown with Nash's summary of the change, and most cards show the before value and the after value before anything is written; the commit is an explicit action. Every committed write is attributed and timestamped. The security page sets out what the cards show.
What stops the agent from inventing a figure?▾
The agent reads and writes through the same computation path as the rest of the system rather than generating numbers itself. Figures it reports are drawn from the model, so they match the reports you can open and expand from rollup to leaf.
Who can commit changes?▾
Users whose role holds the write-data permission: planners and administrators by default, while analysts and viewers read and report. A dimension scope limits which entities, departments and products each user can write to. A change Nash proposes is written only when a user who holds the permission for it confirms it, and the audit trail records who confirmed it and when. Consolidation set-up cards and held close-run loads are confirmed by an administrator.
Does it work across multiple entities and currencies?▾
Yes — both are dimensions of the same model, so FX translation and entity roll-ups are applied consistently to planning, reporting and variance alike.
Watch the agent work on your model.
Fifteen minutes, your data, no slides. You'll see a draft raised and committed end to end.