Investor praise without a cheque usually means the demo has proved technical possibility, not customer demand. When runway is short, three focused customer interviews can produce a better fundraising story than another month of pitching the same assumptions.
At 6:40 p.m. in Accra, Kojo closed the fifth investor call of the week and stared at the message he had written in his notebook: “Impressive demo. Keep us updated.” His laptop was warm, his coffee untouched, and the product had performed exactly as planned.
Kojo is an invented composite, but the decision in front of him is familiar. He could spend another month asking investors to believe the market would appear, or cancel three pitch calls and speak to the operations managers he expected to buy the product. With limited runway, either choice could cost him the company.
Praise can hide the unanswered question
Kojo’s product used AI to review incoming purchase requests, flag missing information and prepare a recommendation for approval. In the demo, a messy request became a clean decision screen in seconds.
Investors liked the speed. One asked about expansion into Europe. Another wanted to know whether the underlying model could support other workflows. Nobody asked to invest.
That distinction mattered. The meetings had validated Kojo’s ability to build and present the product. They had not established that a buyer would change an existing process, allocate a budget and accept the operational risk of using it.
Praise made the situation harder to read because it felt like progress. Each positive call gave Kojo one more reason to improve the deck, add a feature or search for a warmer introduction. Yet the unanswered question remained painfully ordinary: who needed this enough to pay for it now?
A polished demo can delay that question. The product looks complete, so the founder starts treating demand as the final item to confirm. In reality, demand may still be the largest assumption in the company.
Three conversations changed the product
Kojo kept the three customer interviews. He asked each operations manager to show him the last purchase request that had caused trouble, rather than describe an ideal workflow.
The first manager barely cared about the recommendation screen. Her team already knew which purchases looked questionable. The problem was chasing missing attachments after a request reached an approver.
The second manager stopped Kojo halfway through the demo. She wanted to know who would be accountable when the AI made a recommendation based on incomplete information. A faster answer offered little value if her name remained attached to the decision.
The third showed him a request sitting unresolved in an email thread. The delay came from uncertainty over who had authority to approve it, not from the quality of the written request.
By the end of the third conversation, Kojo’s strongest demo feature had become secondary. The real job was helping a team gather the evidence, route the request to the right person and preserve a visible human decision. That pointed toward a smaller product with a less dramatic demo.
This is the uncomfortable value of customer interviews. They can remove the feature you were hoping investors would fund.
Kojo had already faced a related choice when deciding whether an automated purchasing workflow should act on its own. The reasoning behind adding human approval to an AI purchasing assistant applies here too: speed matters only after responsibility is clear.
Fundraising improves when the roadmap gets narrower
The interviews did not guarantee revenue. None of the managers signed a contract in the room, and Kojo still had to test whether the revised problem was urgent enough to earn a budget.
They did give him a more useful next step. Instead of building broader automation, he could test one workflow: collect the missing evidence, identify the approver and require a human decision before anything moved forward.
That narrower scope changed his fundraising material as well. His earlier pitch depended on a large market story and a smooth demonstration. The revised version could explain what three prospective buyers had shown him, which assumption had failed, and what he would test next.
An investor may still decline. But “we learned that buyers care about accountability before recommendation quality” carries more weight than “investors love the demo.” One describes evidence that changed a decision. The other describes a pleasant meeting.
This also protects runway. Another fundraising month consumes time even when engineering spend stays flat. Customer conversations can reveal that a planned hire, integration or feature serves a problem buyers rank third. That is why making the roadmap admit its limits can be more valuable than defending the roadmap you presented last month.
Make the next interview difficult to perform
On Friday morning, Kojo removed two slides from his deck and rewrote the prototype around the approval trail. The animation looked less impressive. The decision it represented was easier for an operations manager to challenge.
That is the standard I would use before booking another investor call. Choose three people close enough to the problem to reject your assumptions. Ask them to open a recent example, walk through what happened and point to the moment where money, time or accountability became exposed.
Do not ask whether they like the idea. Ask what they do today, who feels the cost, what happens when the process fails and which budget would cover a replacement. Then change something meaningful based on the answers.
Kojo’s next investor update was shorter. The product no longer promised to make the decision. It helped the right person make one with the required evidence in view.
His notebook still contained “Keep us updated.” Underneath it, he added three names and the next assumption each had agreed to test.
Comments
No comments yet.