Why Your First Sales Hire From Salesforce Might Fail

The science of performance portability, stage fit and why great CVs can produce bad hires

There's a hiring decision I see repeatedly in early-stage SaaS.

The business has found some traction.

The founder has closed the first customers.

There's enough revenue to believe something is working.

Now it's time to build sales properly.

So the company goes looking for someone who has "seen scale."

Salesforce.

HubSpot.

Microsoft.

ServiceNow.

Snowflake.

Pick your logo.

The logic seems perfectly reasonable.

Find somebody who's carried a huge number inside a world-class sales organisation and bring that experience into the startup.

They know what good looks like.

They know the playbook.

They've operated at scale.

What could go wrong?

Quite a lot.

Because there's a question hiding underneath that CV that we don't ask often enough:

How much of that person's previous performance belonged to them, and how much belonged to the system around them?

That isn't just a startup hiring theory.

There is some fascinating research behind it.

The Performance Portability Problem

Harvard Business School professor Boris Groysberg and colleagues studied what happened when star knowledge workers moved between organisations.

Their research followed star securities analysts changing employers.

You might expect a star to remain a star.

They didn't necessarily.

The researchers found that stars who switched firms experienced an immediate decline in performance that persisted for at least five years.

But the really interesting part was when the decline was greatest.

Performance suffered most when people moved to organisations with weaker capabilities and when they moved without colleagues from their previous environment.

Those moving to firms with better capabilities, or alongside members of their team, showed no significant short or long-term decline.

The conclusion matters far beyond financial analysts:

Performance isn't always completely portable.

Some of what looks like individual excellence is embedded in the environment surrounding the individual.

And that should make anyone hiring from a highly developed sales organisation think.

You're not hiring their previous company

Imagine a candidate sitting opposite you.

They've consistently delivered 130% of a £5m quota at a major SaaS company.

That's impressive.

But what created the 130%?

Certainly their capability.

But perhaps also:

The brand that opened doors.

The category customers already understood.

The SDR organisation generating meetings.

The marketing engine creating demand.

The sales engineer running technical discovery.

The partner ecosystem creating introductions.

The RevOps team designing territories.

The enablement team developing playbooks.

The customer base providing references.

The manager coaching deals.

The data identifying the right accounts.

The product maturity reducing risk for buyers.

And years of accumulated organisational learning embedded in the sales process.

When you hire the person, you don't get any of that.

You get the person.

Yet we look at the outcome created by Person × System and often attribute it almost entirely to the person.

That's the mistake.

A better way to think about performance

I think there's a useful mental model here.

Not a literal equation, but a way of interrogating someone's track record:

Individual Capability × Organisational Capability × Market Context = Observed Performance

The CV shows you the output.

Your job in an interview is to understand the inputs.

And that becomes particularly important when somebody is moving between radically different environments.

Because your £2m ARR startup probably doesn't look much like Salesforce.

You may have limited brand recognition.

An evolving ICP.

Inconsistent pipeline.

A couple of usable case studies.

No dedicated enablement.

Limited RevOps.

A founder still involved in major deals.

Pricing that's still being tested.

Messaging that's still changing.

A CRM containing more hope than data.

And perhaps three people in marketing.

The candidate hasn't suddenly become less talented.

The environment in which you're asking that talent to perform has changed.

The Capability Delta

I'd call the gap between those two environments the Capability Delta.

Imagine the candidate previously operated somewhere with mature capabilities across:

Brand.

Demand generation.

Sales enablement.

RevOps.

Customer proof.

Product maturity.

Partner ecosystem.

Sales methodology.

Management infrastructure.

Market awareness.

Then compare those capabilities with what exists in your company today.

The bigger the difference, the larger the Capability Delta.

And the larger the Capability Delta, the more important another question becomes:

Can this person recreate enough of what they're about to lose?

That, to me, is a much more useful hiring question than:

"Have they worked somewhere impressive?"

Because a big Capability Delta isn't automatically bad.

Someone from Salesforce might be an exceptional early-stage hire.

But you need evidence that they weren't simply a beneficiary of the capabilities you're now removing.

This gets even more interesting

Groysberg and Linda-Eling Lee later examined star performers hired into two different situations.

Some were hired to exploit an existing capability.

Others were hired to explore, meaning they had to initiate something new.

Stars hired to reinforce existing activities experienced a short-term performance decline.

Those hired to create new activities experienced both short and long-term declines.

In other words, transferring proven talent into an environment where they had to create rather than operate was considerably harder.

Sound familiar?

Because that is remarkably close to the distinction between joining a mature sales organisation and becoming the first sales leader in an early-stage SaaS business.

One asks:

Can you operate the machine?

The other asks:

Can you build one?

Builder vs Operator

These are different muscles.

An excellent operator knows how to take an established system and improve it.

They optimise.

Coach.

Inspect.

Forecast.

Standardise.

Specialise.

Manage complexity.

Create leverage through teams.

Drive consistency across an existing motion.

Those capabilities become incredibly valuable as a company grows.

But an early-stage builder is being asked to do something different.

They need to operate when the answers aren't known.

Test the ICP.

Challenge positioning.

Rewrite messaging.

Build the first outbound motion.

Create qualification.

Recruit the first few sellers.

Get personally involved in deals.

Work out why pipeline isn't converting.

Build forecasting when the data isn't trustworthy yet.

