A negotiated valuation tells you what investors agreed the company was worth for one transaction. It does not tell you how much cash reached the company, when that cash arrived, or whether the company can afford another engineer.
At 7:18 a.m. in Accra, Kofi read the funding headline while holding the payroll file open on his laptop. Kofi is an invented composite, but the decision is familiar: a founder with a small SaaS team, a promising AI feature and less cash than the public story suggests.
The article valued his company at $20 million. His bank balance could cover the current team for a limited number of months. The first investment payment had arrived, but legal costs, existing salaries, cloud bills and overdue product work had already claimed much of it.
An engineering candidate expected his answer before lunch.
If Kofi hired her, the company could build the AI workflow faster. If the next customer contracts slipped, that same hire could bring forward the month when he had to delay payroll. The headline made the company look rich. The payroll file showed how little room he actually had.
Valuation cannot pay an engineer
A valuation is part of a financing calculation. It sets the price investors pay for ownership. Payroll needs cash that has cleared into an account and remains available after current obligations.
Those two numbers can sit far apart.
A company may announce a large valuation after raising a comparatively small amount. Some of the round may arrive in stages. Fees and old commitments may reduce what remains. Investors may also expect the capital to support several priorities, including distribution, compliance, infrastructure and hiring.
I have seen founders begin making decisions from the public number. The valuation becomes permission to add a senior hire, move into a larger office or increase model spending. Yet none of those bills accepts equity value as payment.
The useful question is painfully plain: after the money arrives and every existing obligation is counted, how many payroll cycles can the company fund?
That number governs the hire.
The hiring decision starts with the failed sales case
Kofi’s model assumed two pending contracts would close. Both prospects had completed product calls. One had asked for revised terms. The other wanted an internal security review before making a commitment.
Neither had paid.
At 9:40 a.m., Kofi removed both contracts from the forecast. He also removed the expected revenue from a feature that had received encouraging demo reactions but no purchase commitment. The runway changed immediately.
The candidate still looked valuable. The timing no longer looked safe.
This is the part founders often resist because it feels excessively pessimistic. I see it differently. A hiring decision should survive the case where promising revenue arrives late. If the company can employ someone only when every open conversation closes on schedule, it has already assigned cash it does not have.
The same tension appears in Kabelo’s unproven demand, where one AI hire could force a choice between payroll and models. Technical capability can create momentum, but hiring ahead of evidence turns a product assumption into a recurring monthly obligation.
Kofi had to decide what evidence would justify that obligation. Demo enthusiasm was too weak. A signed agreement without cleared payment still left timing risk. He needed paid demand, or enough unrestricted cash to carry the hire if demand took longer than expected.
A smaller commitment can preserve the product decision
By late morning, the bad ending remained possible. Kofi could lose the candidate. Worse, he could hire her, miss the contracts and face a payroll decision before the AI feature produced revenue.
At 11:32 a.m., he changed the offer.
Instead of committing immediately to a full-time role, he proposed a defined paid project around the riskiest part of the workflow. The scope had a clear end. The candidate could assess the company through real work, and Kofi could test whether the feature changed a customer’s willingness to pay.
She could refuse. The company might still lose her.
That risk was cleaner than adding a salary because a funding article had made restraint feel embarrassing.
A staged engagement will not fit every role. Some product work needs continuity, ownership and deep context. The principle still holds: match the size of the commitment to the strength of the evidence. A reversible experiment belongs earlier than a permanent increase in burn.
I made a related distinction in the choice between Friday payroll and hiring an AI engineer before testing demand. Payroll is an obligation created by an earlier decision. A new hire creates the next one.
Build the plan from cash, timing and proof
Kofi finished the day without the certainty the headline implied. He had a valuable company on paper, a smaller amount of usable cash and a product bet that still needed proof.
His hiring plan now had three gates: the investment money had to clear, existing obligations had to be reserved, and customer evidence had to justify a larger engineering commitment. Until then, the project stayed narrow.
The next morning, the payroll file was still open beside the funding article. This time, Kofi closed the article first.
Comments
No comments yet.