Three Agents, Half a Headcount

A working number to anchor on: the deployed teams I see running well are running at roughly 0.5 AI to 1 human. Not 1:1. Not 10:1. Half the agent count of humans, with each agent supporting multiple human roles many-to-many. A five-person team supported by three Fidelic agents — say a CS Lead, an Inbound BDR, and a Research Analyst — is not an eight-person team. It is a five-person team whose Monday morning briefings, renewal-risk alerts, and inbound replies are already in their inbox by 9am. The humans walk in to the work that requires them, not to the work that piles up overnight.

Hiring by seat is the default mistake

Your last ten hires were probably evaluated against a job description: list of responsibilities, list of required skills, fit for the team. The hire is the seat. The seat is the unit. AI inverts that unit. KORA does not decide what to work on; it works on what its constitution says it can. The work is listed, the limits are named, the version is listed. You are not buying "someone who can also do X if it comes up" — you are buying a slice of scope, with a published list of what falls outside that slice. Seat-shaped thinking — "I need an AI marketer" — is asking the agent to fill a role; agentic thinking is asking which scope you have that piles up overnight, and which agent fills it.

Three agents, ~80% of one role

Take a marketing function. The strategist's week is a mix of: brand-voice drafts, competitor monitoring, content calendar maintenance, content production, briefing the founder for press calls, sitting in product reviews. Three agents cover most of that scope. VEXA handles the strategy briefs and the founder-prep packets. KALA handles the calendar and produces the first-draft long-form. SYRA handles the keyword surface and the AEO mirroring. Together they cover roughly 80% of what a junior-to-mid marketing strategist's week looks like — the part that scales. The 20% they don't cover is the part you should not want them to: the brand calls, the agency negotiations, the original positioning work that makes a company sound like itself. That is the part that doesn't scale, and that's where your human strategist's time is now actually free to live.

How to pick the first three

Look for the work that piles up between Friday at 6pm and Monday at 9am. Inbound replies that sat unanswered for 60 hours. Renewal-risk signals that no one was watching. Research that someone needed to read on the plane and didn't have time to commission. That overnight pile is the cleanest signal of misallocated scope, and it is the single best predictor of where the first agent will pay back fastest. The three I see hire first, in this order: a CS Lead (KORA) when you have three or more CSMs and an account list above 75 customers; an Inbound BDR (VYRA) when you have an inbound funnel that loses leads to slow first-touch; a Research Analyst (OREN) when your founder spends Monday morning reading instead of deciding. Three agents, three slices of scope, half the headcount you would have asked for if you were thinking in seats.

Names and versions exist for a reason

The agents in the Roster are named — KORA, VYRA, VEXA, SYRA, KALA, OREN, VELA, ELRA, DARO — and they carry a generation suffix on the canonical surface (KORA-01, VYRA-01). The first batch all ship as -01. When the underlying model improves materially or the constitution changes meaningfully, the next generation ships as -02 with a public diff. The names aren't human names because the agent is not pretending to be a person, and the version isn't hidden because we owe the buyer the right to know what they are deploying. "AI that's always improving" is exactly what the version number is designed to refute. You know what you are getting, you can refer to a generation in writing, and you decide when to roll forward.