Are You Ready to Hire a Salesperson? 5 Questions

1. Do You Understand Why Customers Buy?

If you're the founder of a growing SaaS company, you've probably closed a meaningful percentage of the business yourself.

You understand the product, the customers, and the problems you're solving. You've also learned things through hundreds of conversations that may not exist anywhere outside your head.

You know which prospects tend to buy, what objections come up repeatedly, which use cases generate the most interest, and what usually causes a deal to stall.

The challenge is transferring that knowledge to someone else.

Your first salesperson won't have your product knowledge, your history with the business, or your authority to make decisions. They'll need to learn how to sell the value of the product without being the person who built it.

That doesn't mean you need a perfectly documented sales process before hiring.

In fact, one reason to make your first sales hire may be to help develop a more repeatable process.

But there's a difference between hiring someone to help refine what you've learned and expecting them to figure out everything from scratch.

Before hiring, I'd want to understand a few things.

Who is buying your product today? What problems are they trying to solve? What typically triggers a buying decision? How long does it take to close a deal? And why do you win some opportunities while losing others?

You don't need perfect answers.

But you should have enough evidence from actual customers and sales conversations to give the new person a reasonable starting point.

Otherwise, you may be asking them to validate the market, establish the sales process, generate pipeline, and close revenue simultaneously.

That's a lot to put on one person.

2. Do You Know Where Their Pipeline Will Come From?

This is one of the most important questions I ask founders.

You're hiring an Account Executive to close business.

Great.

Where are the opportunities coming from?

Will the person inherit an existing pipeline? Are you generating enough inbound demand? Is someone booking meetings for them? Or are they expected to create most of their own opportunities?

These are different selling environments, and they require different capabilities.

I've interviewed plenty of successful salespeople who performed very well with a steady flow of qualified meetings.

That doesn't automatically mean they can build pipeline from scratch.

The reverse is also true. Someone who excels at outbound prospecting isn't necessarily experienced at managing a complicated sales cycle with multiple decision-makers.

Neither is inherently better.

It depends on what your business needs.

Let's put some numbers around it.

Suppose you want a salesperson to close $750,000 in new annual recurring revenue.

Your average contract is $15,000.

That means you need 50 new customers.

If your win rate is 25%, you'll need approximately 200 qualified opportunities to produce those 50 customers.

That's simplified math. It doesn't account for ramp time, deal timing, churn, or differences in opportunity quality. But it exposes an important question.

Where are those 200 opportunities going to come from?

If your business currently generates 60 qualified opportunities per year, something needs to change.

Maybe you need more marketing investment. Maybe you need someone who can prospect. Maybe your founder-led network has been producing deals that won't be available to a new salesperson.

Or maybe the quota needs to be reconsidered.

The point isn't that you need to solve every pipeline problem before hiring.

It's that the salesperson, the pipeline strategy, and the revenue expectations have to make sense together.

You can't simply assign a quota and assume the opportunities required to hit it will appear.

3. Do You Know What Success Should Look Like in the First 90 Days?

Most founders can tell me what they want a salesperson to produce in their first year.

Fewer have thought carefully about what should happen in the first 30, 60, and 90 days.

That's a problem because early performance can be difficult to interpret without realistic expectations.

Consider two SaaS companies.

The first has a 14-day sales cycle, steady inbound demand, and an established process. A new salesperson may be able to learn the product, begin taking calls, and close initial deals relatively quickly.

The second has a 90-day sales cycle, limited inbound demand, and no existing pipeline for the new hire.

Expecting both salespeople to produce the same revenue in their first month would make little sense.

And yet companies often create ramp expectations without doing the math.

I'd start by working backward from the actual sales cycle and the work required to build pipeline.

What should the salesperson know after 30 days? What activities should they be performing independently after 60? What evidence should exist after 90 days that they're progressing toward the revenue expectations?

That evidence might include qualified pipeline created, discovery calls completed, opportunities advanced, or initial deals closed.

The milestones will vary by business.

What shouldn't vary is the need to define them before the person starts.

There's another part of this that founders sometimes overlook.

What will you be doing during those first 90 days?

Who's going to train the salesperson? Listen to calls? Help them understand why deals are won or lost? Provide feedback? Step into opportunities when necessary?

If you're making your first sales hire because you want to stop selling, you may be disappointed by how involved you still need to be.

You're not just hiring someone to take work off your plate.

You're taking responsibility for helping that person become productive.

Over time, the right hire should give you more leverage.

But that doesn't happen automatically on their first day.

4. Are You Hiring a Builder or an Operator?

This question came up in that founder intake conversation I mentioned earlier.

