How Do You Define What Counts as a Good Outbound Meeting?

What counts as a good outbound meeting?

A good outbound meeting is one where the right person at an on-ICP account shows up, confirms a real problem you solve, and agrees to a clear next step. Meetings that only meet one or two of those tests should still be logged, but they should not be counted as wins. Defining this up front keeps outbound honest.

Most outbound teams measure meetings booked. It is easy to count and easy to celebrate. It is also easy to game. A rep, an outsourced provider, or an AI SDR can fill a calendar with polite conversations that never turn into pipeline, and the dashboard will look great until the quarter ends.

The fix is not a new tool. It is a written definition of a good meeting that sales, marketing, and whoever runs outbound all agree on before the next campaign starts.

Why is meetings booked a weak outbound metric?

Because it measures activity on the prospect's calendar, not progress toward revenue. A booked meeting can be a no-show, the wrong person, a company you cannot serve, or a curious prospect with no problem to solve. Counting all of those as success rewards volume and hides the quality problem until pipeline comes up short.

The incentives make it worse. If an SDR is paid per meeting, they will book anything that agrees to a call. If an outsourced provider reports meetings booked, they will optimize for that number. Neither is acting in bad faith. They are doing what the metric asks.

A better metric does not replace meetings booked. It adds a quality filter on top. You still track how many meetings happen, but you also track how many meet the bar, and you make the second number the one that matters in reviews.

Which criteria should define a good meeting?

Use four tests: the account fits your ICP, the attendee has influence over the decision, the prospect confirms a problem you solve, and the meeting ends with an agreed next step. Each test is a yes or no answer the account executive can give right after the call. Together they separate pipeline from polite conversation.

The ICP test is the easiest to check before the meeting even happens. If the account would not pass your fit score, the meeting should not count, no matter how friendly it was. Outbound should not be the place where ICP rules get bent.

The influence test is about who attended. It does not have to be the final decision maker. A champion who owns the problem and can bring others in is enough. A junior employee who was curious about the email usually is not.

The problem test is the heart of it. Did the prospect describe, in their own words, a problem your product solves? Not a problem you suggested and they politely agreed with. Their own words. The next step test confirms momentum: a second meeting, a demo for a wider group, a trial, or a shared evaluation plan with a date.

How do you write the definition so people actually use it?

Keep it to one short paragraph and four checkboxes, store it where meetings are logged, and make the account executive tick the boxes within a day of each meeting. If the definition lives in a slide deck, nobody will remember it. If it lives on the meeting record in the CRM, it shapes behavior every day.

In HubSpot or Salesforce, that usually means four simple yes or no properties on the meeting or deal record, plus a calculated field that marks the meeting as qualified when all four are yes. The tooling is simple. The discipline of filling it in is the hard part.

Write the criteria in plain language. "Prospect described a problem the product solves" is clear. "Pain identified" is vague enough that everyone will tick it. If two reps could disagree about a checkbox, rewrite it until they would not.

This sits naturally next to your lead definitions. If you have already written a definition of a sales-accepted lead, the good meeting definition is the next step down the funnel and should use the same language.

Who should decide whether a meeting was good?

The account executive who took the meeting, with a quick review by a manager. The person who booked the meeting should not grade it, because their compensation depends on the answer. Separating the booker from the grader is the single most effective way to keep the definition honest over time.

This can feel awkward on a small team, where the founder books and runs most meetings. In that case, write down the four answers right after each call and review them weekly with whoever else is involved in sales. The point is to create a record that is not adjusted later to fit the story.

For outsourced SDR providers or AI SDR tools, the separation is even more important. Their reports should show meetings booked. Your reports should show meetings that passed your definition. If the two numbers drift far apart, you have a quality problem to discuss. I wrote about how to measure whether an AI SDR is working, and this definition is the core of that measurement.

How should no-shows and reschedules count?

Track them separately and never count them as good meetings. A no-show is a cost, not a result. A reschedule is neutral until the meeting happens. Watching the no-show rate by channel, campaign, and booker tells you a lot about how meetings are being set and whether prospects actually wanted them.

A high no-show rate is often the first sign of a quality problem. It usually means the prospect agreed to a call to end the conversation, not because they had a reason to meet. If one campaign or one booker has far more no-shows than others, look at the messaging and the booking process there first.

Some teams try to fix no-shows with reminder sequences. Reminders help a little. But the bigger lever is booking meetings with people who have a reason to show up, which brings you back to the problem test.

How does this definition change outbound strategy?

It shifts effort from volume to fit. Once the team is measured on good meetings, the incentive is to target better accounts, write messages that surface real problems, and qualify before booking. You will usually book fewer meetings and create more pipeline, which is the trade every revenue leader should want.

Messaging changes first. Emails that promise a quick chat give way to emails that name a specific problem and ask whether it is real for the prospect. Those get fewer replies, but the replies are more useful.

Targeting changes next. If meetings from a certain segment rarely pass the problem test, that segment probably is not your ICP, whatever the fit score says. The good meeting data becomes a feedback loop for your ideal customer profile. My guide on what should count as a qualified lead for a two-person team covers the same kind of trade-off earlier in the funnel.

What should you report each week?

Report meetings held, meetings that passed all four tests, the pass rate, and the no-show rate, broken down by channel and by booker. Then add one line on why failed meetings failed, using the four tests as categories. That gives leadership a quality view of outbound in under a minute.

Trend the pass rate over time rather than reacting to single weeks. Small teams have small numbers, and a single bad week can be noise. A pass rate that falls for a month is a real signal.

Finally, connect good meetings to pipeline created. Over a quarter, you should see that good meetings convert to opportunities at a much higher rate than the rest. If they do not, your definition needs work, and that is worth knowing too.

What should you do next?

Write a four-part good meeting definition this week: on-ICP account, attendee with influence, a problem confirmed in the prospect's words, and an agreed next step. Add four checkboxes to the meeting record in your CRM, have the account executive fill them in within a day, and start reporting the pass rate next to meetings booked.

Share the definition with anyone who books meetings for you, including outside providers and AI tools. It is much easier to agree on the bar before the campaign than to argue about it after.

If you want help defining what a good meeting means for your sales motion, or setting up the CRM properties and reports to track it, reach out. Let's chat about building an outbound system that measures pipeline, not just calendar invites.