An investor’s promise of introductions only matters when it connects a founder to a named buyer with a real reason and authority to purchase. Asking “Who is one likely buyer, and what happens after you introduce us?” can expose the difference between useful access and a hopeful contact list.
Kojo, a composite Ghanaian founder, tested that difference on a Friday afternoon in Accra. His laptop battery was low, rain had started hitting the windows, and his small team needed a decision before Monday: keep building the reporting feature their investor said would “open doors,” or use the remaining runway to fix onboarding for the customers already trying the product.
The name that would settle the roadmap
For six weeks, the investor had repeated the same promise. Once the feature was ready, he would introduce Kojo to companies in his network.
The promise had influenced product meetings. Kojo’s engineer had postponed two smaller fixes. A contract designer had prepared screens for the new reporting flow. The team had begun talking about potential buyers as if they were waiting behind a closed door.
On Friday, Kojo asked a narrower question.
“Can you name one company that would likely buy this, and the person there who owns the problem?”
The investor paused. He mentioned a large business where he knew a senior executive, then admitted he did not know whether that executive controlled the relevant budget. He suggested another company, but the relationship belonged to someone he had not spoken with recently. A third name came up as a possible fit, although nobody had confirmed that the problem was urgent.
There was no buyer waiting. There were people the investor might contact.
That distinction put Kojo’s roadmap at risk. If the team spent another month building for an assumed purchasing path, they could reach the end of their runway with a polished feature and no qualified conversation. The smaller onboarding problems would still be there, quietly costing them the demand they had already earned.
Access has to survive five concrete questions
An introduction becomes commercially useful when someone can describe the path after the email. Kojo wrote five questions in his notebook:
- Who experiences the problem strongly enough to act?
- Who can approve spending?
- Why would they consider solving it now?
- What evidence would they need before a pilot?
- What happens if the first contact says no?
The investor could not answer them yet. That did not make him dishonest. It meant the promise had been treated as evidence before anyone had tested it.
Founders often hear “I can introduce you” during fundraising, accelerator sessions and partnership meetings. The phrase feels valuable because it compresses an uncertain sales process into one reassuring sentence. The actual work remains hidden: finding the budget owner, confirming urgency, earning an internal referral, surviving procurement and giving the buyer enough confidence to begin.
A famous contact can help with the first email while having no control over the next decision.
This is why a named company still provides weak validation. The founder needs a plausible purchasing path, not a logo for the pitch deck. The same discipline applies when evaluating investor momentum. In the twelve investor meetings Kojo moved, the pause matters because activity and progress can look identical until a decision forces them apart.
The call changed before the product did
Kojo stopped asking for broad access. With the weekend approaching, he proposed a smaller test.
He would send the investor a short description of the problem, the type of person who usually owned it and three questions that contact could answer without sitting through a product demo. The investor would forward it to one person who fit that description. No feature presentation. No request for a pilot. Kojo wanted to learn whether the problem existed inside that business and whether someone had authority to pursue it.
This turn arrived before the team committed another month, but only barely. The engineer was due to begin the reporting work on Monday.
The investor agreed to try. He could not promise a reply, which was precisely the point. Kojo now had an experiment with an observable result instead of access described as an asset.
He also changed the internal rule. Introductions would influence the roadmap only after a buyer confirmed the problem, its urgency and the next step. Until then, the team would treat every promised connection as a lead to qualify.
That rule protects more than engineering time. It keeps founders from borrowing confidence from someone else’s reputation. A warm email may reduce the distance to a conversation. It cannot create purchasing authority, budget or urgency.
Make the introduction earn the build
On Monday morning, Kojo’s engineer opened the onboarding backlog instead of the reporting branch. The team fixed the point where prospective customers were dropping out and left the proposed feature in a short decision document.
Nothing dramatic had been won. The investor still had to make the introduction, the contact could ignore it, and any eventual buyer could reject the product. Those uncertainties were finally visible.
Before changing your roadmap around promised access, ask for one likely buyer and map the next three steps after the introduction. If nobody can describe those steps, keep the promise in the sales pipeline and out of the engineering schedule.
Comments
No comments yet.