Explore Flowstate

The Flowstate platform
Helm

Know what AI costs. See what you get back.

Understand spending, share budgets and connect AI use to the work it supports.

Recent insights All insights

Buy tokens, rent GPUs, or own the rack?

Open-weight models are now good enough to make self-hosting a financial question rather than a capability one. I modelled four options, an office rack, colocation, rented GPUs and per-token APIs, to find where each one actually wins. The answer turns on utilisation, and it isn't the one the internet keeps giving.

Turn a $3m AI bill into $1.9m

Most teams overpay for AI twice without noticing: they run everything through the default flagship model, and they buy the tokens on a metered plan they can't see into. An intelligent proxy fixes both. Here is the maths, a calculator you can drag, and where Flowstate fits.

Start with the work All use cases

Understand AI spending and value

See where the budget goes and what the business gets back.

Share one AI budget across your tools

Fund people, teams and projects across connected services.

Give your team more capacity

Reduce the preparation, checking and follow-up around recurring work.

Connect AI use to delivered work

Follow AI activity into projects, code and business results.
Quick links
Flowstate / People + AI Talk through your priorities
Documentation
Get help
Docs / API & MCP

Effort

Effort is what people actually worked on, week by week: the share of each working day spent on each project, from your project tool and the weeks your teams submit. Allocations are the plan; effort is what happened. Capitalisation and R&D claims are costed from effort. See Effort reporting.

There’s no REST endpoint for effort. Read it through the MCP server. For the plan it’s compared against, use Assignments.

Units

Effort is never hours. get_project_effort and get_team_effort return person-days: working days of effort summed over the window. A person working full time on one project for 20 working days returns 20, not 1.

Tools

Every tool takes optional startDate and endDate (ISO 8601). Windows default to the last three months.

ToolRequiredReturns
get_project_effortprojectIdEffort on the project by person, with cost
get_team_effortteamIdThe team’s effort by project, with cost
get_unattributed_effortEffort not linked to any Flowstate project
get_effort_gapsPeople active in the window with no effort recorded, or with effort but no submitted week. Organisation-wide; rows carry the team.
get_uncosted_effortPeople with effort in the window but no salary or rate on file, so their effort is costed at zero
get_submission_leaderboardOn-time and late week submissions per submitter. Organisation-wide.

Get projectId from search_projects and teamId from search_teams.

Tools act with the caller’s Flowstate permissions. Cost needs a financial view permission; without it, effort still returns and cost is left out.

Find who hasn’t submitted this week

  1. Call get_effort_gaps with startDate and endDate set to the week.
  2. Call get_submission_leaderboard for the same window to see who submits late.