We scan new podcasts and send you the top 5 insights daily.
In a raw startup, the CRO's job is less about managing a team and more about being a product manager. By bringing founders on sales calls, the CRO's role was to secure paying customers and then hold engineering accountable for making the technology work, forcing product development based on real-world demand.
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.
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.
To transition from working 'in the business' to 'on the business,' Snowflake's CRO was told his hands-on, 'deal hound' approach wouldn't work at scale. The solution was to hire other capable 'drivers,' trust them to do their jobs, and hold them accountable. If a leader has to do their team's job, it's a problem with the team member.
Snowflake hired its first salesperson pre-revenue not to sell, but to get the product into customers' hands to break it. This person acted as a de facto product manager, gathering critical feedback that led to a core architectural change, proving the value of a GTM hire before product-market fit.
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.
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.
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 product leader with a technical background is better equipped to make credible and achievable product bets. This dual perspective allows them to avoid overpromising, push back on both customer demands and engineering timelines with authority, and make smarter trade-offs between perfection and shipping.
Early-stage companies often mistakenly hire a big-name CRO who has managed a $500M business. This leader is unequipped for the hands-on, resourceful work required to build a go-to-market function from scratch. Hire for the job that needs to be done today, not the one a year from now.