People, Contractors, and AI Agents on One Org Chart
The Workforce Graph puts every worker - employee, 1099 contractor, and AI agent - in a single hierarchy. Each node carries a trust score, a risk score, and a real annual cost priced against the same P&L, and an AI agent row carries the scopes it was granted, like payroll.write or funds.move. No HRIS or hiring marketplace can build this, because none of them model the money and the agents too.
Illustrative product view
One hierarchy, three kinds of worker
An org chart used to be a picture of humans. But an AI agent that can move money or write payroll is a worker with authority - and it belongs on the same chart as the human who owns it. The Workforce Graph holds all three kinds of worker in one hierarchy, so accountability is legible instead of scattered across an HRIS, a vendor list, and a pile of API keys.
| Node type | How it joins | What it carries |
|---|---|---|
| Employee | Swaps in from your real HR records | Manager, comp, trust score, risk score, fully-loaded cost |
| Contractor | 1099 / vendor worker record | Scope of work, spend, trust and risk, cost against the same P&L |
| AI agent | Registered with its granted scopes | Scopes (payroll.write, funds.move, ledger.read…), trust, risk, estimated run cost |
A trust score, a risk score, and a real cost
- Trust score - a behavioral track record, so a node earns or loses standing over time rather than getting a static label
- Risk score - the blast radius of the scopes a node holds, so an agent with funds.move is treated as riskier than one that only reads the ledger
- Fully-loaded cost - humans from comp; agents estimated from token and tool usage - and both are priced against the same P&L lines your finance team already reports
- Every node rolls up, so you can ask “what does this team cost, humans and agents together?” and get one number
Why an HRIS or a hiring marketplace can’t build this
An HRIS models humans only - it has no concept of an agent’s scopes. A hiring or talent marketplace models the supply and demand of humans - it never prices an AI agent’s authority or run cost against your books. Fintra can put all three on one chart precisely because people, money, and agents already live in one model. The org chart isn’t a new silo; it’s the view that finally makes the whole workforce comparable.
Frequently asked questions
Can I really put AI agents on my org chart?
Yes - an AI agent is registered as a node in the Workforce Graph alongside employees and contractors, carrying the scopes it was granted (like payroll.write or funds.move), a trust score, a risk score, and an estimated annual run cost, reporting to the human who owns it.
Where do the cost and score numbers come from?
Human cost comes from real comp records. Agent cost is estimated from token and tool usage, and the trust and risk scores are heuristics computed in-process - real logic on a non-durable store. All of it is priced against the same P&L your finance team reports on.
Does the graph take any action automatically?
No. It is advisory by design - it surfaces workers, scores them, prices them, and recommends. Revoking an agent scope, changing pay, or ending an engagement stays a human decision.
How is this different from an HRIS?
An HRIS models humans and has no concept of an AI agent’s scopes or run cost. Fintra models people, contractors, and agents on one hierarchy and prices every node against the same books, so the whole workforce - human and machine - is finally comparable.
What does an agent scope like payroll.write mean?
It is a specific authority the agent was granted - the ability to write to payroll. Fintra shows scopes as first-class fields on the agent’s row so they can be reviewed next to the owning human, factored into the risk score, and revoked.
Stay in the loop
One practical finance briefing a week - new guides, checklists, and benchmarks.
One brain for people, work, and money
See humans, AI agents, support, and finance decisions in a single governed workspace.
Talk to us