Chad Peets on Building Sales Teams, Hiring and Product Collaboration

Chad Peets argues that an early sales leader can help create a sales playbook before a product exists. He also strongly favors office work for inside sales development. These are his prescriptive views, not findings from a controlled comparison of work arrangements.

Peets tells Harry Stebbings that he initially wanted to be a stockbroker after watching Wall Street. He studied finance and joined Merrill Lynch, but became uncomfortable with product-pushing and the prospect of soliciting friends and family to build a client base.

A client introduced him to software sales recruiting. Peets says he left a $100,000 first-year job for a commission-only role, became the recruiting firm’s top producer and started Peets Associates after its partners split in 2001. These career and performance claims are his recollections.

Peets believes some people have an innate selling ability, though coaching can improve them. He says he was comfortable making calls and anticipating objections. That is his view of talent, not evidence that sales ability cannot be learned by others.

His recruiting method was to specialize in software sales, learn candidates’ motivations and match them to what a company could offer. He says he screened many people out from their career histories and claimed a typical ratio of two candidates presented for one hire. The interview does not independently verify that ratio.

Stebbings asks how focus works for a product sold across industries. Peets prefers horizontally applicable products because a single vertical limits the potential market, though he recognizes successful vertical companies. He distinguishes this broad product market from deeply understanding the particular people he recruits.

Money matters to salespeople, Peets says, but he also looks for a desire to improve and sell a valuable product. To test candidates’ claims, he asks why they changed jobs and looks for evidence that they deliberately chose leaders who would develop them. These are his hiring heuristics, not universal tests of motivation.

For chief revenue officers at Sutter Hill companies, Peets says he has recruited from an existing professional ecosystem. Stebbings raises the concern that this can narrow candidate diversity; Peets acknowledges the network’s importance and says it is expanding as a new generation of leaders emerges.

Peets says returning to an early-stage sales leadership job after a major success is demanding, making the next generation important. He describes Sutter Hill’s practice of bringing a CRO into a company before the product exists, using Observe as an example. His favorable comments concern a company in which he has an investment relationship.

The reason, he argues, is that a sales specialist can conduct extensive prospect discovery, ask what would create value and feed those findings to product and engineering as the offering moves from early versions to general availability. Founders should participate, but he doubts they have the time or sales expertise to conduct the full process alone.

Peets disagrees with the common advice that a founder should first create the sales playbook and hire a leader later. He says recruiting a CRO and supporting discovery may require substantially more than a small seed round, perhaps around $10 million. He explicitly limits this model to Sutter Hill’s incubated companies rather than claiming it fits every startup.

For Peets, the right CRO works directly with product on the roadmap. He recalls Snowflake initially selling to a narrow adtech customer profile and says sales must identify features that can expand the addressable account list. Hiring more representatives before the needed product capabilities arrive can leave them unable to sell.

He warns against assigning broad territories without a defined ideal customer profile. A representative may chase one large prospect and demand a long list of unique features, diverting the company even if that deal never closes. He prefers aggregating discovery across customers to identify features that open a wider group of accounts.

Stebbings asks why sales should not also own product marketing. Peets says some sales teams create their own content, but understanding customer conversations does not automatically make someone a strong content creator. He wants sales to pass the evidence to product marketing, which can develop the message.

A CEO must support collaboration between product and sales, he says. Otherwise product can build what it expects customers to want while sales struggles, and the functions blame one another. The CEO should make the connection between product commitments and the revenue forecast explicit.

Compensation should encourage the behavior the company needs. Peets gives an illustrative example: if initial deals are healthy but expansion is slow, paying a higher commission on expansion may change the team’s focus. The percentages in his example are hypothetical, not a universal compensation plan.

On annual contract value, he agrees that a $10,000 account may not support an expensive field sales motion. He favors inside sales at that size with carefully controlled acquisition costs, and says companies should choose the boundary between inside and field sales based on their economics.

As a rough rule, he wants a representative to produce around three times on-target earnings: for example, $900,000 of productivity against $300,000 of compensation. He advises against expanding a field team with substantially lower productivity unless reliable data show improvement. The benchmark is his heuristic, not a guarantee.

Peets would ideally ramp an inside representative in roughly 90 days and an enterprise seller in six months, although he says enterprise ramp often trends toward nine. If ramp takes longer than the sales cycle alone explains, he suggests examining enablement, product and the nature of the business.

A CRO can often handle enablement for a small team, he says, but around 30–40 representatives it may need a dedicated and consistent program. The timing depends on the company. Managers should execute the agreed training plan rather than each building a disconnected version.

Peets believes customer success matters, even though he recalls Snowflake initially operating without a separate customer-success organization. He attributes unusually rapid expansion there to product strength, including his example of a $15,000 initial deal growing to $150,000 in six months. His Snowflake affiliation and the anecdotal scope matter.

He wants customer success to monitor implementation, utilization and whether the customer receives the expected value, while the salesperson remains involved and handles expansion. Handing off immediately after the initial deal can encourage representatives to close commitments customers will not use.

For example, a representative paid on bookings could persuade a customer likely to consume $50,000 to commit to $100,000. If consumption falls short, the relationship and renewal are at risk. Peets says incentives should make the initial sale the start of the customer journey, with rewards for subsequent expansion.

