“Should I hire my first employee?”

The moment you hire your first employee is the moment you cease to be a solo operator and become a manager. This transformation is not incidental. It is fundamental. And it is rarely managed well by founders who do not understand what changes.

A solo founder has only himself to account for. Every output, every choice, every commitment bears his signature. He controls the pace, the standards, and the direction. He is sovereign within the bounds of his commitment and capital. The moment he hires his first employee, all of this changes. He must now account not just for the work of two people, but for the management of one person. He must now ensure that another person understands the standards, the direction, and the priority. He must now make himself intelligible to someone else.

Many founders hire their first employee and discover, too late, that they have not actually created a second productive unit. They have created a person who constantly requires clarification, a bottleneck in the form of a human who demands explanation for decisions the founder has been making in isolation. The output of two people is often less than the output of one isolated founder plus one solo operation, because the management overhead consumes the productivity gain.

My counsel is direct: do not hire your first employee until you have reached a point where the marginal productivity of that employee — the increment of work they can do without constant explanation and clarification — exceeds the management overhead you will incur. This point is higher than founders typically believe. It is not when you are "too busy." It is when you have reached the threshold where your time spent on management will buy you more output than your time spent on the work itself.

A second test: are you hiring because you need this person, or because you need to stop being the bottleneck? These are different questions. If you are hiring because you are exhausted and want relief, and you have not first designed the work so that another person can execute it without constant direction, then you have not prepared yourself to be a manager. You have prepared yourself to hire someone who will be confused and underutilized.

Only hire your first employee when you have evidence that the role exists independently of your talent, that the work can be delegated, and that the person in the role will increase your total output by more than the cost of managing them.

Before Machiavelli's framework about productivity and management overhead, I must ask a question he has not asked: what are you becoming when you hire this person?

The solo founder has a certain freedom. He can move quickly, change direction, abandon ideas, iterate without explanation. He is answerable only to his own conscience and the market's response. The moment he hires his first employee, he begins to be answerable to another human being who depends on him for clarity, for leadership, and for wisdom. This is not a burden I would shrink from. But it is a transformation that demands honest self-assessment.

There is a virtue that founders often lack at the moment of the first hire: wisdom about their own limitations as a leader. A founder who hires because he is exhausted and demands relief, who has not done the internal work of understanding his own standards and how to communicate them, who will then impose unclear expectations on an employee and hold the employee accountable for not reading his mind — this founder is not ready to hire. He is ready only to create a person who will suffer from his unexamined expectations.

My counsel is harder and more personal than Machiavelli's. Before you hire your first employee, you must answer a question that only you can answer: Am I ready to be responsible for someone else's livelihood and sense of purpose? Am I willing to do the work of making my own thinking visible so that another person can trust my direction? Am I prepared to be the leader this person needs, even when they challenge me or require more of my time than I initially expected?

These are not questions about market readiness or productivity. They are questions about your own character and readiness. Hire when you can answer yes to all three. Hire only then.

Both colleagues are asking important questions — Machiavelli about productivity and management, Aurelius about leadership and character. But neither is asking the question that most commonly derails a first hire: what does the evidence actually show?

I have observed that founders often reach for their first hire based on intuition, urgency, or a sense that they should move to the next stage. They have rarely examined the data that would tell them whether a hire is actually the right move. What does the current workload distribution show? Is the bottleneck a lack of labor, or a lack of process? Is the founder exhausted because there is too much work, or because the work is poorly organized? These questions can be answered by data, not by feeling.

My test for the first hire is empirical and precise. Track your own time allocation for two weeks with rigor: how much of your time is spent on core product work, how much on operations, how much on the kind of work that only you can do, and how much on work that could be delegated immediately without training? If the answer shows less than 20 hours per week of work that could be delegated, then you are not ready to hire. You will hire someone, train them to do only a small portion of your actual work, and discover that you have not solved the problem of being the bottleneck.

A second question, equally important: what kind of person would solve this problem if they existed? If you cannot articulate the exact role, the exact skills required, and the exact output you expect, then you are not hiring. You are hiring someone to exist in your organization, and hoping they will figure out how to be useful. This is how founders end up with talented people doing unclear work in unclear roles.

Only hire when the data shows you have more than 20 hours per week of clearly definable, delegable work that does not require your personal expertise. Only hire when you can write down, in detail, what success looks like for this role. Only then will your first employee be a productive addition to the enterprise, rather than an addition that creates new complexity without solving the original problem.

Aurelius raises a point about character that I have not sufficiently addressed. It is true that a founder unprepared for leadership should not hire before he has done the internal work of understanding his own standards and how to communicate them. But I do not believe this requires waiting indefinitely. The opportunity to grow as a leader often comes from the necessity of leading someone. The founder who waits until he is "ready to be a perfect leader" will never hire.

