Should I hire my first employee?

Cerno is a private AI boardroom that runs consequential decisions through a structured process and returns a brief like the one below. This example is illustrative; your own would reflect your pipeline, your cash and the actual shape of the work.

How this brief was reached

The advisors formed independent positions, a Devil's Advocate challenged the leading one, and the vote landed 4–1 in favour of hiring — with two dissents kept on the record, one of which the recommendation adopts outright.

The Risk Officer's point is the one that shaped the brief. Asked to invert the decision — what would guarantee this hire fails? — the board's answers were not about the person at all. They were about the owner: hiring whoever is available soonest because they're drowning, never writing down what the job is, and continuing to do the work themselves. All three are in the owner's control, and all three became actions.

The CFO's dissent was not adopted, but it set the stop condition. A first hire converts a variable problem (too much work) into a fixed cost (a salary every month). That is fine while the work holds up; the brief's job was to say what happens if it doesn't, in advance, while nobody is emotionally invested in the person.

Confidence is moderate rather than high because the biggest assumption — that the declined work is repeatable — is the one the owner is least able to see clearly from the inside.

What the board weighed

Capacity is real; permanence is assumed. Five months of turning work away is a strong signal. But "I've been busy for five months" and "I will be busy for the next twelve" are different claims, and the second is the one a salary depends on. The board treated the first as a fact and the second as an assumption to test.

A first hire is a one-way door in disguise. On paper, employment has a probation period and can be ended. In practice, the person has left somewhere else, told their family, and turned down other offers. Reversing it costs them badly and costs you your reputation as someone to work for — and small businesses run on reputation. The board's answer was not "don't hire"; it was to find the smaller door: a fixed term, or part-time, with a review both sides know is coming.

The job has to exist before the person does. The most common first-hire failure is a role that was never defined, so the owner and the employee disagree about it from week two. "Write the five things this person does that you stop doing" is the whole test. If those five things can't be written, the business doesn't have a job yet — it has a feeling of being overwhelmed, which is a different problem.

The owner is the risk. Not the hire. Owners who've done everything themselves for years find handing over slower than doing it, and quietly don't. Three months later the employee has nothing meaningful to do and the owner is as busy as before, now with a salary to pay. The brief puts handover in the diary as a task, because things that aren't tasks don't happen.

If your situation differs

If the work is lumpy — busy quarters and quiet ones — the reversible version of this decision is a contractor, not a part-time employee. You buy hours against work that exists, and carry nothing in the quiet months.

If cash is tighter than six months, the CFO's dissent becomes the majority. A first salary on three months' runway is a bet that the hire pays for themselves almost immediately, which first hires rarely do while they're being trained.

If you already have a person in mind, be honest about whether the role is being written around them. That can work; it also means you're hiring a person, not filling a job, and the review at three months needs to ask whether the job turned out to exist.

The frameworks behind it

This decision turns on inversion — asking what would guarantee the hire fails produced every action in the brief — and on reversibility: the fixed-term start is the move that keeps a one-way door two-way while you find out whether the work is really there.