A hiring plan should stop when the new salaries shorten the time available to prove the next customer or product decision. Preserve the roadmap only when it still contains a credible path to revenue or validation; otherwise, protect the team and reduce the scope of what you plan to ship.
At 8:17 on a Monday morning, Tumi sat in a coworking space in Cape Town with two offer drafts open beside a spreadsheet. Her coffee had gone cold. One candidate would own the product interface, the other would help build the integrations customers kept asking for. She had planned to approve both before the weekly team call.
Then she changed one cell.
The new salary commitments pulled the runway forward far enough that the next fundraise would arrive before the product had completed its most important test: would a buyer pay for the workflow after seeing it in use?
Tumi had already told the candidates to expect an answer that morning. The bad ending had two versions. She could hire both, keep the roadmap intact on paper, and reach the next financing conversation with a larger team and no evidence that the product had earned its place. Or she could pause the hires, ask the existing team to narrow its work, and risk losing people who needed a clearer future than “we are being careful.”
Neither choice felt like good leadership at 8:17.
A runway calculation changes what a hire means
A hiring plan is often framed as a capacity decision. Two more people mean more product work gets done. That is true only if the work they unlock has a direct connection to the decision that keeps the company alive.
For Tumi, the two roles had been designed around a broad roadmap. More polished screens. More integrations. A version that could serve several customer types at once. The roadmap made sense during a period when the team expected capital to be easier to access. By Monday, the calculation had changed.
Early-stage capital tightening changes the meaning of every fixed monthly cost. A hire can still be the right call, but it needs a sharper reason than “we will need this person eventually.” The question becomes: what specific uncertainty will this person help us resolve before the company runs out of room to change course?
That is different from asking whether the candidate is strong. Both of Tumi’s candidates were strong. It is also different from asking whether the company can technically afford them this month. The harder question is whether the company can afford the decisions it will be unable to make later.
A founder who adds headcount before naming the next proof point can accidentally turn a product bet into an obligation. Soon the team is maintaining the work created to justify the team.
Preserve the decision that creates evidence
Tumi closed the offer drafts before the team call, but she did not cancel the hiring plan outright. She separated the work into two columns.
In the first column: work required for one buyer to use the product in a real setting, including the integration they had already asked for and the manual fallback the team could support themselves.
In the second: work that would make the product easier to sell later, but would not tell Tumi whether the buyer had a problem worth paying to solve now.
The first column stayed. Most of the second moved.
That distinction is uncomfortable because it forces founders to admit that a roadmap contains different kinds of work. Some work creates evidence. Some work prepares for a scale that has not been earned. Both can be valuable, but they should not receive the same protection when runway tightens.
This is where an AI product can become especially expensive to misjudge. A convincing demo may need more data connections, model evaluation, monitoring, and product polish before it reaches a customer. If the buyer’s underlying demand remains unclear, hiring to finish the demo can make the uncertainty harder to see.
The useful question is: what is the smallest version of this product that lets a real buyer make a real decision?
For a related example of that gap between a promising AI workflow and proof of buyer demand, see The Accra Workflow That Still Couldn’t Prove a Berlin Buyer Would Sign.
A smaller team needs a narrower promise
By midday, Tumi had rewritten the next six weeks around a single customer workflow. The existing engineer would build the required connection. Tumi would handle implementation conversations herself. The product designer role became a short contract for the screens needed in the trial, rather than a permanent hire built around the full roadmap.
This was not a neat solution. The team would move more slowly. A few useful requests would wait. The candidates might accept other roles. Tumi had to say those things plainly instead of disguising the pause as a strategic hiring process.
But the company had a clearer promise by the end of the day: one customer could use one workflow, and the team would know what happened when they did.
That is the trade worth protecting. A roadmap should earn its expansion through evidence, not through the pressure to keep new people busy.
Later that afternoon, Tumi sent one candidate a direct note explaining that the permanent role was paused because the company was narrowing its next customer test. The candidate thanked her for the clarity and said she would keep the door open. The other offer remained unsent.
The spreadsheet still showed less time than Tumi wanted. It no longer hid the choice.
Make hiring gates before the next urgent Monday
Write down the proof point each proposed hire must help produce. Use a sentence concrete enough to be disproved: “This person helps us get three active buyer workflows running,” rather than “This person helps us move faster.”
Then test the plan against the calendar. If the hire starts after the relevant customer decision needs to be made, their contribution belongs to a later stage. If the work can be completed through a contract, manual support, or a narrower release, keep the commitment reversible until demand is clearer.
Finally, give the team the real version of the decision. People can work through a narrower roadmap. They struggle when the company insists everything remains unchanged while the runway says otherwise.
The Monday hiring plan stopped because Tumi gave the next customer decision more protection than the original roadmap. By Friday, the team had a trial setup to build, one deferred offer, and a smaller set of promises they could actually keep.
Comments
No comments yet.