long-form-interview· Chad Peets

Why You Need a CRO Pre-Product

A great sales organisation is built backwards from the prevailing model: hire the CRO BEFORE the product, let sales drive the product roadmap by ICP expansion, recruit a small set of innate-talent reps via a binary 2-candidates-1-hire process, and protect the profile against scaling pressure even when it slows the plan.

chad-peetssutter-hillsnowflakechris-degnansales-recruitingcrosales-org20vc93% confidence

Why this is in the corpus

High-density CRO playbook from Chad Peets (Sutter Hill, hired entire Snowflake sales team alongside Chris Degnan; built the fastest sales-organisation scale in software history at the time). Concrete benchmarks: 3× OTE productivity, 90-day inside ramp / 6-month outside, mid-market-first then enterprise (Snowflake/Sigma). Sharp anti-patterns: engineer-in-the-interview, CS-owns-expansion, Wells Fargo-distorts-roadmap. Pairs naturally with Carles (ElevenLabs), Shaunt (Figma), and Lucas Swisher (Coatue) for a complete operator-investor sales picture.

Summary for skimmers

Chad Peets, Sutter Hill MD and the recruiter behind Snowflake's sales scale-up, on building world-class sales organisations. Core unconventional thesis: hire the CRO PRE-PRODUCT. The CRO is the only role with the time, sophistication, and operating discipline to make thousands of customer-discovery calls and feed insights back to product before there's a product to sell. Most founders are product/engineering people; they cannot do this work at the volume required. Once the CRO is in, sales DRIVES the product roadmap by ICP-expansion logic: at 50 ICP accounts, identify the 5 features needed to expand to 150, commit to a delivery date with product, then hire ahead based on the commitment. Behavioural / comp design: salespeople are predictable, the comp plan programs behaviour. Land/expand asymmetric commission (e.g., 10% on land, 12% on expand) drives expansion focus. Productivity benchmarks: rep should generate 3× OTE; ramp times of 90 days inside / 6 months outside (9 months acceptable for enterprise). Recruiting at scale: 2-candidates-1-hire ratio. Interview process is binary at every step (2 interviews to seller decision; if you can't decide, you're the problem). Only sellers and qualifiers in the pipeline — never engineers, never HR — because they slow process, add interview risk, and create friction when sales hires over their objection. Resume-driven motivation diagnosis: a 12-month/12-month/12-month resume tells you everything; 95% of sellers eliminated pre-call. Mid-market first, then enterprise (Snowflake, Sigma). Wiz the only enterprise-first build Chad has seen succeed. Inside sales should be in the office — that's a recruiting WIN, not a loss; sellers willing to commute are the ones investing in their career. Top-talent recruiting is harder than ever because rep willingness to sacrifice has structurally declined. CEO-CRO forecast alignment is a hard gate at Sutter Hill: the CRO must agree before the forecast is set; CEO-driven fundraising-back-into-forecast destroys the company. Anti-patterns: letting one big account (Wells Fargo) distort the roadmap, letting CS own expansion (sales owns expansion), hiring engineers / HR into the sales interview pipeline.

Briefing

What survives the editorial filter

This page should feel like a smart colleague already listened for you and left only the operating logic worth keeping. Not everything said in the episode makes it through.

Trust signal

direct_practitioner_account

Guest type: practitioner.

Best used for

