Inside Know AI
By Zeel Jain
THE EDITORIAL ARC · PART 3 OF 5 The org chart, the agents, the handoffs. How a small AI-native company actually divides work between humans and software, and the framework you can use to redesign yours.
WHY THIS EXISTS
Most AI org charts are theatre.
Most companies running AI still have a 2018 org chart with AI tools sprinkled on top. Same boxes, same reporting lines, same job titles, just with “powered by AI” in the bio.
That’s not an AI company. That’s a company that uses AI. The structure looks different when you actually rebuild around it. This guide shows you what ours looks like and the framework we used to get there.
“You can’t bolt agents onto a 2018 org chart and call it an AI company. The chart itself has to change.”
What you’ll have when you’re done
- A walk through the actual Know AI org chart - humans, agents, hybrids.
- The Role Triage framework: how to decide what becomes human, agent, or hybrid.
- The hiring shift: who you should be hiring next, and who you shouldn’t.
THREE ROLE TYPES
Every job in your company is one of three.
Most companies haven’t named which is which. That’s the source of the mess. Once you’ve sorted every job into one of these three types, the rest of the org-chart redesign is mostly mechanical.
01 Human roles
Work only a human can do. Judgement, relationship, taste, accountability. The role exists because a person is required and not because the work is high-volume or fast-moving. These roles get fewer over time, but more senior.
02 Agent roles
Work fully owned by software. High-repetition, well-scoped, auditable, with clear inputs and outputs. The agent is the worker. A human owns and reviews, but doesn’t do. These roles expand fastest in any AI-native company.
03 Hybrid roles
Humans whose primary work product is the briefs and reviews of agents. They don’t do the work — they manage the software that does. This role didn’t exist three years ago. It’s now one of the most leveraged roles in any serious AI company.
THE TWO LAWS
1. Every agent has a human manager. No exceptions.
2. No human does an agent’s job. If a person is doing high-repetition, well-scoped, auditable work, you’ve miscast a role. Promote them, hire an agent, or both.
INSIDE KNOW AI
How we’re actually structured.
Sanitised but real. The shape, the roles, the agent footprint. Names abstracted, logic intact.
Founder : Human role
Strategy, hiring, brand, partnerships, and the editorial direction of the company. Doesn’t do high-repetition work. Reviews agent outputs in the content and ops surfaces.
CTO : Human role
Technical architecture, infrastructure decisions, hiring engineers. Owns the build platform the rest of the company works on top of.
Operations Manager : hybrid role
The most leveraged role in the company after the founders. Roughly 60% of their time is spent managing agents — writing briefs, reviewing outputs, retiring old agents, updating escalation rules. The other 40% is human ops work that can’t be delegated yet.
Engineering team : Human roles, agent-augmented
Senior engineers, no juniors. Each one supervises Claude Code as a primary tool — what would have been junior copy-paste work is now agent-handled. The engineer’s job is judgement and review.
Content team : Hybrid + agent roles
One human content lead. Three named agents underneath: script writer, voice guardian, carousel composer. The lead manages the agents and reviews. The agents produce.
Sales/customer surface : agent role with human escalation
The WhatsApp sales bot is the first responder. Hand-offs go to a human only when the brief’s escalation rules trigger. The human owns the relationships, the agent handles the volume.
WHAT THIS LOOKS LIKE ON A CHART
If we drew the actual chart, agents have boxes too. Each agent box has a name (the agent’s job), an owner (the human responsible), and a reporting line. The chart looks like a network, humans and agents both have lines in and out. Reporting goes up to managers, sideways to the agents a person manages, and down to the outputs those agents produce.
ROLE TRIAGE
How to sort every job in your company.
Run this on every role in your current org chart. The framework returns one of three answers: human, agent, or hybrid.
Question 1: Is the work high-repetition and well-scoped?
If yes, it’s a candidate for an agent role. If no then it’s a human role.
Question 2: Are the inputs and outputs auditable?
Auditable means: a human can review the work and decide if it’s good or bad in under a minute per item. If the work fails this test, it can’t be safely delegated to software. Keep it human.
Question 3: Does the work require judgement, relationship, or taste?
If yes, then the human stays in the seat. If no, then the agent can take it.
Question 4: Who manages the agent if you delegate it?
If there’s no clear human owner, you don’t have an agent role yet. You have a wish. An agent without an owner is orphaned software, and orphaned software produces orphaned outputs.
THE REDESIGN EXERCISE
Run Role Triage on every role in your current org chart. The output: a new chart with three kinds of box. The agent boxes are usually the surprise. You didn’t realise how many you already had, or how many you should have. Once they’re on the chart, they get owners. Once they have owners, they get managed. Most AI work compounds from there.
THE HIRING SHIFT
Stop hiring juniors. Start hiring hybrids.
The most consequential change in an AI-native org chart isn’t structural. It’s about who you hire next. Three rules we now follow at Know AI.
Rule 1: Don’t hire juniors for jobs an agent can do.
If the job is high-repetition and auditable, hire an agent. Use the budget you would have spent on a junior to hire someone more senior, or to free up a senior to manage the agent.
Rule 2: Hire hybrid managers explicitly.
When you hire an operations or content manager now, hire for the ability to manage software. The job description should include ‘writes briefs for agents,’ ‘reviews agent outputs,’ and ‘retires agents that aren’t earning their slot.’ Make it explicit. Most candidates haven’t done this. The ones who get it are the rare hires.
Rule 3: Senior humans, not flat human teams.
The org chart of an AI company gets flatter in human terms but denser in agent terms. Each remaining human is more senior than what they would have been in a 2018 chart, because they’re managing more leverage. Hire and pay accordingly.
THE LEVERAGE TRADE
A senior hire managing 4 agents is more productive than a junior team of 5. Cheaper too, in many cases — but that’s not the main reason to do it. The main reason is that the senior hire produces senior-quality work, because the brief, review, and management layer is senior-quality. Quality compounds when you put senior people in the manager seat.
If this was useful
This is part 3 of a 5-part editorial series on building AI workflows that actually compound. Real receipts from systems we run at Know AI. No jargon, no hype.
Follow @zeeel.ai on Instagram for the rest of the series.
SEND ME YOUR CHART
Run Role Triage on your team’s current org chart. DM me the new version on Instagram with the keyword ORGCHART. I read everything that comes in. Patterns across replies become the next post.