Built for the way finance
actually works.
Same system, three lenses — each tuned to what your role needs to ship today. None of this is a separate product or a separate licence.
Built for the way finance
actually works.
Same system, three lenses — each tuned to what your role needs to ship today.
Board-ready numbers with an audit trail — zero rebuilds.
- ✓Every figure saved is recorded
- ✓Defensible forecasts
- ✓Board-grade governance
Planning as a continuous system — not a monthly cycle.
- ✓Scenarios update instantly
- ✓No model rebuilds
- ✓Driver-based multi-entity rollups
Know your runway instantly — no need to ask finance.
- ✓Real-time clarity
- ✓Decisions in minutes
- ✓Self-serve burn + runway
Three seats
The same numbers, three questions.
CFO
The question a CFO gets asked in the board room is not “what is the number” but “where did it come from”. NashOS answers that without a follow-up email: every figure saved is recorded with who saved it and when, report lines expand from rollup to leaf, and most edits committed from a Nash draft card keep the value before and after.
FP&A
Most FP&A time is spent rebuilding rather than analysing. Because drivers, entities and currencies share one computation path, a change to hire pace or price recomputes runway, burn and EBITDA in place — so the scenario conversation happens in the meeting rather than the week after it.
Founder
Runway is the number founders check most and wait for longest. Here it is computed from the same ledger finance uses, so a self-serve answer and the board deck cannot drift apart.
FAQ
Role-specific questions
Do we need a separate licence per role?▾
No. The three views are the same system, with what each person sees governed by their access. The pricing page sets out the three tiers and what each includes.
Can a founder see runway without touching the finance model?▾
Yes. Read access to computed figures such as cash, burn and runway is separate from the ability to draft or commit changes, so self-serve visibility does not create edit risk.
How do we stop analysts committing changes they shouldn't?▾
By role and scope. The built-in analyst and viewer roles do not hold the write-data permission, so the server refuses any figure they try to save, and Nash does not prepare a card that changes figures for them. A dimension scope limits which entities, departments and products a planner or administrator can write to, and a held close-run load waits for an administrator. No change is written without a user explicitly confirming it, and the audit trail records who confirmed it.
Will our auditors accept this?▾
Most edits committed from a Nash draft card carry their before value, after value, actor and timestamp; grid saves and bulk loads are recorded per save with who and when; report lines expand from rollup to leaf; and administrators can filter the audit log and export it as CSV. Confirm scope with your own auditor before relying on it for a specific standard.
Which seat are you in?
Tell us your role and we'll run the walkthrough from that lens rather than a generic tour.