When to Make Your Next Hire: A Cash-First Decision Framework
Most founders hire reactively. Someone burns out, a client complains about slow turnaround, or a new opportunity shows up that you don't have the capacity to handle. You hire. You figure out the math later.
That's not a strategy. It's triage. And it's one of the most common ways businesses between $1M and $10M quietly destroy their margins.
The question "when should I hire?" deserves a real answer — one grounded in cash position, not urgency or optimism.
Start With the Cash Reality, Not the Revenue Story
Revenue growth feels like permission. It isn't.
Revenue is a promise. Cash is what you actually have to work with. Before any hiring decision, you need to know three things with precision:
1. Your current runway. How many months of operating expenses do you have in the bank right now, at your current burn rate? If the answer is less than three months, you have no business adding payroll.
2. Your receivables lag. If your average collection period is 45 days, you can be "profitable" and still not have the cash to fund a new hire's first paycheck. Know the gap between when you earn revenue and when you collect it.
3. The fully loaded cost of the role. Not the salary. The salary plus payroll taxes (roughly 8–10% for the employer side), benefits, equipment, software, and onboarding costs. A $70,000 salary hire realistically costs $85,000–$95,000 in year one. Model that number, not the one on the offer letter.
The Capacity Utilization Test
Before hiring, answer this honestly: are you actually out of capacity, or are you out of efficient capacity?
A team running at 60% utilization with a bottleneck in one role doesn't need a new hire — it needs a process fix. A team running at 90%+ sustained utilization across billable or productive hours has a real capacity constraint.
The utilization test is simple:
Track hours or output for 30 days
Calculate actual productive output vs. available capacity
If utilization is consistently above 80–85% for 60+ days, you have a defensible case for headcount
Below that threshold, you may be solving a workflow problem with a payroll decision. That's an expensive mistake.
The Payback Period Question
Every hire should be evaluated like an investment: what's the expected return, and how long until it pays back?
For revenue-generating roles — salespeople, account managers, client-facing staff — the math is relatively direct. If a new account manager can handle $300,000 in annual recurring revenue and costs $90,000 fully loaded, you're looking at a 3.3x revenue multiple on their cost. The question is how long it takes to ramp them to full capacity. If ramp time is six months, you're carrying $45,000 in cost before they're producing at target. Model it.
For operational or support roles, the return is indirect — it shows up in retention, capacity unlocked in higher-value roles, or reduced error rates. That's harder to quantify, but not impossible. Ask: what does this role free up? If hiring an ops coordinator frees the founder to do $200,000 more in business development or client work per year, the coordinator's $65,000 cost is an easy call.
If you can't articulate the payback period — even roughly — you're not ready to make the hire.
The 13-Week Cash Flow Test
Here's the practical gate I'd apply before any hire: build a 13-week rolling cash flow forecast that includes the new position.
Plug in the fully loaded weekly cost. Model your revenue collections realistically — not optimistically. Look at what happens to your cash balance in weeks 4, 8, and 13. If the forecast shows your cash dropping below one month of operating expenses at any point in that window, you need to solve that problem before hiring.
This isn't about being overly conservative. It's about not letting an enthusiasm-driven hiring decision become a cash crisis three months later. The 13-week forecast makes the risk visible before it's real.
When Waiting Costs More Than Hiring
There are cases where delay is the more expensive choice.
If a key employee is actively burning out and at flight risk, the cost of losing them — recruiting fees, training time, client disruption — likely exceeds the cost of the support hire that would have prevented it. If you're consistently turning down work because you don't have the capacity to deliver it, every week of delay has a real revenue cost.
The framework doesn't say never hire. It says: know what you're deciding. Quantify the cost of hiring and the cost of not hiring. Make a deliberate choice, not a reactive one.
Vera's Take
The founders I see get in trouble aren't the ones who hire too aggressively — they're the ones who hire on a revenue projection that never came in, without stress-testing the cash impact. A hire based on "we're tracking to $2M this year" is very different from a hire based on "we have $2M collected and in the bank." Know which one you're making. And build the 13-week forecast before you post the job description, not after you've made the offer.
If you want this applied to your business — running the numbers on your next hire, building the cash flow model, or pressure-testing your headcount plan — that's what Vera CFO is for.