Sales Hiring and Ramp Guide: Hire Better, Get Them Productive Sooner

Sales interviews select for the skill being demonstrated in the room. A candidate who is warm, quick, and persuasive in conversation is displaying exactly the competency an interview measures well, and it is often not the competency the job requires most. In the majority of small-company sales roles, the daily work is disciplined follow-up, accurate qualification, and the willingness to have a slightly awkward conversation about budget. None of those show up in a pleasant forty-five minutes.

The second reason is that expectations are usually set by arithmetic that cannot work. A business with a four-month sales cycle hires someone in January and is disappointed by March. Nothing that person could have done would have produced revenue in that window, but the disappointment is real and it shapes how they are treated for the rest of their tenure.

Both problems have the same remedy: decide in advance what you are looking for, test for it rather than talk about it, and derive the ramp from your own cycle rather than from impatience.

Write this before the advert, and keep it to one page.

Four outcomes

Not duties, outcomes. Something like: build and hold a qualified pipeline of a defined size in the target segment; close a defined value of new business in the year; keep the CRM record accurate enough that a colleague could pick up any deal; and develop two named accounts into references. The test of a good outcome is that you and the candidate would independently agree on whether it happened.

Competencies under each outcome

For pipeline building, that might be originating conversations without warm introductions, and disqualifying quickly. For closing, it might be handling a pricing conversation without discounting reflexively. Naming the competency tells you what to test for, which is the entire point of the exercise.

Two things you are not hiring for

This is the part most people skip and the part that improves decisions most. Perhaps you are not hiring for industry experience, because your buyers are unusual anyway and you would rather have someone who asks naive questions. Perhaps you are not hiring for team leadership, because there is no team to lead for two years. Writing these down stops you drifting towards the impressive generalist and away from the person who fits the actual job.

Know which sales role this is

Working inbound enquiries at speed and originating cold conversations are different jobs that happen to share a title. The first rewards responsiveness, throughput, and consistency. The second rewards persistence, comfort with rejection, and research. Some people do both well, but hiring as though they are interchangeable is how you end up with an excellent inbound closer who cannot make themselves prospect, or an excellent originator who is bored within a quarter.

Structured competency interview

Same questions, same order, every candidate, scored against the competencies from the scorecard. This feels rigid and it is the reason it works: it lets you compare answers rather than compare how much you liked each person. Ask for specific past instances rather than hypotheticals, and follow every answer with what did you do specifically and what happened next, because vague answers become clear or fall apart under that pair of questions.

The live exercise

The single highest-value component. Send a one-page brief a short time before: here is our product, here is the person you are speaking to, here is what you know. Then run a fifteen-minute discovery call where a colleague plays the buyer and is deliberately unhelpful once or twice.

Score the questions they asked, not the polish of the delivery. Did they establish what the buyer is trying to achieve before describing the product? Did they ask what happens if nothing changes? Did they find out who else is involved in the decision? Did they cope when the buyer gave a vague answer, or did they accept it and move on? Write the rubric before the first candidate, and score immediately after each one rather than at the end of the day.

References with real questions

Skip the character check. Ask three things: what did this person need from a manager to do their best work, what was the environment like when they were at their most effective, and what would you put in place for them if you were hiring them again. These get honest, useful answers because they are not framed as a judgement, and they tell you whether your environment resembles the one where the person succeeded.

Keep it short

Two conversations and a decision within a fortnight. A five-stage process across six weeks is not thoroughness, it is indecision, and the candidates with the most options drop out first.

Ramp length is not a matter of opinion. It follows from your sales cycle.

That shape assumes a sales cycle of roughly six weeks. Stretch every phase proportionally if yours is longer. The important structural point is that each phase ends with a gate that is passed by demonstration, not by the calendar turning over. A rep who cannot yet run discovery unaided at week four does not proceed to month two pretending otherwise; they get another week and specific coaching.

Count the manager hours before you make the offer

The ramp above needs perhaps five hours of manager time in week one, three or four hours a week through month one, and two hours a week after that. If the manager does not have those hours, the ramp will not happen, and the new hire will conclude within a month that they are on their own. That is a decision worth making before the offer rather than discovering in week three.

A seven-person business hires its fourth salesperson. Average deal cycle is around eight weeks. The scorecard says the outcomes are originated pipeline in a segment the team has not covered, a defined new business number, and CRM records good enough for cover during absence. It explicitly does not require industry experience.

Four candidates reach the live exercise. The strongest interviewer in conversation asks three questions in the discovery exercise and spends eleven of fifteen minutes describing the product. Another candidate, noticeably less smooth, asks nine questions, pushes politely when given a vague answer about budget, and asks who else would need to agree. The rubric makes the choice obvious in a way the conversation would not have.

The ramp is set at four months rather than three, because eight weeks is the cycle. Month one target is conversations and opportunities only, with no revenue expectation stated anywhere, including verbally. Month two adds a pipeline creation target. Months three and four carry a reduced quota, and full quota begins in month five.

At day thirty, the leading indicators show activity slightly above the team average and opportunity creation below it. The manager listens to three recorded calls and finds the rep is qualifying too gently, accepting soft answers on timing. That is a specific, coachable problem, identified in week four rather than at the first quota review. Two weeks of focused practice on one question shifts the conversion.

At day ninety the rep has two deals at final stage and closes the first in week fourteen, which is roughly what the arithmetic predicted. Nobody is surprised, which is the actual achievement.

Hiring the interview rather than the job

Fix: a scored live exercise, with the rubric written before you meet anyone, weighted at least as heavily as the conversation.

Ramp expectations that ignore the sales cycle

Fix: derive ramp from cycle length, write it into the offer, and say it out loud in the first week so the new joiner is not privately concluding they are failing.

Onboarding as a document folder

Fix: gates passed by demonstration. Run the demo, handle the objections, complete an observed discovery call. Reading is preparation, not evidence.

No leading indicators, so problems surface at the first quota review

Fix: track conversations, opportunities created, and follow-up completion from week two. All three move long before revenue and all three are coachable.

Carrying an obvious mis-hire out of discomfort

Fix: an honest thirty-day checkpoint with evidence in front of both of you. Ending it at day forty is kinder to everyone than ending it at day two hundred, including to the person leaving.

Uneven territories disguised as performance differences

Fix: before concluding anything about a new rep, check what they were given. Lead volume, account quality, and territory are management decisions, and comparing attainment across unequal patches tells you nothing about the people.

Compare cohorts rather than individuals. Are people hired this year reaching their first deal sooner than those hired last year? Is the spread between your fastest and slowest ramp narrowing, which suggests the process is doing the work rather than the individual talent? Are the strong early performers still with you at twelve months? And a simple qualitative check: ask each new hire at day sixty what they wished had happened in week one. The same answer from three consecutive hires is the next thing to fix, and it is usually cheap.

Every leading indicator above is a query rather than a report someone compiles: conversations held per rep per day, opportunities created by owner, follow-ups completed on time, and days from start date to first closed deal. If those numbers require someone to assemble a spreadsheet, they will be looked at monthly, which is too late to change a ramp.

HelloGrowthCRM logs calls and messages against records automatically, so activity and pipeline creation by owner are visible daily without anyone reporting on themselves, and recorded conversations give a manager something specific to coach against. There is a free plan to start on, and paid access is $10/user/month billed annually.

Related reading: sales automation, lead management software, CRM with a built-in dialer, CRM for small business, what a CRM is, product features, and pricing.