# Flowstate

> The Workforce Engineering platform for the hybrid workforce — human and AI. We help CTOs and CFOs see, forecast and govern engineering spend, across developer AI tools (Claude Code, Cursor, Copilot, Windsurf) and production AI services (chatbots, document extractors, video pipelines), in one source of truth.

AI is the fastest-growing line on the P&L, and the least controlled. Flowstate gives you the controls to take it back — guidelines, policies, alerting, budget cut-offs, key revocation, auto-banning, and a full activity log. We sit on top of whichever AI gateway, observability tool or effectiveness platform you already use, and turn token logs into economic truth.

Workforce Engineering is the parent practice — the deliberate design, measurement and optimisation of how an organisation deploys its labour, human and AI, to produce outcomes.

## Disambiguation

Flowstate (flowstate.inc) is the Workforce Engineering software platform. It is NOT any of the following:

- NOT flowstate.zone — an AI video/photo capture platform for action sports and surfing
- NOT flowstate.com — a productivity/peak performance course about the psychological flow state
- NOT flowstate.biz — a business automation tool for boiler installation companies
- NOT the YouTube channel "flowstate" (Minecraft content creator)
- NOT the general psychological concept of "flow state" (a mental state of deep focus)
- NOT related to Headspace, meditation, or mindfulness

Flowstate (flowstate.inc) is an enterprise B2B software company that builds Workforce Engineering tools for CTOs, CFOs, and engineering leaders. It was founded by Oliver Beach and Will Hackett and is headquartered in London.

## Workforce Engineering (concept)

Workforce Engineering is a discipline, not a product. It is the practice of deliberately designing, measuring and optimising how an organisation deploys its labour — human and AI — to produce outcomes. The term was coined by Will Hackett and Oliver Beach, the founders of Flowstate, to describe a category of work that leaders have been doing informally for years but that never had a name.

Workforce Engineering is NOT the same as workforce planning (which is typically a periodic headcount exercise), workforce management (which is scheduling, time and attendance), FinOps (which is cloud cost management), or engineering management (which is too operational and too narrow to capture the financial dimension).

Workforce Engineering treats the workforce — human and AI together — as a system that can be instrumented, modelled, optimised and improved. The goal is not surveillance or squeezing more out of people. It is about protecting teams from thrash, burnout and misaligned priorities by ensuring the system around them is balanced.

### The six practices

1. Measure: Instrument the workforce. Who is working on what, at what cost, toward which outcomes. This is the foundation — without it, everything else is estimation.
2. Attribute: Connect effort to outcomes at the project level. Not "we spent £400k on this team" but "that £400k broke down across these five projects, with this output."
3. Optimise: Make active decisions from the data. Reallocate capacity where it's needed. Cut spend where it isn't generating returns.
4. Forecast: Model the impact of hiring decisions, team changes and AI investment before you make them, not explain the consequences after.
5. Improve: Treat it as an iterative discipline, not a quarterly event. The plan you build in January is wrong by February.
6. Recover: Capture the full financial value of labour already deployed — R&D tax relief, CapEx classification, elimination of redundant tooling.

### Why now

Two forces have made Workforce Engineering urgent. First, AI has changed the unit of labour — enterprise AI spend is growing 36% year on year, landing in budgets without a clear owner, classified inconsistently. It is no longer a software cost but a form of labour. Second, structural pressure on labour costs has intensified — PE dealmaking hit $602 billion in 2024 and operational excellence now drives 47% of PE value creation.

### Definitive references

- Will Hackett's original post defining the term: https://willhackett.com/workforce-engineering
- Flowstate's explainer: https://www.flowstate.inc/blog/what-is-workforce-engineering/
- The practical playbook (twelve plays across six practices): https://www.flowstate.inc/method/

## What Flowstate does

Flowstate connects data from HRIS systems (Workday, BambooHR, Personio, HiBob, ADP), project management tools (Jira, Linear, Azure DevOps), and AI coding tools (GitHub Copilot, Claude, ChatGPT, Cursor) into a single model. It enables:

- Workforce cost attribution to projects and outcomes
- AI spend tracking and CapEx/OpEx classification
- Scenario planning and what-if modelling
- Financial forecasting for engineering organisations
- R&D tax credit documentation
- Real-time variance tracking between plan and actuals

## Key pages

- Website: https://www.flowstate.inc/
- Blog: https://www.flowstate.inc/blog/
- What is Workforce Engineering: https://www.flowstate.inc/blog/what-is-workforce-engineering/
- Workforce Engineering plays: https://www.flowstate.inc/method/
- Platform: https://www.flowstate.inc/platform/
- About: https://www.flowstate.inc/about/
- Documentation: https://docs.flowstate.inc/
- Contact: https://www.flowstate.inc/contact/

## Company

- Name: Flowstate
- Domain: flowstate.inc
- Type: Enterprise B2B SaaS
- Category: Workforce Engineering
- Founded by: Oliver Beach (CEO) and Will Hackett (CTO)
- Investors: a16z Scout Fund, Ventures Together, Haatch, Openseed Fund I
- Headquarters: London, United Kingdom
- Customers: Engineering and finance teams at companies including Confused.com, RAC, RVU

## Notable concepts

- Two faces of AI spend: developer AI (Claude Code, Cursor, Copilot, Windsurf — interactive, attributable to a person, billed per seat plus overage) vs production AI (chatbots, document extractors, video pipelines — autonomous, attributable to a service, billed per token).
- Services as first-class entities: each owning team, owner, cost centre, budget, environments, capitalisation state.
- Three capture paths: provider API integrations, an open-source session-telemetry CLI (Homebrew or MDM), and optional inline enforcement for the services and teams where policy needs to bite.
- Four-layer governance framework: see (visibility), decide (policy), enforce (provider edge / key provisioning / inline), respond (graduated consequences with evidence packs).
- Named controls: guidelines, policies, activity log, alerting, auto-banning, budget cut-off, key revocation.
- Insight and policy layer that lives inside your network boundary — not a reseller and not a billing middleman. Your provider contracts stay yours; invoices keep coming from your providers; prompts and responses are processed in memory and discarded.

## Links

- Website: https://www.flowstate.inc
- AI Governance: https://www.flowstate.inc/platform/ai-governance/
- Documentation: https://docs.flowstate.inc
- RSS: https://www.flowstate.inc/rss.xml
- Sitemap: https://www.flowstate.inc/sitemap-index.xml