I walked into my first investor meeting prepared to pitch. I was not prepared to be stress-tested.
Every founder I spoke to before my first investor meeting told me to have my pitch deck tight, my market size number defensible, and my traction story compelling. I spent three weeks on the deck. I practised the pitch until I could deliver it in ten minutes or thirty, depending on the room. I felt as prepared as I knew how to be.
What nobody told me was that the investor I was meeting would not follow my script at all. Not because she was being difficult — because she was doing her job, which is to find the cracks in a founder's thinking before writing a cheque, not after.
How the meeting actually went
The first fifteen minutes went reasonably well. I covered the problem, the market, the product, and the early traction. She listened, asked a few clarifying questions, and seemed engaged.
Then she put down her pen and asked a question I had not prepared for.
She said: tell me about a founder who used your product, found it genuinely unhelpful or actively misleading, and did not convert. Walk me through what happened.
I froze. Not because I did not have that story — I had several. But because my preparation had been entirely oriented toward telling the story of what was working. I had rehearsed my wins. I had prepared to minimise my challenges. I had not sat down and seriously thought about what my failures could tell me about the product and the business.
I gave a clumsy answer about a founder who had churned early because the product was not yet at the stage of development it needed to be for their use case. It was technically true. It was also an answer designed to deflect rather than reveal.
She pushed. She asked what specifically did not work for them. She asked what I had changed in the product as a result. She asked whether I had spoken to them after they churned and what they said.
I had not spoken to them after they churned. I did not know what specifically had not worked because I had not done the work of understanding it. I had logged the churn, told myself it was an early-stage product quality issue, and moved on.
What she was actually testing for
She was not asking about failures to catch me out or to build a case against investing. She was trying to answer a specific question: does this founder understand their product well enough to learn from its weaknesses, or do they only know the story they want to tell?
Investors at the early stage are fundamentally making a bet on the founder's capacity to update their beliefs in response to evidence. A founder who only knows their wins has not demonstrated that capacity. A founder who can articulate clearly what went wrong, why, and what they changed as a result has demonstrated exactly that.
I understood this intellectually. I had not internalised it in a way that changed my preparation.
What changed after the meeting
The investor passed on the round. Politely, encouragingly, with a note that she would be happy to reconnect after I had more usage data. The standard decline.
But the conversation shook something loose in me. I went back through my complete user history — everyone who had signed up, everyone who had converted, everyone who had churned, everyone who had tried the product and not converted. I contacted every churned user and non-converted trial who I had email contact with. I asked one simple question: what specifically was the product not doing well enough to earn your continued use?
Sixteen people responded. The responses were uncomfortable to read. They also contained two clear patterns I had not seen before — patterns that pointed to specific product decisions I had made based on my own assumptions about what users needed, assumptions that turned out to be wrong.
I fixed both. One of them meaningfully improved my trial-to-paid conversion rate within thirty days. The other has become the basis for a significant product feature I am building now.
The investor who passed gave me something more valuable than a cheque. I go into every investor conversation now specifically looking for the question I cannot answer well — because that is where the next important piece of product work is hiding. It took me an embarrassing amount of time to learn that this is a gift rather than an attack.