SaaS SDR training: practice from first call to booked meeting

Short answer

SDR (sales development representative — the salesperson who makes first contact with a prospect and books a meeting) training in a SaaS company should practise four skills: a relevant opener with a company that fits the ideal customer profile, short qualification — problem, timing, decision-maker — handling typical SaaS objections, and handing the meeting to the account executive (AE) with a good note. An SDR's success is measured by well-qualified booked meetings, not closed deals.

The SDR role is usually filled by new hires and has high turnover. That makes practice especially important: if every new SDR learns in their first weeks on real prospects, the company loses a share of its most valuable leads each time.

The four stages of an SDR conversation

1. 1OpenerWho you are and why you are contacting this particular company — one or two sentences with one fact about the company. A permission question: "do you have two minutes?"
2. 2Short qualificationThree or four questions: do you have this problem, how is it handled now, by when does it need solving, who decides. Full discovery is the AE's job.
3. 3Objection"We already have a tool", "no budget", "send me an email", "now's not the time".
4. 4Meeting and handoffA dated meeting and a short, precise note for the AE.

The general script for setting a meeting with a decision-maker is in B2B meeting setting, and question technique in discovery questions. This article focuses on the SDR programme itself — profiles, handoff and plan.

From ideal customer profile to practice profile

SaaS companies usually have an ideal customer profile (ICP) written down already: sector, size, role, problem. For practice, derive three or four concrete conversation profiles from it:

• The operations manager: feels the problem but does not decide. Agrees to a meeting if the value is tied to their daily work, and is willing to invite the decision-maker.
• The small-company founder: short on time, asks about price and simplicity, has no patience for a long pitch.
• The manager already using a rival tool: says "we have X"; the real reason is that the tool does one part badly.
• The IT or security gatekeeper: asks about integration, data storage and security.

Weak and good answers

The dialogue fragments are illustrative. Prospect: "We already have a CRM; we don't need a new tool."

• Weak: "Our system is much better than yours; it has 50 features." The rival is run down and no reason is asked.
• Weak: "OK, sorry to bother you." The conversation ends at once and nothing is learned.
• Good: "Understood — plenty of people start there. I'm curious: where does your sales team lose the most time in your current CRM?" If the answer shows a problem: "That's exactly what we could show in a 20-minute meeting. Would Wednesday or Thursday work? It would help if the team lead who uses the system joined too."

The AE handoff note

The SDR's job does not end at booking — the AE should arrive prepared. A short handoff note has five lines:

• Company and role: who was spoken to, and are they a decision-maker.
• Problem: in the prospect's own words.
• Current solution: which tool or process, and what is not working.
• Timing and trigger: why now — a new branch, a new team, a budget cycle.
• Who will attend the meeting, and the agreed purpose.

It is worth checking this note in practice too: after the conversation the SDR writes the note and the manager compares it with the transcript — does the note match what the prospect said?

A four-week programme

1. 1Week 1 — product and ICPThe product, the ideal customer, competitors, approved answers. First practice with a simple profile at the end of the week.
2. 2Week 2 — opener and qualificationThe operations-manager and founder profiles; goal — a relevant opener and three qualification questions.
3. 3Week 3 — objectionsThe rival-tool and IT-gatekeeper profiles; "send me an email" and "not the right time".
4. 4Week 4 — real callsA limited number of first real calls with a mentor; one conversation a day is reviewed together and the weak stage repeated in practice.

The general structure of a new hire's first 30 days is in new sales rep training; the SDR programme is a shorter, more intensive version.

Measures for SDRs

• In practice: asking the qualification questions, a clarifying question after an objection, a dated meeting.
• In reality: not the number of meetings booked, but the share the AE accepts as "qualified".
• Handoff quality: the AE's view of the note — did they arrive prepared?

Measuring only the number of meetings pushes SDRs to book weak meetings. A practice score is a learning signal, not the basis of an SDR's bonus.

Illustrative example: B2B SaaS

This is not a real customer case. A company selling warehouse management software hires three new SDRs. Week two's reports show the SDRs listing product features in the opener and saying nothing about the prospect's company. One public fact per company is added to the profile's "knowledge" field, with a drill: use that fact in the opener. In week three the AEs note that handoff notes describe the problem in the SDR's assumptions rather than the prospect's words — the handoff note becomes its own practice topic.

Common mistakes

• Making the SDR do full discovery — the conversation drags and the meeting is lost.
• No fact about the company in the opener.
• Giving up immediately at "we already have a tool", or running down the rival.
• Booking a meeting with no handoff note for the AE.
• Measuring SDRs only by the number of meetings.
• Giving unapproved answers to security and integration questions.

Limitations

Simulation does not replace list quality or call timing — even the best SDR cannot get a meeting from a company that does not fit. Cold calling and email rules are regulated by country. A good result in practice does not guarantee the same number of meetings in reality.

In Vexvon AI Training

In Vexvon AI Training a SaaS company builds its own ICP-derived profiles; the AI test call suits cold-call practice and the Telegram chat suits written outreach practice. In scoring, needs discovery, objection handling, sales structure and next step are separate criteria; the company can add its own, such as "AE handoff note". New SDRs are added in bulk from a CSV or XLSX file.

Next step

Derive three practice profiles from your ICP and agree the five-line handoff note template with your AEs. For SaaS trial conversion see trial calls too; other sectors are in sales training by industry. To build it together, contact us.