Chris Degnan on Building Snowflake's Sales Team from the First Customer

Snowflake chief revenue officer Chris Degnan joins Harry Stebbings to discuss the sales organization he helped build from its earliest days. Degnan's recurring advice is to learn the product deeply, meet customers consistently and keep prospecting. The interview reflects his experience at Snowflake and its consumption-based business.

Degnan found sales through a management training program at Franklin Templeton after discovering that human resources was not for him. He enjoyed competition and explaining how an offering could improve a customer's work. He later moved into business-to-business technology sales.

Investor Mike Speiser recruited Degnan to Snowflake before it had a website or a permanent CEO. Degnan liked the founders and believed analytics would move to the cloud. He joined as director of sales and the company's first sales employee, not as a senior executive with a completed playbook.

On arrival, Degnan says, he discovered there were no customers and worried about leaving a well-paid job for lower cash compensation and equity. He credits his wife's support through the uncertainty. In hindsight the equity was valuable, but at the time the decision felt risky.

His basic playbook was to be a student of the product and conduct eight customer sales calls a week. That cadence left room for follow-ups, prospecting and two or three new-business meetings, he says. He contrasts it with a previous target of 15 weekly meetings that he found impractical.

Initially, Snowflake's goal was customer feedback rather than closing sales. Degnan described the proposed product and asked companies to try it or say whether they might buy. Repeated conversations helped identify prospects that were already adopting cloud infrastructure and had an understood data-warehousing problem.

Degnan says Amazon Redshift helped establish the cloud data-warehouse market; in his view, customers with frustrations about the product became useful prospects. He chose to focus on cloud-native companies rather than spending the early years convincing every customer to move from on-premises systems. His comparison reflects Snowflake's competitive interest.

If a seller must first convince a buyer that a problem exists, Degnan warns, the cycle can be much longer. He favors a large market where customers already recognize their pain. He also says founders must combine a clear vision with an openness to customer feedback rather than assuming they know every answer.

For a first sales hire, Degnan likes someone with something to prove and the willingness to do prospecting and customer calls personally. An experienced leader can work if willing to do the basics. He cautions against hiring a CRO too early, suggesting that a vice president of sales may give a young company more flexibility as its needs change.

Degnan held himself accountable by sending the company a weekly account of his eight calls, including what customers said. Engineers and founders received direct feedback that could shape the product. He still asks representatives managing major accounts for regular updates and focuses particularly on problems marked red.

A useful update identifies the company and person met, the conversation, objections and next steps. Degnan recalls a customer asking for a technical capability called windowing: rather than inventing the solution himself, he brought a founder to hear the need. The product team, not sales, decided what to build.

He argues that sales and product should meet customers together whenever possible. Direct context helps engineers understand why a feature matters and decide how it fits the product. Degnan describes his own role as connecting the teams, not setting the technical roadmap.

For forecasting, Degnan looks for a compelling customer event or reason to act. Early at Snowflake, he says, a prospect could not enter the forecast until it had tried the product. A friendly relationship alone does not establish that a purchase will happen, particularly when budgets are tight.

He recommends asking direct questions about whether a contact intends to act and who actually owns the decision. To create a realistic timeline, work backward from the customer's desired outcome and account for contracts, procurement, security and implementation. The schedule should reflect the buyer's process rather than the seller's hope.

Large enterprises can be tempting for a startup because the potential contract is large. Degnan warns that a prospect may demand many features, then change jobs or priorities before buying. He prefers finding customers who fit the intended profile, can buy sooner and will actually use the product.

A pipeline needs volume and a mix of faster-moving opportunities as well as longer enterprise pursuits. A single large deal can distort a quarter and leave little repeatable business behind. Degnan returns to his weekly call and prospecting habits as a way to keep the pipeline moving.

To build multiple relationships in an account, Degnan tests whether a technical champion can introduce the team to an economic buyer. A sales representative may use an executive's presence to make that introduction easier. He calls the representative the director of the deal and himself an actor who should play the role requested.

CEO Frank Slootman told Degnan that personally handling every major deal had made him a bottleneck. Degnan says he began hiring leaders who could run important accounts and ask for his help when needed. Letting go and trusting those leaders was difficult but necessary to scale.

