Second, I’d go for a SaaS expert at your ACV (price point) over a domain expert in just about any senior hire — VP Product, VP Sales, VP Marketing.

The general reason is this: we overvalue domain expertise. Everyone else in the company already understands the market. The new folks should have plenty of help to draw upon until the pick the domain expertise part up. If I’d looked for great e-signature experts in ’06 and ’07, we’d have gone bankrupt before I’d found any. Didn’t much matter.

The reason I strongly recommend SaaS experience (from a successful but probably not BigCo experience) is the sheer volume of features and workflows and customer demands over B2C or freemium products, and other domains. Folks outside of SaaS and enterprise can struggle to manage dozens of enterprise-grade integrations (with deep workflow integrations in each), juggle 1000s of customer-centric feature requests, and balance that all out with the Future Vision …

As much as we’d all like to believe it’s enough to Just Build A Great Product, in SaaS, that’s necessary — but not sufficient.

Third, I’m skeptical most product folks from B2C, from Gaming, from low-end freemium can make the jump to more enterprise-y SaaS B2B.

It’s too many endless, somewhat boring, new features, new functions, new enhancements, new use cases, new corner cases you need to provide for. E.g., Salesforce is just very, very different from Gmail.

I wish they could make the jump, the B2C folks, because they make prettier, easier-to-use products.  But they just fizzle out when it comes to managing the endless myriad of workflows in more complex and more enterprise B2B software.

SaaS apps get endlessly complex under the hood over time, as features compound upon features — even if the best ones maintain a very elegant, easy-to-get going user interface.


And as a Fourth bonus criterion, it really, really helps if your VP of Product has managed at least a very small dev team themselves, at least once in their career.

At least an outsourced team, or something, at a minimum.  First, this almost assures they’ve truly put products into product, per the prior point.  Second, it means they’re likely senior enough to do the role.  And third, it dramatically increases the odds your engineering team will respect them.  Many engineering teams just plain don’t respect product managers and leaders that don’t have an engineering background or at least something close to it.  Some disagree, but I just wouldn’t make the hire at this position (VP of Product) if they’ve never managed at least a small dev team of some sort.

A related post here:

If You Don’t Think You Need a VP of Product, VP of Marketing, Etc. — Then You Haven’t Worked With a Great One

(product image from here)

Related Posts

Pin It on Pinterest

Share This