Hiring affordability decision guide
Can I Afford to Hire Another Employee?
Salary is only part of the decision. A new hire changes payroll, employer costs, benefits, equipment, timing, and sometimes revenue or operating capacity. The useful question is what the hire does to cash and runway under realistic assumptions.
The complete hiring decision
Make the immediate cost and delayed benefit visible
Build the new cash outflow from every supported cost, place it on the proposed start date, and compare runway before and after. Keep any expected benefit in a separate, timed assumption.
What does the employee really cost?
Start with cash compensation, then add employer taxes or statutory costs, benefits, insurance where applicable, recruiting, equipment, software, workspace, onboarding, and any one-time fees. Use the amounts that apply to the business and jurisdiction rather than a generic percentage.
Separate one-time cash from recurring payroll. The onboarding laptop changes the start month; salary and recurring benefits change every supported month after the start date. If a cost is uncertain, show the range or assumption instead of hiding it in salary.
How much runway will the hire use?
Compare the current cash path with a second path that adds the fully loaded cost on the proposed start date. Review the resulting monthly cash, lowest point, net burn, and runway. Do not divide today’s bank balance by salary alone.
Current cash is not the same as unused credit, and visible cash may already support payroll, tax, vendors, tools, debt, and other commitments. Hiring affordability belongs inside that broader position.
What if the employee starts 30, 60, or 90 days later?
Moving the start date can preserve cash and create time to collect revenue, finish a milestone, or improve evidence. It can also delay the capacity the role is meant to create. Compare the same role at several start dates rather than treating hiring as a yes-or-no decision.
The runway improvement from delaying is not automatically equal to the delay. Existing burn continues while the company waits, so use a dated model instead of adding three months to the headline.
What if the role is expected to create revenue?
State what the role must do, when productive capacity begins, when a sale could occur, and when customer cash could arrive. A signed deal, recognized revenue, and realized receipt are separate states. Keep the expected benefit out of confirmed cash until the relevant state occurs.
Test at least a delayed-benefit case. A salesperson may need ramp time; a delivery hire may unlock billable capacity only after work is sold; an operations hire may protect existing revenue without creating a clean new-revenue line. The model should match the role’s actual job.
When should I delay the hire?
Delay can be prudent when the job is poorly defined, the assumed benefit has little evidence, cash is already committed, a near-term shortfall appears, or the business would lose too much room if customer timing slips. Delay is most useful when it creates a specific evidence or cash milestone.
When can hiring sooner make sense?
Hiring sooner can make sense when the work is clearly constrained, the business can carry the full cost through ramp, the decision fits the existing plan, and waiting would create a measurable operating cost. The case is stronger when the role and start date are explicit and the downside remains supportable without assumed revenue.
Decision variables
Build the hiring case from the cash up
A supportable decision shows the costs, dates, assumptions, and competing obligations instead of reducing affordability to salary or a single runway target.
Fully loaded cash cost
Salary plus applicable employer costs, benefits, tools, equipment, recruiting, and onboarding.
Start and payment dates
The proposed start date, payroll cadence, one-time purchases, and any delayed benefit dates.
Current commitments
Existing payroll, vendors, tax, debt, software, and approved obligations competing for the same cash.
Role effect
Whether the employee adds capacity, replaces another cost, protects delivery, or may create revenue later.
Downside case
The path if ramp takes longer, collections arrive late, or the expected benefit is lower than planned.
Worked hypothetical
Worked hypothetical: runway before and after a hire
A company has $960,000 in cash and a simplified net burn of $80,000 a month, implying 12 months of headline runway. A proposed employee has a $14,000 monthly fully loaded cash cost and $6,000 of one-time equipment and onboarding. No new revenue is included.
- Before the hire
- 12.0 months$960,000 divided by $80,000 simplified monthly net burn.
- Start immediately
- About 10.1 months($960,000 - $6,000) divided by $94,000 monthly net burn.
- Start after 90 days
- About 10.6 months totalThree months at $80,000, then ($720,000 - $6,000) divided by $94,000.
The later start preserves roughly half a month in this simplified path, while the immediate start creates capacity sooner. A separate scenario should model the role’s benefit and what happens if that benefit arrives late. This hypothetical excludes uneven receipts, taxes, and other dated obligations.
Decision framework
Founder and CFO hiring checklist
- 01
What is the fully loaded cash cost, including one-time and recurring items?
- 02
When does cash start leaving the business?
- 03
Is the role replacing an existing cost or adding a new cost?
- 04
Does the plan assume new revenue or capacity from the role?
- 05
When can that benefit realistically begin, and when could cash arrive?
- 06
What happens if the benefit or collection is late?
- 07
What known obligations compete for the same cash?
- 08
What does runway look like if the employee starts 30, 60, or 90 days later?
Applying the decision in RunwayCal
Model the hire without turning an assumption into current reality
RunwayCal supports explicit team costs, hiring timing, cash commitments, the current runway, and separate scenarios. Start from the recorded financial position, add the proposed role and date in a hypothetical path, and compare the cash and runway effect before changing the plan.
If the role is expected to create revenue or capacity, keep the amount, start date, ramp, and collection timing visible. RunwayCal calculates what the entered assumptions imply; it does not guarantee the benefit or recommend the hire.
Related questions
Questions that usually follow
Does every new hire reduce runway?
A hire increases cash outflow unless it replaces another cost. It may create value or future cash, but the cost usually begins before the benefit is certain. Model those states and dates separately.
How much runway should I have before hiring?
There is no universal threshold. Assess the fully loaded cost, current commitments, revenue timing, downside case, reversibility, and the financial room the business needs for its own uncertainty.
Should expected revenue offset the employee’s cost?
Show it in an explicit scenario with a realistic ramp and collection date, but do not treat expected revenue as cash already received. Also test the path if the benefit is delayed.
Can delaying a hire preserve three months of runway?
Not necessarily. Existing burn continues during the delay. A dated model will show the actual difference between start dates; do not simply add the delay to the current runway number.
What is the most important hiring assumption to test?
Test when the full cash cost begins and when the expected operating benefit can realistically affect cash. The gap between those dates is often the part the business must fund.
Related resources
Continue with the underlying concepts
Model the full hire before approving the start date.
Compare the current plan with the employee’s real cash cost, timing, and delayed-benefit case.
Explore Hiring Planning