Thought Leadership

Essay 05. The founder question nobody at the event wanted to answer out loud.

You built it with agents. Now who is your first human?

A generation of tech founders has reached a functioning product with almost nobody on the team. They are not avoiding humans out of principle. They are avoiding overhead, and they are right to. Which means the first few people cannot be justified on volume, because agents already handle volume. They have to be justified on something an agent structurally cannot hold. This essay names that test, and then names the three people it selects. Three, before any thought of a team. Bring these three in first and the team that follows costs a fraction of what it would have.

10 min readEssay 05 of the seriesSkilledUp Life · Thought Leadership
The founder's day, and its edge
Keep the three you are genuinely best at. Everything past the line is the hiring question.
What only the founder should hold

The product

The thing being built, and the taste that decides what it becomes.

Institutional memory

The company's own context, which every agent draws on and no competitor can copy.

The agent fleet

Enjoyable, and the most satisfying part of the day. Also the first thing to reach its limit.

The edge of one person's attention
Demand

Nobody knows the product exists. Positioning and relationships live with a person.

Hire 3 or 1
The human layer

Sourcing, onboarding, retaining, and the standard everyone is held to.

Hire 2
Fleet at scale

Five agents can be supervised by a founder. Fifty cannot.

Hire 1
Accuracy of output

Where being wrong reaches a customer and costs something real.

Folds into hire 1
Finance and compliance

Real, and largely absorbed by self-serve tooling. What remains sits inside operations.

Folds into hire 1
Five things fall off the edge. Only three of them are people. The other two fold into the first of those three, because operations covers accuracy and compliance from the inside. That is the entire argument of this essay in a single row.
01

The reluctance is rational. Start there.

Most commentary aimed at these founders is scolding. Hire people, build a culture, stop trying to do everything alone. It lands badly, because the founder is not being stubborn. They are making an accurate calculation.

Headcount carries management time, onboarding, payroll risk, notice periods and the considerable cost of being wrong about a person. Agents carry none of that. They arrive competent, they do not need a one-to-one, and they can be switched off on a Tuesday afternoon with no consequence. Against that comparison, "you have too much to do" has stopped being a reason to hire anybody.

So the honest version of this argument concedes the point. Agents genuinely did remove the throughput justification for early headcount. What they did not remove, and cannot remove, is the ceiling.

Agents extend the floor. They take whatever the founder already knows how to specify and they do more of it, faster, at any hour. The ceiling is different. The ceiling is the limit of what the company is capable of attempting, and in a company of one, the founder is the ceiling. Every agent added raises the floor closer to it. None of them lift it.

Agents raise the floor. Only humans raise the ceiling.

02

The test: what can an agent never be held to?

Before naming any role, apply one test. If an agent can hold it, an agent should hold it. There are exactly four things an agent cannot, and every defensible early hire traces back to one of them.

Accountability

An agent cannot be answerable. It cannot sign, cannot be liable, cannot carry the consequence of an outcome, and cannot be the name a customer or an investor holds responsible.

Shows up as: the founder personally checking everything before it leaves, because there is nobody else to be responsible for it.

Reciprocity

Customers, candidates, partners and investors want a person on the other side, one who remembers them and has something at stake. A relationship needs two parties capable of being changed by it.

Shows up as: conversations that stall the moment they need someone to commit to something.

Noticing what nobody asked

Agents answer the question put to them, superbly. They do not raise the thing that was never prompted, and the thing never prompted is usually the thing about to go wrong.

Shows up as: problems that were visible for weeks and surprised everybody anyway.

Undefined goals

Give an agent an unclear objective and it produces a confident answer to a question nobody asked. Deciding what the objective actually is remains human, and it remains the most valuable thing in the company.

Shows up as: enormous output, no observable progress.
If a role can be described entirely as a set of tasks, it is already an agent's role. The first humans are hired for what cannot be specified in advance.
03

The three the test selects.

Three roles, and no others, survive the test at this stage. Each one is a person the founder is currently being, badly, in the gaps between building.

In plain terms, before the titles get in the way: operations, HR, and marketing and sales. One person for each. Not a department, not a function to be staffed out, and not the beginning of an org chart. Three people, chosen because between them they cover everything the founder cannot hold and nothing that an agent already handles.

