Building a Reusable Discovery Playbook for Deep Tech Sales

The skill that wins your first customer is not the skill that wins your fifth. Most founders don’t notice the switchover until they’re stuck.

It starts as a quiet anxiety. Most deep tech founders feel it after landing their first one or two customers: it took longer than it should have, you got there partly by luck, and you’re not entirely sure what actually worked. Each new conversation still feels like starting from scratch.

So the symptoms repeat. You’re asking the wrong people the wrong questions, offering POCs before you’ve qualified the pain. You can sense that winging your way to ten customers is going to break you - but you don’t know what to systematise, because you don’t yet know what you don’t know.

The fix is a playbook. Not a 50-page document nobody reads. A living system that captures what you’ve learned and makes it repeatable.

What Goes in a Discovery Playbook

Here’s what a reusable discovery playbook includes:

• Prospect identification: What signals tell you someone has this problem? (Industry, company size, recent funding, known pain points)
• Qualification questions: A core set of discovery questions that separate real pain from polite interest, plus any specific ones for your market
• Green and red flags: What answers mean “move forward” vs. “politely close this conversation”
• Conversation flow: How to move from small talk to the real pain in 30 minutes
• Mapping the buying motion: Who do you need to talk to? In what order? How do you move from the technical contact to the economic buyer?
• POC design criteria: “We only run a POC if the customer answered green on questions 2 and 3”
• Next steps: What happens after discovery, before any commitment?

I’ve seen teams build a seven-section playbook that covered the entire go-to-market motion - from ICP definition through pricing conversation. Each section had decision trees and specific language to use. By customer five, their sales cycles were running twice as fast as customers one through three.

POCs Are Not Discovery

In deep tech, the POC is too often used as a discovery tool. A prospect shows interest, you offer to run a small proof of concept to “see if there’s a fit,” and the technical conversation feels productive. Most of the time, nothing converts.

The mistake is using the POC to find out whether the pain is real. Discovery is supposed to do that work. By the time you’re scoping a POC, you should already know that the problem is a business blocker, that there’s a budget owner, and that solving it will move a number someone is accountable for. If you don’t know those things, the POC isn’t qualifying the deal - it’s burning your time and your customer’s politeness.

I worked with a deep tech materials science startup that learned this the hard way. They were pitching solutions before understanding problems. Every conversation ended in “let’s run a POC,” and the POCs themselves were beautiful. The technology was solid. None of it mattered, because they were solving problems nobody had a budget to fix.

When they flipped the order - discovery first, POC only if the pain was qualified - their conversion rate tripled. They ran far fewer POCs. Every one converted, because by the time the POC was scoped, the customer had already told them why they needed it and how much it was worth.

That’s not about being a better salesperson. It’s about running a more honest process. Discovery forces both you and the customer to answer hard questions before either of you has built emotional investment in an outcome.

What to Do Monday Morning

1. Write down your five discovery questions. The ones that matter for your specific market. Test them on your next three calls.

2. After each call, score it. Green flags on questions 2, 3, and 5? Qualified. Otherwise, close professionally and move on.

3. Build a one-pager documenting what you learned. Add to it each week. By week four, you’ll have a playbook.

4. Stop offering POCs in discovery calls. At least for the next month. Instead, say: “Let me talk to my technical team about what this would look like, and we’ll come back to you with a proposal.” Give yourself time to think.

5. Commit to one customer discovery call per week where you’re explicitly training yourself on this. One per week, focused, with detailed notes on what worked.

The difference between founders who scale to $10M ARR and those who get stuck at $3M is often this: the successful ones figured out how to have honest conversations before they built anything. The stuck ones are still running POCs to see if the problem is real.

---

Still qualifying deals by gut feel? At VECTOR, we help deep tech founders build repeatable discovery systems that separate real pipeline from polite interest. Apply to work with us - or start with the five questions that actually qualify deals.