Degnan wants sales managers who lead from the front and understand what they sell, rather than only managing spreadsheets. He admits candidates can say the right things during hiring and behave differently in the field. Spending time with their teams helps reveal the gap, although he says judging it remains hard.

He believes an early marketing hire should generate qualified pipeline and meetings. In his view, founders and salespeople can work together on product messaging, while marketing must be accountable for creating opportunities. This prioritization is his advice, not a claim that product marketing never has value.

At Snowflake, Degnan says the sales and marketing teams moved away from arguing over definitions of marketing-qualified and sales-qualified leads. They focused instead on quality meetings that convert into pipeline. Stebbings notes that activity targets can be gamed; Degnan says pipeline integrity matters.

Degnan still believes in outbound prospecting, including calls, messages, conferences and partner introductions. He says he personally uses outreach when recruiting. A representative who waits for marketing to deliver every opportunity may fail to find enough champions.

Because Snowflake charges by consumption, Degnan watches customer revenue daily. A sudden fall can signal a problem or workload moving elsewhere; a sudden rise also matters because a customer may overspend unexpectedly. He presents real-time usage as useful feedback, not a guarantee that churn can always be predicted.

Asked whether CFOs are spending, Degnan says companies still buy when a product solves a significant problem. He uses his own rejection of a forecasting tool he did not feel he needed as an example of the difficulty of selling a 'nice to have' in a tight environment.

Degnan says talent development depends on being open to feedback himself and getting experienced leaders to help newer ones. He learns from representatives on customer calls and encourages peers across regions to coach one another. He describes the team as a shared responsibility rather than a manager working alone.

He believes salespeople need pressure and urgency, and says he does not personally feel secure in the job. He expects representatives to understand the product and conduct customer calls; his view of pressure is a management philosophy, not a universal measure of a healthy team.

Degnan says leaders should give feedback but ultimately make difficult decisions when people are not progressing. He distinguishes productivity timelines by segment at Snowflake: roughly three to six months for more junior corporate sellers, six to nine for mid-market enterprise, and about twelve for large enterprise. These are company-specific expectations, not general benchmarks.

He recommends hiring more than one representative in a new territory when possible, so a single person is not the only test of the market. If performance differs, a manager can compare their approaches and coach. Although Degnan is confident in the comparison, territory and individual differences can make causation less certain than his shorthand suggests.

On difficult feedback, Degnan says directness need not mean being unkind. He describes the tension between personal friendships and professional obligations, recalling leadership changes at Snowflake. His conclusion is that leaders must be willing to make decisions even when relationships make them painful.

Degnan credits board member John McMahon with candid advice about the skills he needed to keep scaling as a sales leader. He suggests founders seek experienced sales advice and assess whether leaders respond to feedback. When a team misses targets, he says, investigate product-market fit, lead generation and communication before assuming a single cause.

Although Degnan says he naturally moves quickly to the next quarter, he also recognizes top performers through reviews and recognition programs. After a disappointing quarter, he advises looking honestly at metrics and external conditions to distinguish market effects from sales execution.

Degnan challenges the conventional customer-success model. In his experience, some teams mainly manage renewals or guide product use without the technical or selling skills he wants. He says he eliminated the customer-success function he inherited and favored sales representatives, sales engineers and professional services instead.

Snowflake's business-value engineering group helps salespeople demonstrate customer outcomes, while representatives own renewal and growth quotas. Degnan argues technical services can help customers implement and consume the product. This is Snowflake's organizational choice and his opinion, not proof that customer success is unnecessary for every company.

He says Snowflake's professional-services group runs at a low, single-digit profit margin and functions primarily as product enablement. It also creates training content for customers and partners. The financial description is his account of the business at the time of the interview.

Before Snowflake's IPO, the company resegmented its sales team and changed territories. Degnan says such change is uncomfortable but argues that leaders should make needed adjustments promptly. He continues to reassess the organization as the business grows.

For an early customer such as Capital One, Snowflake had to develop a deployment model to meet security needs, he recalls. Today he says a public company must be more careful about special commitments. He still joins both large deals and smaller first-customer meetings when a representative has a clear role for him.

Degnan says his lesson from Slootman is urgency. He initially worried for months that the new CEO would replace him, until a Christmas message and stock grant reassured him. He closes by emphasizing the partnership between sales and engineering and praising Amazon's ability to support Snowflake even while competing with some of its products.