A loan only extends runway when the business can make its first repayment without relying on the release it is funding. If repayment arrives before revenue can plausibly land, the debt has converted a product bet into a fixed cash deadline.
In April 1970, Apollo 13’s crew had a problem with no spare time built into it. An oxygen tank failure forced Jim Lovell, Jack Swigert and Fred Haise to use the lunar module Aquarius as a lifeboat. Carbon dioxide was rising, and the command module’s square filter cartridges did not fit the lunar module’s round system. NASA’s Mission Control had to devise an adapter from materials already aboard, then get the instructions to the crew while there was still time.
NASA’s Apollo 13 history documents the episode because the constraint mattered more than the original mission plan. The crew returned safely on April 17. The rescue depended on solving the immediate bottleneck, not on continuing as though the planned landing still set the timetable.
A repayment date works the same way. It becomes the bottleneck. The product roadmap may still be sensible, but cash now has a deadline that does not care how close the release feels.
The repayment date changes the decision
Six weeks of runway creates pressure. An offer of debt can feel like an answer because it gives the team more calendar time to ship.
Then the repayment schedule arrives.
If the first payment lands before the next release can earn revenue, the relevant question changes. The founder is no longer deciding whether the release is worth building. They are deciding whether existing cash, contracted income, or a conservative revenue case can carry the repayment if the release slips, adoption is slower than expected, or a buyer takes longer to approve.
That distinction is easy to miss when the offer is framed around the total amount. The total is less important than the first payment date, the monthly obligation, and the cash buffer left after payroll, infrastructure, tax, contractors, and the work needed to support existing customers.
In 2025, African tech funding reached $4.1 billion, with growth driven mainly by larger tickets and record debt activity. That does not make debt wrong for an early-stage company in Accra, Lagos, Johannesburg, Berlin, or the US. It makes the repayment mechanics worth reading with more care. Debt is often priced around certainty that a young product has not earned yet.
Build the downside case before accepting
The useful model is painfully plain: remove the release revenue from the spreadsheet.
Keep the current revenue. Keep signed contracts only where the delivery and payment timing are clear. Add the full debt obligation. Then ask what the company looks like if the release earns nothing for another quarter.
If that version forces you to miss payroll, stop customer support, or take a distracting contract at a bad margin, the loan has not bought freedom to build. It has bought a new emergency.
I would also separate “can ship” from “can collect.” A product can be ready for a demo and still be months from a paid deployment. Buyers may need an internal owner, security review, procurement approval, or proof that the workflow has accountability before they commit. That gap has derailed more plans than the build itself. Ama’s polished demo. No pilot until the workflow had a clear owner. is a useful reminder that product readiness and buying readiness move on different clocks.
Choose the constraint you can survive
Sometimes debt still makes sense. It can fund work attached to a signed customer contract, cover a known receivable gap, or preserve a release that already has committed buyers and a credible collection path.
The terms must match that reality. A first repayment after expected collection is a different instrument from one that arrives while the product is still looking for demand. So is a facility that can be drawn against confirmed invoices rather than a lump sum that starts charging immediately.
The harder choice may be smaller: pause part of the release, reduce the scope to the workflow a buyer will pay for first, or take revenue work with a clear boundary around the roadmap. None of those options feels clean when runway is short. They may still protect the company’s ability to make the next decision.
That is why the overseas contract question and the debt question often sit beside each other. Both can buy time. Both can also consume the attention needed to create the product revenue meant to replace them. The Friday Contract That Bought Twelve Months, and What It Cost the AI Release examines that trade more directly.
Put the payment on the roadmap
Before signing, add every repayment to the same roadmap that contains product milestones. Put it beside the beta date, customer implementation work, payroll, and expected collection dates.
Then name the action you will take if the release is late. Cut contractor spend? Sell a smaller paid implementation? Pause a feature? Renegotiate before the payment is due? The answer needs to exist before the money lands, when there is still room to act.
Apollo 13 did not get home by insisting on the original mission. The crew and Mission Control focused on the constraint that could end the mission first. A founder considering debt should do the same: protect the payment date before treating the loan as runway.
Comments
No comments yet.