How to Run Customer Conversations That Qualify Deals
Most deep tech founders skip discovery and jump straight to demos. Here's the playbook for running customer conversations that separate real pain from polite interest — so you stop wasting POCs on the wrong prospects.
We’d run the proof of concepts (POCs), we’d validated that our tech had worked, we’d sacrificed runway to invest in making this one work for the customer we needed to win.
On demo day, everything went well - the customer engineering teams told us they were satisfied, even the big boss came out to congratulate us.
Then, nothing. For months and months we waited patiently to hear about that prized production contract we wanted to get our tech - CloudMade’s ML platform - into cars. When our patience ran thin we started calling our contacts, asking them what was going on.
Over the next few weeks the truth came out - the tech team who we thought were the decision makers who could get us into cars were really one part of the picture. Before we’d make it into production we’d have to talk to dozens more teams from product marketing, to sales, to production engineering, to purchasing. We were nowhere near, and our revenue forecasts pushed out by years.
We weren’t building a sales pipeline. We were subsidising our customers’ R&D.
Should We Waste Time Asking Questions?
None of the founders I talk to are intentionally sabotaging their growth. But put in front of a customer, most revert to sales mode - pitching their product, selling their vision. When founders do try to ask open questions, they’re often met with evasive customers who don’t have the answers.
What I see is a paralysis rooted in fear. Founders know they should be having deeper conversations, but they’re afraid of asking the wrong thing, to the wrong person, and losing the opportunity.
A founder told me this candidly: “Can we be honest with [customers] and [ask to] speak to different teams to understand [their] problem? Or is that going to react poorly? I don’t know.”
That’s real. It’s the sound of a founder who’s afraid asking the wrong questions will destroy the deal.
But here’s the thing: asking the right discovery questions builds the deal. It’s what separates founders who sell to 10% of their pipeline from founders who sell to 40%.
Sell The Outcomes Customers Need
Without discovery, you can’t tell the difference between two very different conversations:
Tech pull: “That’s a really clever solution. Our engineers would find this interesting. Let’s explore it.”
Solution pull: “We’ve been losing money to this problem for two years. It’s our highest-priority blocker for scaling. Let’s see if your solution works.”
They sound the same in the moment. Both lead to “let’s do a POC.”
But the first customer will spend 6 months in proof-of-concept mode, learning your technology, because the conversation was always about the technology. The second customer will spend 6 weeks because they care about the outcome, not the learning process.
Discovery is what lets you tell the difference before you offer a POC.
The Five Questions That Actually Work
You need a set of questions that cut through politeness and surface real pain. Here are five that separate signal from noise:
1. What is this problem costing you in dollars, today?
Green flag: A specific number. “We’re losing about $2M a year to this inefficiency.” Or timeline-based pain: “We lose 3 months every cycle because of this bottleneck.”
Red flag: “Well, we’re not sure exactly…” or “It’s hard to quantify.” That’s not pain. That’s an interesting problem.
2. If nothing changes, what happens in 12 months?
Green flag: Concrete consequences. “We’ll miss our production targets and lose the contract.” Or “We’ll have to hire three more people at $150K each.”
Red flag: “We’ll probably figure something out” or “We want to stay competitive.” That’s polite concern, not business pressure.
3. Who else controls whether you move forward on this?
Green flag: “It’s me and the VP of Operations” or “The CFO needs to sign off.” You get names and titles. You understand the decision structure.
Red flag: “Probably the executive team will decide” or vagueness about who approves what. You don’t know who to sell to.
4. Have you tried solving this before?
Green flag: “Yes, we tried X for 18 months and it didn’t work because…” You get context on why other approaches failed.
Red flag: “Not really” or “We’ve just been managing around it.” They haven’t invested in solving it yet. They might never.
5. What would solving this unlock?
Green flag: Revenue, cost savings, or new market access. Concrete downstream effects. “If we could do this 50% faster, we could take on three new customers.”
Red flag: “It would be nice” or “It would improve efficiency.” Vague benefit, not a business driver.
Moving from Technical Contact to Economic Buyer
The engineer you’re talking to doesn’t control budget. Someone else does. And you’re terrified that asking to talk to that person will offend your champion and kill the deal. (We wrote a full guide on how to sell to the CEO and the engineer simultaneously.)
It won’t!
Frame it this way: “Look, I want to make sure this is the right fit for your business, not just a cool technical project. Can we spend 15 minutes with the person who thinks about this problem from a business angle? I want to understand the commercial side better.”
That’s not threatening. That’s professional. It says: I’m serious about solving your problem, not just tinkering with your tech.
If your technical contact is the right kind of champion, they’ll actively help you reach the economic buyer. Because they know the same thing you’re learning: cool tech that doesn’t solve a business problem doesn’t move forward.
What to do now
The most important thing you can do next is start asking discovery questions that uncover the commercial needs that drive decision making — and push to talk to the people who own those outcomes:
- Audit your POCs - can you answer the 5 questions?
- Contact your champion - can they answer the 5 questions?
- Ask to talk to commercial owners — find the person who can answer the 5 questions.
Get Help
VECTOR is a 6-month commercialisation programme for deep tech founders who know their technology works but can’t turn customer interest into signed contracts. We work with you to build the discovery process, qualification systems, and go-to-market playbooks that turn scattered conversations into predictable revenue. If you’re running POCs that don’t convert, or you’re unsure which customers are worth your time, apply to work with VECTOR.