Can You Afford to Hire? The Fully-Loaded Math Most Founders Skip

Every founder I work with eventually says some version of the same thing: "I think we are ready to staff up." It usually arrives when the team is stretched, the inbox is overflowing, and the owner is doing three jobs at once. The instinct is right. The math behind it is almost always wrong.

The reason is simple. Most founders price a hire at the salary number. That number is the smallest part of the real cost, and the salary alone tells you almost nothing about whether the hire makes sense. The better question is not "can I cover the paycheck." It is "what does this person need to produce, and how long until they pay for themselves." Here is how I walk owners through it.

"What does this hire actually cost me?"

When a founder tells me a role pays a certain amount, I add a quiet multiplier in my head, because the salary is the sticker price, not the out-the-door price.

A real hire carries a stack of costs on top of the wage. There are payroll taxes and statutory contributions that land on every paycheck. There are the tools and software seats that person needs to do the work. There is hardware, a workspace if you have one, and the benefits or perks you offer to stay competitive. Then there are the costs nobody puts on a spreadsheet: the hours you and your team spend interviewing, onboarding, training, and answering questions for the first few months.

Add it all up and a hire commonly costs meaningfully more than the salary line suggests. A marketing agency owner once told me a new role was a modest monthly commitment. When we mapped the full picture, software seats, a recruiter fee, and the senior person pulled off billable work to train the new one, the true first-year cost was a different conversation entirely. None of it was hidden. It was just never added up.

So the first move is always the same. Build the fully-loaded number. Salary, plus the payroll costs on top, plus tools, plus the onboarding time priced at what that time is worth. That is the number you are actually deciding on.

"Should I add a contractor or make a full hire?"

Once founders see the loaded cost, the next question follows naturally. Do I need to commit to a full hire, or can a contractor solve this.

The honest answer depends on the shape of the work. A contractor fits when the need is specific, the work has a clear scope, and the volume is uneven. You pay for output, you scale it up and down, and you carry far less fixed overhead. A full hire fits when the work is continuous, when it requires deep context about your business, and when you need someone fully inside the operation rather than renting a slice of their week.

The trap is choosing the contractor purely because the hourly rate looks cheaper than a salary. A higher hourly rate on a contractor can still cost you less overall, because you are not carrying the payroll costs, the tools, the downtime between projects, and the management overhead of a permanent seat. A software startup I worked with kept resisting a contractor because the rate felt expensive. On a loaded basis, the contractor was the cheaper path for a year, and it bought time to confirm the role was permanent before committing to it.

Rule of thumb: hire permanent for the work that is always there. Contract for the work that comes in waves.

"If I add this person, does the math still work?"

This is the real question hiding under "can I afford it," and it is the one that separates a confident hire from a hopeful one.

A hire has to do one of two things. It either generates new value, more revenue, more output, more capacity to take on work, or it saves value, freeing up expensive time, cutting a cost, removing a bottleneck. Sometimes both. Before you sign anything, you should be able to say out loud what this role is supposed to produce in dollars of value, even roughly.

Here is the framing I give founders. Take the fully-loaded monthly cost of the hire. Then ask what this person needs to generate or save each month to cover that cost. If the role is revenue-generating, how many units of work, how many clients, how many sales does that translate to. If the role is a cost-saver or a time-freer, what does the time you get back let you earn or build instead.

A construction company owner wanted to add an estimator. On its own, the salary felt heavy. But when we framed it as capacity, the estimator would let the owner bid on more jobs and stop turning work away, the value the role unlocked was several times its loaded cost. The math worked, and more importantly, the owner could see exactly why.

"How many months until the hire pays for itself?"

Naming the value is half of it. The other half is time, because almost no hire pays for itself on day one.

Every new person has a ramp. They are learning your systems, your customers, your standards. For the first stretch they cost full price and produce a fraction of their eventual output. So the right question is not just "does this pay off," it is "in how many months." A payback measured in a small handful of months is comfortable. A payback measured in many months means you need to be sure the cash can carry the gap, and sure the role is permanent enough to justify the wait.

This is where cash and profit part ways. A hire might be clearly profitable over a year and still strain your cash for the first few months while they ramp. You need to fund the ramp out of real cash, not the value you expect them to create later. A beverage brand I worked with had a profitable hire on paper that would have run their cash uncomfortably low during the ramp window. We adjusted the start date by a quarter, let collections catch up, and the same hire became a calm decision instead of a tight one.

"How do I know my team has room before I add more?"

Before adding anyone, it is worth a quick look at whether your current team is genuinely full or just busy. Those are different things.

Capacity is how much productive work your team can do. Utilization is how much of that capacity is actually going toward valuable work. A team can feel slammed while a real share of its hours goes to low-value tasks, rework, or things that should be automated. If that is the picture, the first hire might not be a person at all. It might be a tool, a process fix, or reassigning who does what.

You do not need a complex system to see this. A simple monthly view of where the team's hours actually go is enough to tell whether you have a capacity problem or a focus problem. Solve the focus problem first when it exists. It is faster and cheaper than a hire, and it makes the next hire land on a cleaner foundation.

Hiring from a plan, not from hope

The difference between the founders who hire well and the ones who regret it is rarely the salary they could afford. It is whether the hire came from a plan or from a feeling.

Hiring from hope sounds like this: we are slammed, this person seems great, we will figure out the value once they are in. Hiring from a plan sounds like this: here is the fully-loaded cost, here is what the role generates or saves, here is the month it pays for itself, and here is the cash that carries the ramp. Same hire, two completely different decisions.

If you can answer the four questions above, you are ready. If you cannot, the answer is not no. It is not yet. Build the number first, and the hire stops being a gamble and starts being a move.

Peter Xia is a CPA and fractional CFO. He shares finance breakdowns for founders on @CanadianCFO.

Next step: run your numbers through the free CFO scorecard.