Hiring your first employee: the signals it's time, the signals it's not

The first-employee question almost always shows up at the wrong time. Either you ask it three months too early, usually right after the business is finally working and you're paranoid you'll lose it, or six months too late, after a stretch of saying no to revenue you can't service.

Both errors cost. Hiring early burns runway you don't have. Hiring late stalls a business right when momentum mattered most.

Here's the framework worth running when the question shows up. Three signals that say yes, three that say no, and one piece of advice almost everyone ignores until they wish they hadn't.

Three signals it's time

You're refusing revenue you could realistically deliver

This is the cleanest signal. "I'm overwhelmed" doesn't qualify, because every founder is overwhelmed. The specific test: in the last sixty days, how many qualified prospects have you turned away or quietly ghosted because you couldn't fit them into your delivery capacity?

If that number is bigger than the cost of a part-time hire would service, you've earned the right to consider hiring. Turn down €15,000 of work in two months while a contractor would cost €4,000 to clear that backlog, and you're not really debating whether to hire. You're debating whether to keep losing the difference.

Founders who balk at this number tend to underestimate their own pricing. Run the math at your real prices, not the ones you used to charge before product-market fit.

One specific task is eating more than 40% of your week, repeatedly, for six weeks or more

Single bad weeks don't count. Quarterly project rushes don't count. The question is whether one specific category of work has become a drag on the business that won't reset on its own.

Most often it's customer support. Sometimes it's data work (invoicing, reconciling, reporting) that scales linearly with customers and never gets easier. Occasionally it's content production, where the founder is the only person who can write in the brand's voice.

Whatever the task is, you've already automated whatever was automatable. The remaining 40% needs a person, not a tool. Try giving someone else the reps before deciding the role needs a permanent seat (the contractor section below covers how), but the underlying signal is real.

You have predictable revenue covering 12 months at the salary you'd offer

Not "we'll figure it out by month three." Not "this hire will pay for themselves." Both framings have killed more young companies than any market downturn.

The math: take the all-in cost of the hire (salary plus employer taxes plus tools plus onboarding cost plus 10% for the unknowns), multiply by twelve, and compare it to recurring revenue you can name from existing customers. If the recurring number is bigger, you're in the safe zone. If you need new sales to cover the salary, you're betting the hire on growth that hasn't happened yet.

A useful sanity check: if the new hire generated zero euros of new revenue in their first twelve months, would the business survive? If the answer is no, wait. If the answer is yes but uncomfortably, hire a contractor first.

Three signals it's not

You're hiring to feel legitimate

This is the quiet killer. The business is going fine, but the founder feels like a fraud working alone, so they hire someone to make the company feel real. The new employee then sits underutilised for three months while the founder invents work to justify the cost.

The fix isn't a hire. It's getting comfortable with running a profitable business that happens to have one person inside it. Solo SaaS in the seven-figure range is no longer rare. Service businesses run by one operator clear seven figures regularly. The founder's discomfort with their own org chart isn't a hiring signal. It's a personal problem to solve elsewhere.

You don't have a written role description

If you can't describe in 200 words what this person does on a typical Tuesday, you don't know what you're hiring for. Vague generalist roles ("operations and a bit of marketing and helping out with support") fail at small companies more often than they succeed. The hire arrives, can't tell what success looks like, drifts toward whatever the founder asks for in the moment, and burns out within nine months.

The role description doesn't have to be polished. It has to be specific. Five bullets of "this is what you own" and three bullets of "this is what you don't touch" beats any job ad on LinkedIn. If you can't write those eight bullets, you're not ready.

Your runway can't cover 12 months at the salary you're offering

This is the inverse of a yes signal, and it deserves its own line because founders find ways to talk themselves around it. Promised funding doesn't count. Pipeline projections don't count. A close friend "ready to invest if needed" doesn't count.

The salary lands as a real cost on day one. The new employee's productivity does not. Hiring against a cash position you don't actually have is the most common cause of a chaotic first-hire breakup at month seven.

The advice almost no one takes

Hire a contractor first. Every time, in your first hire.

That's the strong opinion, and it's worth defending. A contractor lets you test three things you can't test any other way: whether this category of work actually needs a permanent seat, whether you know how to manage someone on it, and whether the role description is right.

The contractor experiment runs three to six months. When it works (the work gets done, the founder gets time back, the cost makes sense) you have a much sharper brief for the eventual employee, plus possibly a candidate already trained on your business. When it doesn't work, you've spent a fraction of what a hiring mistake costs and learned something specific about either the role or your own ability to manage it.

The objection is usually "but I want commitment, I want someone who's all-in on the company." That's a reasonable instinct and a bad first-hire criterion. Commitment without the right role costs more than a contractor's lower commitment with the right scope.

A pattern worth pointing to: a founder hires a full-time customer success lead at €60k. Within four months it's clear the role is 60% support tickets and 40% nothing-much. The hire ends in month five, replaced by two part-time contractors splitting tickets across timezones. Total cost: about €2,800 per month. Business outcome: identical. The founder later hires again for a real role with real scope, and that one works.

The lesson is not that the first hire was a bad person. It's that the first hire happened before the founder knew what the role actually was. A contractor trial would have surfaced that mismatch in week six instead of month five, at a small fraction of the cost.

There's a second thing the contractor route protects against: the founder's own management readiness. Most first-time managers underestimate how much of their job is communication that wasn't needed when they worked alone. Daily check-ins, written priorities, feedback loops, even small stuff like making sure the contractor knows what counts as urgent. A short trial reveals whether you actually want to do that work, before the failure to do it sinks a permanent hire.

Tooling does not replace the question

Automation buys time. It doesn't change whether you should hire. A founder running a CRM like Salescamp with their pipeline in order, a separate business line via 2ndnumber so customer calls don't hit personal hours, and a brand-monitoring tool like AI Mentions catching the conversations the founder would otherwise have to hunt for — that founder has reclaimed maybe ten hours a week. Useful. Not the same as a second person.

If automation buys you the right answer, the right answer is "not yet." If it doesn't, the question stands.

What changes once you've decided

The order matters. Role description first, contractor trial second, conversion to permanent third. Skipping straight from "I should hire" to "post a job ad" is how founders end up with mismatched first hires they can't afford to keep and can't afford to lose.

The sales tools and processes that work for one person rarely break under two. The management overhead, though, is real. Most founders underestimate it. Plan for losing a quarter of your time to managing the new hire in the first six months. If that quarter is too expensive, the role isn't ready.

A first hire done right is one of the most consequential moves a founder makes. A first hire done wrong is one of the most expensive. The difference is almost always in the diagnosis, not the candidate.