Agent Operator
In plain terms: Operations
Passes the test onAccountability. Somebody has to sign for what the fleet produces.
What they own
The fleet. Briefing it, supervising it, catching where it is wrong, and being the named human on everything that leaves in the company's name. Compliance sits here too, because what remains of it after self-serve tooling is a matter of checking and signing rather than a role of its own.
Why not an agent
An agent supervising agents compounds the error rather than catching it. Verification only means something when the verifier can be held responsible for missing something.
What compounds
The fleet stops being capped by the founder's attention. Five agents become fifty. Every correction the Operator makes is deposited into institutional memory, so the fleet gets quietly better rather than merely busier.
The hard part
Founders enjoy running the agents. This is the hire that requires giving up the best part of the day, which is exactly why it gets postponed past the point of usefulness. The pathway into this role is the subject of essay 04.
HR, in the talent-architect sense
In plain terms: HR
Passes the test onReciprocity. People join companies because of people.
What they own
How humans join and contribute. Learning how the company genuinely operates, recording it, and then sourcing, onboarding and retaining everybody who follows, including the next Agent Operators.
Why not an agent
Because the subject matter is human motivation. An agent can screen a hundred profiles and cannot tell whether somebody will still be here in six months, or notice that the third joiner in a row left for the same unspoken reason.
What compounds
Every later human becomes faster and cheaper to bring in. That is the only justification a reluctant founder respects, and it is a real one: the second hire costs a fortune in founder attention, and the tenth costs almost none.
Why so early
In a conventional company HR arrives at thirty people. Here it arrives early for a specific reason. A founder tapping a talent pool does not receive one candidate, they receive many at once, and that is a throughput problem from the first day rather than the thirtieth.
Demand
In plain terms: Marketing and sales
Passes the test onUndefined goals. Positioning is a judgement, not a task.
What they own
The reason anybody knows the product exists, and the conversations that follow. Channel choices, positioning, and the relationships that need a person on both ends.
Why not an agent
Agents produce material at extraordinary volume, which is precisely the problem. Volume without positioning is noise, and deciding who this is for and why they should care is the undefined-goal problem in its purest form.
What compounds
Everything else in the company is worth more. A better product with no demand is worth nothing, and demand built once keeps returning. The marketing pathway sets out where this talent comes from.
The hard part
Founders who love building tend to postpone this one indefinitely, on the reasoning that a good enough product will be discovered. It will not.

Notice what is absent. No general manager, no first engineer, no assistant in the pre-agent sense. Section 06 explains why each of those feels obvious and is not.

04

Which one is first depends on one thing.

Any article claiming a single universal first hire is guessing. The order genuinely changes, and it turns on one observable fact rather than on stage, funding or team size.

Do you have customers yet? That is the whole branch. Both routes arrive at the same three people within a year, and starting on the wrong one costs six months.

If the answer is no

Product built. Nobody using it.

The constraint is demand, not operations. Hiring an Agent Operator here simply produces more unwanted output faster.

  1. 1DemandSomebody whose entire remit is that people find out this exists and talk to you about it.
  2. 2Agent OperatorOnce there is genuine demand to serve, the fleet has something worth scaling.
  3. 3HRArrives when the fourth and fifth humans are needed, and makes them repeatable.
If the answer is yes

Customers arriving. Founder saturated.

The constraint is capacity and the human system. Demand is already proven, so protect the ability to serve it.

  1. 1Agent OperatorReturns the founder to product and institutional memory within the first month.
  2. 2HRImmediately behind, because hire three onwards should not cost what hire two cost.
  3. 3DemandNow about deliberate growth rather than survival, so it can be built properly.

In both sequences HR and Agent Operator are two of the first three. The argument does not depend on which route a founder takes.

05

The asset is the memory, not the agents.

Founders have started describing this as their company AI brain. The term will date, so call it what it is: institutional memory. The accumulated context of how this company operates, what it decided and why, what is true about the product today, and how it sounds when it speaks.

It deserves a section here because it reorders the hiring question entirely. Every founder at that event has access to the same models. Agents are rented and interchangeable. Institutional memory is the only part that is proprietary, which makes it the actual asset being built, and it changes who the first humans should be. They are not the people performing tasks. They are the people who build and maintain the asset.

