A founder should pause fundraising when the company cannot explain how its recent customers found and chose the product. More investor meetings may produce a cheque, but they cannot repair an acquisition story the team does not yet understand.
At 4:40 p.m. on a Friday in Accra, Kojo stared at twelve investor meetings on his calendar and moved every one of them. Kojo is a composite founder, but the decision is familiar: the product worked, three customers were paying, and nobody could trace the path that brought them in.
One customer remembered a WhatsApp introduction. Another mentioned a demo, though two people had given demos that month. The third said they had “heard about the company,” which explained nothing. Kojo had planned to spend the following week discussing growth. He could not answer the first question beneath that word.
Three customers, no repeatable path
Kojo’s co-founder wanted to keep the meetings. Their runway was narrowing, and twelve conversations represented months of introductions, follow-ups and calendar negotiations. Cancelling them could mean losing investor attention precisely when the company needed cash.
That was the bad ending on the table. The meetings might never return. Without funding, the team could face a hiring freeze while an engineer was already carrying too much of the product.
Still, keeping the schedule created another risk. Kojo would enter each call with three customers presented as evidence of demand, while quietly treating their arrival as luck. An investor could ask which channel produced them, how long conversion took, who made the buying decision, or what happened between first contact and signed agreement. Each honest answer would be some version of “we need to check.”
I have seen founders compensate for that gap by making the story larger. A referral becomes “community-led distribution.” A founder’s personal relationship becomes “a partner channel.” Three unrelated sales become an early motion ready for capital.
The language improves. The evidence does not.
The question before the cheque
Fundraising can hide a customer knowledge problem because it gives the team a second audience to satisfy. The pitch deck becomes urgent. Customer interviews move to next week. A clean chart receives more attention than the messy sequence of messages, demos, objections and internal approvals that produced the sale.
Kojo needed to answer a narrower question: could the team deliberately find a fourth customer who resembled any of the first three?
That required reconstructing each journey from the beginning. Who first named the problem? What event made it urgent? Who introduced the company? Which message earned a reply? What almost stopped the deal? Why did the buyer act then rather than wait?
The exercise resembles the evidence gap in Kojo’s Customer Knowledge Gap. Six Months of Runway at Risk. The missing information often sits inside ordinary conversations, not analytics dashboards. A founder remembers closing the account but forgets which sentence made the buyer lean forward.
By Friday evening, Kojo had replaced the investor schedule with three customer calls and one internal review. There was no framework on the whiteboard. Each row held a customer name, a first credible contact, the person who pushed the purchase forward, the objection that nearly ended it, and the next action the team could repeat.
What the delay had to produce
Postponing twelve meetings only made sense if the delay changed the company’s knowledge. “We need more time” would have been avoidance. Kojo gave the pause a job.
For the next two weeks, the team would retrace all three sales and test one acquisition path. They would write down where each prospect came from before the demo, rather than after the contract. They would separate founder reputation from product demand. They would also record failed outreach, because a channel with one fortunate introduction and twenty silent prospects tells a different story from a channel that repeatedly starts serious conversations.
This distinction matters across Accra, Lagos, Berlin and New York. Early sales often travel through relationships before a company has a formal distribution system. There is nothing weak about that. The mistake is describing a founder’s private network as a process another person can run.
A similar tension appears when revenue itself pulls the product away from its intended direction, as in Pilot Contracts: How Kwame Protected the Core Product While Extending Runway. Money can extend runway while making the underlying decision harder to see.
The calendar filled again
Two weeks later, Kojo reopened the investor calendar. He still had only three paying customers. He had no dramatic growth curve and no claim that demand was proven.
He had something more useful: one customer path the team could attempt again, two paths dependent on personal relationships, and a clear account of where the evidence remained thin. Some investors would consider that too early. That answer was better than raising against a distribution story the company could not reproduce.
Before the first rescheduled meeting, Kojo opened the original calendar invite and removed the slide labelled “repeatable acquisition.” In its place, he added the next test, the person responsible and the signal that would count as progress.
The fundraise had stopped on Friday. The guessing had stopped with it.
Comments
No comments yet.