And it's one I think more founders should ask.

Do you need someone who can help build the sales motion, or someone who can execute an established one?

Those aren't necessarily the same person.

A builder is generally comfortable working through ambiguity.

They can test messaging, experiment with prospecting approaches, identify what's working, and help create a process that other salespeople can eventually follow.

An operator may be especially effective in an environment where the market, process, and expectations are already reasonably clear.

They know how to execute consistently, manage their pipeline, follow a methodology, and produce results.

Good salespeople can have elements of both.

But if your company is still figuring out how to sell consistently, that should influence the type of experience you prioritize.

Think about a salesperson coming from a large, well-known SaaS company.

They may have an impressive performance history, excellent training, a strong brand behind them, SDR support, and a sophisticated sales enablement function.

Now put that same person into a $2 million ARR startup.

There's no SDR. The founder is still involved in important deals. Messaging changes as the company learns. The CRM isn't perfect. There may not be a documented playbook.

That salesperson might thrive.

Or they might struggle because the environment requires capabilities they haven't had to demonstrate.

That's why I don't get overly excited about a recognizable company name or an impressive résumé without understanding the conditions behind the results.

I want to know what the person actually did.

Did they create their own opportunities? Help develop a process? Improve conversion rates? Work effectively without a lot of support?

Or were they exceptionally good at executing within a system someone else had already built?

Both can be valuable.

But you need to know which one you're hiring.

The goal isn't to find the most impressive salesperson. It's to find the salesperson whose capabilities match what your business needs next.

5. How Will You Verify They Can Actually Do the Job?

Once you've answered the first four questions, you're in a much better position to start interviewing.

You understand the business, the pipeline requirements, the early expectations, and the kind of salesperson you're looking for.

Now you need to determine whether candidates can actually do the work.

This is where I see founders put too much weight on polished interview answers.

They ask candidates to describe their sales process, explain how they handle objections, or talk about their biggest deals.

Those questions can be useful.

But describing how to sell isn't the same as demonstrating the ability to sell.

If prospecting is critical, I want to understand exactly how the candidate has generated opportunities in previous roles.

If discovery is critical, I want to see how they approach a realistic discovery conversation.

If the candidate claims consistent quota attainment, I want to understand the numbers behind it.

What was the quota? What percentage did they achieve? How did they rank against their peers? How much of their pipeline did they generate themselves?

And if they missed quota, what happened?

I'm not looking for a perfect performance history.

I'm looking for someone who understands their performance, can explain what drove the results, and can demonstrate the capabilities required for this particular job.

Sometimes that means asking a candidate to walk through a deal in detail.

Sometimes it means giving them a realistic scenario and watching how they approach it.

Sometimes the most revealing part of an interview is the second or third question you ask after their initial answer.

You don't need a complicated assessment process.

You need a process that collects meaningful evidence.

If your salesperson will spend a significant part of the job running discovery calls, it makes sense to evaluate discovery skills before hiring.

If they'll need to create pipeline, you should test whether they know how.

And if they'll be helping build the sales motion, you need evidence that they're comfortable working without a fully developed playbook.

Don't assume those capabilities exist because someone interviews well.

Give them an opportunity to demonstrate them.

For a more detailed look at building that evaluation process, see Building a Sales Hiring Process That Actually Works.

Being Ready Doesn't Mean Having Everything Figured Out

I don't expect a founder-led SaaS company doing $2 million in ARR to operate like a company doing $50 million.

You probably won't have the same sales infrastructure, training resources, or level of process maturity.

And that's fine.

Your first salesperson may play an important role in helping you build those things.

But before you hire, you should understand what you already know, what still needs to be figured out, and what you're expecting the new person to contribute.

That's the distinction.

If you need someone to help establish a repeatable sales process, hire for that.

If you need someone to execute a process that's already working, hire for that.

If you don't have enough pipeline to support the quota, address that in your hiring plan.

And if you haven't defined what success looks like, do it before you're evaluating someone's performance against expectations they never had a fair chance to meet.

You don't have to be perfectly ready.

You do need to know what you're hiring someone into.

Before You Start Interviewing

If you're considering your first salesperson or another critical sales hire, work through these five questions before posting the job.

We've also developed a Sales Hiring Readiness Worksheet to help founders think through the role, expectations, and decisions that should be made before starting a search.

[Get the Sales Hiring Readiness Worksheet]

And if you'd like help determining what kind of salesperson your business needs, that's a conversation we have regularly at GSD Coach & Recruiting.

We help founder-led SaaS companies define the role, establish realistic compensation and expectations, and recruit salespeople who fit the business they're joining.

Schedule a Recruiting Discussion

‍