Your VP Sales Doesn't Need to Code, But They Can't Be Clueless
Picture the interview. Two finalists for VP Sales. One can demo your product cold. The other has a legendary playbook for scaling sales teams. You can only hire one. Who do you pick?
Most founders I know default to the playbook. Process scales, product knowledge is trainable. But Jason Lemkin over at SaaStr thinks that's a recipe for disaster. In his latest piece, he argues that in B2B startups under $20-40M ARR, a VP Sales who doesn't deeply understand the product will fail "again and again and again."
He's not wrong. But he's also not entirely right. The truth is messier than a binary expert vs. process debate. Our analysis of 26,531 real-world problems across industries shows that sales leadership failures split into two distinct camps: product cluelessness and process incompetence. The winning hire is the one who knows which camp they're in and can bridge the gap.
Let's break it down.
The Product Knowledge Trap
Lemkin's core claim is that a sales leader must be able to demo the product, understand the top 20 customer use cases, and answer the top 20 objections. If they can't, they'll melt. Our data backs this up in specific scenarios.
In B2B SaaS alone, we track over 4,200 problems. A significant subset involves sales teams misrepresenting product capabilities or failing to connect features to customer pain. Average severity? 3.8 out of 5. That's high. When a sales leader doesn't understand the product, the damage cascades: bad demos, wrong positioning, wasted pipeline. Founders report that these problems are not just annoying—they're revenue killers.
But here's the nuance Lemkin glosses over. Product expertise is not a binary switch. It's a spectrum. A sales leader who can articulate value propositions and steer discovery calls may be far more effective than one who knows every keyboard shortcut. The trick is matching depth to deal complexity.
Where Process Beats Product
On the flip side, our data shows that many sales leadership failures have zero to do with product knowledge. They're process failures: no scalable qualification framework, weak pipeline management, inability to coach reps. A sales leader who nails process but is weak on product can still build a high-velocity engine—if they have the humility to lean on sales engineers and product marketing.
One pattern we see repeatedly: founders hire a VP Sales from a big company, dazzled by their process talk, then discover they can't operate without a massive support infrastructure. At a 10-person startup, that's fatal. But the opposite failure happens too: promoting a product genius to VP Sales, only to watch them drown in forecasting spreadsheets and hiring plans.
The real skill? Adaptive expertise. A leader who can ramp up product knowledge fast and also systematize sales. In our database, the most successful sales leaders are those who treat product learning as an ongoing discipline, not a one-time onboarding task.
The AI Wildcard
Lemkin's article was written before the current wave of AI sales tools hit mainstream. That's a huge miss. AI is changing the calculus.
We're seeing a surge in tools that automate demo personalization, provide real-time competitive intelligence, and even coach reps on objections. This means the product expertise bar for a sales leader is actually dropping. They don't need to know everything—they need to know how to leverage systems that know everything. But that raises a new bar: data literacy and process design.
The sales leader who thrives in the AI era is the one who can build a system where product knowledge is embedded in the tools, not just in their head. That's a very different profile than the one Lemkin describes.
What to Actually Look For
So, how do you hire? Forget the binary. Test for three things:
- Learning velocity: Can they get from zero to credible product knowledge in 30 days? Give them a demo, ask them to explain it back. See how they probe.
- Process instincts: Do they ask about your sales stages, win rates, and rep ramp times? Can they identify your biggest bottleneck without being told?
- Leverage mindset: Do they talk about building systems or being the smartest person in the room? The former scales; the latter is a single point of failure.
And then, support them like hell. Lemkin is right that founders should join 4-5 calls a week with the new VP. It's not micromanagement; it's calibration. If after 60-90 days they still can't articulate your value prop without slides, you have your answer. But if they've built a repeatable process and reps are ramping faster, maybe product depth wasn't the bottleneck.
The Bottom Line
The next time you're interviewing a VP Sales, don't ask "Are they a product expert?" Ask "Can they become one fast enough, and can they build a team that doesn't depend on them being one forever?"
The answer to that question is what separates a mis-hire from a force multiplier.
PainSignal tracks 26,531 problems across 90+ industries to help founders spot patterns before they become pain. See the data behind this analysis.
This article is commentary on the original article by Jason Lemkin at SaaStr. We encourage you to read the original.
Explore more problems and app ideas across Software/SaaS, Sales.
Browse App Ideas