Three uncomfortable properties follow. Memory does not populate itself: it is assembled from what humans notice, decide and record, so a company of one has a memory made of exactly one person's context, and it starves because that person is occupied building. Memory left alone gets actively worse: stale pricing, superseded decisions, product claims no longer true, all of it acted on confidently and at volume, which makes a neglected memory more dangerous than none. And memory is what makes new people productive quickly, because onboarding is almost entirely context transfer.

That last property is the one that closes the loop. The asset that makes agents effective is the same asset that makes humans effective. Which is why the two roles below both feed it as a byproduct of doing their own jobs rather than as a documentation project nobody ever gets to.

Founder

Intent and taste

Why the product is this and not that. Nobody else can deposit this, and it is the reason the founder should keep the memory rather than delegate it.

Agent Operator

What the fleet got wrong

Which context produced good outcomes, where each agent tends to fail, what had to be corrected. Nobody else is positioned to see it.

HR

How things are done here

The standard, the method, who knows what, what was decided and by whom. In a conventional company this is tribal knowledge. Here it is the memory itself.

Hire the people who build the asset.

06

Four hires that feel obvious and are not.

Each of these was the correct early hire five years ago. Each fails the test now, for a different reason, and the reasons are worth separating because two of them are not about AI at all.

Skip for nowA general operations manager

Hired to bring order, which is a real desire and the wrong solution. At this size there is not enough process to manage, and the role tends to generate the process that justifies it. The parts that genuinely need holding are already inside the three roles above.

Skip for nowA junior engineer

The traditional first hire, and the one agents changed most completely. Well-specified implementation is exactly what agents do best. What remains scarce is deciding what should be built, and that is not a junior remit. Hire this person when the product outgrows the founder's own hands, not before.

Skip for nowA content or social media person

Easily confused with the Demand hire, and materially different. Producing material at volume is now close to free. Deciding what is worth saying, to whom, is the scarce judgement. Hire for the judgement and let the agents handle the volume.

Skip for nowAn assistant, in the pre-agent sense

The remit that was diary management, travel booking, expense processing and data entry has not moved to AI. It ceased to exist, undone by booking links, card apps and integrations before agents arrived. Essay 04 sets out task by task what survived and what simply ended. Hiring for the old remit buys a job that no longer has anything in it.

Notice that two of the four were removed by ordinary self-serve tooling rather than by AI. Founders reasoning only about what agents absorbed will still hire one job that quietly ended years ago.

07

None of this requires committing to headcount.

Here is the part that resolves the objection rather than arguing with it. Everything above can be tested through Volunteers, which is not headcount. No payroll, no notice period, no permanent commitment made on the strength of a hypothesis about a role that barely has a title yet.

That matters most for the two roles a founder is least certain about. Bringing in an Agent Operator means discovering, within weeks, whether handing over the fleet actually returns the founder to the product. Bringing in an HR Volunteer means finding out whether a human layer is genuinely a throughput problem or whether it was imagined. Both questions are answered by trying, and neither answer requires a contract.

The exchange is honest in both directions. The founder receives judgement they could not otherwise justify at this stage. The Volunteer receives something a course cannot manufacture: a real founder who needs the outcome, real customers on the other side, and consequences attached to being wrong. Essay 04 argued that this is where the competences are actually acquired. The same arrangement is what lets a founder discover their first three humans without betting the company on the guess.

And the sequence is self-reinforcing. The HR Volunteer learns how this specific company operates, deposits it into institutional memory, and then sources the Agent Operators and the demand talent that follow. The second human is the one who finds the third, the fourth and the tenth.

Which is the real reason to start with three rather than with a team. Nothing here argues that a company of four is the destination. It argues about order. A team assembled after these three arrive is quicker to bring in, clearer about the standard, and considerably less likely to contain a role that no longer needs to exist.

69,000+
Volunteers across HR, marketing and the Agent Operator pathway.
225+
Tech startups who found their first humans this way.
148+
Countries our Volunteers join from, remotely.
The next step

Start with three. Then build the team.

Operations, HR, and marketing and sales. Three people who cover what a founder cannot hold, and who make every human after them faster to bring in. The team comes next, and it comes more cheaply because these three arrived first.