The primary job of go-to-market is communication with humans outside the company. Sales, marketing, support—all of it is outbound communication. And communication has voice: tone, positioning, the way you frame a problem before you pitch the solution. That voice should be, over time, trainable.

I’ve been training an “eric voice” skill for Claude Code. It drafts emails, Slack messages, blog posts, and customer replies in my voice. Not a generic “professional tone”—my actual patterns, my tendency to lead with the technical detail before the business implication, my habit of short declarative sentences. It’s not just a good imitation. It’s often better than me—more consistent, more disciplined about structure, less prone to the rambling I do when I’m tired. The first draft is almost always tighter than what I’d write from scratch.

But agents converge toward the mean. Left unsupervised, any LLM drifts to median internet prose. The human in the loop isn’t there to write—they’re there to steer. To notice when the positioning has drifted, when the tone has gotten too safe, when the framing no longer matches what you learned from the last ten customer conversations. This is the reverse centaur: the human isn’t doing the work, but the human’s judgment is what keeps the work from being mediocre.

This is a lot of how kings of old used to hold court. Listening to petitioners wasn’t just good for the petitioners—it was how the king stayed calibrated on what the people actually needed. GTM leadership works the same way. You’re not just communicating outward. Every sales call, every support ticket, every marketing response is a signal coming in. The CEO who delegates all GTM to agents without listening loses the signal. The one who stays in the loop—reviewing drafts, steering tone, reading the inbound—keeps both the communication and the company’s positioning sharp.

Headcount as infrastructure

Think about headcount the way you’d think about infrastructure design. App servers are the easiest to replicate—stateless, horizontally scalable, throw more instances at the problem. The database is the hard part, because contention and consistency are delicate to scale.

The CEO is the primary database. They hold the state that everything else reads from: the company’s positioning, the product vision, the voice, the priorities. The CEO is the juncture between GTM and EPD—the single source of truth that both sides replicate from.

On the GTM side, you need two read replicas. GTM is embarrassingly parallel—more outbound, more coverage, more conversations—but it all has to be consistent with the positioning the CEO sets. Contractors and agents slot in naturally here. The replicas execute; the CEO reviews the output and course-corrects. GTM in a loop.

On the EPD side, you also need two read replicas, but for a different reason. Engineering has real contention—two engineers touching the same system create merge conflicts, architectural disagreements, subtle bugs from misaligned mental models. The codebase needs a coherent design philosophy, not five different patterns for the same problem. You need the replicas not for throughput but for incident coverage and redundancy—the system can’t go down when one node is unavailable.

In theory, you could compress further: three people. One GTM DRI, one EPD DRI, and the CEO as the read replica for both sides. The CEO doesn’t need to be the primary on either—they just need to stay consistent with both, which is exactly what a read replica does. The DRIs own their domains; the CEO maintains coherence across them. At three people, replication lag is essentially zero—you’re all in the same room, same Slack, same context. Compare that with a 100-person company, where the CEO is weeks behind on what engineering shipped and sales is pitching features that don’t exist yet. The lag isn’t a people problem; it’s a scaling problem. Three people with agents can stay in sync in a way that a hundred people with meetings cannot.

The back of the house vanishes

For companies of roughly five people, the “back of the house” tends to disappear entirely. Recruiting, HR, finance, procurement, office management, legal, IT, analytics—these functions either get absorbed by the founders or handled by agents and services.

This isn’t new. Five-person startups never had an HR department. What’s new is that the ceiling for operating without these functions has risen dramatically. Agents handle procurement workflows, generate financial reports, manage IT provisioning, draft legal documents for human review. The point at which you need a dedicated person for any of these has moved from ~20 employees to maybe never, for a certain class of company.

The org chart of a five-person AI-native company looks less like a small version of a big company and more like a core team with an orbit of agents, each trained on a different function. GTM in a loop. Support in a loop. Finance in a loop. The human is always in the loop—but the loop is the unit of organization, not the department.