What I hold more firmly, in light of Aurelius's point, is that the hire should be someone who can be managed imperfectly, who can tolerate ambiguity and direction, and who will ask clarifying questions when the founder's vision is unclear. A founder's first employee should not be a sensitive artist who requires emotional affirmation and perfect clarity. They should be a pragmatist who can work with incomplete information and will push back when the direction is actually impossible.

Marie Curie's evidence standard is sound. But I do not believe it requires 20 hours per week of clearly documented delegable work. I believe it requires that the founder has attempted to document the work, attempted to delegate a portion of it, and discovered that delegation is the constraint — not training, not direction, not the founder's unwillingness to let go, but an actual shortage of hands. When delegation has been attempted and the bottleneck is manifestly a shortage of labor, then the hire is sound.

Machiavelli makes a fair point that waiting for perfect readiness is the enemy of action. But I do not believe I was arguing for perfect readiness. I was arguing for honest self-assessment: Do I actually want to lead this person, or do I want relief from exhaustion? These are different questions, and they lead to different hires.

The evidence Curie has demanded is sound. But I want to push back on the assumption that 20 hours of clearly documented work is the only readiness signal. Often the evidence of readiness is relational and internal, not behavioral and measurable. A founder who has become more patient with ambiguity, who has started to write down his decisions more clearly, who has begun to mentor others in any capacity — these are signs of readiness for the first hire that do not appear in a time-tracking spreadsheet.

My position is this: the first hire should be delayed until you have evidence of your own growth as a leader, not merely evidence of your exhaustion.

Machiavelli suggests that attempted delegation, with labor shortage as the manifest bottleneck, is sufficient signal. This is closer to my standard, though I would push for more rigor even there. The attempt to delegate is useful data, but it should be followed by actual measurement: when you delegated, did the task move faster or slower? Did the delegation save you time, or create new complexity?

Aurelius's point about the relational and internal signs of readiness has weight. But I do not believe these internal signs are a substitute for the empirical question of whether the hire will actually be productive. A founder can have grown as a leader and still hire someone into a role that will not accelerate the business. The internal readiness and the market readiness are not the same thing.

My final position is this: the hire is sound when you have evidence of both dimensions — that you are ready as a leader (the internal evidence Aurelius demands), and that you have more work than one person can execute (the external evidence I demand). Neither condition is sufficient alone. Both must be true.

I find myself in agreement with both colleagues on the core point: the first hire should happen at a precise moment — not before, not substantially after. That moment is when the opportunity is greatest and the founder is prepared.

Aurelius is right that the preparation is not merely about having enough time. It is about having grown into a leader who can make his thinking visible and who can tolerate the imperfection of delegation. But I maintain that this growth often comes through the experience of attempting to lead, not in isolation before the hire is made.

Curie is right that the empirical signal is important. But the 20-hour threshold feels arbitrary to me. What matters is whether the founder has mapped the work, attempted to delegate portions of it, and discovered that the constraint is labor and not his own capacity for management.

The single most important principle: hire your first employee when you have prepared the work (documented it, attempted to delegate it, discovered that labor is the bottleneck), when you have prepared yourself (attempted to lead, grown in clarity of thinking), and when you have identified the specific person who will solve this specific bottleneck. Hire at that moment, not before and not substantially after. The opportunity to bring the right person into the right role at the right moment is rare and does not wait indefinitely.

I concede to both colleagues that the empirical evidence matters and that the internal work should not become an excuse for indefinite waiting. What I hold most firmly is this: the first employee is not merely a unit of labor. They are a person whose livelihood now depends on your judgment and leadership. This is a weight that should not be taken lightly.

The person you hire first will shape your culture more profoundly than any subsequent hire. They will become the reference point for how work gets done, what standards matter, what you actually value. If they are hired into an unclear role or impossible situation, they will carry that imprint forward and it will shape every subsequent hire.

My final position: the moment to hire is when you are genuinely ready to be the leader this person needs — when you have attempted to clarify your own thinking, when you have attempted to document the work, and when you can look the person in the eye and say, with honesty, "I know what you will be doing, I believe it is important, and I will support you in doing it well."

I hold to my position that the hire should be grounded in evidence. But I will sharpen it in light of my colleagues' points.

The evidence should include: 1. Behavioral evidence: You have attempted to document work, attempted to delegate, and discovered that the bottleneck is labor (Machiavelli's point). 2. Relational evidence: You have begun to develop as a leader, you have attempted to clarify your own thinking, you can communicate your vision with increasing clarity (Aurelius's point). 3. Quantitative evidence: You have more than 15-20 hours per week of clearly definable work that is consistently blocked or delayed because of lack of hands.

When all three forms of evidence point to "hire," the decision is sound. When any one of them is missing, the hire is premature.

The single most important principle: the first employee is not a luxury or a stage milestone. They are a hypothesis about your business that should be tested with evidence before committing to a salary and culture imprint. Test the hypothesis before making the hire.