How to Avoid Pitching in Customer Interviews

Pitching is the founder's most natural interview mistake. You booked the call because you care about the idea. The customer asks what you are working on. You want to give context. Suddenly you are explaining the product, the roadmap, the pricing logic, and why this will save them time.

It feels helpful. It is usually too early.

In discovery, pitching changes the subject. The conversation stops being about the customer's life and becomes a reaction to your proposed solution. That reaction can be friendly, detailed, and completely misleading.

The real damage

A pitch gives the customer a job: evaluate the idea. Most people try to be kind while doing that job. They say it sounds interesting. They suggest features. They compare it to tools they know. They ask whether it integrates with Slack.

Those responses are not worthless. They are just not the first evidence you need.

Before you pitch, you need to know:

• Did this problem happen recently?
• What did the customer do when it happened?
• What workaround exists today?
• What consequence made it painful?
• Who owns the decision to change?
• Has money, time, reputation, or political capital already been spent?

Once you pitch, it becomes harder to separate the customer's real world from your product frame.

A Hacker News discussion about learning sales captures the practical version of this: if the product solves a real problem, conversations become easier; if not, the founder needs to understand what people actually need. That understanding comes before persuasion.

What pitch mode sounds like

Pitching does not always sound like a demo. It often hides inside "context."

Bad:

"We are building a dashboard that automatically summarizes all your customer calls and flags churn risk. It connects to your CRM and helps managers coach the team."

Cleaner:

"How do you currently notice when an account is at risk?"

Bad:

"The product only costs $29 per seat, so it should pay for itself if it saves one hour a month."

Cleaner:

"Have you paid for anything to solve this problem before? What made that worth it or not worth it?"

Bad:

"Let me show you the prototype, then you can tell me what you think."

Cleaner:

"Before I show anything, can I understand what happened the last time this went badly?"

The repair is not silence. The repair is sequence. Learn first, pitch later.

Use a "no pitch until" rule

Set a rule before the call: no product explanation until you have at least one concrete story.

A concrete story includes:

• A specific recent incident.
• The steps the customer took.
• The people or tools involved.
• The consequence.
• The workaround.

If you do not have that story, you are not ready to pitch. You are still guessing what the pitch should be about.

This is especially useful for technical founders. Technical fluency makes it easy to explain. Discovery requires you to delay the explanation long enough to learn what should be explained.

How to answer "what are you building?"

You do not need to be evasive. You can be honest without turning the call into a pitch.

Try:

"I am exploring this space, but I do not want to bias you yet. Could I first understand how you handle it today?"

Or:

"There may be a product angle, but I am still trying to learn the problem. What happened the last time this came up for you?"

Or:

"Happy to share it near the end. First, can I ask a few questions about your current workflow?"

Most people accept that. If they do not, that is also signal. A customer who only wants to critique a solution may not be the right discovery conversation for the problem stage.

When pitching is allowed

There is a moment when pitching becomes useful. After you understand the customer's current situation, you can make a grounded offer:

"Based on what you described, we are testing a way to reduce the manual reconciliation step. It may not fit because your approval process sounds complicated. Want to see the rough version?"

That sentence is different from a blind pitch. It ties the product to what the customer already said, names uncertainty, and invites a next step without pretending discovery is already complete.

Sales matters. But sales built on weak discovery becomes theater.

How Vera trains this

In Vera, pitching is one of the highest-penalty interview traps. When the founder starts explaining features, defending the idea, or selling before learning, the AI customer reacts like a polite prospect. They may sound interested, but they stop giving the deeper evidence the founder needs.

That is the point. The customer conversation can feel good while the truth score falls.

A good practice rep is not one where the AI customer loves the idea. It is one where you learn to earn the right to pitch by first understanding the customer's world.