The modern company is already hybrid. Not hybrid in the work-from-home sense — hybrid as in *made of two kinds of workers*. Humans who hold a title, own a department, pick up the slack when a sibling team falls behind. And agents: the code reviewer that ships in Slack, the triage bot that drafts first-response emails, the procurement assistant that reconciles invoices overnight. They do not take vacation. They do not negotiate comp. But they do work, and the output lands in the same ticket queues and Git histories as everyone else's.

Ask any COO at a twenty-to-two-hundred-person tech-forward company whether agents are part of their operation, and the answer is yes. Ask whether they show up on the org chart, and the answer is no. Somewhere between those two sentences is the problem.

Why the gap exists

Org charts evolved for a world where the only thing that "reported to" someone was a person. HRIS systems inherited that assumption. Compensation modules assume salary. Performance review modules assume a 1-on-1. Onboarding flows assume an I-9 form. The entire shape of the modern HR stack — every module, every integration, every compliance feature — bakes in the premise that a worker has a Social Security Number.

Agents do not fit. So for years, teams have routed around the problem. Platform engineering tracks agents in a wiki. Ops leads keep a spreadsheet. Finance puts the API bill on a credit card and calls it SaaS. And the org chart — the one artifact executives actually look at when they are thinking about how the company is structured — stays purely human. The shape of the business on paper does not match the shape of the work.

Here is the uncomfortable implication: the operator's mental model is already hybrid. The diagram they hand to a board or paste into an all-hands is not. That gap is where misaligned decisions are made. It is why leadership funds a headcount plan without accounting for the agents that will do half of the work. It is why a layoff debate happens without anyone asking which of those seats are already automated. It is why a new function stands up without a single line item for the three agents it will need to make any of the humans productive.

The operator's job is changing

The person who has to reconcile this gap is not the CEO and not the CHRO. It is the operator — the COO, VP Ops, or founder who doubles as the business's nervous system. Their calendar is the one that breaks when the gap widens. They are the translator between what HR understands (humans, roles, managers) and what IT understands (endpoints, services, API keys). And right now, neither side has a tool that captures both.

A hybrid-workforce org chart is a tool for that person. It is not a rebrand of HRIS. It is not a vendor management system. It is the single place where you can answer, in one picture: who does this work, human or agent, and who is accountable when it goes wrong.

What a hybrid org chart actually is

The constraints are simple to state and non-trivial to implement.

First, agents are first-class nodes. Not footnotes. Not a separate tab. Not a dashboard. Agents appear on the same tree as humans, in the same hierarchy, with the same click targets. A reviewer agent that reports to the head of engineering renders in the same column as the senior engineers — because that is where the work slots in.

Second, the differences are explicit. Humans have a hire date, a salary, a performance rating. Agents have a provider, a model, a system prompt, a human owner. A hybrid chart shows what applies and omits what does not. It does not pretend an agent has a birthday. It does not pretend a human has a context window.

Third, the reporting graph is bidirectional. Agents can report to humans. Humans can report to agents (it is already happening in teams where the orchestrator agent assigns work to contractors). Agents can report to other agents. The graph walks cleanly in any direction because the relationship type is "reports to," not "has a W-2 from."

Fourth, the privacy model is tighter than what HRIS systems usually ship. When you share a public version of the chart — to an investor, to a candidate, to a partner — names, titles, and departments go out. Emails, salaries, performance ratings, system prompts, API endpoints do not. The stripping is mechanical and enforced at three layers, because operators cannot afford to re-learn this lesson every six months.

Fifth, the pricing matches the thesis. If agents are peers, they count toward the same limit as humans. A plan that charges per seat for humans and ignores agents is a plan that encourages shadow hiring. A plan that counts the combined total makes the real conversation — "how big is our operational footprint?" — tractable.

Why now

Three things shifted in the last eighteen months. First, agent deployment graduated from prototypes to production at companies that are not AI startups. The twenty-to-two-hundred-person tech-forward company now runs at least three agents in the critical path. Second, the average operator has a name for what is bothering them: "we don't have a source of truth for who does what anymore." Third, and most quietly, the people who already have a makeshift answer — a wiki page, a spreadsheet, a slide deck — are hitting its limits. A spreadsheet cannot render a reporting graph. A wiki cannot enforce a privacy policy. A slide deck cannot be queried.

The org chart, when it works, is the operator's most-used artifact. When it stops working, the operator invents whatever the next best thing is. Right now, that invention is happening one spreadsheet at a time, unevenly, across thousands of companies.

What we built

Chartav.io is an org chart where humans and AI agents live side by side. Agents are first-class peers. The reporting graph walks in both directions. Public shares are PII-stripped by construction. The tier limit counts humans and agents together, because the bill that shows up is one bill.

It is not a separate product line for AI companies. It is an org chart for a company that is not lying to itself about how it runs.

If your operator has a wiki page about agents and an outdated headcount slide, the gap is already there. You can keep routing around it, or you can close it.

**[Build your org chart →](https://chartav.io)**