The overseas contract should be paused or repriced when the full cost of fulfilling it exceeds the revenue it brings in. A founder needs to count delay, rework, and the people pulled from the roadmap before calling a contract “cash flow.”
On Friday afternoon, Kofi sat at a table in Accra with a shipment ledger open beside a cup of tea he had stopped drinking an hour earlier. This is an illustrative composite, but the decision is familiar. Three days of border delays had turned a delivery that looked profitable on the signed contract into one that required more cash, more calls, and more staff time than the invoice could recover.
The shipment was still moving, but the customer had begun asking for updates every morning. Kofi’s operations lead had already spent two evenings tracing paperwork. The engineer who was supposed to finish an onboarding change for the product had been pulled into building a temporary tracking view for the overseas client.
The bad ending was no longer abstract. If the goods arrived late, Kofi could lose money on the contract and weaken trust with a customer he had worked hard to win. If he walked away, he risked looking unreliable in a market where overseas contracts can feel too valuable to question.
Revenue had hidden the real cost
The ledger showed the contract value in one column. It did not show the cost of being stuck.
There were the direct expenses: additional handling, storage, calls to intermediaries, and work that had to be repeated because a document passed through too many hands. Then there were costs that rarely appear in the first version of a forecast: a founder’s attention, a team’s interrupted week, and a product release that loses its clean window because the people who own it are now solving a logistics problem.
That last category matters most for a small company. A larger business may be able to assign someone to manage a delayed shipment. A small team often has one person who understands the workflow, one engineer who can fix the exception, and one founder who has to decide which disappointed customer gets an answer first.
I have learned to treat these as real costs, even when they do not produce a receipt. A contract can pay on time and still consume the capacity required to build the thing that will make the next twelve months better.
That tension sat underneath the Friday contract that bought twelve months, and what it cost the AI release. Cash can extend runway. It can also quietly redirect the company.
The border changed the unit economics
Kofi’s first estimate assumed a normal journey. That assumption was the margin.
Once the shipment paused, every decision around it became more expensive. The team was no longer fulfilling a repeatable order. They were managing an exception. Exceptions create their own work: explaining status to a customer, checking which information is current, deciding whether to absorb an added cost, and trying to protect a relationship without promising what nobody controls.
The useful calculation on that Friday was simple:
Revenue from the contract, minus direct fulfillment costs, minus the cost of delay, minus the work displaced from the core business.
The final two terms are harder to estimate, so founders often leave them out. That makes the contract look healthier than it is.
Kofi wrote down what the team had postponed that week: the onboarding change, two sales follow-ups, and a customer conversation that could have clarified whether the product’s next feature was worth building. He did not claim each item had a precise value. He only needed to see that the contract’s headline revenue was funding work that was pulling the company away from its own direction.
A pause can protect the relationship
By late afternoon, Kofi had stopped trying to make the original terms work. He called the customer with a narrower proposal: finish the shipment already in motion, share the actual status without optimistic promises, and pause any further orders until both sides agreed on a delivery structure that could survive a delay.
That conversation carried risk. The customer could decide that another supplier was easier. Kofi could lose future revenue at the exact moment his company wanted more of it.
But continuing under terms that guaranteed a loss would have created a different kind of failure. It would have taught the customer that his team would absorb every unpredictable cost. It would also have taught his own team that the roadmap was negotiable whenever a contract became noisy.
The turn came when the customer accepted the completed shipment and agreed to revisit the arrangement before placing another order. There was no victory lap. The next deal still needed better assumptions, clearer ownership, and room for disruption.
On Monday, the engineer returned to the onboarding work. Kofi reopened the ledger with a new rule beside it: every overseas contract gets a delay scenario before anyone calls its margin real.
Build the downside into the decision
A border delay is only one version of the same founder problem. The overseas client, the large integration, the urgent custom request, and the paid pilot can all look like progress while they pull scarce people into work that does not compound.
Before accepting the next contract, name the condition that would erase the margin. It may be a delayed shipment, a customer approval that never arrives, a dependency outside your control, or one key person being unavailable for a week.
Then decide what happens before the condition appears. Price for it. Set a pause point. Put one person in charge of updates. Define which roadmap work cannot be traded away without a deliberate founder decision.
Kofi’s revised ledger did not make the next shipment safer. It made the choice clearer. The contract would need to carry the cost of being complicated, or the company would keep its people on the work only it could do.
Comments
No comments yet.