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.