An outbound sales CRM is the single record that shows four things about each prospect: who they are, who on your team owns them, how far they got, and whether you may still contact them. Your sequencer sends the messages, and your data tools find the people. Only one of the three should decide whether someone gets another touch: the CRM.
Set it up in this order: a short field list, stages built for outbound (contacted, replied, interested, booked, showed, won), a two-way sync limited to status, owner, last touch and suppression, and only then the tool.
Here is one month, May, from a campaign my team ran for a software development company in Germany: 9,000 people contacted, 453 email replies, 34 sales calls booked, 28 that took place, and 4 contracts. A pipeline with only "lead", "meeting" and "won" squeezes that month into three numbers and hides the two drops a CRM has to catch: 453 replies to 34 booked calls, then 34 booked to 28 that showed.
A disclosure before the tool talk: on my team's client campaigns, the client pays for the CRM directly, like the other tools, and it is not part of our monthly fee.
Which job belongs to the CRM and which to your other tools?
Its main job is to make sure no lead ever gets lost. I do not mind which CRM a team uses, as long as everyone who replied, asked for later or said no can be found again in one place.
Your prospects do not care what CRM you pay for. They do notice when someone writes to them after they said stop. That is a CRM job.
A new tool will not rescue a weak offer or a bad list. If a campaign does not convert with small numbers, a bigger platform will not make it convert with big ones. Fix the list and the offer first. Then pick the tool.
Vendor pages blend the layers into one product story, so separate them before you shop:
| Layer | Its job | What it owns |
|---|---|---|
| Data tools | Find and verify the people | The list before import, with a verification date |
| Sequencer (sales engagement platform) | Send the steps, time them, stop on a reply | Send history and step timing |
| CRM | Hold the truth about each person and account | Owner, stage, next step, do-not-contact status |
One rule decides where each field goes. If a field decides who gets contacted next or who owns the record, it lives in the CRM. If it only describes how a message was sent, it stays in the sequencer.
What do you need to log in a CRM for outbound prospecting?
Log only what a rep or a manager needs to act on a record in under a minute. Use this field map:
| Field | Example value | Why it is there |
|---|---|---|
| Person and company | Name, title, company, work email, LinkedIn URL | Identity, and a duplicate check before import |
| Segment | Industry, headcount band, country | Sorting, reporting and country rules |
| Source | List name, build date, verification date | Traces a bad batch back to where it came from |
| Owner | One rep | Stops two people writing to the same person; give each rep a separate territory |
| Stage | Replied | Drives reporting and the next action |
| Last touch | Date and channel | Shows who went quiet, and since when |
| Next step | "Call booked 14 Oct" or "Revisit Q2" | Nothing depends on someone's memory |
| Reply summary | "Uses a vendor, contract ends March" | Gives a second rep the context |
| Suppression status | OK, do not contact, unsubscribed or bounced, plus date and reason | Read by every sending tool |
The segment and source fields pay off when a campaign goes quiet. When that happens, sort the list by title, country and company size before anyone touches the copy. Rewriting the copy will not fix a bad list. Sorting is only possible if those fields were filled in at import.
The verification date matters because lists go stale. HubSpot cites MarketingSherpa research showing B2B data decays at 2.1% per month, which it puts at 22.5% per year. A list verified in January is not the same list by December.
Keep these out of the CRM:
- Message drafts and templates. They belong in the sequencer, where the steps are edited.
- Open rates. Google's sender guide says Google keeps no open-rate data of its own, and that low opens do not reliably point to a delivery fault (Google). Never move a stage on an open.
- Warm-up and mailbox health data. The sending tool watches that; reps cannot act on it.
- Personal details that do not help the next action.
Which pipeline stages match outbound best?
Generic pipelines start at "qualified" or "meeting". For outbound, that is too late, because most of the work happens before any meeting exists. Use these stages:
| Stage | A record enters when | It leaves when |
|---|---|---|
| Contacted | The first step goes out | They reply or the sequence ends |
| Replied | Any human reply arrives | Someone reads and sorts it |
| Interested | They agree to talk or ask for details | A time is set |
| Booked | A meeting is on the calendar | The meeting happens or falls through |
| Showed | The meeting took place | A deal opens or they drop out |
| Won | A contract is signed | It moves to your account team |
| No response | The sequence ended in silence | You come back later with a new angle |
| Not now | They asked you to return later | The revisit date arrives |
| Unqualified | Wrong fit, role or size | Only if the facts change |
| Do not contact | They opted out or asked you to stop | Never |
Booked and showed must be SEPARATE stages. In the month above, 34 calls were booked and 28 took place, so the CRM has to count both. If bookings count as meetings, the month looks better than it was, and you miss a reminder problem you could fix this week.
No-shows are not unique to one campaign. Ziel Lab reports a RevenueHero analysis of 6,428 B2B meetings that found an overall no-show rate of 6.5%, ranging from 1.2% to 18.1% by industry.
"Not now" needs a date. "After our budget round" in spring is a real lead in autumn, if the record says so.
Report every stage each week, so you see which ratio moved instead of one total. A weekly outbound report should show these same rows, one per stage.
Set the monthly goal one stage earlier, too: "start 50+ conversations this month" instead of "book 10 sales calls." Conversations come first. Calls come out of conversations. Clients come out of calls. So the conversation count is the number your team can actually push.
How should your CRM and sequencer sync?
The CRM is the source of truth for owner and contact status, and the sequencer owns sending. Sync both ways, but only these fields:
| Field | Direction | When it fires |
|---|---|---|
| Owner | CRM to sequencer | On assignment, before enrollment |
| Do not contact | CRM to sequencer | At once, removing the person from every sequence |
| Unsubscribe and hard bounce | Sequencer to CRM | At once, written into suppression status |
| Reply | Sequencer to CRM | On reply; the sequence stops and the stage moves to Replied |
| Last touch | Sequencer to CRM | After each sent step |
| Meeting booked | Calendar to CRM | Moves the stage to Booked and stops the sequence |
Before you switch the sync on, set these rules:
- Check the CRM before every enrollment. Before a contact enters a sequence, check the CRM's suppression list; on a shared list, also check that the contact has an owner. No list goes into the sending tool without that check.
- Unenroll on any human signal. A reply, a booking or an opt-out ends the sequence on every channel. If LinkedIn and email run together, treat them as one outreach sequence with a single unenroll rule.
- Do not close records early. Across my team's outreach, follow-up number 3 is usually the one that earns the reply. A rule that marks people "lost" after step one throws away the step that pays.
Replies need a person, too. Once replies start coming in, I put an inbox manager on them so none sits unread. That person moves the stage. The sync only tells the sequencer what happened.
One exception, for a founder working alone: if the CRM plan caps leads and the list runs into the tens of thousands, cold contacts can sit in the sequencer and get a CRM record at their first reply. Rule 1 still applies: push the CRM's do-not-contact list down before every send.
Every other layer of the cold email tool stack does one job and hands the truth back to the CRM. Whether outbound is the right motion at all is a different question, the one behind inbound versus outbound sales.
What compliance rules should the CRM protect?
Opt-outs and do-not-contact status belong in the CRM, because it is the one place every channel reads. This is not legal advice.
United Kingdom. In the ICO's guidance, direct marketing includes post, calls, texts and emails. PECR, the UK's e-marketing law, lets you email corporate subscribers with B2B marketing without consent. Two conditions: name the sender clearly, and give an address where the business can object. Live marketing calls to businesses have to be checked against the CTPS and TPS (the UK's business and personal opt-out registers for calls) and your own do-not-call list (ICO). So give the record a screening field, with a date.
United States. The FTC says CAN-SPAM does not exempt business-to-business email. Opt-outs have to be handled within 10 business days, and fines are counted per email (FTC CAN-SPAM guide). That clock is easy to miss when opt-outs sit in one rep's inbox, which is why the suppression field should sync on its own.
Gmail. Since February 1, 2024, anyone emailing Gmail accounts needs SPF or DKIM and a spam rate under 0.3% as measured in Postmaster Tools. Anyone sending over 5,000 messages a day to Gmail also needs DMARC and one-click unsubscribe (Google sender guidelines). None of these settings live in the CRM. Its part is a clean suppression list for the sequencer, because ignored opt-outs turn into spam complaints.
Country. Put a country field on every record so the sync can block markets by rule. For Germany, Austria and Czechia the rule is simple: cold email only with a compliant basis, LinkedIn otherwise.
Calls. My team stays out of cold calling; warm calls to contacts who have replied, engaged or opted in are an optional add-on, and only the CRM can say who qualifies. If you would rather hand the booking itself to someone else, that is the job of appointment setting.
Is a spreadsheet enough as a CRM for outbound?
For a first test with one sender on one channel, a spreadsheet is enough, and whether you need a CRM before outbound at all is an earlier question. The row count is rarely what breaks it. A second person is: two people working one file soon hold two versions of who replied, and an opt-out typed into one copy never reaches the other.
Even one person makes mistakes in a spreadsheet. Ray Panko's summary of spreadsheet experiments found that in nine studies of people building spreadsheets alone, 1.1% to 5.6% of cells were wrong on average.
Move to a CRM on the day any of these becomes true:
- A second person sends, replies or books from the same list.
- You run more than one channel, so one person can end up with two histories.
- Opt-outs have to reach a sending tool without someone copying them across.
- You need weekly stage reporting without rebuilding a pivot table.
- A "not now" needs a reminder months away.
Until then, give the sheet the same columns as the field map above, so the move later is a straight import.
Can HubSpot be used for cold email and outbound?
As the record, yes. As the engine for cold volume, HubSpot's own documents describe a narrower job. Its sequences send timed, one-to-one sales emails through each rep's connected work inbox. The limits:
- You need an assigned Sales or Service seat.
- Each sequence holds at most 10 email templates.
- By default, a contact is unenrolled when they reply or book through a meeting link.
Source: HubSpot Knowledge Base. That suits a rep working a few hundred named accounts. Spreading cold volume across many domains and mailboxes is a job for a separate sending tool.
As of October 2026, sequences come with HubSpot Sales Hub Professional, at $90 per seat a month billed annually or $100 monthly, and Enterprise, at $150 billed annually. Free and Starter ($9 a seat billed annually, $15 monthly) have no sequences (HubSpot Sales Hub pricing guide, updated September 2026).
The practical split:
- Keep the CRM as your record, owner and stage system.
- Use its sequences for one-to-one follow-up with people who replied or engaged.
- Run cold volume from a separate sending tool on separate domains, so a cold campaign never risks the account that holds your customer history. If you want that side run for you, that is what a cold email agency does.
What is the best CRM shortlist for outbound teams?
The right CRM depends on who touches the list. The shortlist rests on published pricing and features, not on a hands-on test. I compare Close and Attio because their pricing pages list outbound features plan by plan, so you can match a plan to a team size. HubSpot Sales Hub, priced in the section above, is the third option when your customer records already live there.
| Platform | Price per user a month (as of October 2026) | Outbound features on the vendor's page | Fits |
|---|---|---|---|
| Close | Solo $19 monthly or $9 billed annually (1 user, 10k leads); Essentials $49 or $35; Growth $109 or $99; Scale $149 or $139; 14-day trial; calling and SMS usage passed through at cost | Built-in email, calling and SMS from Essentials; workflows, power dialer and bulk email on Growth; predictive dialer and lead visibility rules on Scale | Teams that handle replies by email and phone from one record; the dialers only matter if you call people who already replied |
| Attio | Free for up to 3 seats; Plus EUR 39 monthly or EUR 31 billed annually (up to 10 seats); Pro EUR 93 or EUR 74; 14-day trial of Pro | Real-time contact syncing and automatic enrichment on Free; enhanced email sending on Plus; call intelligence and sequences on Pro | Small teams that want a flexible record and add sequences later |
Other names you will see on comparison pages, as of October 2026:
- Salesforce Sales Cloud costs $25 per user a month (Starter Suite) up to $550 (Max), with most editions billed annually.
- Pipedrive lists EUR 14 (Lite) to EUR 79 (Ultimate) per user a month billed annually.
- Apollo, a contact database with sequences, lists Basic at $49 per user a month billed annually, and Professional at $79, per Apollo's own plan guide.
- Salesloft and Outreach publish no list price.
Match the setup to the team:
| Founder-led | SDR team, 2 to 10 reps | Multi-rep, several markets | |
|---|---|---|---|
| Who touches the list | One person | Reps plus an inbox manager | Reps split by territory, plus managers |
| Minimum CRM need | Stages and a not-now date | Owner field, shared suppression, two-way sync | Visibility rules per rep, reporting by territory |
| Where cold contacts live | Sequencer, with the CRM record created at first reply | CRM, with an owner before the first send | CRM, with an owner before the first send |
| Shortlist fit | Close Solo, Attio Free | Attio Plus, Close Essentials or Growth, HubSpot Sales Hub Professional with a separate sender | Close Scale, HubSpot Sales Hub Enterprise with a separate sender |
If you are choosing this month, write your field map and stage list on one page first. Run each trial with your real list, and keep the tool that enforces both without workarounds. A tool that needs a workaround for suppression or owner today will need it every week. Fix the record first. Then scale the sending.
Setting up a CRM for your first outbound test? Book a call, share your stages and fields, and I will tell you which ones I would cut before the first send.
Questions about outbound CRM compliance
Who is liable if an agency sends the emails for you?
Under CAN-SPAM, both of you can be. The FTC is clear that outsourcing your email leaves your own duty in place, and that the sender itself can also be held liable. So keep the master suppression list in your own CRM, push it to whoever sends for you, and ask for their unsubscribes back every week.
How fast must an unsubscribe reach every tool?
If you send marketing email through HubSpot, its anti-spam policy wants unsubscribe requests processed within 24 hours, far tighter than the US legal deadline. The FTC adds that an opt-out link has to stay working for 30 days after each send, so never switch off a campaign's unsubscribe link the day it ends.
What must every cold email to US contacts carry?
Per the FTC: honest From and Reply-To details naming the real sender, a subject line that matches the body, your postal address, and an opt-out route. Put the address in the template footer, set once in the sequencer. The CRM only needs the opt-out status and the date it arrived.
How long should you keep non-repliers in the CRM?
Keep them in "No response" with the date their sequence ended, and give each record a review date. For UK contacts, the ICO says UK GDPR applies whenever you can identify a person, even in a business role, so each named record needs a lawful basis to stay, and if you cannot name one, delete the personal details.
