Sales Call Objectives: Examples for Every Stage of the Deal

Priya had a 9:30 with the purchasing lead at a surgical center she'd been chasing for two months. Her sales call objective, written in the CRM the night before, was "build rapport and learn about their needs." The meeting went well. They talked for 40 minutes, laughed about parking, and agreed to "stay in touch."

Back in her car, Priya opened the CRM to log the call and realized she had nothing to put in the next-step field. Nobody had agreed to do anything. (Priya is a composite, but most reps have written that objective at least once.)

Sales call objectives are what separate a pleasant meeting from a step forward in the deal. You probably already know you should set one. The hard part is writing one that the customer can actually say yes to, at the stage the deal is really in.

This guide gives you a formula for writing them, a five-question test, 30 examples across 10 stages of the deal, and a simple way to check your calls against them each week. For the full pre-call template and checklist, see our guide to sales call planning; this article goes deep on the objective itself. And if you'd rather say your plan out loud than type it, ParrotNotes records it and gives you an AI summary.

What is a sales call objective?

A sales call objective is the specific thing you want the customer to agree to do by the end of the call. It's written as a customer action, not as something you'll do. "Present our pricing" is your activity. "The CFO agrees to review the pricing with us on Thursday" is an objective.

The best-known way to sort what a call achieves comes from Neil Rackham's research for SPIN Selling. His team studied more than 35,000 sales calls made by 10,000 salespeople in 23 countries over 12 years, and sorted the outcomes of a call into four kinds:

• Order: the customer buys.
• Advance: the customer agrees to an action that moves the sale forward, like bringing in another decision maker.
• Continuation: the conversation goes on, but nobody has committed to anything new. "Let's talk next month."
• No sale: the customer says no.

In a long sale, most calls can't end in an order. So the objective of a sales call is usually an advance. Priya's call ended in a continuation, which feels like progress and isn't.

How to write a sales call objective

Use one line:

By the end of this call, [named person] will agree to [specific action] by [date].

Then write a second, smaller objective in case the first one isn't there. Training firm Richardson tells sellers to "set a primary and secondary call objective". The secondary, or fallback, is still a customer action. It just asks for less.

Here's the formula applied to a first meeting:

• Primary: By the end of the call, Ana will agree to a second meeting with the plant manager before the 15th.
• Fallback: Ana will tell you who else signs off on a purchase this size, and what each of them cares about.

The five-question test

Richardson also asks that objectives meet SMART criteria. Adapted for a single call, that's five questions. If any answer is no, rewrite the objective before you go in.

1. Is it a customer action? The customer does something, not just you.
2. Can you tell afterwards whether it happened? You could write it in the CRM's next-step field without fudging.
3. Does it fit the stage? Asking for a signature in a first meeting fails this. So does asking for "more information" from a buyer who has already seen two demos.
4. Does it move the sale forward? It gives you access to someone or something new: a person, data, a site, a decision.
5. Does it have a date? "Soon" doesn't count.

Planning a call out loud is often faster than typing it. Record a 60-second plan in the parking lot, then record a two-minute recap after the call and check one against the other. Try ParrotNotes free: every recording gets an AI summary, so the plan and the result sit side by side.

Sales call objectives examples for every stage of the deal

Each stage below has three objectives: the advance you'll ask for, a fallback, and an information objective (what you need to learn whether or not the advance happens). Swap in your own names, dates and products.

Opening the deal: first contact and first meeting

A first contact objective should be small. On a cold call, the meeting is the whole win.

Finding the problem: discovery and the stakeholder meeting

Discovery is where information objectives do the heavy lifting. Our guide to running a discovery call covers the questions, and SPIN Selling's implication questions are built for the "cost of the problem" objective. If several people influence the deal, a stakeholder map shows you whose meeting to ask for next.

Showing the fit: demo and site visit or trial

A product demonstration without a next step is the most common continuation in sales. Decide before the demo what you'll ask for at the end of it.

Getting the yes: proposal, negotiation and close

Dale, a composite distributor rep, walked into a proposal meeting with one objective: get the PO. The buyer liked the proposal and couldn't sign it. Anything over $50,000 went through a procurement committee that met on the first Monday of the month.

Dale's fallback, written the night before, was a call with procurement. He asked for it, got a date, and learned the committee wanted three years of pricing, not one.

Without the fallback, he'd have driven away with "we'll get back to you." For the talk at this stage, see our guides to sales negotiation and closing techniques.

After the sale: onboarding check-in and account review

Account calls drift into continuations more than any other kind, because the relationship is already friendly. A written objective keeps a check-in from becoming a coffee.

Objectives that aren't objectives

Most weak objectives are activities, hopes or feelings. Here's how to turn each into a customer action.

Information still matters. It belongs next to the advance as a second line, not in place of it. That's why every row in the tables above has both.

Check your sales call objectives after the call

An objective only helps if you check it. After each call, mark the outcome in one word: advance, fallback, continuation or no sale. Then compare the outcome with what you planned. Our sales call debrief has the full set of questions to answer before you drive off.

At the end of the week, count them. Rosa, a composite sales manager, asked Tom, one of her reps, to do this for a week. Here's what his 12 calls looked like:

Seven of the 12 calls moved something. The four continuations had one thing in common: in three of them, the written objective was "check in" or "follow up." The next week, Tom rewrote every objective with the formula and wrote a fallback for each. Rosa used the tally in their one-on-one instead of guessing which deals were stuck.

The tally works best when the outcome is written right after the call, while you still remember who agreed to what. Parked in the car, a two-minute voice recap does it. ParrotNotes records offline, transcribes once you have a connection, and pulls out the action items, so the "who agreed to what" is in the note. The Free plan includes 5 AI-powered recordings a month with action items and sales frameworks like BANT, MEDDIC and SPIN.

Make every call ask for something

Sales call objectives aren't paperwork. They decide what you'll ask for before the friendly part of the meeting runs out the clock.

• Write it as a customer action, with a name and a date.
• Always add a fallback, so a "not yet" still moves something.
• Pair it with an information objective: what you need to learn either way.
• Match it to the stage. A meeting is a win on a cold call and a continuation in a negotiation.
• Count your outcomes weekly: advances, fallbacks, continuations and no sales.

Start with tomorrow's calls. Write your sales call objectives as one line and one fallback each, then check them when you're back in the car. Download ParrotNotes free: you get 100 minutes of recording a month and an AI summary on every recording, enough to plan and recap a week of calls out loud.