Outbound sales

Most outbound teams do not need more leads. They need fewer bad accounts.

I have seen teams send thousands of emails to companies that could never buy, then blame the subject lines when nothing happens. The spreadsheet looks productive. The pipeline does not. Adding another sequence usually makes the problem harder to see.

Outbound sales is seller-initiated prospecting. A rep identifies a company, finds the people likely to care, and starts a conversation through email, phone, LinkedIn, events, or another direct channel. In inbound sales, the buyer starts by requesting information, booking a call, or responding to content.

The difference is important. An outbound prospect may not be looking for a vendor yet. The seller has to establish why the conversation is relevant before asking for time, information, or a buying process.

Start with accounts, not messages

The best cold call cannot save a bad account list. Before a team writes a sequence, it needs an ideal customer profile that a rep can actually use.

“B2B companies that need better reporting” is not an ICP. A usable version might be: US fintech companies with 200 to 1,000 employees, a new CFO, and a recent audit finding involving reconciliation. That description gives a rep criteria for finding accounts and a reason for contacting them.

The profile should cover more than industry and employee count. Include the systems the company uses, the likely owner of the problem, the size of the operation, and events that can make the problem urgent. A data security vendor might prioritize companies moving workloads into a particular cloud environment or hiring their first security operations leader. A payments company might focus on businesses changing processors, expanding internationally, or introducing subscription billing.

These triggers do not prove a company is ready to buy. They give the rep a defensible reason to investigate. That is enough for the first message.

My view is that teams get this backward constantly. They debate whether email or phone works before deciding which accounts deserve contact. Channel choice matters, but it is rarely the first constraint. A poor account with a clever message is still a poor account.

Treat outbound as an account motion

A B2B purchase rarely belongs to one person. Sending a sequence to one contact and waiting for a reply is not account-based selling. It is contact-based hope.

Consider a 600-person software company that has hired a new VP of Infrastructure and is preparing for a SOC 2 renewal. A security vendor might contact the VP, the security manager, and procurement, but each message should address a different concern. The VP may care about audit risk and engineering time. The security manager may care about evidence collection and policy coverage. Procurement may care about vendor review and contract terms.

The rep should map the likely buying group, then write a reason for each relevant person to engage. That is multi-threading. It is not adding ten names from the same company to an automated sequence.

The channel plan should reflect the account and the person. A technical founder may answer a short, direct email. A director at a larger company may be easier to reach by phone after a funding announcement or executive hire. Procurement may not respond until someone else inside the account has confirmed there is a project.

The first message should make a narrow observation and ask a question that can be answered without a meeting. For the software company above, a useful opening might be:

Noticed you brought in a new VP of Infrastructure ahead of the SOC 2 renewal. Are evidence requests still handled by engineering, or has that moved to a dedicated security owner?

That is more useful than “We help companies simplify compliance.” It gives the prospect a chance to confirm, correct, or reject the premise.

What an SDR owns

An SDR usually owns the prospecting layer, not the final close. That work includes researching accounts, finding relevant contacts, calling, writing emails, following up, and deciding whether a conversation merits an AE’s time.

The handoff should contain evidence rather than adjectives. “Interested in learning more” tells the AE almost nothing. A useful handoff might say:

The VP of Finance at a 300-person logistics company confirmed that the team still reconciles carrier invoices manually. They are reviewing finance systems after a new CFO joined in March. She asked for an integration overview and included the controller on the next call.

That note identifies the problem, the trigger, the stakeholder, and the next action. It also gives the AE a way to judge whether the meeting belongs on the calendar.

Teams often measure SDRs mainly on meetings booked. That creates an obvious bad incentive. Reps book anyone who accepts an invite, while AEs spend their time rejecting poor-fit opportunities. A better measurement chain follows the handoff: held meetings, AE acceptance, qualified opportunities, pipeline created, and revenue from outbound-sourced accounts.

A practical cold prospecting example

Take a 40-person compliance software company selling to regional banks. It cannot afford to contact every bank in the market, so it begins with 150 accounts that match its ICP.

The team ranks those accounts using three signals: a recent compliance leadership hire, an announced core banking system change, and expansion into commercial lending. Each signal suggests that reporting, controls, or audit workflows may be under review. None guarantees a project, which is why the rep still needs to qualify the situation.

For a top-tier bank, the rep maps the chief compliance officer, head of risk, and operations lead. The opening message does not say, “We help banks automate compliance.” It references the system change and asks whether the transition has affected evidence collection or control testing.

If the operations lead confirms that quarterly evidence reviews still happen across spreadsheets, the rep can ask who owns the process, how much time it takes, and what must be ready before the next audit. Those answers determine whether a meeting makes sense. The rep is not trying to force a product tour into the first conversation.

That is cold outreach, but “cold” only describes the prospect’s familiarity with the seller. The useful work happens before the send: account selection, contact mapping, trigger research, message writing, and a decision about what would count as a qualified next step.

If the bank has no relevant trigger, no operational pain, and no reachable stakeholder, the answer is not more touches. Record the reason, lower the account’s priority, and use the time elsewhere.

Metrics that show what is actually broken

Activity metrics tell you whether the team is working. Calls made, emails delivered, conversations held, and positive replies can expose execution problems, but they do not establish that outbound is creating revenue.

Look at the measures by account tier, trigger, message, and rep. Held meetings from high-fit accounts matter more than total meetings. AE acceptance shows whether SDR qualification is credible. Qualified opportunity rate reveals whether conversations are connected to a commercial problem. Pipeline and closed revenue show whether the motion is worth continuing.

The pattern matters more than any single number. A low reply rate can come from weak copy, poor deliverability, a bad list, or an offer that does not matter. A healthy reply rate with almost no qualified opportunities usually means the targeting is wrong or the message attracts curiosity without buying intent. A high meeting rate followed by frequent AE rejection means the qualification bar is too low.

When a campaign fails, do not change every variable at once. First check whether the accounts fit. Then check whether the trigger is real. Then review whether the message describes a problem the contact owns. Only after those checks should the team argue about subject lines, send times, or adding another channel.