B2B SaaS Email Marketing

Your nurture sequence is talking to one person. The purchase is being decided by nine, in a Slack channel you cannot see, over about four months. That mismatch explains most of what looks like an email performance problem in B2B SaaS: the copy is fine, the timing is fine, and the message is arriving at an individual who cannot act on it alone.

Roughly 94 percent of buying groups build a shortlist before they contact a seller, on the buyer research that gets cited most in this category. Your email program runs entirely inside that invisible stretch. So it has one job, which is arming whoever inside the account already wants you.

Why contact level nurture keeps missing

Contact level nurture assumes the person reading is the person deciding. In a mid market SaaS deal with six to ten stakeholders, that assumption is wrong for eight of them. The champion reads your email and agrees. Then they have to convince a finance lead who never opened it, an IT admin worried about SSO, and a security reviewer who wants a SOC 2 report and a data processing agreement.

Here is the specific failure. Your highest scoring contact is usually an analyst or a practitioner doing research, because researchers open everything. Lead scoring rewards that behaviour, routes them to an SDR, the SDR books a call, and the call goes nowhere because the person has no budget authority and never claimed to. The score was measuring curiosity.

Account level scoring fixes the routing. Aggregate every signal across the domain, weight buying roles higher than researcher roles, and set the threshold on the account. A company with one person reading five posts is researching. A company with four people from three departments hitting your pricing and security pages in ten days is buying, and the difference is invisible at the contact level.

There is a second reason contact nurture underperforms in B2B SaaS, and it is structural rather than analytical. The emails that matter most are the ones that get forwarded, and forwarding is invisible to your ESP. A champion who pastes your pricing comparison into a Slack thread with their VP has done more for the deal than forty opens, and your dashboard records one click. Teams optimising against the dashboard therefore optimise against the wrong behaviour, writing shorter clickbait subject lines when the winning move is producing something a person would be willing to put their own name next to internally.

Worth saying plainly: none of this means contact data is useless. You still need it for deliverability, for role detection, and for knowing who to write to. What changes is the unit of decision. The account decides when a sequence runs and how much volume it gets. The contact only decides which version of the message arrives.

Account level lists in a contact level ESP

Almost every ESP models contacts, not accounts, which is why this design is rarer than it should be. The workaround is straightforward: add an account object (or use the company record your CRM already has), compute account level fields on a schedule, then write those fields down onto every contact at the domain.

The fields worth computing are narrow. Engaged contact count in the last 14 days, distinct departments engaged, highest intent page touched, days since the account’s last product event, open opportunity flag, open support escalation flag, and total marketing emails sent to the account this week. That last one is the pacing field, and it is the one nobody builds.

Recompute nightly at minimum. Hourly if your product is self serve and signups arrive continuously, because the cost of a stale engaged_contacts_14d field is a sequence that starts three days after the moment it was supposed to catch. HubSpot can do most of this with company properties and calculated fields, Customer.io needs objects and relationships, and if you are running Marketo you already have the account structure and probably are not using it.

The four role tracks and what each one actually needs

Four tracks cover most B2B SaaS deals. Layer them on top of the account trigger, so the account decides when a sequence starts and the role decides what arrives.

Role track	Their real question	The asset that works	What kills the deal
Champion	Will this make me look right?	Forwardable business case, internal email template, a peer example	No ammunition for the internal meeting
Economic buyer	What does this cost and what does it replace?	One page cost model, consolidation math, payback period	Feature lists with no price
Admin or IT	How long will implementation take me?	SSO and SCIM docs, migration guide, integration list, realistic timeline	Discovering an integration gap in week three
Security and procurement	What is my exposure if this goes wrong?	SOC 2 Type II report, DPA, subprocessor list, pen test summary, trust page	A security questionnaire that takes you two weeks to return

The security and procurement track is the one most teams skip, and it is the one that quietly kills deals in the final month. If your company runs Vanta or Drata, your trust page already exists and probably has a self serve document request flow behind it. Link to it early and in plain language, because a reviewer who can pull the SOC 2 report at 4pm on a Thursday without emailing anyone is a reviewer who does not add two weeks to your cycle.

Detecting role is less precise than anyone admits. Job title strings are messy, self reported form fields are worse, and enrichment tools disagree with each other often enough to matter. Use a simple mapping with a default: if the title contains security, compliance, risk, privacy or legal, route to the security track; finance, procurement, VP or C level to the economic buyer track; IT, ops, admin, engineering or platform to the admin track; everyone else defaults to champion. That default is doing real work, so make the champion track your strongest one.

The champion enablement kit

Your champion has to sell internally in a meeting you will never attend, using material they assemble themselves, usually badly and at short notice. Give them a kit. Three assets, sent at the right moment, in a form they can forward without editing.

The internal email template is the asset with the highest return and the lowest adoption. Write it as though the champion wrote it. First person, their company’s context, one paragraph on the problem, one on the proposed fix, one sentence asking for a decision or a meeting. Keep it short enough to paste into Slack. The champion enablement playbook has the full version with copy you can lift.

