CRM vs ESP
CRM email marketing
When to send from the CRM versus a dedicated email tool, how logging helps sales, and why marketing blasts inside a CRM still need ESP habits.
Two different send paths share a contact record
A CRM's job is the person and the deal: who owns the account, what was promised, what happens next. An ESP's job is the campaign: authentication, throttling, templates, unsubscribes, bounce handling. CRM email marketing is what happens when companies try to do the second job from the first system because the contacts already live there. Salesforce and HubSpot both sell this overlap. The overlap is a product choice, not a law of nature.
That can be the right call for sales follow-up. It is often the wrong call for a 40,000-person newsletter. The CRM will happily let you select a view and send. Mailbox providers still treat that traffic as bulk mail. You inherit ESP problems without ESP tooling unless the CRM vendor also runs a real sending stack.
CRM send
Fine for a sales follow-up to 12 people
ESP send
Bulk, auth, unsub, bounce handling
What sending from the CRM gets you
Logged activity is the honest win. A rep sees that marketing already sent the case study, so they do not paste it again. Deal stages can suppress people who are in procurement. Territory rules can keep a campaign off someone else's accounts. If your marketing tool is a separate island, none of that is automatic.
Sales sequences (HubSpot sequences, Salesforce emails, Outreach-style steps wired into the CRM) belong here when a human is in the thread. Those messages should look like they came from a person, because they did. Volume should stay closer to a mailbox than to a blast. When a sequence starts looking like a newsletter with merge fields, you have crossed into marketing send and should switch tools.
What a dedicated ESP still does better
Dedicated email tools obsess over placement: dedicated or shared IPs, complaint loops, seed lists, template rendering, and a subscription center that is not buried in CRM settings. Ecommerce ESPs also understand catalogs, inventory, and browse events. Most CRMs treat those as custom objects you have to build.
Deliverability teams prefer one marketing sending domain with clean DNS, not every salesperson's CRM blast going out through a mix of Gmail API and a forgotten marketing add-on. If sales already sends from connected inboxes, keep marketing on a separate subdomain (news. or mail.) so a bad campaign does not sink the reps' one-to-one mail.
A split that holds up
Use the CRM to decide who is eligible and to log what happened. Use an ESP (or the CRM vendor's actual marketing-email product, which is an ESP with a CRM skin) to send anything that is not a personal reply. Sync unsubscribes and bounces both ways the same day. If a person hits unsubscribe in the ESP and the CRM still shows them as 'subscribed,' you will mail them again and they will complain.
Do not run two competing newsletters, one from Salesforce and one from Mailchimp, against the same file. Pick a system of record for marketing permission. The CRM can be that system if you treat subscription as a first-class field, not a note on the record.
Common questions
Is HubSpot a CRM or an ESP in this split?
Both, which is why people get confused. The CRM record is the source of truth for the person. Marketing Hub email is still a bulk sender with DNS, lists, and unsubscribes. Use it like an ESP that happens to sit on the same contact. Do not use a logged sales email as a substitute for that product.
Can I skip an ESP if my CRM has a send button?
For a few dozen personal follow-ups, yes. For campaigns, only if that send button includes authentication, list-unsubscribe, bounce handling, and a way to export suppressions. Many CRM 'send' features are wrappers around a mailbox. Wrappers do not give you a marketing reputation.
Related
Prefer markdown? CRM email marketing.md