Case Study

The Follow-Up That Knows Where You Came From.

How we replaced a single generic HubSpot nurture sequence with four source-specific follow-up tracks — so every lead gets a sequence built for how they arrived, not a sequence built for no one in particular.

HubSpot lead source routing workflow system
4
Source-Specific Follow-Up Tracks
100%
Leads Routed to Matched Sequence
0
Generic 'Thanks for Reaching Out' Emails
1
HubSpot Portal, Fully Orchestrated

The Problem

The firm was generating leads from four distinct sources — a live seminar program, paid search campaigns, referrals from professional contacts, and organic content. Each source produced a lead with fundamentally different context. All four were entering the same generic HubSpot nurture sequence.

High-intent seminar leads got the same slow drip as cold paid clicks. Referrals — who needed almost no nurturing — sat in a queue waiting for an email that felt like it was written for a stranger.

What We Built

We rebuilt the lead intake architecture around source context. Every lead entry point was tagged with a source property on contact creation. UTM parameters were standardized across paid campaigns and mapped to HubSpot contact properties on form submission.

Four workflow branches replaced the single nurture sequence: seminar leads receive a content-forward sequence that builds on what they already know; paid leads receive a fast, direct sequence; referrals receive a personal-feeling sequence that skips the education phase; organic leads receive a content sequence matched to the topic that brought them in.

We were sending the same email to someone who watched a 45-minute webinar and someone who clicked a Google ad two minutes ago. Those are completely different people at completely different points. The system finally treats them that way.

The System Architecture

HubSpot workflow architecture with four parallel enrollment branches triggered by a source property set on contact creation. UTM parameter capture via hidden form fields mapped to HubSpot contact properties. Standardized UTM framework across all paid campaigns. Landing page architecture with source-specific form variants. Manual entry protocol for referrals. Each branch carries independent email sequences, task creation, and conversion tracking.

The Results

Every lead now enters a sequence built for their specific context. Seminar leads stopped receiving emails explaining concepts they'd already sat through. Referrals stopped waiting three days for a booking prompt they were ready for on day one.

Source context became visible in HubSpot from the moment of contact creation — making pipeline reviews faster and follow-up decisions easier.

Client

Professional services firm — high-ticket B2C, South Florida (anonymized)

Engagement

Sprint
Initial build: 2 weeks

Stack

  • HubSpot CRM
  • HubSpot Workflows
  • UTM Framework
  • Landing Page Architecture

Services

  • HubSpot Automation
  • Lead Routing Design
  • UTM Architecture
  • Workflow Build

Your Turn
Similar problem?
Every system we build starts with understanding what's broken.
Book a call →