Appearance
Get started
Flowstate puts your people, contractors and AI on one plan. It shows what they cost, what they produce, and the teams and projects they work on. Use this page to find where to start.
New to Flowstate?
Read How Flowstate fits together first. It shows how the parts connect, and what each one needs before it shows a useful number.
Everyday help
- Eddy: ask Flowstate's assistant a question in plain words, and get taken to the screen that answers it.
- Inbox: the tasks and updates Flowstate sends you.
- Live data and scenarios: plan a change without touching your live data.
- How costs are calculated: where every cost figure comes from.
Set up what you need
Pick what you want to do with Flowstate. Each checklist says what to do, who does it, where, and how you'll know it's done.
Everyone starts with Set up sign-in and invite your team. Then work through the foundations your outcome needs, in the order shown.
● needed · ○ optional · – not needed
Measure your human + AI workforce
See whether people use AI, where it sits in the work, and what it returns.
| Outcome | Org basics | People & teams | Projects | Project tool | AI providers | Cloud Proxy | Business metrics |
|---|---|---|---|---|---|---|---|
| Track AI adoption | ○ currency | ● teams, work emails | – | – | ● | ● | – |
| Track AI in your workflows | ○ | ● | ● | ● | ● | ● | – |
| Prove AI's return with business metrics | ○ | ● salaries | – | – | ● | ○ | ● |
| Measure what delivery returns | ○ | ● salaries | ● | ○ ticket links | – | ○ AI impact | ○ project value |
Know where the money and time go
The record underneath: what AI costs and who it's for, and what people spend their weeks on.
| Outcome | Org basics | People & teams | Projects | Project tool | AI providers | Cloud Proxy | Business metrics |
|---|---|---|---|---|---|---|---|
| Attribute AI spend | ● currency | ● work emails | ○ by project | ○ by project | ● | ○ by project | – |
| Know what people are working on | ○ | ● managers, salaries | ● | ● | – | – | – |
Plan, budget and report
| Outcome | Org basics | People & teams | Projects | Project tool | AI providers | Cloud Proxy | Business metrics |
|---|---|---|---|---|---|---|---|
| Plan headcount | ● | ● | ○ | – | – | – | – |
| Run a budget cycle | ● | ● managers | ○ | – | – | – | – |
| Staff a project | ○ | ● | ● | ○ | – | – | – |
| Hit your CapEx target | ● | ● salaries | ● | ● effort | – | – | – |
| Run a continuous R&D tax claim | ● | ● | ● | ● | – | – | – |
| Map your functional organisation | ○ | ● | – | – | – | – | – |
- Track AI adoption: someone counts as active once they've had an AI session, and sessions come from the Cloud Proxy. Provider connections alone show seats and spend, not who is active.
- Track AI in your workflows ties AI sessions to projects through your project tool. Seeing AI-assisted pull requests also needs GitHub.
- Prove AI's return with business metrics needs salaries and rates for the people behind each metric, and your AI providers connected, so each unit of output has a cost.
- Measure what delivery returns also needs GitHub. Linking pull requests to projects works with Linear and Azure DevOps.
- Attribute AI spend works from provider bills alone. Splitting spend by project needs the Cloud Proxy and your project tool.
- Staff a project: you can plan who works on what without your project tool. To see what a project has actually spent, you also need effort reporting.
- Know what people are working on: teams can submit their weeks without organisation basics, but exchange rates and resource types decide what that effort costs.
- Hit your CapEx target and Run a continuous R&D tax claim are built on submitted effort. Set up effort reporting first, or alongside them.
- Map your functional organisation: organisation basics add job roles, custom fields, and the currency cost is shown in.
How these docs are organised
| Section | What's in it |
|---|---|
| Get started | How Flowstate fits together, the shared foundations, and a checklist for each outcome. |
| Workforce | Employees, contractors, vacancies and teams; allocations and staffing; functional groups; scenarios; analytics; business metrics. |
| Delivery | The roadmap of projects and initiatives, effort reporting, and engineering insights. |
| Finance | The forecast, budget cycles, capitalisation and R&D tax claims. |
| AI | Agent insights, Agents & copilots, My AI, AI settings and caps and the Cloud Proxy. |
| Settings & admin | Users and roles, organisation settings, data import, billing and security. |
| Integrations | A page for each connector. |
| Developers | The REST API, MCP, webhooks and custom integrations, and the changelog. |
How an implementation runs
- Kickoff. You meet your Flowstate contact to agree which outcomes you're setting up, who's involved, and decisions such as how often you'll capitalise.
- We switch on your modules. Your Flowstate contact turns on the parts of Flowstate your outcomes use. Until then, those screens show a holding page.
- You work through the foundations. Start with sign-in and access, then the foundations your outcomes need.
- You set up each outcome. Each outcome's checklist takes you through it step by step.
Who you'll need
| Role | Usually looks after |
|---|---|
| Finance lead | Reporting currency, exchange rates, fiscal year, cost centres and overhead, AI spend and caps, and signing off costs, budgets and claims. |
| AI or operations lead | AI adoption, the agents you run, and the business metrics that show what teams produce. |
| Engineering or delivery lead | Projects and initiatives, the project tool connection, team structure and effort. |
| IT or security | Sign-in, single sign-on and SCIM, connections to AI providers, and the Cloud Proxy. |
| HR or people data owner | Employees, contractors, vacancies, salaries, job roles and locations, and keeping them up to date. |