Workforce Engineering

One roster for everyone — and everything — that costs you money to ship software. Employees, contractors, vacancies and AI agents sit in the same plan, allocated to the same teams and projects, costed in the same currency. No more spreadsheet gymnastics to answer "what does this team actually cost".

Most tools tell you the org chart. Flowstate tells you what the org chart is doing this quarter, what it will cost next quarter, and what changes if you move ten people sideways.

What you get

• A single source of truth for employees, contractors, vacancies, teams and AI agents.
• An FTE allocation editor that splits people across teams and projects with a real Gantt, not a colour-coded grid.
• A roadmap that ties projects to drivers and initiatives, with the actual ticket data from your PMS.
• Effort tracking that captures where time really went — manual entry where you need it, PMS sync where you have it.
• Scenarios — sandboxed copies of your plan where you can fire half the org, hire 30 engineers in Lisbon, or move a team to a new cost centre, then compare the results before merging.
• Workforce Analytics for the questions execs actually ask: where are we spending, what is the headcount bridge, what does the labor mix look like next year.

How it fits together

The model is small on purpose. People are allocated to teams. Teams (and individuals) are allocated to projects. Costs flow up — through the cost attribution chain — into team budgets, project budgets, cost centres, and ultimately the Finance pillar.

When you want to change something without breaking live data, you do it in a scenario. When you want to know what changed and who needs to approve it, you use the inbox.

Where to start

If you want to...	Read
Understand the data model	Domain model
Set up cost calculations	Cost attribution
Plan a restructure	Scenarios workflow
Wire in a PMS	Integrations
Move data via API	API reference