Sort every outbound reply that is not a meeting into one of three objections: "not now", "not us" or "already have a vendor". Each one points at a different fix. Blesso, a done-for-you B2B go-to-market service, reports these categories each week and changes channels or signals after two misses, never the target.
Key takeaways
- A weekly outbound report has three tiers: activity, market response and business outcomes. Categorised objections sit in tier two.
- 'Not now' is a timing problem. It points at your trigger signals.
- 'Not us' is a fit problem. It points at your list and at who you reach.
- 'Already have a vendor' is a switching problem. It points at what you watch for and where you show up.
- After two misses, change channels or signals. Do not lower the target.
The three tiers in one minute
Blesso reports on outbound in three fixed tiers, in the same order every week. You can read the full detail in what a weekly GTM report should contain. Here is the short version.
| Tier | What it holds | Who answers for a miss |
|---|---|---|
| 1. Activity Blesso controls | Accounts sourced, scored and enriched; contacts mapped; sequences run; content shipped | The operator |
| 2. Market response | Reply rates, meeting attendance, account-page engagement, categorised objections | Both; the approach changes |
| 3. Business outcomes | Pipeline created, opportunities opened, closed-won traced to source | Shared; it moves slowly |
Tier one is the work. Tier three is the result. Tier two is the only tier that tells you why a result is not coming. That makes it the tier you can act on.
Why tier two decides what you change
If tier one is on plan and tier three is low, something sits between them. That something is how the market reacts. A reply count alone does not say what to do. Twelve replies could be twelve polite refusals or twelve questions.
Categories fix this. When each reply that is not a meeting lands in one of three piles, the biggest pile names the problem. Each problem has a different remedy, so the sort turns a vague "replies are weak" into a decision.
What each objection tells you
The meanings below are a working reading, not a measured law. They come from how the three words differ in what they say about the buyer. Check them against your own replies before you act.
| Objection | What the buyer is telling you | What it points at |
|---|---|---|
| Not now | The problem is real, the moment is wrong | Trigger signals |
| Not us | The problem is not ours, or someone else owns it | List fit and contact mapping |
| Already have a vendor | The problem is solved, for now | Switching triggers and reach |
"Not now": the timing is wrong
This reply accepts the problem. It rejects the date. A pile of these means your list is probably right and your timing is not. You reached the account before it had a reason to act.
The fix sits in signals. A signal is an event at the account that suggests a need, such as a hiring push. Blesso triggered the sequences for HappierHire, an AI hiring platform, on hiring signals. A sequence that fires on a trigger meets the buyer closer to the moment. A sequence that fires on a static list does not.
"Not us": the fit is wrong
This reply says the account, or the person, is not your buyer. A pile of these is a list problem or a contact problem. Either the account does not have the need, or it does and you wrote to someone who does not own it.
Two checks tell them apart. Read the titles of the people who said it. If they are the wrong role, your contact mapping is the issue, and a second channel to the right person can help. If the titles are right and the answer is still no, your signals let in accounts without the need. Tighten the signals that qualify an account.
"Already have a vendor": the need is covered
This reply says the problem is solved. It does not say the buyer is happy. A pile of these means you are reaching accounts that already bought, at a time when they are not looking.
The fix is to watch for the moment a covered need reopens. That can be a change at the account or a new leader. It can also be a second touch on another channel, so the buyer sees you again when the vendor disappoints. Treat the reply as a note to follow up later, not as a refusal to delete.
The rule that links the objection to the change
Blesso's rule is short: miss twice and we change something. More channels, or different signals. Not a lower target. The target is set before month one from your ACV, your market and how narrow your list is. A miss does not make the market smaller, so the number stays where it is.
The objection type decides which change to make. Here is how Blesso applies the rule to each pile. It is a decision aid, and the exact change depends on your market.
| Biggest pile after two misses | Change first | Why |
|---|---|---|
| Not now | Different signals | Move the send closer to a trigger |
| Not us, wrong role | More channels | Reach the person who owns the problem |
| Not us, right role | Different signals | Screen out accounts with no need |
| Already have a vendor | Different signals, then more channels | Catch the reopening, then stay visible |
Lowering the target is not in the table. It would hide the problem. If the target moves down whenever a month misses, tier two stops carrying information, because no number can ever fail.
A worked example with made-up numbers
This is an estimate, not a customer result. Say a month ends with 80 replies that are not meetings. They sort like this:
| Objection | Replies | Share of 80 |
|---|---|---|
| Not now | 40 | 50% |
| Not us | 16 | 20% |
| Already have a vendor | 24 | 30% |
The share is the count divided by 80. Forty divided by 80 is 50%. The biggest pile is "not now". If this is the second miss, the change is different signals, because half of the refusals are about timing. Adding channels would send the same badly timed message in a second place.
Now change the example. Suppose "not us" were 40 of the 80 and the senders held the wrong titles. The same two misses would call for more channels to reach the right role. The numbers are invented; the point is that the pile decides the change.
How to run the sort yourself
- Pull every reply from the period, and remove booked meetings and automatic out-of-office notes.
- Put each remaining reply in one pile: not now, not us, already have a vendor. If a reply fits none, keep an "other" pile and read it.
- Count each pile and divide by the total to get a share. Keep the counts beside the shares.
- For "not us", split the pile by whether the sender's title matched your buyer.
- Compare the result with last period. A pile that grows is the signal.
- After two misses, apply the table above and change one thing. Change one thing so that you can see its effect next period.
A missed target is easier to read when it is a held-meeting count, not a booking count. See booked versus held meetings and what to change when an agency misses its meeting target for the target side of the rule.
How Blesso handles it
Blesso reports categorised objections in tier two every week, next to reply rates, meeting attendance and account-page engagement. It counts meetings from your calendar, not its dashboard, and it agrees the target before month one. When a target is missed twice, it changes channels or signals. The how we work page lists the full rules, and the case studies page shows published results, each for one customer and none an average.
Read the rules on the how we work page and the results on the case studies page.
FAQ
What are the three outbound objections to track?
Track 'not now', 'not us' and 'already have a vendor'. They describe timing, fit and a covered need. Each one points at a different change, so a founder who sorts replies into them can see which change to make first.
What should I do when most replies say 'not now'?
Change your signals so the message lands nearer a trigger event at the account. 'Not now' accepts the problem and rejects the date. Your list is likely right, so do not rebuild it.
Is 'already have a vendor' a dead end?
No. It says the need is covered today, not that it stays covered. Watch for changes that reopen the need, and stay visible on a second channel. Keep these accounts on the list and follow up later.
Why not lower the meeting target after a miss?
A lower target hides the problem. The market did not shrink because a month missed. Blesso changes channels or signals after two misses and keeps the target, so tier two keeps its meaning.
How many replies do I need before the sort is useful?
There is no fixed number. With a small count, one reply moves a share by several points, so read the raw counts and not only the shares. Keep the categories steady and compare period to period.
Sort first, then change one thing
The biggest pile names the problem. Two misses name the moment. Change signals or channels, and keep the target.