Skip to content

The Workforce Engineering platform.

Built for the hybrid workforce — human and AI.

Workforce Engineering is the practice of deliberately designing, measuring and optimising how an organisation deploys its labour — human and AI — to produce outcomes. Flowstate is the platform built for it.

Flowstate founding team
Will Hackett
Will Hackett
Co-founder & CTO

The unit of labour changed. The operating model didn't.

AI has broken the assumption that managing a workforce is a headcount problem. A team of fourteen that used to own a product vertical might now have the effective output of twenty — or eight — depending on how well they're using AI tools. The role of the engineer has fundamentally shifted from individual contributor to orchestrator of AI agents. But our operating models still treat them like standard headcount. Meanwhile, enterprise AI spend is growing 36% year on year. Most of it lands in budgets without a clear owner, classified inconsistently, reviewed quarterly at best.

That's not a software line in your budget any more. It's a form of labour — with the same questions attached as any other: what did it produce, was it worth it, how should we allocate it next period?

At the same time, structural pressure on labour costs has never been higher. PE dealmaking hit $602 billion in 2024. Technology captured a third of all deals. Operational excellence now drives 47% of PE value creation, up from 18% a decade ago. The old proxies — headcount, utilisation rates, output per head — were already inadequate. They're now actively misleading.

The existing categories don't help. Workforce Management is scheduling and shift workers. FinOps is cloud costs. Engineering Management is too operational, too narrow. None of them describe what's actually needed: engineering the system around your workforce so that human ingenuity and AI scale are properly aligned.

The companies that build this infrastructure now will have a structural advantage over those that figure it out two years later, after the spend has scaled and the waste has compounded. They'll also protect their best people from the burnout of misaligned priorities.

That's what Flowstate is.

AI is the fastest-growing line on your P&L.

It scales with activity, has no natural ceiling, and lands in budgets without an obvious owner. Invoices tell you what you spent — not why, where, or whether it was worth it.

Real governance is more than a dashboard. It's seeing where every AI dollar goes, deciding what's on-policy, enforcing it where the traffic flows, and resolving drift before it becomes a quarterly surprise.

Workforce Engineering is the parent practice. AI financial governance is its sharpest current expression.

Lineage

Brex made corporate-card spend governable. Carta made workforce equity governable. Concur made T&E governable. Flowstate makes hybrid-workforce spend — human and AI — governable.

We're founders. It's what we do.

Oliver and Will have both built companies from scratch, scaled teams across continents and know first-hand what it takes to connect engineering and finance around a shared picture.

They kept seeing the same problem across every enterprise they worked with — engineering organisations spending tens of millions a year with no shared operating model between the CTO and CFO. The tools existed for headcount planning and the tools existed for project tracking, but nothing treated the workforce as a single system that both sides could trust. That's the gap Workforce Engineering fills.

Getting this right has historically been so painful that guessing was the rational choice. Flowstate makes the right answer easier than the guess.

We love early stage. We love the part where you're close enough to the problem that every conversation with a customer changes the product. Our first enterprise customer blocked every Friday for two months so we could sit in their office and build the thing together. That's how Flowstate was shaped — not in a conference room, but in the mess of real planning cycles with real engineers and real finance teams.

Meet the founders

Oliver Beach

Oliver Beach

Co-founder & CEO

Eleven years building in the future of work — at Emeritus, WeWork, Flatiron School and Jolt. Before all of that, a high school accounting teacher. Which makes him one of the rare people in tech who can explain capitalisation to an engineer and explain engineering to a CFO — and mean it both times.

Oliver sees the gap others walk past. The disconnect between engineering and finance isn't a data problem or a tooling problem. It's a language problem. Two groups of smart people, both doing their jobs well, unable to communicate because nothing in their stack translates between them. He started Flowstate to be that translator — and to make the conversation between CTOs and CFOs feel like it should have always been this easy.

Will Hackett

Will Hackett

Co-founder & CTO

Writing software since he was ten. Twelve years of building and scaling products across startups and enterprise — Linktree, Blinq, private equity platforms — with deep experience in AI/ML and FinTech. Australian, based in London, and the kind of engineer who thinks about systems at every level: the code, the team, the economics and the organisational structure that either enables or destroys all three.

He writes about engineering economics, AI workforce dynamics and why middle management mostly exists to justify itself. His post on explaining the $20M engineering spend is probably the clearest articulation of why Flowstate needs to exist. Before Flowstate, he built and wound down an AI startup — and the lessons from that failure are baked into everything about how the product is built: small team, no ceremony, ship what matters, stay honest about what doesn't work yet.

willhackett.uk

What we stand for

Curiosity over assumptions.
We talk to customers before we build. We'd rather understand the problem deeply than ship the obvious answer quickly. Every feature in Flowstate exists because someone in a real planning cycle needed it — not because a competitor had it.
Through the wall, not around it.
Our first enterprise customer needed their entire scenario planning cycle rebuilt for quarter-end. Two weeks' notice. A team of two. We did it. That's how we operate. When something needs to happen, it happens.
Say the thing.
We'd rather have an honest conversation that's uncomfortable than a polite one that wastes everyone's time. That applies to how we build, how we sell and how we talk about what the product can and can't do today.

Backed by

We're supported by investors who've lived versions of this problem themselves.

  • a16z Scout Fund a16z Scout Fund
  • Ventures Together Ventures Together
  • Haatch Haatch
  • Openseed Fund I Openseed Fund I

The way engineering teams work is changing. The operating model should change with it.