Rehearsing With a Mentor
Before meeting investors, founder Leo rehearses his pitch with experienced mentor Grace. She challenges his assumptions and helps him make the case more precise without losing its energy.
Dialogue12

Thanks for making time, Grace. I’ve got ten minutes before the investor meeting, so I’ll run the pitch as planned. Please stop me wherever it sounds vague or overconfident.
Gladly. And don’t optimize for sounding impressive; optimize for being credible. Start with the customer’s problem, and tell me how you know it’s urgent.
Small food distributors still manage deliveries through spreadsheets and phone calls. That creates missed orders and wasted miles. We interviewed forty-two operators, and most said coordination consumes hours every day.
“Most” is doing a lot of work there. How many described a measurable cost, and how many merely agreed that the process was frustrating? Investors will distinguish pain from purchasing intent.
Twenty-six could quantify late-delivery penalties or excess fuel costs. Eleven have agreed to paid pilots; six are active now. I should lead with those figures, not imply all forty-two are ready to buy.
Exactly. Now, you claim the software cuts delivery costs by eighteen percent. Is that an observed result, or a projection based on your model? Be precise about the distinction.
It’s an average from the six active pilots, comparing their first four weeks with the previous month. The sample is small, and one customer’s routes changed, so I can’t claim the product alone caused the entire reduction.
Good. That caveat won’t weaken the claim; it shows you understand attribution. What’s the strongest evidence that customers will keep paying once the pilot ends?
Three pilots have converted to annual contracts, and two more are reviewing proposals. The contracts are modest, but they show willingness to pay. I’ll avoid presenting pipeline as booked revenue.
Then make the investor’s decision easy to follow: costly problem, evidence of demand, early results, and what you still need to prove. Don’t bury the risks in a footnote.
Understood. I’ll keep the energy, but anchor every claim to what we’ve actually observed. If they challenge the small sample, I’ll say what we’re doing next to test whether the result holds.
That’s a stronger pitch—and a more investable founder. Go in curious, not defensive. A skeptical question is often an invitation to show how carefully you think.
Vocabulary8
- optimize for being credible
To focus on seeming trustworthy rather than merely impressive. Use this when explaining what quality you want to prioritize.
- purchasing intent
Evidence that potential customers are likely to pay for a product, not just that they like the idea. It helps distinguish interest from real demand.
- paid pilots
Small, paid trials that let customers test a product before making a larger commitment. The phrase can describe early commercial validation.
- attribution
The process of determining what caused a particular result. Here, it means working out how much of the cost reduction came from the software.
- willingness to pay
A customer’s readiness to spend money on a product or service. It is useful when discussing whether demand can become revenue.
- booked revenue
Revenue that has been formally secured or recorded, rather than revenue that may come from future deals. Use it to distinguish confirmed sales from pipeline.
- anchor every claim to
To connect each statement to specific evidence. This phrase is useful when describing a careful, evidence-based argument.
- go in curious, not defensive
Approach a challenging conversation with openness instead of treating questions as attacks. It is a useful reminder for interviews, negotiations, and presentations.
Key Sentences8
- 1
And don’t optimize for sounding impressive; optimize for being credible.
This concise contrast explains how to prioritize trust over showiness. Reuse the structure “Don’t optimize for X; optimize for Y” to emphasize a better goal.
- 2
Investors will distinguish pain from purchasing intent.
This sentence makes a useful distinction between customers having a problem and being ready to pay for a solution. You can adapt “distinguish A from B” to clarify two related but different ideas.
- 3
The sample is small, and one customer’s routes changed, so I can’t claim the product alone caused the entire reduction.
This is a careful way to state a result while acknowledging limits in the evidence. Reuse “I can’t claim X caused Y” when you need to avoid overstating causation.
- 4
I’ll avoid presenting pipeline as booked revenue.
This sentence shows how to distinguish potential deals from confirmed income. The pattern “avoid presenting X as Y” is useful for setting precise expectations.
- 5
Don’t bury the risks in a footnote.
This direct advice means important risks should be stated clearly rather than hidden in small print. You can use “Don’t bury X” to urge someone to make key information visible.
- 6
I’ll keep the energy, but anchor every claim to what we’ve actually observed.
This sentence balances persuasive delivery with evidence-based claims. Reuse “keep X, but anchor Y to…” when you want to preserve a quality while adding rigor.
- 7
If they challenge the small sample, I’ll say what we’re doing next to test whether the result holds.
This prepares a response that acknowledges uncertainty and explains the next step. The phrase “test whether the result holds” is useful when checking if early findings are reliable.
- 8
A skeptical question is often an invitation to show how carefully you think.
This reframes criticism as an opportunity to demonstrate thoughtful reasoning. Reuse the pattern “X is an invitation to show…” to present a challenge in a constructive light.