A promising WhatsApp request becomes evidence of demand only when the customer takes the next costly step, such as sending money, signing an agreement or sharing required records. Silence after “send” reveals the gap between wanting an outcome and accepting the risk needed to get it.
At 9:17 on a humid Accra morning, Kojo was holding a mug of tea and reading a message from someone who wanted to buy crypto before noon. Kojo is an invented composite, based on a pattern founders encounter when a lively conversation reaches the point of commitment.
The buyer had arrived with urgency. He asked which assets were available, how quickly the transaction could happen and what details Kojo needed. Each reply came within a minute. Kojo began treating the request as an order.
Then he sent the payment instructions.
The typing indicator appeared, disappeared and appeared again. No transfer followed. By lunchtime, Kojo had sent one careful follow-up. The message showed as delivered. The conversation stopped there.
The request felt more valuable than it was
Kojo had already made a product decision before the money moved. He was considering whether to spend the afternoon tightening the transaction flow, because the morning request seemed to confirm that customers wanted a faster way to buy.
I understand that temptation. A detailed WhatsApp conversation feels close to revenue because the customer supplies context, asks practical questions and creates a deadline. The founder starts solving the request in real time.
But conversation has almost no switching cost. A buyer can ask about availability while comparing three other sellers. They can agree to proceed before remembering that the money sits in another account. They can want the asset and still distrust the transfer method.
The hard part begins when the customer must expose something: money, identity, internal approval or reputation.
Until then, the founder has evidence of interest. That evidence matters, but it cannot carry the same weight as commitment.
“Send” introduced the real product
Kojo initially thought he was offering access to crypto. The silence showed that the customer was also evaluating trust, timing and the possibility of losing money.
That changed the question in front of him. “How do I make this faster?” was premature. He first needed to learn what made the buyer stop.
There were several plausible explanations. The customer may have lacked funds. The payment instructions may have felt unfamiliar. The exchange rate may have changed the decision. He may simply have chosen someone else. Kojo could not honestly select one explanation from silence.
So he did something less satisfying than building. He recorded the transaction as incomplete and wrote down the last action the customer took. Then he changed the next conversation.
Instead of waiting until the final message to surface the commitment, he asked earlier whether the buyer was ready to transfer funds that morning and whether the proposed payment method worked for them. A hesitant answer would save both sides a long exchange. A clear answer would move the transaction closer to the point where trust could be examined.
This is the same discipline behind testing demand before making an expensive hire, as I explored in Should I Hire a Senior Engineer or Spend Six Months Proving Demand?. Move the costly decision closer to the evidence.
Build around completed commitments
A founder can easily turn Kojo’s morning into a dashboard full of flattering activity: one inbound lead, several messages, a quoted transaction and strong stated urgency.
None of those measures tells him why the transfer did not happen.
A more useful record follows the customer through observable commitments. Did they confirm the amount? Did they accept the payment method? Did they move money? If they stopped, what was the final completed step?
That sequence gives a small team somewhere concrete to investigate. Three conversations that stop after payment instructions may justify testing a different trust signal or payment process. Three conversations that stop before the amount is confirmed point somewhere else.
The shared spreadsheet matters here because informal sales conversations lose their shape quickly. By Friday, the founder remembers enthusiasm more clearly than hesitation. That is one reason the shared spreadsheet a demo did not account for can contain more truth than the polished workflow around it.
This approach also protects runway. Kojo does not need to automate every message or commission a new transaction system because one buyer went quiet. He needs enough comparable attempts to locate the repeated point of refusal.
The next morning starts with a better test
Kojo’s bad ending remained possible: he could spend his limited runway fixing speed while buyers were actually stopping because they did not trust the handoff. A faster path to the same silence would leave him with less cash and no better explanation.
The turn came when he treated the failed transfer as product evidence instead of a sales annoyance. He moved the commitment question earlier, recorded the last completed step and resisted inventing a reason for the silence.
The following morning, another WhatsApp request arrived. Kojo still answered the practical questions. This time, before planning his day around the transaction, he asked whether the buyer was ready to move the money using the proposed method.
His tea was still warm when he reached the question that mattered.
Comments
No comments yet.