We scan new podcasts and send you the top 5 insights daily.
In a raw startup, the CRO's main job isn't leading a sales team. It's being on the front lines defining use cases, validating pain points, and determining product fit. They function as a product manager, only transitioning to a traditional sales leader once a repeatable go-to-market motion is established.
The CRO, not product marketing, is closest to the customer and knows what they will buy. The product roadmap should be a collaborative effort driven by the CRO, who can directly tie feature delivery to ICP expansion and revenue forecasts. This creates accountability and predictable growth.
Founders often hire their first sales leader to solve the problem of selling, which they haven't yet cracked. This role requires an entrepreneurial "renaissance rep" to discover the sales motion, not someone with a big-company resume to simply execute a known playbook. This mismatch in expectations is a primary cause of high turnover.
In an early-stage company, the Chief Revenue Officer's primary role is often product management. They must dig into customer use cases to discover how the product creates value and identify emergent markets, as when Black Duck pivoted to security after a key customer call.
In the pre-product-market fit stage (the first ~20 deals), the sales leader's primary role is not just closing revenue, but acting as a product manager. They must be in every meeting to gather objections, find pockets of value, and translate raw market feedback into actionable insights for the engineering team.
A common failure mode for new CROs is attempting to create the sales playbook in isolation. Core pillars like ICP and value proposition are company-level decisions. The CRO's role is to be interdependent, facilitating this cross-functional creation process, not dictating it.
A pre-product CRO conducts thousands of market conversations to validate demand and guide the product roadmap. This de-risks development by ensuring you build a product that customers will actually buy, a task more suited to a sales expert than a founder.
Snowflake's first CRO, Chris Degnan, joined two years before the product launched. His primary role was not selling but gathering customer feedback to guide engineering, acting as a "shadow CTO." This redefined the initial sales function as a product discovery and validation role.
A CRO's primary role isn't managing today's revenue but architecting the engine for tomorrow's growth. This requires placing creative, long-term bets on new markets, products, and channels—like government sales—even if they don't generate immediate revenue, to ensure future acceleration.
The ideal sales hire changes dramatically across scaling stages. Initially, you need a "product manager" type who can handle ambiguity and provide product feedback. A top rep from a large company would fail because they rely on established processes and support systems that don't yet exist.
Many new CROs hesitate to challenge the CEO on company strategy. This is a mistake. A CRO's value is providing their unique market perspective as a peer on the executive team, even when it creates friction. This candor is essential for the company's success.