Can the Business Afford the Next Hire?
Hosted by Kelly Mattarocci, CPA
Being busy does not automatically mean you need another employee. In this episode, Kelly unpacks the full economic commitment behind a hire—compensation, complexity, management demand, and ramp-up time—and walks through a practical framework for deciding whether to hire, outsource, automate, redesign, or wait. You'll learn how to define the result a role must create, test assumptions before committing fixed cost, and ensure the business can carry the investment long enough to reach its ROI.
Key Takeaways
- ✔ Salary is not the cost of a hire—and affordability is not the same as making payroll
- ✔ How to distinguish a true capacity constraint from workload pressure
- ✔ The fully loaded cost of a hire: compensation, recruiting, technology, training, and complexity
- ✔ A four-part hiring framework: constraint, commitment, return, and alternatives
- ✔ Why hiring sits at the intersection of Visibility, Control, and Alignment
Full Transcript
Can the Business Afford the Next Hire?
The System of Money Podcast, where money stops being a mystery and becomes a system. Series 1, Episode 3, Can the Business Afford the Next Hire, hosted by Kelly Mattarocci.
[00:18]
Welcome to the system of money, where money stops being a mystery and becomes a system. I'm your host, Kelly Mattarocci. Last week we talked about the decisions your numbers should help you make. Not just what happened, but also what happens next. And one of the most expensive decisions a growing company makes is also one of the most emotional ones. And that's hiring. You're busy, the team, it's stretched, customers, they always want more. Things are being dropped. Someone says, We need another person. And suddenly a job description is circulating before anyone can clearly identify the actual problem. That's backwards. Being busy does not automatically mean you need another employee. Sometimes you do need another person. Sometimes you need a better process. Sometimes you need clearer accountability. Sometimes you need to stop selling work that creates activity that's destroying margin. And sometimes, frankly, you need to stop pretending your current team can absorb more responsibility without something breaking. Today, we're going to answer a deceptively simple question. Can the business afford the next hire? We're not going to answer it with payroll alone. Because salary, it is not the cost of a hire. And affordability, it is not the same as having enough cash in the bank to cover next Friday's payroll. The real question: can this business responsibly add the cost, complexity, management demand, and expectations that come with another person? And will that person create a result worth more than the resource the business has to commit? That is the decision, not could another set of hands help? Of course another set of hands could help. That is not the analysis. That is wishful thinking with a job posting attached.
[02:36]
Let's get into this. The hiring trap. Here is what usually happens. The business grows, work increases, response times grow slower, employees start working harder, the owner gets pulled into more details, small mistakes become recurring problems. Then along the way, someone says, We're at capacity. Maybe you are. But capacity is one of those business words people use when they want to end the conversation. We're at capacity. Sounds like a fact. Often it is only truly a feeling. And feelings, they do matter. They tell you where to investigate. They do not tell you what to approve. Before you add permanent cost, you need to understand what is actually creating the pressure. Is it demand consistently being higher? Is the company doing more profitable work? Is a key employee performing work far below their capability? Is rework consuming the team? Are approvals sitting with one person? Has the business added customers without removing low value expectations? Is the team using five manual steps because no one has redesigned the process? Or has the owner simply trained everyone to solve problems by adding people? That last one, it gets expensive fast. A hire can solve a real constraint. A hire can also hide a broken operating model. And hidden problems do not disappear. They get benefits, laptops, and a manager.
[04:33]
The first question is not who. The first mistake leaders make is starting with the person. We need a marketing coordinator. We need another salesperson. We need an operations manager. We need a CFO. Maybe, maybe you do. But titles create an illusion of clarity. Before you decide who to hire, define the business result needed. Not the task, the result. Those are not the same thing. A task sounds like manage the customer onboarding process. A result sounds like reduce onboarding from 21 days to 10 days while maintaining quality and increasing customer capacity by 30%. A task says, follow up with leads. A result says, Create a consistent follow-up system that increases qualified opportunities without requiring the owner to personally chase every prospect. A task says, help with the books. This is a dangerous one. Help with the books could mean data entry. It could mean monthly close. It could also mean correcting unreliable reporting. It also could mean creating forecasts. It could mean challenging capital allocation decisions. Those are not one job. They're not even the same level of thinking. If you cannot define the result, you are not ready to hire. You're ready to investigate. That may sound blunt, and that's good. A vague role is expensive for the company and unfair to the person you put in it. A person cannot succeed at a job leadership has not bothered to define. Then six months later, everyone is frustrated. The owner says, they're not strategic enough. The employee says, no one can tell me what success looks like. And both of them, they are right.
[06:46]
Something that is important to understand: a hire, it is not a salary. Let's deal with one of the most common misconceptions. A $90,000 employee does not cost $90,000. The salary, it's the obvious number. The real economic commitment includes compensation-related cost, recruiting, equipment, technology, training, management, attention, and ramp up time. Also, there's the cost no one puts into the budget, complexity. Every person added to a company increases the number of relationships, handoffs, decisions, and communication paths inside that business. That does not make hiring bad, it makes hiring consequential. When you add a person, you're not just buying 40 hours. You are changing the system. So stop asking whether the business can cover the salary and ask whether the business can carry the fully loaded investment long enough for the role to become productive and reach its ROI. That is a much better question.
[08:00]
Busy, it does not automatically mean hire. Here is a part that many owners miss. Hiring does not create full capacity on day one. The salary, it starts on day one. The value, it does not. A new employee requires recruiting, onboarding, training, management attention, and time to become productive. And most importantly, time to understand how the company actually works. That ramp up is part of the investment, not an inconvenience sitting outside. And the pressure leaders are feeling is real. According to Microsoft's 2025 Work Trend Index, 53% of leaders said productivity needs to increase. At the same time, 80% of the global workforce, including employees and leaders, said they don't have enough time or energy to do their work. That is real tension. The business needs more capacity. The people, they're already stretched. That doesn't automatically mean the answer is another employee. The same research found that 82% of leaders were confident they would use digital labor to expand workforce capacity within the next 12 to 18 months. And when leaders were asked about their workforce strategies, 47% identified upskilling existing employees as a priority. While 45% identified expanding team capacity with digital labor. That matters to this hiring decision. Because before you add a permanent headcount, you should know whether the work requires another employee, a better trained employee, a redesigned process, better technology, or some combination of the four. Do not use automation to avoid a necessary hire. But do not hire someone to perform work the business should first simplify, eliminate, or automate. A hundred thousand dollar employee is not merely a hundred thousand dollar salary decision. It is a commitment of money, management capacity, technology, training, time, and trust. The business does not win because it hires. The business wins because the role creates a result worth more than the total investment.
Source: Microsoft, 2025 Work Trend Index Annual Report: The Year the Frontier Firm Is Born, published April 23, 2025. Research included 31,000 workers across 31 countries, LinkedIn labor-market trends, and Microsoft 365 productivity signals.
[10:39]
Let's discuss a realistic business scenario. We're going to make this practical. Imagine a growing professional services company. Revenue, it's up, the team, it's busy. The owner is still reviewing proposals, approving schedules, stepping into client issues, and answering questions that should never have reached their desk. The leadership team recommends hiring an operations manager. The salary, it fits the budget. Technically, there is cash in the bank. The current forecast shows the company can make payroll. So the hire, it looks affordable. But let's take a closer look. Why is the owner overloaded? Is it because there's no operational leader? Maybe. Or is it because no one knows which decisions they're allowed to make? Are schedules being escalated because authority, it's unclear? Are client issues reaching the owner because service boundaries don't exist? Are proposals requiring approval because pricing is inconsistent? Is the team waiting for answers because the owner has made themselves the unofficial operating system of the company? If that is the real problem, hiring an operations manager without changing decision rights does not solve it. Now two people are waiting on the owner. Congratulations. You added payroll and preserved the bottleneck. That's not scaling. That is giving dysfunction an assistant. The role, it could still be the correct hire. But the result has to be bigger than take the work off the owner. The result, it may be create an operating structure in which scheduling, delivery expectations, and resource decisions are resolved at the appropriate level, reducing the owner's involvement in routine operations from 10 hours a week to three. Now we have something we can evaluate. Now we can define authority. Now we can establish metrics. Now we can assess whether the candidate has the judgment to create the result. And now we can determine whether the company is willing to let them do it. Because that is another uncomfortable truth. Some owners say they want a leader. What they really want is a highly paid employee who will make exactly the same decisions the owner would have made. That's not leadership capacity. That is an expensive limitation.
[13:20]
The fourth part of the hiring framework you can use for the next hiring decision. What constraint are we solving? What is the full economic commitment? Is hiring the best way to produce the results we want? Now let's walk through these. Question number one: What constraints are we solving? Do not start with workload. Begin with the constraint. Workload tells you people are doing a lot. A constraint tells you what is preventing the business from producing the results it needs. The constraint, it might be demand. The constraint might be capacity, perhaps it's capability, process, technology, decision authority, management, or strategy. Those are all very different problems. If there is not enough demand, another hire may make the problem worse. If demand is strong, but delivery capacity is genuinely limited, a hire may be necessary. If the team lacks a specialized capability, you may need expertise, but not necessarily a full-time employee. If the process is broken, another person may simply help the company perform the broken process faster. If technology can remove repetitive work, adding a person may be the slower and more expensive choice. If decision authority is the constraint, you may already have the right people in place. They just can't act. And if strategy is the constraint, do not hire someone into a business that has not decided where it's going. People cannot execute clarity leadership has failed to create. And if the answer is, well, at least everyone will be less stressed, be careful. Reducing unsustainable workload is a valid outcome. Burnout, it's expensive. Turnover, it's expensive. Poor customer experience, it's expensive. But even then, identify what work the new person will absorb, why that work exists, and how the business will know pressure has actually improved. Otherwise, workload, it expands to fill the new capacity. It always seems to find a way.
[15:30]
Question number two. What is the full economic commitment? Now we get a little financial, but not theoretical. Start with the fully loaded cost. Estimate everything the role requires in the first year. Compensation, payroll related costs, benefits, recruiting, equipment, software, training, professional development, travel, management time, outside support, and reasonable ramp up inefficiency. Then identify the timing. When does spending actually begin? Immediately? When should productivity begin? When should the role reach expected performance? What has to happen before the role can produce the intended result? This matters because even a good hire can create a cash problem if the timing is wrong. A role may be profitable over 12 months and still create a dangerous cash squeeze over the next 90 days. Profitability and cash timing, they are related. They're not identical. Then run at least three scenarios. Not because spreadsheets are magical, because one forecast is usually just optimism wearing a formula. Number one, expected. Demand continues reasonably close to the plan. The person ramps at the expected rate. The role delivers the intended value on schedule. Scenario number two, delayed. The ramp takes longer. Revenue, it arrives later. Training requires more time. The manager is less available than expected. Ask whether the business can handle the delay without creating a crisis. Scenario three, downside. Sales slow. A major customer leaves. The hire underperforms. The expected savings, they don't appear. The economy changes. Another business priority requires cash. And what happens then? Do you still have adequate reserves? Can the company meet its commitments? Does the hire leave the business with choices? Or does one disappointing quarter force a panic decision? A strong company does not evaluate a hire under only perfect conditions. It asks whether decisions remain survivable when reality is less cooperative, because reality rarely reads that forecast.
[18:00]
What should the role actually return? Once you understand the cost, define the return. Not every return will show up as immediate new revenue. That's fine. But it still needs to be observable. The return could be financial, operational, strategic, or risk-related. The key is that it must be observable. Or the ability to pursue opportunities the current organization can't absorb. Set a time horizon. What should be true after 90 days? After six months, after twelve months. Do not wait until the annual review to decide whether the investment is working. By then everyone has created a story. The employee has one, the manager has one, finance has one, the owner has one. And none of them are using the same definition of success. Define the evidence before the person starts. That is better for business. And it is better for the employee. They deserve to know the game they're being asked to win.
[19:30]
Is hiring the best way to produce the result? This is a question companies frequently skip. They directly move from we have a problem to let's hire someone. Hiring, it is one option. It should not be the default answer. For the result you need, the business may choose to hire. They may choose to outsource, perhaps automate, redesign, reassign, eliminate, or wait. Let's separate them. Hire. Hire when the need is ongoing, strategically important, substantial enough for a full-time role, and best performed by someone embedded in the organization. Hire when the company needs judgment, ownership, cultural integration, institutional knowledge, or leadership capacity. Outsource. Outsource when you need specialized capability, but not full-time capacity. This can be useful when the work is episodic, technical, easier to define through deliverables, or likely to change as the company grows. But outsourcing is not a magic way to avoid management. If it is still poorly defined, you have just moved the confusion outside the building. Automate. Automate when the work is repetitive, rules-based, consistent, and supported by reliable information. Let me say that again. And supported by reliable information. Do not automate confusion. A broken process performed faster, it is still a broken process. Adding technology without ownership often creates a second system of employees to work around. That is not innovation. That is a subscription. Wait. Wait when the evidence is not strong enough, the cash timing is wrong, the strategy may change, or the business has not committed to the conditions the role needs to succeed. Waiting, it is not avoidance when it is deliberate. But waiting without a test is just indecision. If you wait, define what evidence will trigger the decision. A demand threshold, a backlog level, a margin target, a cash reserve, a repeated capacity constraint, a signed contract, a measurable decline in service. Do not say we will revisit this later. Say we will approve this role when these three conditions are true. That's control.
[22:37]
The no surprise check. Before approving the role, I want finance, the hiring manager, and the executive sponsor to answer the same five questions. What exact business constraints are we solving? Number two, what measurable result will this role own? Number three, what is the full 12 month cost and cash timing? Number four, why is hiring better than outsourcing, automating, redesigning, reassigning, eliminating, or waiting? Number five, what conditions would cause us to delay, change, or stop this investment altogether? If the answers are different depending on who you asked, you don't have alignment. You have a job description. Those aren't the same thing. Do not hide behind unanimous enthusiasm. A leadership team can agree on a bad decision. Agreement, it's not evidence. What you want is shared logic, a clear assumption, a defined result, a known commitment, an accountable owner, a review point. That creates a decision the organization can manage even if the outcome is not perfect. Because mature leadership is not about pretending every hire will work. It's about making the reasoning visible, monitoring the evidence, and acting early when assumptions prove wrong.
[24:11]
Now, let's connect this to the system of money. Inside the system of money, hiring sits at the intersection of visibility, control, and alignment. Visibility means you understand the constraint, not just the noise around it. Control means the company can evaluate the commitment, timing, risk, and expected return before spending the money. Alignment means finance, management, and leadership agree on the result the role must create and the authority required to create it. This is not about making hiring colder. It's about making the hiring more responsible. A person, it is not a line item. They are making a career decision. Your company is making a strategic commitment. Both deserve more than we're slammed, let's get somebody in here.
[25:04]
All right, let's talk about this week's leadership exercise. I want you to choose one role your company is considering. Current opening, a planned hire, perhaps a replacement, maybe an executive role, maybe a contract or conversion. Any meaningful people investment. Then create a one-page hiring case. Write it down. What is the constraint? What is the business unable to do today? The result. What must become measurably different because the role exists? The alternatives. Could the company outsource, automate, redesign, reassign, eliminate, or wait? The full commitment. What will this role actually cost over twelve months? And the return. What financial, operational, strategic, or risk-related value should this role create? Lastly, the owner. Who is accountable for making the hiring successful? If you cannot complete the page, pause the posting. Not forever. Long enough to make the decision you're about to ask another human to bet their career on. That is not bureaucracy. That's leadership.
[26:27]
So in closing, can the business afford the next hire? Maybe. But do not let cash in the bank make the decision for you. Do not let an exhausted team make the decision for you. Do not let an ambitious manager make the decision for you. And definitely, do not let a beautifully written job description convince you the role is necessary. Start with the constraint. Define the result, calculate the full commitment, compare the alternatives, test the assumptions, then decide. Because the goal is not to build the largest team. The goal is to build the strongest business. More people can create more capability. They will also create more cost, more communication, more management, and more complexity. Headcount is not a trophy. And being able to make payroll is not the same as being able to afford the hire. A responsible hire should strengthen the business. It should not merely distribute the stress. Next week, we're going to talk about where profit disappears as the business gets busier. Because activity feels productive. Revenue, it looks impressive. And neither one of them guarantees that the business is becoming stronger. We will look at complexity, rework, discounting, unprofitable customers, poor handoffs, and the work your company keeps doing even though it stopped making sense a long time ago. I'm your host, Kelly Mattarocci. This week's System of Money Insight, do not hire a person because the business is busy. Hire when you understand the constraint, can define the result, and are prepared to give the role what success requires. Anything less, it's not growth. It is expensive improvisation. If this episode gave you a clearer way to evaluate your next hire, follow the System of Money Podcast now. That way next week's episode is waiting for you instead of buried under 50 shows you forgot to follow. And please don't just share this episode and disappear. If you want the practical questions and decision tools behind these conversations, sign up for the System of Money Insights at marketandmargin.com slash podcast. No more noise, not motivational fluff, practical tools for leaders building businesses worth owning. Because money is not just an outcome. Money is feedback. And when you learn how to interpret that feedback, you stop reacting, you start leading, and you begin transforming money from a source of stress into a system of control, into your system of money. See you next week.
Discussion Question
What is one role your company is currently considering? Can you clearly define the constraint it solves and the measurable result it must create?
