Selling Into a New Vertical: Gate Reps First

Chapters
What does learning a new vertical on live accounts cost?
It costs live pipeline. If your reps learn the buyer's vocabulary, stakeholders, and objections on real accounts, your first deals in that industry become the practice environment. Burning real pipeline as training material is the most expensive coaching method a sales org can choose.
The opposing case deserves a fair hearing. Some leaders hold that reps learn best on live calls and that practice environments add little. Live calls do carry a real buyer with a real agenda, using words nobody scripted. We agree those words are the most valuable raw material you have. We disagree about where reps should first meet them. Record the first calls, mine them, and let reps rehearse against those exact words before the next account is routed.
Treat vertical expansion sales training as three artifacts the enablement lead owns: a scenario set, an objection inventory with agreed first responses, and a routing gate. The sections below build each one, then give you a drill to run this week.
TL;DR
Before selling into a new vertical, build a short scenario set from your team's first real calls in that industry. Agree one first response for each vertical-specific objection, and route vertical accounts only to reps who pass a scored rep on those scenarios. The gate is a passing transcript, not a date on the plan.
- Source every vertical scenario from your own first calls: buyer terms, stakeholders, and objections in the buyer's exact words.
- Agree one first response per vertical objection and drill it until reps deliver it without notes.
- Route vertical accounts on a passing scored rep graded against your own methodology, not on time served.
- Read scores per rep, per scenario, never as one blended number.
- Run the first-response drill this week. Its pass bar is verifiable from the transcript alone.
Build the vertical scenario set from your first real calls
Start with transcripts, not a market primer. Pull every recorded call your team has had in the new industry. If nobody has had one yet, have a manager or a senior rep take the first discovery calls and record them.
Read each transcript and mark three kinds of moment. First, a term the buyer used that the rep did not know or misused. Second, a stakeholder the buyer named who does not appear in your current personas. Third, an objection your library has no first response for. Write each one down in the buyer's exact words. Those words become persona lines, so whoever plays the buyer says what a real buyer said.
Then turn the marks into a short set of industry-specific scenarios. We recommend starting with three to five, each tied to one call stage, one rubric row, and one exit criterion. Take the rubric rows from your own methodology, because generic rubrics produce feedback reps rationally discount. If your team runs SPIN, the discovery row might read: rep asks an implication question about the vertical problem before naming any product capability. For the full build method, see Sales Roleplay Scenarios From Real Calls.
Build every vertical scenario from buyer words in your own transcripts, never from a generic industry primer.
| Scenario | Source moment in your transcripts | Rubric row (observable) | Exit criterion |
|---|---|---|---|
| Vertical discovery call | Buyer used an industry term the rep did not recognize | Rep restates the buyer's term correctly and asks what the problem costs them | Buyer confirms the restated problem in their own words |
| New stakeholder | Buyer named a role absent from your personas | Rep asks who else signs off and what that person needs to see | Buyer states the stakeholder's role and one criterion they care about |
| Vertical objection | Buyer raised an objection with no agreed first response | Rep delivers the agreed first response, then asks one open question | Buyer answers the question rather than closing the topic |
How do you agree one first response for each vertical objection?
Collect the vertical-specific objections from your marked transcripts and write one first response for each. Then get your managers to agree on it before anyone drills it. One response per objection, not a menu. Its job is to earn the next turn of the conversation, not to close the objection.
A format we recommend has three parts. Acknowledge the objection using the buyer's own term. Give one sentence of honest position. Ask a question that hands the topic back. Take an objection like Our auditors have to sign off on any system that touches inventory counts. An agreed first response could be: That's a sensible control. What did your auditors ask for the last time a system touching inventory counts was approved?
Some strong reps argue that agreed first responses make them sound canned, and that their best handling is improvised. A line read flat from a card does sound canned, and we would not certify that delivery either. Our point is narrower. Rehearsal is what makes improvisation safe. Once the first response is automatic, a strong rep improvises the branches from understanding instead of being caught flat.
When the objection is about your firm's track record in the industry itself, do not write a new response from scratch. Use Industry Experience Objection: A Scored Drill, which covers that objection end to end. Keep it out of the vertical inventory you build here.
Should routing gate on a date or a passing scored rep?
Gate routing on a passing scored rep. A rep receives vertical accounts when their transcript on the named vertical scenarios meets the pass bar, not when a calendar date arrives. A 30-60-90 plan with dates but no gates is a countdown, not a ramp, and we recommend your vertical rollout plan avoid the same design.
The case for dates deserves a fair hearing. Its advocates hold that time-in-role is a reasonable readiness proxy and that most reps ramp at roughly the same pace. A date is also simple to administer and fair on its face. We still hold that time served is not readiness evidence. A date tells you when a rep was expected to be ready. A scored transcript tells you whether they are. Put experienced reps through the same gate; if they are ready, it costs them one session.
Write the gate as three lines. Named scenarios: the vertical discovery call and every objection in the vertical inventory. Pass bar: each rubric row met on a scored rep, read per rep and per scenario, never as one blended number. What it opens: vertical lead-tier routing, or the first solo discovery call on a vertical account. Add a manager checkpoint that carries a decision: advance, repeat, or escalate. If you already run a 30-60-90 onboarding ramp, add the vertical gate as a named row there rather than writing a separate plan.
Keep the decision on the transcript. Manager intuition alone systematically overrates confident reps and underrates quiet ones. In XL Roleplay, flags in the coaching report link back to the exact moment in the transcript. The checkpoint can open the failed row's moment directly instead of re-watching the whole session.
A drill to run this week: the vertical first-response rep
We recommend about 10 minutes of prep before the session. Pick one vertical objection from your inventory that appeared on a live deal, load its agreed first response, and choose the objection-handling rubric row. For an industry-experience objection, run the linked drill instead. We recommend a 30-minute run: 5 minutes of setup, 15 minutes of drilling, 10 minutes of debrief. Each rep runs the scenario at the discovery stage. The buyer raises the objection in the exact words from your transcript.
Every check in the pass bar is verifiable from the transcript alone. First, the rep's first turn after the objection contains the agreed first response in substance, using the buyer's term. Second, that turn ends with one open question, not a stacked set. Third, the rep names no product capability before the buyer answers. All three, or it fails. Treat talk/listen ratio as an input to investigate when a rep fails, not as part of the bar.
Here is a failing attempt. Buyer: Our warehouse team won't touch another screen during peak season. Rep: Totally understand, but our platform is really easy to learn, so let me show you the mobile app. The rep defends instead of acknowledging, asks no question, and names a capability before the buyer says another word. A passing attempt delivers the agreed line and stops: Agreed, peak season is the wrong time to add a screen. When your team last adopted a new system, what made it stick?
Debrief one moment and one behavior. Play back the objection turn and ask the rep what they would change before you render a verdict. Then put the re-run on the calendar. A failed drill is re-run, not marked complete.
Frequently asked questions
How many scenarios should a new vertical set include?
We recommend starting with three to five, each tied to one call stage and one rubric row. Add scenarios when new transcripts surface terms, stakeholders, or objections the set does not cover.
What if no one on the team has had a call in the vertical yet?
Have a manager or senior rep take the first discovery calls and record them. Build the scenario set from those transcripts before you route vertical accounts to anyone else.
Should experienced reps skip the vertical gate?
No. Run them through the same named scenarios. If they are ready, the gate costs them one session, and the transcript replaces an assumption with evidence.
Can we score vertical scenarios with a generic rubric?
Score them against your own methodology's rubric rows and call stages, with the vertical's terms and stakeholders written into the rows. Generic rubrics produce feedback that reps rationally discount.
Who should own new vertical sales enablement?
We recommend the enablement lead own the scenario set, the objection inventory, and the gate definition. Front-line managers own the checkpoint decision for each rep: advance, repeat, or escalate.