Can My Business Afford Another Employee?

The part of a new hire I worry about most is usually not the salary.

It’s the gap.

Payroll starts on a date everyone can put on a calendar. The benefit of the hire rarely does.

A new salesperson may need months to build pipeline. An operations hire may create capacity before the company has sold enough work to fill it. A controller can improve the close almost immediately and still not “pay for herself” in any neat revenue line. A project manager may let the owner stop doing three jobs at once, which is valuable and annoyingly difficult to deposit at the bank on Friday.

Meanwhile, payroll is beautifully punctual.

That’s why, when a business owner asks me, “Can my business afford another employee?”, I don’t start by dividing the salary by twelve and looking at this month’s profit.

I want to see what happens between the first paycheck and the point where the reason for hiring the person actually shows up in the business.
Before committing to the hire, use my fully loaded employee cost calculator to estimate salary, payroll taxes, benefits, and overhead. Then put those costs into the cash forecast.

The offer letter is the easy number

Suppose you’re considering a $75,000 employee.

The first mistake would be treating $75,000 as the cost.

There are employer payroll taxes, benefits if you offer them, workers’ compensation, unemployment insurance, recruiting, equipment, software, training and whatever else the role requires. The SBA has long used a rough rule of thumb that an employee can cost about 1.25 to 1.4 times salary, although I’d use the actual costs for the company before approving anything.

For 2026, the employer share of Social Security is 6.2% on wages up to the applicable wage base, and Medicare is 1.45%, according to the IRS Employer’s Tax Guide. That’s before unemployment taxes, benefits, insurance and the rest of the supporting cast arrives.

So maybe the $75,000 employee is really a $95,000 decision. Maybe more. Maybe less.

That still isn’t the number I care about most.

I care about when each dollar leaves.

A profitable hire can still create a cash problem

This is where hiring decisions get strange.

Imagine a service business that has enough demand to justify another client-facing employee. Management expects the person to eventually support $180,000 of additional annual revenue.

Great.

Now put dates on it.

The employee starts November 1. Recruiting fees and a laptop hit before then. Salary and benefits begin immediately. November is mostly onboarding. December is useful but still light. By January the employee is doing real client work.

The first invoice for some of that work goes out in January.

The customer pays in February.

The economics of the hire may be perfectly sensible over twelve months while the cash curve looks much less charming in months one through four.

That’s the gap.

And I think businesses get into trouble when they answer a timing question with an annual number.

Annual revenue can cover annual payroll while February still becomes unpleasant.

I’d model the hire twice before I approved it

I’d want a base case and a slower case.

Not twelve scenarios. We don’t need to turn one job posting into a NASA launch.

In the base case, I’d put the real start date into the forecast, add the fully loaded cash cost, include the one-time costs and then model when the operational benefit is expected to begin.

If the role directly creates revenue, I’d separate four dates that people have a habit of blending together: when the person starts, when the person becomes productive, when the company earns the revenue, and when the customer actually pays.

Those are not the same date.

For a non-revenue role, I’d define what is supposed to change instead. Maybe overtime falls. Maybe outside accounting fees decline. Maybe throughput increases. Maybe the founder gets twenty hours a week back and can spend those hours selling. Maybe the hire reduces a risk the company has simply been lucky enough not to pay for yet.

Then I’d run the slower case.

What if productivity takes sixty days longer?

What if collections slip?

What if the expected sales lift is half the plan for the first quarter?

What if an existing customer leaves during the ramp?

I’m not trying to make the hire fail in Excel. I’m trying to find out whether the business can survive a version of reality that is less cooperative than the recruiting plan.

This is the same reason I like scenario planning for decisions that create a new fixed commitment. The useful question isn’t whether I can invent a downside. I always can. It’s whether a plausible downside changes the decision.

The lowest cash point tells me more than the bank balance today

A business can have $400,000 in the bank and still be in a poor position to hire.

Some of that cash may already belong, economically speaking, to taxes, payroll, debt service, annual insurance, inventory, a planned expansion or a miserable receivables month everyone knows is coming.

Conversely, a business with a smaller bank balance may be perfectly capable of adding someone because collections are predictable, margins are strong, existing operations generate cash every month and the hire has a short ramp.

The bank balance is a photograph.

Hiring is a movie.

I want to see the lowest projected cash balance after the hire, when it occurs, what assumptions got us there and how much room is left if one of those assumptions is wrong.

That is also why a generic rule like “keep three months of payroll” never fully satisfies me. It can be a useful reference point. It isn’t a substitute for understanding the company’s actual cash cycle. I wrote separately about how much cash a small business should keep in reserve, because the right buffer depends on what that cash has to survive.

Sometimes waiting is more expensive

There’s another side to this that gets missed when finance becomes too enamored with saying no.

Not hiring has a cost too.

If the owner is doing billing at 10 p.m. instead of selling, that matters. If a team is turning away profitable work because nobody has capacity, that matters. If overtime is climbing, customer response times are deteriorating or one employee has become the human version of a single point of failure, waiting can be the riskier decision.

I’d put those costs into the discussion instead of pretending the choices are “spend money” and “spend nothing.”

Sometimes the alternatives are hire now, hire in ninety days, hire part-time, use a properly classified contractor, automate part of the work, raise prices, stop accepting low-margin work or keep forcing the current team to absorb it until something gives.

Those are different financial decisions.

A good headcount plan should make those tradeoffs visible rather than treating every approved position as a row waiting for a start date.

The number I’d want before saying yes

If I had to reduce the whole hiring decision to one output, I wouldn’t choose ROI.

I’d choose the cash low point under a believable slower-ramp case.

Tell me that number, tell me the month it occurs, and tell me what has to go right to keep the business above it.

Then we can have a useful conversation about whether the hire is affordable.

Because “this person should pay for themselves within a year” may be completely true.

Payroll will still expect to be paid long before the year is over.

If you’re trying to decide whether the business can absorb a hire, expansion or other new fixed commitment, I can help build the forecast around the actual decision through FP&A consulting and decision support.