A prestigious term sheet can still be the wrong money when its growth conditions force a founder to abandon the market insight that made the product valuable. The decision comes down to one question: will the capital help you test that insight, or require you to replace it before the evidence is in?
At 4:17 on Monday afternoon, Kojo had the term sheet open beside a cold cup of coffee in Accra. Kojo is an invented composite, but the decision in front of him is familiar: accept funding from a famous foreign investor by close of business, or keep building with a runway that had already become uncomfortable.
One condition sat at the centre of the document. The company had to shift its next phase of growth toward larger European customers and report progress against that market.
The investor saw higher contract values. Kojo saw the removal of the one thing his team understood better than its competitors.
The condition changed the product
Kojo’s company helped small distributors turn orders arriving through calls and chat messages into records their teams could track. The software mattered, but the local insight came before the software: purchasing decisions rarely followed the tidy path shown in a sales deck.
A shop owner might ask about stock in a voice note. A distributor might confirm availability by phone. Payment evidence could arrive separately. Someone still had to connect those fragments before an order became real.
Kojo’s team had spent months learning where that process broke. They had watched staff copy information between conversations and spreadsheets. They had removed fields that looked essential in the product spec but slowed down the person trying to record an order. They had kept manual checks where automation produced confident mistakes.
The term sheet would fund more engineers, a European sales lead and several months of operating room. It would also make the local workflow secondary. To meet the investor’s conditions, Kojo would need to prioritise buyers with established procurement systems, formal integrations and cleaner data.
That looked like expansion on paper. In practice, it meant building a different product for a different problem.
I have seen the same tension appear when a promising deal asks for an architecture the current product was never meant to support. The difficult part is separating useful customer pressure from a request that redirects the company. I explored that distinction in what happens when a pilot requires an architecture your product does not support.
The famous name made the trade harder to see
By 5:06, Kojo had drafted an acceptance email.
The investor’s reputation carried its own argument. Future fundraising might become easier. Hiring might become easier. Other founders would recognise the name immediately.
Rejecting the offer carried a specific bad ending. Kojo could run short of cash before proving that distributors would pay enough to support the company. The investor might back a competitor. His team could spend the next year protecting a local insight that never became a durable business.
He left the email unsent.
Then he opened the operating model and changed one assumption: instead of treating the growth targets as financial milestones, he treated them as product requirements. Which customers would the team have to pursue? What would those customers ask the engineers to build? Which current learning loops would stop because nobody had time to run them?
The answer was clearer than the valuation.
Within two quarters, most product decisions would be judged by whether they helped win the foreign accounts named in the plan. The team would still describe Africa as its starting market, but its calendar, hires and roadmap would point elsewhere.
Money does not need voting control to redirect a company. Conditions, targets and reporting expectations can do the work quietly.
The decision was about evidence
At 5:41, Kojo called the investor.
He did not argue that the local market deserved loyalty. Loyalty would have been a weak basis for risking the company. He explained that the team had evidence about one operating environment and assumptions about the other. The term sheet required them to spend heavily on the assumptions while pausing the work producing evidence.
The investor held the condition.
Kojo declined.
That answer did not improve his bank balance. On Tuesday morning, the runway was still short, two hiring conversations were still paused, and the team still needed paying customers. Saying no preserved the question they had earned the right to answer: could their understanding of fragmented ordering become a product customers repeatedly paid for?
This is where founders can misread conviction. Protecting a roadmap does not mean refusing every large customer, foreign contract or investor request. It means knowing which uncertainty the company exists to resolve, then checking whether new money helps resolve it.
A term sheet should be translated into Monday morning work. Which meetings appear? Which customer gets priority? Which experiment disappears? Kojo’s earlier roadmap decision offers another way to examine those consequences before signing.
Write down what the money would make you stop doing
On Monday evening, Kojo closed the unsigned document and added one sentence to the team’s planning page: “We will test whether our local workflow insight can support repeatable distribution before we fund expansion into cleaner markets.”
That sentence was narrower than the investor’s vision. It was also testable.
Before accepting capital, write down the three activities the growth conditions will force your team to start. Then write down the three activities that will lose time, people or attention as a result. The second list often contains the real price of the deal.
Kojo returned to the office on Tuesday without the famous name on his cap table. At 9:10, he joined the product review and watched his team examine another order that had arrived in fragments. The company still had a financing problem.
It still had its reason for existing, too.
Comments
No comments yet.