Chad Peets (Sutter Hill, hired Snowflake's sales team) on the unconventional sales-org playbook — CRO before product, sales drives the product roadmap by ICP expansion, 2-candidates-1-hire binary interviews, 3× OTE productivity rule, land/expand commission asymmetry, mid-market-first then enterprise, and the structural decline in top-rep recruiting that defines the era.

Hold lightly

No explicit downgrade reason stored yet for this episode.

Principles

Durable claims that survive beyond the speaker's biography — each with explicit limits, transferability judgment, and evidence.

Principle

Hire the CRO pre-product — counter to prevailing wisdom

A founder cannot do thousands of customer-discovery calls at the volume required AND build the product AND raise capital. The CRO pre-product is what produces the right product, the right ICP, the right roadmap.

Sutter Hill explicitly hires the CRO pre-product. Keith Butler at Observe is the canonical case — five years in, company killing it. The CRO operates pre-product as a customer-research-and-roadmap function, not as a deal-closer.

Use when: Founder + investor teams with seed budgets of $10M+ and intent to build category-defining companies.

Skip when: Smaller seed rounds where $10M-pre-product is unaffordable; pure consumer products where customer-discovery does not require sales-level discipline.

For category-defining ambitions: budget for a CRO pre-product. The discovery work is too large for the founder.

“We bring in a CRO pre-product, right? Most people don't do that. So how do you know when you're building the product, if you've built the product the market wants? You think you know? But you don't.”Chad Peets

“You need a sales expert that can go conduct thousands of phone conversations that is sophisticated enough... otherwise you could build a product that nobody wants to buy.”Chad Peets

Durability: Durable; the operating logic of customer-discovery-at-scale-needs-sales-shaped-discipline holds across categories.

Principle

Sales drives the product roadmap — feature-by-ICP expansion

Product teams build what they think customers want. Only the CRO has direct knowledge of what customers actually need to buy; sales-led roadmap by ICP-expansion logic is the binding constraint on category growth.

Snowflake example: started in ad-tech only. To expand the ICP, identified the security/feature requirements, got product to commit, hired ahead. CRO Wells-Fargo trap: chasing big single accounts distorts the roadmap; sales-led ICP-expansion is the discipline against this.

Use when: Companies past PMF with multi-quarter product roadmap and multiple ICP cohorts.

Skip when: Pure horizontal-PLG products where roadmap is community-driven; pure consumer with no ICP.

Build a sales-led roadmap loop: count ICP accounts, identify expansion features, commit to delivery dates, hire ahead. Don't let product set roadmap independently.

“You need a CRO that has experience and is sophisticated enough to go work collaboratively with the product organization to design the product roadmap... right now we have 50 ICP accounts, you have to know what do I need to expand that ICP, what features. So I can go from 50 to 500.”Chad Peets

“If you deliver these features by this date, then I can expand from 50 to 100 ICP accounts. And by the way, I can add salespeople. So Mr. Product guy, I'm gonna go hire salespeople based on your commitment.”Chad Peets

Durability: Durable; the ICP-expansion logic is structural across enterprise categories.

Principle

Salespeople are predictable — comp plan literally programs behaviour

The comp plan is a behavioural-programming language. Whatever the company wants reps to optimise, the comp plan can drive — but the leadership has to know what they want first.

Chad's example: 10% on land, 12% on expand drives expansion focus. Different markets, different cycles, different ratios — the structure is the same.

Use when: Sales-org leaders designing or revising comp.

Skip when: Pure-base-salary roles where comp does not drive behaviour.

Treat comp design as behavioural programming. Decide what behaviour you want; design comp to drive it. Re-tune annually.

“Salespeople are great because they're predictable. I can get you to do whatever I want you to do by setting up the comp plan accordingly... I can say, hey Mr. Sales rep, I'm gonna pay you 10% on the land, 12% on the expand. Just by doing that I'm gonna get a lot more focused on the expand.”Chad Peets

Durability: Durable; the comp-as-programming framework holds across categories.

Principle

Sales talent is innate — coach to better, can't teach to good

The recruiting filter is the highest-leverage moment in sales-org building. Profile-vs-coachable confusion costs disproportionate time and money.

Chad: some people are petrified of the phone, freeze when asked to call out. Innate talent shows up at the resume-and-screen stage. 95% of sellers are eliminated pre-call by reading their motivation history through their resume.

Use when: Sales-org leaders building scaling hiring processes.

Skip when: Highly-trained-from-zero programs (rare in sales).

Filter for innate sales ability at the recruiting screen, not in onboarding. Coaching budget belongs on the coachable, not on the unwilling.

“You can't teach someone. Either someone can sell or they can't. You can teach someone to be better, but if they don't have the innate ability to sell, some people are petrified of the phone... I just did not have that fear.”Chad Peets

Durability: Durable; the structural difference between teachable-skill and trainable-instinct holds.

Frameworks

Reusable systems and operating models — including when they help and when they break.

Framework

3× OTE productivity rule + ramp-time benchmarks

Productivity and ramp-time benchmarks are operational quality-control checkpoints, not aspirational metrics.

If you have 10 reps and productivity is $600K against $300K OTE, "you better not be hiring." Either get productivity up or stop scaling. If ramp is 9 months but the cycle is 4 months, peel back the layers — enablement problem, product problem, or just the nature of the business.

Productivity: rep generates 3× OTE; <3× = stop hiring
Ramp inside: 90 days
Ramp outside: 6 months ideal, 9 months max for enterprise
If ramp exceeds benchmark, peel back: enablement problem? product problem? cycle nature?
Use benchmarks as gates on additional hiring, not as soft KPIs

Use when: B2B sales orgs above 10 reps with measurable per-rep productivity.

Skip when: Pre-PMF sales where the binding constraint is product, not productivity.

Stop hiring when productivity is below 3× OTE. Diagnose ramp shortfalls by layer (enablement / product / cycle nature) — don't default to hire-more.

“My reps should be able to generate three times their OTE. So if your OTE is 300, you should be able to get 900K in productivity.”Chad Peets

“Six months for an enterprise seller. Inside, 90 days. Reality is it probably trends more towards 9 months in enterprise.”Chad Peets

Durability: Durable; the 3× OTE benchmark has been industry-standard for over a decade.

Framework

Land/Expand commission asymmetry — drive the behaviour you need

Comp asymmetry is a precision tool to fix specific behavioural gaps. The most common one is land-vs-expand misalignment.

Example: land sales cycle is 4 months at $75K, expand cycle is 12 months at +$50K — too slow, too small. Lever: 10% commission on land, 12% on expand. Reps shift effort. Other levers: spiffs for priority products, accelerators above quota.

Audit land vs expand cycle and dollar size
If expand is lagging, raise expand commission 1-3 percentage points above land
Watch behaviour for 1-2 quarters; rebalance if needed
Use spiffs for priority products; accelerators for above-quota

Use when: Sales orgs with both land and expand motions.

Skip when: Pure transactional one-and-done sales.

Use commission rates as precision levers. If a behaviour is missing, find the rate-per-dollar-effort signal that controls it.

“My expand motion is taking 12 months and I'm expanding from 75 and getting an expansion of 50. That's not good... I can say hey Mr. Sales rep, I'm gonna pay you 10% on the land, I'm gonna pay you 12% on the expand. Just by doing that I'm gonna get a lot more focused on the expand because I pulled that lever.”Chad Peets

Durability: Durable; the comp-asymmetry mechanism is well-replicated.

Framework

CEO-CRO forecast alignment is a hard gate at Sutter Hill

Forecast-alignment failure is the canonical CRO-firing pattern. Sutter Hill protects against it by gating: no CEO-driven forecast can be set without explicit CRO agreement.

Common bad pattern: CEO has a fundraising target, backs into a forecast, hands it to CRO. CRO accepts because they want to keep their job. Misses 9 months later. CRO gets fired. Better pattern: business drives forecast → CRO + CEO + CFO agree → fundraising aligns to that forecast, not the reverse. At Sutter Hill, this alignment is non-negotiable.

Business drives the forecast first, not fundraising goals
CRO + CEO + CFO must all agree
If CRO disagrees, the forecast is wrong — re-set
Fundraising aligns to the agreed forecast, not the other way around

Use when: Boards and CEOs of growth-stage companies with operating CROs.

Skip when: Pre-PMF startups where the forecast is largely speculation regardless.

Add CRO-agreement as a hard gate on every forecast cycle. CEO-handed forecasts that the CRO does not own are the canonical CRO-firing pattern.

“Sutter Hill company CEO says here's the forecast for next year. We say great, Chad Peets, John McMahon, your CRO are in agreement with this, right? Because if they're not, that's not the forecast.”Chad Peets

“CEO says I gotta go raise a round. Forecast needs to look like this next year, guess what Mr. CRO, here's your forecast. CEO's got a decision. You either stand up for it right there, or you accept the fact you're getting fired in nine months.”Chad Peets

Durability: Durable; the CEO-CRO misalignment is a perennial sales-org failure pattern.

Signals

What appears to be shifting, for whom it matters, and what happens if you ignore it.

Signal

Top sales-rep recruiting is harder than ever — willingness to sacrifice has structurally declined

The pool of reps willing to put work in for development + meritocracy + winning has shrunk. Most reps now optimise for benefits, paternity, schedule flexibility — different game.

Chad: "Recruiting today is harder than it has ever been for the type of rep we are looking for. A lot of reps just don't care. Which is a concept I simply do not understand." His response: don't budge on the profile. Build with the smaller pool of willing reps; let competitors take the rest.

Use when: Sales-org leaders calibrating hiring expectations.

Skip when: Categories where the rep profile required is the lower-sacrifice profile (some PLG inside-sales).

Don't budge on the profile when scaling. The smaller pool of willing reps still exists; widen sourcing channels and recruiting effort, don't lower the bar.

“Recruiting today is harder than it has ever been for the type of rep that we are looking for. For somebody that's willing to put the work in, that's looking for the development that we offer. A lot of reps today just don't give a shit. They just don't care.”Chad Peets

Durability: Time-sensitive at the threshold; the underlying generational shift is harder to reverse.

Opportunities

Only included where there is a buyer, a real wedge, and a plausible revenue path — not vague idea theater.

Opportunity

Opportunity: Fractional CRO services for pre-PMF startups

$100M+ TAM at $20-40K/month engagements.

“Most founders need a CRO''s thinking, not a CRO''s commitment.”Chad Peets context

Durability: Time-sensitive.

Named gap.

Lessons still worth keeping

Useful takeaways that did not fully clear the bar for durable principle status.

Lesson

Inside-sales-in-office is a recruiting WIN, not a loss

Inside-sales reps who are willing to commute are the ones investing in development; they get better faster from cross-functional proximity. Remote-friendly competitors collect the lower-development-willing tail.

A founder told Chad he was losing inside-sales recruits to remote-friendly competitors. Chad: "You're winning and you don't even know it." Inside salespeople who commute get more reps with the team, hear product / customer-success / CS conversations, develop faster.

Use when: Inside-sales orgs being pressured to go remote.

Skip when: Outside-sales / field-sales where in-office is irrelevant; pure-CS roles where co-location adds little.

Reframe inside-sales-in-office as a positive selection filter, not a recruiting drag. Build the company with the reps willing to commute.

“I said the fuck you are, you're winning and you don't even know it. Any inside salesperson should recognize that by being in the office, they are gonna get better faster... If a sales inside salesperson is not willing to make the sacrifice of a 30 minute commute every day to further his own career, I don't want that person.”Chad Peets

Durability: Time-sensitive in the post-COVID context; the structural argument about co-location-and-development is durable.

Lesson

Mid-market first, then enterprise — the Snowflake/Sigma pattern

Sequencing mid-market → enterprise is the structural default for enterprise SaaS. Companies trying to start in enterprise without a Wiz-class team will burn out.

Sigma is "a mid-market company by design" — not because it's only for mid-market, but because that's where the early product can compete on satisfaction. Snowflake at very early days could only sell ad-tech. Once the product matures, expand upmarket.

Use when: B2B SaaS founders sequencing GTM from $0 to $100M ARR.

Skip when: Categories where enterprise is structurally easier than mid-market (rare).

Default to mid-market first. Move upmarket only when product readiness and team size justify it. Don't copy Wiz unless you're Wiz-class.

“When we build companies, let's go back to Snowflake. We start in mid-market because I want to take a very small set of accounts, typically smaller accounts because their demands are less and I want to nail it.”Chad Peets

“Wiz is the only one I've seen do it successfully where they started in the enterprise.”Chad Peets

Durability: Durable; the GTM sequencing logic holds across enterprise categories.

The Plays

Try these this week

Verb-first executable actions — each one tied to a stated outcome in the episode.

Resume-driven motivation diagnosis — the 95% pre-call rejection

“95% of the people that sell software, I'm never calling because I can look at your background and say I know a lot about you. I know what motivated this person... if you said you went to work for Chris Degnan because you knew he was gonna develop you, I can validate that based on the career moves in your resume.”
— Chad Peets

30-60 min per resume diligence per

1
Document the company's profile signals
What companies have produced great hires for you? What types of moves indicate the right motivation? Build an explicit profile.
2
Read each job change as a motivation data-point
For every transition, ask: what motivated this person to leave? Was it money, base, quota, brand, leader, development, customer, mission?
3
Reject pre-call when the motivation history does not match what you offer
Money-only motivators move on. You cannot offer them what they want at startup scale. Don't waste the call.
4
Validate the 5% who fit in the call
For candidates whose motivation history matches, the call is validation, not discovery. Probe the specific transitions to confirm.
5
Calibrate the profile annually
Track which hires worked vs failed; refine the profile based on actual outcomes. The profile is a living artifact.

Scripts

recruiter-frame

Why did you leave [previous company] for [current company]? — followed by validation against resume timeline.

Before you start

· Documented profile of motivation signals for your company stage
· Recruiter trained to read resume-as-motivation-history
· Hiring managers aligned on the profile (no override pressure)

recruitingsales-hiringsourcingearly-stagegrowth-stagescalehyper-scale

The 2-candidates-1-hire interview process — Snowflake at scale

“Two candidates, one hire every time. If you're gonna scale like that, you can't have 10 interviews per hire. It kills the productivity.”
— Chad Peets

~2-week recruiting cycle per hire when running at scale per

1
Define the profile clearly and document it
Track record, motivations, resume signals, prior-company calibration. Without an explicit profile, every step downstream is noise.
2
Recruiter pre-screens at the resume level
95% of reps eliminated pre-call by reading their resume against the profile. Match resume motivation history to what your company offers; non-match = no call.
3
Bring two candidates to the hiring manager per role
Recruiter has done enough diligence that hiring manager hires one of the two every time. Volume of interviews per hire stays at 2-4, not 10.
4
Two interviews to first decision: one for selling, one for qualifying
Each is a binary stage. If after 2 hours the hiring manager cannot decide, the manager is the problem.
5
Subsequent interviews are also binary
Each interviewer is uniquely qualified to assess selling OR qualifying. Each interview is move-forward / not. No long deliberations.
6
No engineers or HR in the sales interview pipeline
Engineers are not qualified to assess sellers; introducing them creates process delay and friction. HR is not qualified to assess sales sellers either. Only sellers and qualifiers in the pipeline.

Before you start

· Documented profile based on company-specific success data
· Recruiter capable of resume-driven motivation diagnosis
· Hiring managers willing to make binary decisions in 2 hours
· Authority to enforce no-engineers / no-HR rule against pressure

sales-recruitinginterview-designhigh-scale-hiringgrowth-stagescalehyper-scale

Decision Moments

Actual decisions, real outcomes

Specific decisions narrated in the episode with their outcomes and transferable lessons.

Sutter Hill incubated Observe pre-product. Standard practice would be to hire the CRO after the product had early customers. Chad and the team chose to hire Keith Butler as CRO before there was a product to sell.

Did: Hired Keith Butler as CRO pre-product. Five years before any product was built, his job was to make thousands of customer-discovery calls and feed insights into the product roadmap.Outcome: Five years in, Observe is killing it. The pre-product CRO discipline produced a product that actually fit market need.

For category-defining ambitions, hire the CRO before the product. Founders cannot do thousands of customer-discovery calls; the CRO can.

Part of an emerging decision pattern across multiple episodes

A founder that Chad was advising said he was losing inside-sales recruits to remote-friendly competitors. Chad was running a search, the founder feared losing the war for talent.

Did: Reframed: in-office requirement is a positive selection filter, not a recruiting drag. Inside salespeople willing to commute are the ones investing in their careers; competitors who go remote-friendly collect the lower-development-willing tail.Outcome: The founder accepted the reframe. The recruiting strategy held: build the company with reps who commute, let competitors take the rest.

Frame office-presence as a positive selection signal, not a default-bad recruiting friction. Inside-sales-in-office is a win, not a loss.

Part of an emerging decision pattern across multiple episodes

A new VP-East was hired into one of Chad's portfolio companies. The VP wanted to bring 5 buddies who did not match the company profile. Chris Degnan (CRO) was busy running 400 people and could not interview every candidate.

Did: Refused to let the new VP override the profile. Chris explicitly empowered Chad to enforce profile discipline against incoming managers.Outcome: The profile held. The 5 buddies were not hired. The company kept the rep quality that made the velocity possible.

Profile discipline is non-negotiable when scaling fast. New managers haven't earned the right to override the profile that produced the company's success.

Part of an emerging decision pattern across multiple episodes

A Sutter Hill portfolio CEO wanted to set a forecast that the CRO did not believe was achievable. The CEO was using the forecast to justify a fundraising round.

Did: At Sutter Hill, the forecast cannot be set without explicit CRO agreement. The CEO was forced to align with the CRO before the forecast was set; if no alignment, the forecast is wrong.Outcome: Sutter Hill portfolio companies maintain CEO-CRO forecast alignment as a hard gate. Outside Sutter Hill, the CEO-driven forecast pattern leads to CRO firing in 9 months.

CEO-CRO forecast alignment is a hard gate. Business drives the forecast first; fundraising aligns to the forecast, not the other way around. Without this, the CRO predictably fails.

Part of an emerging decision pattern across multiple episodes

Tensions surfaced

Contradictions and trade-offs the episode raises — judgment calls a thoughtful operator has to navigate.

Tension

Tension: CRO-before-product vs CRO-after-PMF

Hiring CRO pre-product locks GTM assumptions; post-PMF wastes 6-12 months.

“Real tension between pre-product CRO or waiting for PMF.”Chad Peets

Durability: Durable.

Two-doctrine debate.

Corpus connection

Where this episode fits for retrieval

What kinds of decisions this briefing is best pulled into.

Primary decisions

• hiring-when-to-hire
• hiring-first-key-hire
• org-design

Temporal flag

timeless