A full calendar can make a startup look healthy while hiding the one number that matters: customers who have agreed to pay. When investor conversations multiply but demand does not, protect time for customer work and treat every meeting by the decision it can produce.
Consider Sipho, an illustrative Cape Town founder building an AI tool for small logistics teams. At 7:40 on a Thursday morning, he sat at his kitchen table in Woodstock with cold coffee, six investor calls on his calendar, and a pipeline spreadsheet open beside them. His target needed nine more customers. None had signed.
Two weeks earlier, the meetings had felt like progress. One investor introduced another. A former operator offered to “compare notes.” A fund asked for a second conversation with a partner. Sipho ended each call with another name, another date, and the pleasant sense that his company was becoming visible.
Now payroll was approaching, the product still needed work, and the nine missing customers had become the difference between extending the runway and cutting the contractor who understood the system best.
The calendar rewarded the wrong work
Investor meetings gave Sipho immediate feedback. People asked thoughtful questions. They praised the size of the market. They suggested partnerships and sent warm introductions.
Customer work felt worse.
A prospect would describe the problem, then disappear after seeing the price. Another wanted an integration Sipho could not afford to build. A third liked the demo but would not involve the person who controlled the budget. Each conversation created more uncertainty rather than less.
That emotional difference matters. Investor calls can leave a founder feeling articulate and ambitious. Customer calls often expose the weak parts of the product, the offer, and the founder’s assumptions. One kind of meeting confirms the story. The other tests whether the story can survive contact with a budget.
I have seen this tension while building products across African, European, and US markets. The names and buying processes change, but the temptation holds. Visible activity is easier to defend than a quiet week spent hearing “no.”
Sipho’s calendar had become evidence of effort. It could not tell him whether anyone needed the product enough to pay.
Every meeting needed a decision attached
By midday, Sipho faced a choice. He could keep all six investor calls and hope one eventually led to funding. Or he could cancel four, risk appearing less available, and use that time to return to the prospects who had stalled.
The bad ending was clear. If he reduced the investor activity and still failed to close customers, he might reach the end of the month with fewer financing options and the same empty pipeline. The contractor would leave. A product issue only that contractor understood would remain unresolved.
For one long minute, the packed calendar looked safer.
Then Sipho changed the question he used to judge a meeting. He stopped asking whether the person was useful, impressive, or connected. He asked what decision could exist at the end of the call.
For customer conversations, the decision might be a paid pilot, a firm rejection, or access to the budget owner. For investor conversations, it might be entry into a formal process, a clear timing constraint, or confirmation that the fund would not invest at this stage.
Anything else was a conversation he could postpone.
This resembles the problem in Can an Investor’s Network Reach the Buyers Who Keep You Alive in Accra?. A network has value when it reaches the people who can change the company’s immediate position. The number of introductions tells you very little on its own.
Demand required harder evidence
Sipho cancelled four calls and reopened every stalled customer thread. He wrote down the exact point where each conversation had stopped.
Three prospects had never discussed price. Two had seen a demo without the budget owner present. One wanted custom work that would pull the product toward a single company. The remaining conversations had ended with polite interest and no agreed next step.
That list gave him more usable information than the investor notes.
He returned to the strongest prospects with a narrower offer: one operational problem, a defined pilot, and a decision date. He also asked the uncomfortable question earlier: who could approve payment?
This did not produce nine instant customers. It produced something more credible. Some prospects declined. One admitted the problem was irritating but not urgent. Another brought the budget owner into the next call. Sipho could finally separate demand from encouragement.
That distinction also protects the roadmap. A founder short on runway can mistake any potential contract for validation, then spend weeks building around one buyer’s internal process. Startup Pilot Strategy: How Ama Protected Her Product Roadmap From Custom Work explores the same risk from the product side.
Friday looked quieter and more useful
By Friday afternoon, Sipho’s calendar had blank spaces again. The pipeline still showed nine missing customers, but it no longer hid behind a row of meetings.
He had one prospect involving the person who could approve a pilot, two clear rejections, and a written record of why the others had stalled. The contractor decision was still unresolved. So was the runway. That honesty gave Sipho something activity had not: a basis for choosing what to do on Monday.
A founder cannot control when an investor becomes ready or when a prospect approves a purchase. A founder can control which uncertainty gets reduced next.
Open next week’s calendar. Beside every meeting, write the decision it could produce. If you cannot name one, give that hour back to the nine customers who are still missing.
Comments
No comments yet.