A hiring plan in a financial model works best when each hire is tied to the bookings that pay for it, instead of a fixed start date. Then a low sales case pushes hires back on its own, the way a founder would in real life.
The company sells a safety service to schools and other large sites. It installs safety hardware on site and runs it for the customer as a managed service, on contracts that last several years. We'd built its financial model earlier in the year, ahead of a planned Series A.
In the spring the plan changed. Venture investors wanted to see more traction first, so the founder set out to raise a smaller bridge to carry the company to the next round. One investor had a plain question. If you only hit half your sales plan, how long does the money last?
Every hire had a date
Like most early models, ours put a start month next to every role. The first version showed a whole executive team joining in month three. When we read the model the way an investor would, we wrote 56 due diligence questions. One asked how likely it was to hire eight or more vice presidents in four months. Another said the forecast had one case and no downside.
A start date doesn't care how sales are going. If bookings come in slow, the dated hire still joins and the salary still lands. So a low case built on dates shows revenue falling while spending stays put. No founder runs a company that way, and an investor knows it.
The quick fix that broke something
The first fix was to push the hires out. The founder moved most of them to month 12, after the planned Series A. On the next call we found the catch. Sales in the model were driven by the number of sales reps. Moving the reps out also moved the sales out. Public school bookings fell to almost nothing for a year, even though the founder and an early rep were already selling to schools.
We added a separate driver for sales the founder brings in. We also kept year one on its own tab, filled in from the real contracts and the months their cash is due. Deals still in the pipeline sit behind a switch the founder can turn on or off.
A hiring plan tied to bookings
Then we changed how hiring works. In the latest version, 51 roles in the headcount table carry a bookings trigger in place of a fixed date. A role is hired in the month the company's bookings first reach its threshold. Some roles have up to three thresholds, so a second or third hire follows as the company grows. Roles the company would fill no matter what, such as the senior hires planned for the raise, start as soon as the Series A arrives.
The thresholds read one attainment dial on the dashboard. Turn the dial down and the sales plan shrinks, and the hires slide later on their own. The founder doesn't have to edit 51 rows to build a downside.
Fixing the cash on the way
Services deals had shown all their cash in the year they were booked. We split them into a deposit up front and a balance on completion. A margin chart had been built on bookings, which made the first year look profitable when it wasn't. We rebuilt it on cash.
What we built
- Bookings triggers on 51 roles, read from one attainment dial
- A year one tab built from real contracts, with pipeline deals behind a switch
- A pre-Series A dashboard and a runway chart that runs from this raise to the next one
- A tab for testing cash changes, and an option to fund the hardware with an asset-backed loan
- A five-case scenario deck at 100%, 80%, 70%, 65% and 50% of the sales plan. Each case has its own cash low point and break-even month
What changed
Before, the model had one answer, and the founder had to rewrite it by hand to get another. Now the investor's question takes one move. Set the dial to half and the costs follow the sales, the way they would in real life.
Don't give a hire a date. Tie each one to the bookings that pay for it, and your low case will show the company you'd really run.
Questions founders ask
How do you build a hiring plan in a financial model?
List every role in a headcount table with its salary. Then, in place of a fixed start month, give each role a trigger, such as the month bookings first reach a set level. Roles you'd fill no matter what, like senior hires planned for a raise, can start when the money arrives. When sales come in slow, the hires slide later on their own, and costs follow sales the way they would in real life.
How much revenue should each employee generate at a startup?
There's no single right number. It depends on the business, and software companies usually run higher than service or hardware companies. Early on, revenue per employee is low because you hire ahead of sales. What investors check is whether the plan hires faster than bookings can pay for. Tying each hire to the bookings that pay for it keeps that ratio believable in every case, including the low one.
When should a startup hire its first salespeople?
Most founders sell first, then add a rep once they know who buys and why. In the model, don't make every sale depend on reps. In this case, sales were driven only by the number of reps, so moving the reps later wiped out a year of school bookings. We added a separate driver for sales the founder brings in, and let later sales hires follow bookings thresholds.