Be honest about the tradeoff here. This kit takes real effort to build, maybe two weeks of a marketer’s time including getting security sign off on what you are allowed to publish, and it will be used by a minority of champions. That is fine. It is used by exactly the champions who are actively selling you internally, which is the population where a small lift is worth the most.

Pacing rules so one account does not get hammered

Cap at the account, then distribute. Four marketing emails per account per week is a workable ceiling, with no single contact receiving more than two. Without this, a ten person account in three overlapping sequences receives thirty emails a month from you, and the people who notice first are exactly the security and procurement reviewers you needed to keep calm.

The distribution rule matters as much as the cap. When the account allowance is spent, prioritise by role: champion first, then economic buyer, then admin, then security. Transactional and product notification email sits outside the cap entirely, but count it when you audit, because from the recipient’s side there is no such distinction.

Over emailing is the most reported problem in B2B SaaS lifecycle programs and the least measured, largely because ESP dashboards report per campaign rather than per recipient. It ranks near the top of the mistakes that quietly degrade a SaaS email program, and the fix is a field and a check, not a rewrite.

Account triggers worth building

Start a sequence on an account state change, not a form fill. These five triggers do most of the work in B2B SaaS, and all of them are computable from data you probably already collect.

A second person from the same domain signs up or engages within 14 days. That is the single strongest buying group signal available to a self serve product, and it should start the champion track immediately. A visit to your pricing page by someone who is not the original contact is the second. Three or more distinct contacts engaging within a 21 day window is the third, and it should route to sales, not to another nurture email.

The fourth is a security or trust page visit from any contact at the domain, which fires the security track and tells your AE that a review is coming. The fifth is usage crossing a plan boundary in a product led account, which is where product qualified lead email plays take over from marketing nurture entirely. For accounts already paying, the equivalent triggers live in expansion revenue email campaigns, where seat and usage thresholds do the same job for growth instead of acquisition.

What the whole thing looks like across a 90 day cycle

A mid market B2B SaaS deal runs about three months from first account signal to signature, and the email program has a different job in each month. Most teams build one long nurture track and run it flat across all ninety days, which is why the middle of the sequence always feels thin.

Month one is discovery, and the account is usually one person deep. Send a little, send it to the champion, and spend your effort detecting the second contact rather than persuading the first. Two to three emails across four weeks is plenty. The measurable goal for this month is not a meeting, it is engaged_contacts_14d moving from one to two, because that single change predicts more downstream pipeline than any click metric you have.

By the second month the committee has assembled, and your program either helps or becomes noise. Role tracks activate, the champion kit goes out, and the security track fires the moment anyone touches your trust page. Volume peaks here at the full four per account per week, spread across three or four people, and the content shifts from why this matters to how this works and what it costs.

Month three is procurement, legal and the internal business case, and the instinct to add persuasion emails here is wrong. Marketing email should go quiet and hand the account to sales with everything documented. What still earns a send is logistics: the implementation timeline, the migration guide, the answer to a security questionnaire, the reference customer who agreed to take a call.

The pattern to copy from that table is the shape, not the durations. An enterprise deal stretches this to six or nine months with two extra rounds of security review, and a $400 per month product compresses it to three weeks with two people involved. Match the volume curve to your actual sales cycle length by pulling the median from your CRM, then divide it into thirds.

The handoff SLA and account level reporting

Write the handoff as a contract with numbers in it. Trigger: two or more engaged contacts in 14 days, at least one in a buying role, plus one high intent page view. Response: SDR acts within 24 business hours. Outcome: logged as meeting booked, nurture return, or disqualified with a reason. No exceptions, because the exceptions are where the data goes missing.

Report on accounts, not leads. The numbers that belong on the dashboard are accounts engaged, accounts handed to sales, handoff to meeting rate, and pipeline from account triggered sequences. Contact level opens and clicks stay available as diagnostics for deliverability and subject line testing, which is what tested subject lines are for, but they do not go in the board deck.

We stopped reporting MQLs in the weekly and started reporting engaged accounts. The number was a tenth the size and finance believed it for the first time.

One number will change how you allocate all of this: segment NRR. Enterprise focused B2B SaaS sits near 118 percent median net revenue retention while SMB focused SaaS sits near 97 percent. Upmarket, the expansion track is where email earns its budget and deserves your best people. Downmarket, recovery and conversion matter more, and an elaborate buying committee program is overbuilt for a two person decision. Run the arithmetic for your own ACV with the email revenue calculator before you commit a quarter to this.

What to build first

Build the account fields. Nothing else in this guide works without engaged_contacts_14d, roles_engaged and account_sends_this_week computed nightly and written to every contact at the domain. It is a week of work with your ops person and it unblocks everything downstream.

Then ship the champion track and the pacing cap together, in that order, and leave the other three role tracks for the following month. Ship the security track third, because it is the one that shortens cycles you are already winning. Compare your starting numbers against the segmented email benchmarks so you know which stage is actually below median, and read how buying group demand generation works upstream of email if you need the paid and content side to match. The rest of the sequence library sits in the SaaS email marketing hub.