Building a Sales Team from Scratch: What 272 Job Postings Tell You

There are two completely different jobs hiding behind the title "VP Sales."

One of them is building a sales team from nothing. The other is scaling a team that already exists. The skills overlap. The day-to-day doesn't. The comp structure doesn't. The risk profile doesn't. And yet most job postings, most career advice, and most interview processes treat them as the same role.

We pulled the data to see how different they are. Out of 1,501 executive sales postings tracked by The CRO Report, 272 (18%) use language like "build from scratch," "first sales hire," "ground up," "zero to one," or "founding." Another 695 (46.3%) mention scaling or growing an existing team. The rest fall somewhere in between or don't specify.

Those two groups, builders and scalers, are distinct jobs. Here's what the data says about each.

Two Jobs, One Title

Here's the simplest way to think about it.

A builder is hired when there's no playbook. There might be revenue. The founders have probably closed some deals themselves. But there's no repeatable sales process, no team, no defined ICP beyond "companies that said yes." The builder's job is to figure out what works, write it down, and hire the first people to execute it. If you've read about the transition from founder-led sales to a VP Sales, this is the role that sits on the other side of that handoff.

A scaler is hired when the playbook exists. Product-market fit is established. There's a sales motion that works. The scaler's job is to pour gas on it. Hire more reps. Open new territories. Build out the management layer. Push average deal size up and sales cycle down.

Same title on the business card. Completely different first 90 days.

Dimension	Builder (18%)	Scaler (46.3%)
Stage	Pre-PMF or early PMF	Post-PMF, proven motion
Primary job	Create the playbook	Execute the playbook
Carries a quota?	Yes, personally	Manages team quota
Team size at hire	0-2 reps	5-20+ reps
Comp structure	Lower base, more equity	Higher base, less equity
Key risk	Product doesn't sell	Team doesn't perform

The 272 build-from-scratch roles in our dataset aren't a small subset. They're nearly one in five executive sales postings. That's a lot of companies looking for someone to start from zero. And it means a lot of VP Sales candidates are walking into interviews without understanding which job they're actually being asked to do.

The Salary-Equity Tradeoff

Here's where it gets interesting.

The 272 build roles with disclosed salary data (16 postings) show an average base range of $184,150 to $228,712. That's below the national VP Sales average of $170,000 to $251,000 at the top end. A VP Sales hired to build from scratch makes less guaranteed money than one hired to scale an existing team.

Why? Equity.

Build roles compensate the base salary gap with ownership. The earlier the company stage, the larger the equity grant, because the risk is higher and the company needs to attract someone willing to take a pay cut on a bet.

Company Stage	Base Range	Typical Equity
Seed / Series A	$188,000 - $250,000	0.5% - 2.0%
Series A / B	$147,000 - $183,000	0.25% - 1.0%
Series B / C	$164,000 - $226,000	0.1% - 0.5%

Notice something counterintuitive. The Seed/Series A base range is actually higher at the top ($250K) than Series A/B ($183K). That's because the very earliest hires sometimes command premium bases precisely because there's no proof the company will work. A company that's raised a $5M seed round and has zero sales employees knows it needs to overpay to attract someone willing to walk away from a comfortable scaling role at a Series C company. The equity at 0.5% to 2.0% sweetens it further.

By Series A/B, the company has some traction. There's less uncertainty, so the base drops, and so does the equity. The math changes again at Series B/C, where the base recovers but equity tightens to 0.1% to 0.5% because the cap table is getting crowded and the shares are worth more per point.

The question every builder candidate needs to answer: do I believe in this company enough to take $20,000 to $50,000 less in base salary in exchange for equity that could be worth nothing or could be worth a multiple of what I'd have earned at the scaling job?

There's no universally right answer. But there's a calculable one. Use a comp modeling tool to run the scenarios before you negotiate.

What "Build from Scratch" Actually Means in Practice

The phrase shows up in 272 postings. But what does the day-to-day look like?

It means you're employee number one on the revenue team. The founders have been selling. Maybe they've closed a handful of design partners or early customers. Maybe they have a few hundred thousand in ARR from inbound leads and warm intros. What they don't have is a system.

Your first 90 days won't look like a VP Sales role. They'll look like an AE role, because you are the AE.

Month 1: Discovery

