Nurture Campaigns.
Engineered to Convert.
You've seen the one-off blasts that go nowhere. You know leads go cold without follow-up. This page walks you through the complete process—from gathering your inputs to building a HubSpot-ready workflow—using Squad4 as a real worked example at every step.
The Numbers
Nurtured leads produce 50% more sales-ready opportunities at 33% lower cost. Companies with mature nurture programs generate 45% more pipeline than those running ad hoc email blasts. This isn't optional—it's table stakes for any B2B operation.
What You'll Build
By the end of this page, you'll have the planning framework, audience map, email structure, and workflow blueprints to build a real nurture campaign—from a basic linear sequence to an intelligent, behavior-driven engine with branching logic and sales handoffs.
The Worked Example
Every section uses Squad4's actual ICP, personas, pain points, and services as the through-line—so you're not learning from templates, you're seeing a real campaign come together. Adapt the same framework to your own company.
Gather Your Intel
Before you touch a workflow builder, you need these eight inputs locked down. If you can't fill in each block for your company, that's the gap to close first. Use Squad4's examples as a reference for what "done" looks like.
Who are you targeting at the company level? Industry, size, revenue, tech stack, growth stage.
Who are the actual humans you're emailing? Their role, seniority, decision-making power, and day-to-day reality.
What keeps each persona up at night? Map specific pains to each persona—not generic problems.
What outcomes do you deliver against those pains? Each value statement should answer a specific pain point.
What are you actually selling? Map each service to the personas and pain points it addresses.
What do you have to offer at each stage? Guides, case studies, demos, calculators, webinars—mapped to the buyer journey.
What action puts someone into the campaign? Form submit, page visit, list membership, lifecycle change.
How will you measure if it's working? Open rates, click rates, MQL conversion, pipeline influenced, time-to-close.
Map Your Audience
Now connect your intel to real people. But first—what's the purpose of this campaign? Every nurture sequence maps to a stage in the buyer's journey. Know which stage you're targeting before you write a single email.
This worked example targets the pre-customer journey—Awareness through Decision. The same framework applies to post-customer campaigns. Explore the full customer lifecycle →
Nail the Email
A great workflow can't fix bad emails. Before you build the sequence, understand the anatomy of a nurture email that actually gets read—and the timing logic behind when to send it.
Emails 2–4: 2–3 days apart. Build the narrative—problem, approach, proof.
Emails 5–6: 3 days. Give them breathing room before the ask.
Key insight: Shorter gaps for engaged contacts (1–2 days), longer gaps for passive contacts (3–5 days). That's where branching logic earns its keep.
1. Welcome — Deliver the promised resource
2. Problem — Name the pain they feel
3. Approach — Show how you solve it
4. Proof — Case study or social proof
5. Differentiate — Why you, not them
6. Convert — Clear next step with urgency
Common Mistakes That Kill Nurture Campaigns
Before you build, learn what to avoid. These are the seven most common anti-patterns we see in B2B nurture campaigns—click any card for the diagnostic signal and HubSpot fix.
Sending the same email to your entire database with no segmentation. High unsubscribes, low engagement, and your domain reputation tanks.
Segment by persona + lifecycle stage at minimumSending 5 emails in 5 days or spacing them 3 weeks apart. Too fast feels spammy, too slow loses momentum and context.
2–3 day gaps early, 3–5 days later in the sequenceCramming multiple CTAs, topics, or asks into one email. The reader doesn't know what to do—so they do nothing.
One email = one idea = one CTAEmails that read like they were written by a template engine. No personalization tokens, no human voice, no reason to keep reading.
Use first name + company + persona-specific pain pointsContacts stay enrolled even after they've booked a meeting, become a customer, or explicitly disengaged. This erodes trust and wastes sends.
Set goal criteria + suppression lists in HubSpotBuilding the campaign and never looking at it again. No A/B testing, no performance review, no iteration. Open rates decay and nobody notices.
Review metrics monthly, A/B test subject lines quarterlyContacts enrolled in multiple nurture campaigns simultaneously, getting bombarded from overlapping workflows. They unsubscribe from everything—not just your campaign.
Use suppression lists to prevent workflow overlapBuild Your Campaign
Now put it all together. These four workflow blueprints show the same nurture campaign at four levels of sophistication—from a basic linear sequence to a fully orchestrated, persona-driven revenue engine. Each diagram maps directly to HubSpot workflow objects.
A simple linear campaign—every contact gets the same emails on the same schedule. Good for getting started, but no personalization or branching. Everyone follows the same path regardless of engagement.
Introduces a single decision point—after the case study email, the campaign checks whether the contact engaged. Engaged contacts get a faster path with a direct CTA. Everyone else continues at the standard pace. One branch, one upgrade.
Email?
A context-aware campaign—branches based on engagement signals and lead score. Contacts who click the case study CTA get an accelerated ~7-day path with a Sales handoff. Disengaged contacts get a re-engagement attempt. Multiple decision points and internal notifications make this a true revenue engine.
Score?
CTA?
Opens?
The full revenue engine—persona-based content paths, lead scoring gates, multi-channel actions, re-engagement loops, and orchestrated workflow chaining. This is what mature RevOps teams run: every contact gets the right message at the right time through the right channel based on who they are and how they behave.
≥ 50?