A vanished round changes the company’s job immediately: preserve the customer outcome that can create cash before payroll forces a worse decision. With eleven weeks left, the founder should stop spending against an expected term sheet and rebuild the plan around money already in the bank.
Monday began with payroll week in view and a term sheet expected after the weekend. By late afternoon, the investor had stepped back. No argument, no dramatic call. The fund had changed its view of the market, and the round was gone.
The company still had eleven weeks of cash. Its product had early users, a roadmap built around an engineering hire, and an AI demo that had impressed people in meetings without yet proving that anyone would pay for it. The first instinct was to keep moving. A delayed round can return. A promising conversation can become a new introduction.
But payroll does not wait for a promising conversation.
Eleven weeks is a planning constraint
The number matters because it turns abstract choices into dates. Eleven weeks is not enough time to run every experiment, make the senior hire, finish the demo, pursue a customer contract, and start another fundraising process.
The company had been treating the round as if it were cash. That is a common error because the work leading up to a term sheet feels like progress: partner meetings, diligence requests, calls with references, a draft in an inbox. None of it pays a salary.
Once the round disappeared, the real question was smaller and harder: what must this company deliver before the cash runs out?
For this founder, the answer was not the broader AI platform. It was one workflow already used by a small group of customers, where a painful manual step could be reduced with human review still in the loop. It was less impressive in a pitch deck. It was also the only part of the product with a credible route to paid use.
That distinction matters for founders building across Accra, Lagos, Berlin, London, or the US. A fundraising process can create a false sense that the next twelve months are already allocated. They are not. Until money lands, payroll belongs to the current bank balance.
Turn the roadmap into a cash decision
The founder paused the hire. That did not mean the engineering work disappeared. It meant the roadmap had to admit what the existing team could actually ship and support.
The remaining work went into three things: keeping current customers active, getting one paid implementation over the line, and measuring whether the narrow workflow saved enough time to justify a recurring price. Everything else moved into a list titled “after revenue or financing.”
That list included the polished demo.
It is uncomfortable to cut work that helped open investor doors. Yet a demo that generates praise without paid use can consume the same runway needed to learn whether a customer will buy. Kojo’s investor praise came with no cheque. Three interviews challenged his roadmap. makes the same point from a different pressure point: approval and demand are separate signals.
This is where founders can make the situation worse by treating every expense equally. Some costs protect a customer relationship or enable a payment. Others support a future story about the business. Eleven weeks requires a sharper distinction.
The payroll plan also needed to be discussed plainly with the team. No invented certainty about fundraising. No vague promise that the round was “still progressing.” People can handle difficult information better than they can handle discovering later that the company was spending from hope.
The eighth server problem
In 2012, Knight Capital deployed software that triggered unintended trading activity after an old code path ran on one server that had not received the update. The company lost roughly $460 million in a matter of days. The SEC’s account of the incident records the operational failure, and the event is a useful reminder that a system can look ready until one neglected assumption is exposed.
A term sheet can become that neglected assumption.
The spending plan might have made sense when the round was likely. On Monday, it no longer did. Leaving it in place would mean paying for a company that existed only in the forecast: the future team, the future product scope, the future runway.
Knight Capital’s problem was technical. The founder’s problem was financial. The mechanism is similar: an old assumption keeps running after the conditions that supported it have changed.
The corrective action is not panic cutting. It is an immediate reset. Freeze new commitments. List the next eleven weeks of unavoidable cash outflows. Identify the one customer outcome that can produce evidence of paid demand. Put an owner and date against every step required to reach it.
Revenue is evidence, not a consolation prize
A customer contract may not replace the full round. It can still change the next conversation with an investor, a partner, or a potential hire.
A paid customer says more than an enthusiastic pilot. It shows that the problem has a budget, that the buyer can make a decision, and that the product can survive contact with a real workflow. The work may expose limits in the product. Good. Those limits are cheaper to learn now than after a larger team has been hired around them.
The disclosed funding data across African technology companies is sobering: debt attracted more capital than Series A equity in one analysis of 1,146 rounds, and only 22% of companies with a first recorded round raised again during the observation window. The lesson is not to avoid venture funding. It is to keep the business legible when funding is unavailable.
By Friday, the founder still did not have a new term sheet. The company did have a smaller plan, a paused hire, and one customer workflow worth protecting. That was enough to make the next week real.
Comments
No comments yet.