The 10-Minute PM Test for GTM-Product Partnership
Hire salespeople with enough product depth that engineers can't tell they aren't a PM
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 3
- Confidence
- 88%
A hiring and org-design bar for building a sales team that product and engineering actually want to partner with. The litmus test: put an account executive in front of ten of your engineers, and it should take them ten minutes to realize the person isn't a product manager. Product depth buys credibility with engineering and lets the sales org double as an R&D signal-generating machine.
Origin
Jeanne DeWitt Grosser's long-standing litmus test, credited by former colleagues Kate Jensen and Claire Hughes Johnson as her superpower for building sales orgs engineers respect.
Core principles
- 01The best GTM orgs are equal parts revenue-driving and R&D
- 02A 20-person sales team talks to more customers weekly than most research functions — that's road-map signal if translated well
- 03Product depth gives sales credibility with engineering and a seat at the strategy table
- 04Company strategy is product strategy meets go-to-market strategy — sales should think like a general manager, not a deal-closer
How to run it
- 1
Hire for product depth, not just closing ability
Screen sellers for enough product understanding that engineers would mistake them for a PM. Vercel's first three GTM engineers were sales engineers who had been front-end developers.
Pro tip Look for a profile that has real sales skill AND a product mindset — someone who can think like a general manager.
- 2
Turn customer conversations into road-map signal
Systematically translate what the sales team hears across many customer conversations into signal for product — distinguishing a one-off objection to overcome from a genuine market opportunity heard repeatedly.
Pro tip 'I've heard this on the last three calls and it would be a real unlock nobody's doing' is signal; a single objection to close a deal is noise.
Watch out The hard part is discerning signal from noise — don't forward every feature request as road-map input.
- 3
Make sales a partner, not a demander
Have the sales org know when to say no to a feature ask, when to objection-handle instead, and lean into product and pricing strategy so it's a true counterpart to product/engineering rather than 'do these things for me.'
In the wild
Vercel hires very technical sales engineers — its first three GTM engineers were all front-end developers before moving into sales, giving them genuine product depth.
→ They could both build agents and credibly partner with engineering; Grosser's sales org is cited by peers as uniquely trusted by product and engineering.
Common mistakes
Hiring sales purely for closing skill
Sellers without product depth lack credibility with engineering and can only demand features, so the sales org becomes an adversary to product instead of an R&D partner.
Forwarding every sales feature request to product
Failing to filter signal from noise floods the road map with one-off objections and destroys the trust that makes sales a genuine partner.
Is it for you?
Best for
Founders and revenue leaders building a technical-product sales org that must partner tightly with engineering
Not ideal for
Simple, low-technical products where deep product fluency isn't needed to sell or to inform the road map
From the transcript
“if you are an account executive in my org and I put you in front”
“of 10 engineers at”
“our company, it should take them 10 minutes to figure out you aren't a product manager”
“the best go to market”
“orgs on the planet are equal parts revenue driving and R&D”
“knows when to say no, knows when to objection handle”
From the episode
What world-class GTM looks like in 2026
Jeanne DeWitt Grosser (Vercel, Stripe, Google)