Reflecting on Snowflake hiring, Peets stresses a consistent candidate profile and a repeatable interview process. He favors prompt yes-or-no decisions and limits interview participation to people he considers qualified to evaluate or sell the role. This is his preferred process; others may value broader perspectives.

He says a new regional leader should not automatically hire former colleagues who do not meet the established profile. The profile can vary somewhat by geography, customer and deal size, but he wants a central team with experience of the product to maintain the core standard.

Peets contrasts selling another product to existing large-company customers with generating new demand for an unfamiliar startup. He believes account executives need support but must also take responsibility for their own pipeline. Experience with one selling environment does not automatically translate to the other.

On firing, he says three weeks is generally too early unless there is an obvious serious issue. A manager should first coach the person and check whether the territory or accounts are the problem. In his view, a change is warranted when reasonable support has failed and outside factors do not explain the result.

A previously successful representative may become exhausted by the grind of generating pipeline, he says. Managers can look for changes in behavior, meetings and pipeline before results deteriorate. Peets interprets some moves from startups to larger companies as a change in appetite for that work; this is his inference, not a reliable conclusion about every candidate.

At Snowflake, he says consistent recruiting messages were important. As information changed, he and sales leaders updated the pitch and made sure interviewers described the opportunity consistently. Conflicting accounts from different managers can undermine a candidate’s trust.

In hindsight Peets thinks the team could sometimes have set a higher hiring bar while scaling. He describes the tension between waiting for a perfect candidate and falling so far behind a hiring plan that the next year’s forecast suffers. Neither speed nor selectivity alone resolves the trade-off.

Peets says he is willing to have conflict but could have communicated more diplomatically. He also distinguishes wanting to join a fast-growing company from caring about career development: he does not consider the former inherently bad, but asks candidates what else motivates them.

He believes excellent salespeople need commitment, development and a desire to win. He contrasts his definition of culture with questions about benefits, family time and office attendance, and says he would not hire some candidates whose preferences differ. These are his personal standards, not evidence that such preferences imply poor performance.

Asked about balance, Peets says he values the quality of time with family over the number of hours. He feels it has become harder to recruit for the intensity he wants and refuses to relax core requirements. His account is a subjective view of work and family, not a general standard.

For inside sales, Peets insists on office attendance because he believes colleagues learn faster together; Stebbings adds that proximity can expose them to product and customer conversations. Peets distinguishes outside sales, where he wants representatives with customers. The interview provides no comparative evidence that remote workers develop less.

Peets says outbound selling is changing and relays feedback that email and LinkedIn messages face saturation, while calls may work better. Stebbings argues for useful content; Peets notes that an unknown startup lacks an established brand and sees potential for AI and targeted content. Neither offers measured channel results.

They discuss moving from product-led growth to enterprise sales. Peets says a developer buying a product and a representative selling to a CTO can involve different organizations and value propositions. He prefers beginning with direct sales before adding product-led growth, while acknowledging that he is not an expert in every such business.

Peets says Snowflake and Sigma began with smaller, mid-market customers to learn and build capabilities before moving upmarket. He rejects a fixed revenue threshold for enterprise expansion: readiness depends on customer feedback and product capabilities. He cites Wiz as an exception in his experience; he has an investment relationship with Sigma and Snowflake.

The wrong customer, not necessarily the smallest, can be the most difficult, he argues. If an account is a poor fit and absorbs disproportionate resources, a company may have to accept churn rather than promise what it cannot deliver.

Peets treats gross revenue retention and net revenue retention as distinct measures: the former reflects retained revenue before expansion, while the latter includes expansion. He views weakening gross retention as a serious product signal and says lower net retention can also reflect go-to-market or customer-success issues. His examples are heuristics, not diagnostic guarantees.

During a difficult period, Peets says sales engineers may leave first because they see product problems, followed by sales representatives. If product listens to customer feedback, communicates a plan and delivers it, the team may hold together; ignored problems can make representatives feel unable to win.

Stebbings raises forecasts set above a CRO’s expectations. Peets criticizes targets derived from a desired fundraising valuation rather than business evidence, such as assuming rep productivity will rise without a reason. He says his firm seeks alignment between the CEO and revenue leaders and urges CROs to challenge unrealistic plans.

At scale, onboarding should be a resourced, programmatic process over months, he says. Companies should not expect revenue before representatives are prepared. On discounting, he says an early deal can even have negative margin when a relevant, referenceable customer can help open a narrow market; the trade-off depends on stage.

In quick fire, Peets says he is learning to accept some changes while retaining core standards. He advises new representatives to invest in learning and new sales leaders to understand the business and meet customers quickly. He rejects the idea that all salespeople care only about money.

He praises Mike Speiser’s judgment and combination of investing and operating experience, then says a common founder mistake is hiring a CRO without knowing what the company needs. Peets acknowledges founders may lack knowledgeable advisers; a poor leadership hire can produce a mismatched team and a long reset.

Asked about his weakness, Peets names impatience. He says Speiser helped him recognize that not every problem can be treated as an immediate emergency: leaders must prioritize, or exhaust colleagues by constantly declaring a new fire. The conversation closes with thanks.