You are turning down work, answering emails at 11pm, and every part of the business runs through you. The obvious answer is "hire someone." The terrifying part is that a salary is the first cost you cannot switch off — you can cancel rent and software, but a person depends on you to make payroll every month. That asymmetry is why capable owners stay stuck long after they should have hired.
This guide replaces the gut-feel decision with a repeatable test: a readiness check, the true cost of an employee, the affordability math, and the two mistakes that sink most first hires.
The takeaway up front: hire when a specific bottleneck is provably costing you more than the true, fully-loaded cost of the person who would clear it — and when your cash, not your profit, can cover that cost through a slow stretch. Readiness is not a feeling or a revenue milestone. It is arithmetic plus an honest look at what is holding the business back.
Readiness is a bottleneck, not a revenue number
There is no magic revenue figure that means "now you can hire." A consultant billing a lot might need no one; a shop with thin margins might need a second pair of hands. The right trigger is a bottleneck — one constraint capping the whole business — and whether removing it pays for itself. Run the bottleneck test:
- Is the constraint persistent, not a one-off busy week? A single hectic month is overtime. The same overload every month for a quarter is a structural gap a hire can fill.
- Is it costing you real money or growth? Turning away orders, slow delivery losing customers, or you stuck doing $20/hour admin instead of $100/hour billable work are all quantifiable. "I'm tired" is real but isn't a number.
- Would the right person actually remove it? Sometimes the fix is a better process or tool, not a salary. Hiring to paper over a broken system just gives you a broken system with payroll.
If the constraint is persistent, costly, and genuinely solved by a person rather than a process, you have a candidate for a hire. If not, fix the process first — it's cheaper.
The true cost of an employee (it's not the salary)
The biggest reason first hires sink a business is that the owner budgets for the salary and forgets everything stacked on top of it. The wage is the floor, not the cost. A fully-loaded employee costs meaningfully more once you add:
- Employer taxes and mandatory contributions — payroll taxes, pension or social contributions, statutory insurance. They vary by country but are rarely trivial.
- Benefits and leave — paid holidays and sick days mean you pay for more days than they work, plus any health cover you offer.
- The cost to employ, not just to pay — equipment, software seats, a desk, and the hours you spend recruiting, onboarding, and managing.
- Ramp-up time — almost nobody is fully productive on day one; budget weeks before they pull their weight.
A practical rule of thumb: take the base salary and add roughly 20-30% to estimate the true annual cost. The exact loading depends on your jurisdiction and benefits, so confirm the local figures — but never plan against the bare salary. The gap between "salary" and "cost of employment" is where over-optimistic founders get caught. This is general guidance, not tax or legal advice; check your country's rules before you commit.
Can you afford it? Use cash, not profit
A profitable business can still be unable to afford a hire, because profit and cash are not the same thing — the timing of money in and out decides whether you can make payroll. That distinction is the subject of the small business finance guide. Test affordability against cash with three checks:
- The runway check. Could you pay this person's fully-loaded cost for three to six months from cash on hand if revenue dipped? A salary is a recurring, non-cancellable commitment; you need a buffer for a bad quarter.
- The break-even check. How much extra revenue — or freed-up billable time — must the hire produce to cover their true cost? Put a real number on it, then ask honestly whether they'll hit it.
- The slow-month check. Model your worst realistic month, not your average. If the salary still clears with the buffer intact, you can afford it. If affordability depends on every month being good, you cannot — yet.
Employee or contractor? Make the call deliberately
Before committing to a full employee, ask whether the work even needs one. A contractor is the lower-risk way to clear a bottleneck without the fixed, ongoing burden of payroll.
Lean contractor when the need is project-based or variable (busy seasons, occasional specialist skills), when you want to validate the role before committing, or when you can't yet absorb the fixed cost of payroll through a downturn. Lean employee when the work is ongoing, core, and daily, when you need control and consistency (set hours, your processes, your standards), or when retention matters and you're investing in someone who grows with the business.
One caution: this line is also a legal classification. Someone who works set hours, under your direction, on core work indefinitely likely is an employee, and misclassifying them to dodge taxes carries real penalties — confirm local rules rather than picking the cheaper label.
The two mistakes that make a first hire fail
Even with the math right, first hires fail for two avoidable reasons.
Hiring too late, for too much. Owners cling on until they're drowning, then try to clone themselves with one expensive "do-everything" senior hire — a role that's hard to fill and costly to get wrong. The better first move is to offload your lowest-value, most repetitive tasks, freeing your time for the high-value work only you can do. Hire to remove the bottleneck, not to replace yourself.
Hiring without a role to step into. Bring someone in with no defined responsibilities and nothing written down, and you'll spend more time managing chaos than you saved. Before they start, write the simple version: what they own, what "good" looks like, and the three or four core tasks they take off your plate in month one. A first hire needs a job, not just a desk.
FAQ
What does an employee really cost beyond their salary?
More than the wage. On top of base pay you carry employer taxes and mandatory contributions, paid leave and benefits, equipment and software, and recruiting, onboarding, and management time. As a planning rule, add roughly 20-30% to the salary, then confirm the exact figures for your jurisdiction.
Should I hire an employee or a contractor first?
Use a contractor when the work is project-based or variable, when you want to validate the role first, or when you can't yet carry a fixed payroll cost through a downturn. Choose an employee when the work is ongoing and core, you need control and consistency, and you want someone who grows with the business. The classification is also a legal one — confirm local rules.
Can I afford to hire if I'm profitable?
Not automatically. Profit is an accounting result; affordability is about cash and timing. Check whether you could cover the full cost for three to six months from cash if revenue dipped, and whether the salary still clears in your worst realistic month. If it only works when everything goes right, wait. This is general guidance, not financial advice — run your own numbers.
What should my first hire actually do?
Usually not "everything you do." The most reliable first hire takes your lowest-value, most repetitive tasks off your plate — admin, scheduling, routine fulfilment — freeing you for the high-value work only you can do. Define what they own and what good looks like before they start; a hire without a defined role creates more work than it saves.
Next step
Decide by arithmetic, not by feel. Name the one bottleneck capping the business, then run the number: take the salary you'd offer, add 20-30% for the true cost of employment, and test it against your cash through a deliberately bad month. If the math survives and the role clears a persistent, costly constraint, write the job description and hire. If it only works on a good month, fix cash or start with a contractor. Build the rest of your operating playbook at dominerbusiness.com.