Create enough process to capture learning without suffocating the company in bureaucracy.

Kill things that aren't working.

And do all of that while still carrying a number.

The irony is that many of the things that make someone successful inside a mature sales organisation may never have required them to develop those muscles.

Not because they couldn't.

Because the organisation didn't need them to.

"But they've seen what good looks like"

This is the obvious counterargument.

And it's a fair one.

Someone coming from a genuinely excellent sales organisation may have been exposed to outstanding leadership, process, enablement and execution.

That experience can be hugely valuable.

But seeing what good looks like isn't the same as knowing what needs to exist now.

That's an important distinction.

The £2m ARR company doesn't need the £500m ARR sales operating system.

It needs the next version of its own.

And importing everything you've seen at BigCo can create a dangerous form of false maturity.

Suddenly there are mandatory CRM fields everywhere.

MEDDPICC has been rolled out.

There are weekly forecast calls.

QBRs.

Pipeline coverage ratios.

Account plans.

Enablement sessions.

Territory rules.

Dashboards.

Stage definitions.

A 47-page sales playbook.

It looks more sophisticated.

But has the company actually learned how to sell?

Process should capture learning. It shouldn't substitute for it.

One of the most valuable characteristics of an early-stage sales leader is knowing what not to build yet.

Stage fit isn't just startup folklore

There is a much broader body of organisational psychology research around the concept of fit.

A major meta-analysis by Amy Kristof-Brown, Ryan Zimmerman and Erin Johnson examined 172 studies and 836 relationships across person-job, person-organisation, person-group and person-supervisor fit.

The broader finding was that fit is meaningfully related to a range of outcomes after someone joins an organisation, including attitudes, performance and withdrawal behaviours.

Context matters.

Which makes our obsession with logo prestige slightly strange.

We often ask:

Where have they worked?

When perhaps the better question is:

How similar was the environment in which they succeeded to the environment we're asking them to succeed in now?

Stage fit works both ways

There's an important caveat here.

This isn't an argument that startup people are better than big-company people.

And it certainly isn't an argument that you shouldn't hire someone from Salesforce.

The mistake works in the opposite direction too.

The person who is exceptional at taking a business from £1m to £10m isn't automatically the person you need from £50m to £200m.

Eventually exploration needs to become standardisation.

Founder proximity decreases.

Teams become teams of teams.

Management layers appear.

Specialisation increases.

International complexity grows.

Forecast accuracy becomes increasingly important.

Heroics become dangerous.

The organisation needs leverage.

The brilliant builder who refuses to become an operator can eventually become just as limiting as the brilliant operator hired before there is anything to operate.

So the argument isn't:

Big company bad. Startup good.

It's:

Hire for the environment you're actually hiring into.

Interview for portability

This changes how I'd interview an early-stage sales leader.

I'd spend less time admiring the outputs and considerably more time deconstructing how they were produced.

You did 130% of quota.

Great.

Where did your pipeline come from?

You built a £20m region.

Great.

What existed when you arrived?

You implemented MEDDPICC.

Great.

What specific problem were you trying to solve?

You managed 30 people.

Great.

How many did you personally recruit, and what did the organisation provide around you?

Then I'd go looking for scars.

Tell me about a time there wasn't enough pipeline and nobody else was coming to fix it.

Tell me about an ICP you discovered was wrong.

Tell me about something you built before RevOps existed.

Tell me about a message that wasn't landing.

Tell me about a quarter you missed.

Tell me what you changed afterwards.

Tell me about a process you removed because it wasn't helping.

Tell me about your first three hires.

Tell me about something you tried that failed.

Tell me about a time the founder was still carrying too much of the sale.

And perhaps most revealingly:

What would you deliberately NOT build in your first 90 days here?

Now we're not interviewing for prestige.

We're interviewing for performance portability.

Deconstruct the CV

Perhaps this is the simplest way to think about it.

When evaluating somebody from a highly successful organisation, don't ask whether their previous company was impressive.

Assume it was.

Instead, take away the infrastructure one component at a time.

No brand.

No SDR engine.

No mature marketing organisation.

No established category.

No RevOps team.

No enablement.

No army of SEs.

No mature playbook.

No predictable inbound.

No huge customer reference base.

Then ask:

What's left?

That's the person you're actually hiring.

And if what's left is still someone who can create demand, diagnose markets, recruit, sell, learn, adapt and build systems from ambiguity...

Hire them.

Their big-company experience may become an enormous advantage.

But if you can't separate their capability from the capability of the organisation around them, you're not evaluating the candidate.

You're evaluating their previous employer.

Hire for the next problem, not the last logo

The most impressive CV in the room can still be completely wrong for the job.

Because past performance is evidence.

But it isn't proof of portable performance.

The question isn't whether someone has experienced scale.

It's whether they've demonstrated the capabilities required to get your company from where it is now to where it needs to go next.

Sometimes the answer will be the person from Salesforce.

Sometimes it will be someone from a 70-person SaaS company nobody on the board has heard of.

The logo isn't the signal.

The environment in which they created their results is.

So before hiring your first sales leader, measure the Capability Delta.

Understand what you're removing from around them.

Work out whether you're hiring a builder or an operator.

And hire for the problems ahead of you, not the prestige behind them.

Because you aren't hiring Salesforce.

You're hiring the person who walks out of it.