You're going to sit in on every customer call the founders have. You're going to read every closed-won and closed-lost deal summary that exists (there probably aren't many). You're going to talk to the five or ten customers who've already bought and ask them why. Not the polished case study version. The real version. What were they using before? What almost made them say no? What do they wish the product did that it doesn't?

You're building the ICP from evidence, not assumptions. The founders think they know who the buyer is. They're usually half right. Your job is to find the other half.

Month 2: Selling

You're carrying a bag. You're running the full cycle from prospecting to close. This isn't optional. You can't write a playbook for a sale you haven't personally made. You need to feel where the deal stalls, hear the objections that come up in every demo, and figure out what the competitive alternatives are that prospects are weighing against you.

This is where a lot of VP Sales hires from scaling backgrounds struggle. They haven't personally run a full sales cycle in years. They've been managing teams, reviewing pipelines, and presenting to boards. Now they're booking their own meetings and writing their own follow-up emails. It's a different muscle.

Month 3: Documenting and Hiring

By now you've closed enough deals (or lost enough) to have opinions backed by data. You write the playbook. Not a 50-page document that nobody reads. A living set of materials: the ICP definition, the qualification criteria, the demo script, the objection-handling guide, the competitive battle cards, the pricing conversation framework.

And you start hiring. More on that below.

The Hiring Sequence That Works

One of the most common mistakes in building a sales team from zero is hiring in the wrong order. The data in our postings reveals what companies are looking for in their build hires, and the expectations consistently follow a specific sequence.

Hire 1: You (the VP Sales / Head of Sales)

The builder. Player-coach. Carries a personal quota while designing the system. Of the 272 build-from-scratch postings, the overwhelming majority describe this hybrid role. You're not being hired to sit in a corner office and review dashboards. You're being hired to close deals and prove the motion works.

Hires 2-4: Account Executives

Once you've personally closed enough to know what works, you hire people to replicate it. Two to three AEs, not ten. The goal isn't headcount. The goal is proving that someone other than you can sell this product using the playbook you've written.

This is the hardest hiring decision you'll make. You need AEs who are comfortable with ambiguity, willing to give product feedback, and capable of selling without a brand name behind them. The AE who crushed it at Salesforce or HubSpot might flounder at a Series A company where nobody's heard of the product and the marketing site has three pages.

Hires 5-7: SDRs (After Outbound Is Proven)

Here's where the sequence matters most. Do not hire SDRs before AEs. Do not hire SDRs before you've proven that outbound works as a channel.

If your AEs are closing deals from inbound, founder referrals, and their own outbound efforts, then you know there's demand. If you then add SDRs to feed more pipeline to those AEs, you're amplifying something that works. If you hire SDRs first and they're booking meetings that AEs can't close, you've wasted money and demoralized two teams simultaneously.

The SDR playbook is already under pressure from AI tools and changing buyer behavior. Don't compound that by deploying SDRs before you have a proven conversion path for the meetings they generate.

Hire 8+: Sales Manager / Team Lead

Only after you have four or more AEs producing consistently do you need a management layer between you and the reps. Before that, you're the manager. Adding a layer too early creates bureaucracy without benefit. The founder or CEO doesn't want to hear about pipeline from someone who heard about it from someone who heard about it from the rep.

What "GTM Strategy" Means in 505 Postings

A third of all executive sales postings (505 of 1,501, or 33.6%) mention GTM strategy. But the term means different things depending on whether you're looking at a build role or a scale role.

In build roles, GTM strategy means: figure out who to sell to, how to reach them, what to say, and how to close them. It's creation. You're writing the go-to-market plan from scratch.

In scale roles, GTM strategy means: optimize the existing motion. Expand into adjacent segments. Launch in new geographies. Add a partner channel. It's iteration on something that already works.

The distinction matters in interviews. If a company asks you to "present your GTM strategy for the first 90 days," and they're a Series A company with $500K in ARR and no sales team, the correct answer is not a polished deck with market sizing and territory plans. The correct answer is: "I'd spend the first 30 days selling to understand the motion, then build the strategy from what I learn." Any plan you create before you've talked to customers is fiction.

If the same question comes from a Series C company with $30M in ARR and 15 AEs, they want the territory plan. They want to know how you'd restructure the team, which segments you'd attack next, and what metrics you'd use to track progress. Same question. Different correct answer.

Only 17 postings across the entire dataset (1.1%) mention product-led growth or PLG. That's a vanishingly small number, and it tells you something about who's doing the hiring. The vast majority of companies posting VP Sales roles are running direct sales motions, not product-led ones. PLG companies tend to hire "Head of Sales" or "Head of Revenue" later in their lifecycle, and those postings often use different language that doesn't always get captured in executive sales searches.

The Tool Stack at Each Stage

Tool requirements show up frequently in postings. Across all 1,501 executive sales postings in the dataset, Salesforce dominates with 180 mentions. HubSpot follows at 48. Then Outreach at 65 and Gong at 32.

But the tool stack that makes sense for a build role is different from the one that makes sense for a scale role. And getting this wrong costs months.

Day 1 Stack (Build from Scratch)

• CRM: HubSpot (free or Starter). Not Salesforce. You don't need enterprise CRM customization when you have zero pipeline. HubSpot's free tier handles contact management, deal tracking, and basic reporting for a team of one to three. When you're closing your first ten deals, the last thing you need is a three-month Salesforce implementation.
• Outbound: LinkedIn Sales Navigator + email. Before you invest in Outreach or Salesloft sequences, you need to know what messages work. Manual outbound for the first 50 to 100 prospects teaches you the messaging. Automation comes after you've found what converts.
• Call recording: Gong or Chorus. This is the one tool worth investing in early. Recording every sales conversation from day one gives you a library of objections, competitive mentions, and buyer language that you'll mine for months. It's also how you'll train your first AE hires.
• Everything else: spreadsheets. Forecasting, territory planning, comp modeling. A Google Sheet beats a purpose-built tool when you have five deals in your pipeline.

Scale Stack (Post-PMF, Growing Team)

• CRM: Salesforce. Once you have more than five reps and a complex sales process with multiple stages, approvals, and integrations, the switch to Salesforce makes sense. The 180 mentions in our dataset reflect this. Salesforce is the platform companies scale on.
• Outbound: Outreach or Salesloft. Sequencing, A/B testing, multi-channel cadences. At scale, you need automation. The 65 Outreach mentions in our data confirm it's the category leader in enterprise sales orgs.
• Revenue intelligence: Gong. At 32 mentions, Gong shows up across both build and scale roles. At scale, it's less about learning the market and more about coaching reps and surfacing deal risks before they blow up the forecast. AI-powered sales tools are increasingly embedded in this layer.
• Data and enrichment: ZoomInfo, Apollo, or similar. When you're building outbound lists for 10+ reps, you need a data provider. At the build stage, manual research works. At scale, it doesn't.

The pattern is clear: start simple, add complexity when the team's growth demands it. The VP Sales who walks into a five-person startup and immediately specs out a $200K annual tech stack has misread the room.

695 Postings: The Scaler Majority

While builders make up 18% of the dataset, scalers account for 46.3%. Nearly half of all executive sales postings are looking for someone to grow what's already working.

The scaler profile is fundamentally different.

• Proven team management. Scalers need to show they've managed 10, 20, or 50+ person sales orgs. The hiring committee wants to know you can recruit, coach, and retain reps at volume.
• Metric fluency. Scalers live in dashboards. Pipeline coverage ratios, win rates by segment, ACV trends, quota attainment curves, ramp times. The builder cares about closing the next deal. The scaler cares about whether 40 people can close 40 deals next quarter.
• Process optimization. The playbook exists. The scaler's job is to make it better. Shorten the sales cycle by two weeks. Improve demo-to-close rates by five points. Find the bottleneck in the handoff from SDR to AE and fix it.
• Cross-functional leadership. At scale, the VP Sales works with marketing on lead quality, with product on roadmap priorities driven by competitive losses, with CS on expansion revenue, and with finance on forecasting and planning. This is a coordination job as much as a sales job.

Comp reflects the difference. Scalers at established companies see higher bases because the risk is lower. The company has revenue, customers, and a working motion. You're not betting your income on whether the product finds a market. You're optimizing a machine that's already producing.

How to Know Which Job You're Interviewing For

Job postings are often vague. A title that says "VP Sales" might be a build role or a scale role, and the description might not make it obvious. Here are the signals to look for.

It's a Build Role If:

• The company has fewer than $2M in ARR
• There are no current sales employees (or one AE hired by the founders)
• The posting mentions "establish processes," "define the playbook," or "build the function"
• Equity is prominently featured in the comp section
• The company is pre-Series B
• The CEO is listed as the hiring manager (not a CRO or existing VP)

It's a Scale Role If:

• The company mentions an existing sales team size
• The posting references "grow from X to Y," "expand into new markets," or "build on existing momentum"
• There's a CRO or Chief Revenue Officer above the role
• The comp is mostly base plus bonus, with equity as a smaller component
• The company is Series C or later, or public
• Specific revenue targets are mentioned ($50M to $100M, etc.)

It's Unclear (Proceed with Caution) If:

• The posting uses both "build" and "scale" language
• There's no information about current team size or revenue
• The comp range is unusually wide ($150K to $300K base)

A wide comp range is often a tell. It means the company hasn't decided whether they want a builder or a scaler, and they're hoping the right candidate will self-select. This is a red flag. If the company can't articulate which job they're hiring for, they probably can't articulate what success looks like in the first year either.

Running the Equity Math

Builders take a comp discount for equity. But how do you evaluate whether the trade is worth it?

Start with the base gap. If the build role pays $228K max and a comparable scale role pays $251K max, that's a $23K annual difference. Over a standard four-year vesting schedule, that's roughly $92K in foregone base salary.

Now look at the equity. At a Seed/Series A company, you might get 1% of the company vesting over four years. If the company is valued at $20M post-money, your 1% is worth $200K at grant. But you're not getting $200K. You're getting the option to buy shares at the current price, hoping the value goes up.

The math that matters:

• If the company 5x's (a good but not exceptional outcome), your 1% of a $20M company is now 1% of a $100M company, worth $1M before dilution. Subtract your strike price and taxes, and you're looking at maybe $600K to $700K. Against $92K in foregone base, that's a strong return.
• If the company 2x's, your stake is worth $400K. After strike and taxes, maybe $250K. Still positive against the $92K gap, but not life-changing.
• If the company stays flat or dies, your equity is worth zero and you've taken a $92K haircut over four years for nothing.

The uncomfortable reality: most startups don't 5x. Many don't survive. The expected value of startup equity, weighted by probability, is often lower than the expected value of the comp premium at a larger company. But expected value doesn't account for the asymmetry. The upside is uncapped. The downside is capped at the base salary gap.

Builders who do this well don't gamble. They evaluate the company the same way a venture investor would. Product-market fit signals. Founder quality. Market size. Competitive positioning. Cash runway. If you're going to take a pay cut for equity, do the diligence. It's your money.

If You Want to Build: What the Data Suggests

Let's assume you've read all of this and you still want the build role. Good. The data points to a few things worth knowing before you jump.

The concentration is at Seed/Series A. That's where the heaviest concentration of build roles sits in our dataset. These companies have raised money, they have a product, and they're hiring their first revenue leader. If you're going to be a builder, this is the sweet spot. The equity is highest, the base is competitive (because they have to be), and you'll have the most influence over how the sales function is shaped.

You need to be comfortable selling. Not directing others to sell. Selling. Personally. The 272 build postings in our dataset aren't looking for strategists. They're looking for closers who can also build an organization. If you haven't carried a quota in five years, you need to be honest about whether you can still do it.

Pick the right founder. In a build role, you report to the CEO. That relationship is everything. If the CEO has unrealistic expectations about timelines, interferes with deal execution, or isn't willing to be part of the sales process during the first six months, the role will fail regardless of your talent. The best question you can ask in a build-role interview: "Tell me about the last three deals you closed. What worked and what didn't?" If the CEO can't answer that with specifics, they haven't been selling, and you're being hired to figure out a market they don't understand yet.

Negotiate the equity hard. The base is what it is. Companies hiring builders have budget constraints. But equity is where the value accrues if the company works. Know the dilution schedule. Know the vesting cliff. Know what happens to your shares if you're let go after the first year. These terms vary widely and they matter more than the base salary difference between two offers.

Set a personal timeline. Building from scratch takes 12 to 18 months to show clear results. If you haven't established a repeatable motion and a growing team by month 18, something is wrong. Either the product doesn't have market fit, the company isn't supporting the sales function properly, or you've misread the market. Give yourself permission to walk away if the data says it's not working, rather than sinking three years into a role that was never going to succeed.