Hiring your first employee, and how it differs from later

By the time a business hires its tenth employee, roles are reasonably well bounded: there is an existing team, established processes, and a gap with an identifiable shape. The first hire is the opposite. What they end up doing is everything that does not yet have an owner, and that set changes month to month as the business changes.

This has a direct consequence for what you should be looking for. Hiring narrowly for a specific skill is a reasonable strategy when the role is stable, and a poor one when the role's contents will be different in six months. What matters more in a first hire is adaptability and judgement — whether they can take an unfamiliar problem, work out what needs doing, and do it without a defined process, because for a while there will be no defined process for most of what arises. It is worth being honest about this in the job description rather than writing a tidy specification you know is provisional. A candidate who reads that the role will shift as the business grows, and finds that appealing, is far more likely to succeed than one attracted by a clean list of duties that will not survive the first quarter.

In practice the qualities that carry a first hire are assessable, though not through a resume. Whether they can work without an established process: ask what they did in a situation where nobody had told them how something should be done. Whether they ask before assuming on things that matter, and act without asking on things that do not, which is the judgement that determines how much supervision they will need. Whether they will say when something is beyond them rather than improvising, since in a business with no colleague to check with, an improvised answer to a customer can do real damage.

Also worth weighing: tolerance for ambiguity, which is genuinely uneven across people and is difficult to develop. Someone who needs clarity to work effectively is not deficient, and they will be unhappy as employee number one. A small realistic task is more informative than any interview question here — something loosely specified, where you can see what they do with the gaps. Whether they ask clarifying questions first, make reasonable assumptions and state them, or produce something confidently wrong tells you most of what you need, and none of it is visible from an interview conversation alone.

The most common founder error with a first hire is expecting the relationship to run the other way — that hiring someone will relieve pressure automatically, and that a capable person will work out what to do. What actually happens is that a new employee with no context, no processes and no colleagues to learn from generates questions, needs decisions, and takes time before they contribute. The first weeks usually cost you more time than they save.

This is not a sign of a bad hire, it is the shape of the transaction, and expecting otherwise leads to resentment and to a new employee who senses they are a disappointment for reasons nobody can articulate. The founder's work here is real: deciding what the person owns, being available for questions without treating them as interruptions, and stating what good looks like. You still own the outcomes — the business's results remain yours after hiring, and delegating work does not delegate responsibility for whether it goes well. Where a first hire fails, the cause is very often that nothing was ever specified, nobody was available to ask, and the person was left to infer a job. That is a founder's failure with an employee's consequences.

Taking on a first employee changes the legal and administrative character of the business, and this is the part most often discovered late. You become responsible for paying wages on time and keeping records of having done so, for issuing terms of employment in writing, and for whatever registrations and statutory contributions apply to an establishment of your type and size.

The specifics matter here and general articles are the wrong source for them. Provident fund and employees' state insurance obligations in India are triggered by thresholds — based on the number of persons employed, and in some cases on a wage ceiling — and those thresholds, the contribution rates and the registration procedures are set by notification and change. India's four labour codes were notified into force on 21 November 2025, consolidating a large number of earlier statutes, so anything written before then may describe a superseded framework. Rather than reproducing figures that may be out of date, the reliable step is to ask an accountant or an employment adviser which registrations your business needs now, at your size, in your state. That conversation costs little relative to the cost of discovering an obligation retrospectively, with arrears attached.

Whatever the statutory position, some administrative groundwork has to exist before the first salary is paid, and it is much easier to establish it at the start than to reconstruct it later. A defined pay date, and the discipline of meeting it, which matters more to an employee than almost anything else you do. A payslip showing the components of pay and any deductions. A record of what was paid and when, kept in a form that survives.

Set up how tax and any statutory deductions will be handled before the first payment rather than after, because retrospective corrections are unpleasant for the employee and generate distrust immediately. Collect and keep the documents you are required to hold, and keep them somewhere appropriately private. It is also worth deciding your approach to leave — how much, how it is requested, what happens to unused entitlement — before it is asked about, since an ad hoc answer to the first leave request becomes the precedent whether you intended it or not. None of this is difficult, and all of it is considerably cheaper to establish for one employee than to retrofit across five once habits have formed.

A first employee changes the business in ways worth considering before advertising. Somebody now depends on you for their income, which constrains decisions you previously made freely — a lean month is no longer only your problem. It commits you to a monthly obligation that does not flex with revenue, which is a genuinely different risk profile from operating alone. And it commits your time to managing, which is work that does not disappear once someone is competent.

It also sets precedents. How you handle the first person's pay, leave, hours and expectations becomes the baseline for everyone after them, because the second employee will find out what the first was given and any difference will need justifying. Deciding these things deliberately for one person is easy; unpicking casual arrangements once there are four is not. None of this argues against hiring — most businesses cannot grow past their founder's capacity without it. It argues for deciding two things first: what specifically moves off your desk, and whether the revenue supports the commitment without depending on a month that has not happened yet. Both are decisions no adviser or tool can make for you, and both are where first hires most often go wrong before anyone is even interviewed.