Appearance
What is Flowstate
Flowstate puts every dollar of payroll and AI spend on the same ledger as the projects they fund. Stop flying blind. Then stop the leaks.
Engineering organisations have two cost lines that move in opposite directions. Payroll is mostly fixed and slow. AI spend is variable, fast, and almost entirely unattributed. We tie both to the same people, the same projects, the same cost centres — so the CFO and the CTO are looking at one number, not two.
Three pillars
Flowstate is one product organised around three jobs.
| Pillar | What you get | Where to start |
|---|---|---|
| AI Governance | Every prompt, seat and API call attributed to a person, team and project. Provider invoices reconciled. Policy enforced at the request line. | AI Governance overview |
| Workforce Engineering | Headcount, vacancies, contractors and AI agents on one roster. FTE allocations to projects. Restructures modelled in scenarios that don't touch live data. | Workforce overview |
| Finance & Compliance | Cost forecasts that match the books. CapEx and R&D Tax review workflows your auditors actually accept. Variance alerts before quarter-end — not after. | Finance overview |
The point is the integration. AI spend is allocated to the same project a person is allocated to. CapEx claims pull from the same effort data that drives the forecast. Restructures in a scenario re-cost themselves end-to-end before you commit a single change.
What Flowstate models
Five entities form the core roster. Everything else hangs off them.
| Entity | What it represents |
|---|---|
| Employees | Full-time and part-time staff with salaries, team assignments and project allocations. |
| Contractors | External individuals or firms engaged on a rate basis — hourly, daily or monthly. |
| Vacancies | Open positions in the hiring pipeline, with target salary ranges and fill dates. |
| Teams | Organisational units that group people for management and cost attribution. |
| Projects | Work efforts that consume resources, tracked through lifecycle stages with timelines. |
These are connected by allocations — FTE-based assignments that link people to teams and projects. An employee at 0.5 FTE on a team contributes half their capacity (and half their cost) there. Allocations are the spine of every cost calculation in the system.
Live data versus scenarios
Flowstate keeps two layers. Live data is the source of truth — the real org, the real costs, the real bookings. Scenarios are sandboxed copies where you model restructures, hires and budget changes without touching live. Approve the scenario and it merges. Discard it and nothing happened.
You can run a hiring plan, a budget proposal and a re-org in parallel without any of them stepping on each other. See the Scenarios guide for the data model.
Get to your first numbers
Five minutes from signed-up to seeing your own headcount and AI spend on screen. Follow the Quickstart.
Next steps
- Quickstart — connect HRIS, install the Agent, see numbers.
- Domain model — how the entities relate.
- Live data vs scenarios — how what-if planning actually works.
- AI Governance · Workforce · Finance — pick a pillar.