Appointment setting

A 42-person cybersecurity company has a strong SOC 2 story, a new VP of Sales, and a calendar full of meetings that go nowhere. Appointment setting is the work of finding a plausible business reason to talk, checking that the prospect is a fit, and booking a sales conversation with the right people.

The booked meeting isn't the goal. A useful sales conversation is.

If a setter books anyone who agrees to thirty minutes, the account executive gets the consequences: the wrong company size, no active problem, no authority, and no reason to buy now. Good appointment setting leaves the seller with context and the prospect with a clear reason for accepting the meeting.

What appointment setting actually involves

Appointment setting sits between prospecting and a sales conversation. It can start with an inbound demo request, a referral, or outbound contact with an account that fits the company's ideal customer profile.

The person doing the work might be an SDR, a dedicated appointment setter, or an outsourced sales development team. They research the account, contact the right person, ask a few useful questions, handle basic objections, and suggest a specific next step when there is enough evidence to justify one.

They also own the handoff. That means recording what prompted the conversation, what problem came up, who needs to be involved, and what the next meeting is supposed to cover.

They don't usually run full discovery or close the deal. The job is narrower: decide whether a sales conversation is worth both sides' time, then make that conversation easy to have.

Inbound and outbound need different treatment. Someone who requests a demo has already shown some interest. A cold prospect has not. Pretending otherwise makes the outreach feel dishonest.

Why appointment setting goes wrong

Most teams ask for time before giving the prospect a reason to spend it.

“Would you be open to a quick chat about how we help companies improve efficiency?” is not a reason. It's a request wrapped in fog. The same goes for a call script that rattles through six product features before asking a question.

Start with a business change you can point to. A payments platform might contact a finance operations leader after a company switches processors. A security vendor might contact after an audit finding or a new compliance requirement. A recruiting firm might contact a people leader after a funding round adds 80 planned hires.

The trigger doesn't prove the prospect will buy. It gives the conversation a credible starting point.

For example:

“I noticed your team recently moved payment processing to Stripe. Companies often review reconciliation controls after that change because reporting gets split across systems. Is your finance team dealing with that, or not really?”

That message tests relevance instead of pretending to know the answer. If the prospect confirms the problem, the setter can explain what a follow-up would cover and offer two times. If they don't, the conversation can end without wasting anyone's afternoon.

This is why cold outreach works better as one coordinated process than as disconnected emails, calls, and LinkedIn messages. Each touch should point to the same business issue. Three unrelated pitches just create three chances to be ignored.

A practical appointment-setting process

Start with account selection, not scripts.

Say a 25-person software company sells enterprise identity management. It can't sensibly have its SDR team contact every technology company in North America. The team needs boundaries first: employee range, geography, technology environment, buyer role, likely pain, and disqualifiers.

Then look for a trigger. A new executive hire, a funding round, a CRM or infrastructure migration, a SOC 2 project, a market launch, or a hiring plan can all justify research. So can a public deadline, such as a new regulation taking effect in six months.

The trigger needs to connect to a problem your company can actually help with. A new VP of Finance isn't automatically a reason to pitch accounting software. A new VP of Finance at a 300-person company moving from spreadsheets to NetSuite might be.

Research the contact and choose the channel that fits. LinkedIn can confirm a role change or give you company context, but a profile view or connection acceptance isn't buying intent. Use it to improve the message, not to manufacture interest.

On the first call, ask enough to establish fit without turning the conversation into an interrogation. “How are you handling this today?” is useful. So is “What changed that made this worth looking at now?” If the issue is real, ask who else is involved and whether there's a project or deadline attached to it.

You don't need a perfect qualification score. You need enough context for the account executive to prepare.

When there is a fit, offer a defined next step. “Would Tuesday at 10:30 or Wednesday at 2 work?” is easier to answer than “Let me know if you'd like to connect sometime.”

Send the invite immediately. Include the purpose, attendees, time zone, video link, and a short recap of the issue discussed. Calendaring software can handle availability and reminders. It can't fix a vague meeting description or create intent.

A worked example

Take a 60-person compliance software company selling to regional banks.

Its SDR team sends email campaigns to compliance officers and books product demos. The meeting rate looks fine, but only 14% of meetings become qualified opportunities. Account executives complain that prospects don't know why they're there.

The team narrows its target to banks with 250 to 2,000 employees that recently hired a chief risk officer or announced a core banking migration. The setter stops leading with the product and starts with the operational risk caused by fragmented evidence collection. The meeting is no longer called a demo. It's a 25-minute review of how the bank prepares for audits.

The opener is simple:

“You may already have this covered, but I saw that your bank is moving core systems this year. That change often creates duplicate control evidence and more manual work for the compliance team. How are you planning to manage that during the migration?”

The prospect says the team still uses spreadsheets and has an audit in six months. The setter confirms that the compliance director and internal audit manager should join, then offers two times.

The invite says:

“Review current audit evidence workflow during core system migration. We’ll compare the current process with two approaches used by similar regional banks. No product demo unless it’s relevant.”

That meeting has a trigger, a problem, the right audience, and a clear reason to exist. The seller can prepare. The buyer knows what they accepted.

The numbers also become more useful. Suppose the team books 32 meetings in a month, 25 happen, 16 meet the agreed qualification bar, and 6 become opportunities. “32 appointments booked” hides most of that story.

Which appointment-setting metrics matter?

Track the funnel in order. Otherwise, one inflated number covers up the failure underneath.

Activity counts still have a place. Calls, emails, LinkedIn messages, and follow-ups show whether the team did the work. They don't show whether the targeting or message was any good.

The more useful measures are:

• Positive response rate: the share of contacted prospects who engage meaningfully
• Meeting conversion rate: booked meetings divided by qualified conversations or positive responses
• Show rate: meetings held divided by meetings booked
• Qualification rate: completed meetings accepted by sales as a legitimate fit
• Opportunity rate: qualified meetings that become sales opportunities
• Pipeline per meeting: expected pipeline created from each completed appointment
• Cost per qualified appointment: delivery cost divided by meetings that pass the agreed bar

Watch the handoff closely. If account executives reject 40% of meetings because the prospect lacks authority or a relevant problem, the setter isn't producing pipeline. If show rates fall after a messaging change, inspect the confirmation email and meeting promise before blaming the prospect.

A good SDR team should review call recordings, replies, no-show reasons, and AE feedback each week. Not to police individual scripts. To spot patterns.

Maybe finance leaders respond to audit triggers while operations leaders respond to staffing pressure. Maybe product demos produce no-shows, while focused process reviews get attendance. The script should help a rep open clearly, ask a useful question, handle pushback, and propose the next step. If it sounds memorized, it probably contains too much copy and not enough judgment.