Back to Blog

How a SaaS Company Built a HubSpot ABM Engine: 3 Phases From Generic Sequences to Account-Based Lead Scoring

Three-phase evolution from generic outbound sequences to intent-based account scoring—built on HubSpot with Factors.ai, G2, and LinkedIn Sales Navigator.

How a SaaS Company Built a HubSpot ABM Engine: 3 Phases From Generic Sequences to Account-Based Lead Scoring overlayed on an graphic depiction of a stepped process with boxes connecting to each other/
Case Study - Project Overview

Project Overview

SaaS Account-Based Marketing on HubSpot

Industry & Client
SaaS/Developer Tools
Engagement
Active Retainer 8/10 Complexity
HubSpot Hubs
Marketing Hub Sales Hub CRM
Integrations
Factors.ai G2 Clay LinkedIn Sales Navigator Sequencing Tool
Primary Challenge
Scaling outbound beyond generic sequences without replacing the existing stack
Hypha Team
Project Manager Senior Inbound Content Developer
Key Focus Areas
ABM Evolution Intent-Based Account Scoring Automated Lead Routing Executive Reporting


Most outbound teams know what it feels like to be running blind. The rep has a LinkedIn Sales Navigator license, a sequencing tool loaded with prospect lists, and a message that goes to everyone the same way. It works well enough as a starting point, but without any signal telling you which accounts are actively researching right now, which ones fit your ICP, or who should get a call today versus next quarter, you can’t prioritize—and that’s a lead scoring gap before it’s anything else. Bridging it is the difference between an outbound motion that plateaus and one that keeps producing.This is the story of how we rebuilt that motion for a SaaS client over three phases: from generic sequences to a full account-based marketing engine on HubSpot, with intent data flowing in from multiple sources, ICP scoring reworked around live signals, automated routing that gets hot accounts to the right rep within 48 hours, and executive dashboards that surface pipeline movement in real time.

The Gist

The client sells developer tooling in a competitive SaaS market. Their outbound motion had a solid foundation in place but lacked the intent layer that would let the team prioritize effectively and leadership see what was actually happening in the pipeline. The work across three phases turned that foundation into a functioning ABM engine—intent data, account-level scoring, and automated routing built on top of what was already there.

When Lead Scoring Isn’t Enough

Going into the engagement, the existing stack was functional. HubSpot was the CRM foundation, a sequencing tool handled outbound email, and reps were sourcing prospect lists from LinkedIn Sales Navigator. What the stack couldn’t do was identify in-market B2B accounts—the ones actively researching, showing buying signals, and worth prioritizing above everything else. Every prospect got the same sequence regardless of buying stage, because there was nothing telling the system—or the reps—who was actually moving. Without intent data, ICP scoring was running on static firmographics alone. Without scoring, there was no regional routing, so leads weren’t consistently reaching the rep best positioned to work them. And leadership had no visibility into pipeline development beyond what reps manually logged.

That’s the ceiling most outbound teams hit when they’ve built a solid Phase 1 foundation but haven’t added an intent layer on top of it.

Phase 1

Getting Reps In

The initial setup followed the pattern common to most SaaS outbound programs. HubSpot served as the CRM backbone, an outbound sequencing tool ran email campaigns, and LinkedIn Sales Navigator sourced prospect lists. Reps pulled those lists, loaded them into sequences, and reached out manually, with the same message going to every prospect regardless of fit or timing.

The foundation was solid—HubSpot was in place, the sequencing workflow was running, and reps were actively working accounts. Where Phase 1 falls short is in its inability to tell you which accounts are actually moving. Answering that question was the work of Phase 2.

Phase 2

Using B2B Intent Data to Score and Route Accounts in HubSpot

This is where the architecture gets serious.

Hypha brought in Factors.ai as the intent aggregation layer. The Factors.ai HubSpot integration pulls live signals from three sources simultaneously: G2 intent data, which captures competitor research behavior from accounts actively reviewing alternatives to their current tools; Clay, which provides company and contact enrichment for ICP fit scoring; and LinkedIn and web activity, which surfaces engagement signals across the buying team. Those three streams combine into a unified intent signal that feeds directly into HubSpot, giving the scoring model live input to work from rather than static firmographic data alone.

With that signal in place, the ICP scoring model was reworked around live intent rather than fit criteria alone. An account where engineers are actively researching competitors on G2 while a senior buyer is engaging across LinkedIn is not the same account as one that merely matches on paper—and the updated model reflects that distinction, weighting real-time signals alongside traditional fit attributes to identify accounts that are actually moving.

The shift from static firmographic scoring to dynamic intent-based ICP scoring is where most B2B marketing intent data implementations either work or fall apart. The data is only as useful as the workflow architecture that acts on it.

From there, HubSpot lead routing handles account assignment automatically. When an account crosses the scoring threshold, it gets tagged as a Marketing Qualified Account (MQA) with a target flag and date stamp applied in HubSpot. The routing sequence from that trigger runs as follows:

  1. Account tagged as MQA in HubSpot, target flag set with date stamp

  2. HubSpot workflow fires, creating a task and notifying the account owner

  3. 48-hour SLA clock starts

  4. Routing logic checks territory assignment and whether an open deal already exists for that account

  5. Rep receives an account brief—a G2 and Factors summary—before making first contact

  6. Multi-channel outreach begins, meeting is booked, SQL is created in HubSpot

ABM Architecture Diagram

The Three-Phase ABM Architecture

HubSpot Implementation

Intent Sources

HubSpot Workflows

Rep Experience

Factors.ai

Hot / Warm account signal

G2 Intent

Competitor research behavior

LinkedIn / Web

ICP fit scoring

Clay

Company & contact enrich

Account tagged MQA

Target flag + date stamped

Workflow fires

Task created, owner notified

SLA clock starts

48-hr follow-up window

Account brief

Intent signal summary

Personalized outreach

Multi-channel sequence

Meeting booked

SQL created in HubSpot

Executive MQA Dashboard

Built for management visibility across the full pipeline
MQA → Pipeline SLA Compliance Attribution


The routing logic in Step 4 is where the real complexity lives. Handling territory assignment, open deal detection, and SLA enforcement within a single workflow isn’t a simple if/then structure—it’s the kind of build that earns an 8/10 complexity rating. What the rep receives at the end of it isn’t just a task notification; they already know what the account has been researching, what their company profile looks like, and where they sit in the ICP before the first outreach goes out.

Phase 3

Replacing MQL with HubSpot Account-Based Scoring

An MQA, or Marketing Qualified Account, scores the account as a whole based on aggregated intent signals across the buying team, rather than scoring an individual lead against Marketing Qualified Lead (MQL) criteria. That distinction is the foundation Phase 3 was built on.

The traditional MQL/SQL model scores individual contacts: a lead hits a point threshold and gets passed to sales. That approach made more sense when buying was linear. In practice, especially at a SaaS company where purchasing decisions involve multiple stakeholders across engineering, marketing, and finance, scoring one contact misses most of the signal. What you actually want to know is whether the account is in motion—and getting there requires scoring at the account level, not the contact level.

Phase 3 replaced the individual lead model with HubSpot account-based scoring using aggregated intent data from Factors.ai. Accounts receive a hot or warm designation based on the combined signal across the buying team, with hot accounts routed immediately through the Phase 2 workflow and warm accounts held in active monitoring. The binary MQL/SQL handoff gives way to a continuous, intent-based account scoring model that reflects how B2B buying actually works.

The executive dashboard built alongside the scoring model ties the whole system together, tracking three things: MQA-to-pipeline conversion, SLA compliance (whether reps are following up on MQAs within the 48-hour window), and attribution. Leadership can pull a 7-day or 14-day view showing how many accounts moved into hot or warm status, how many became active pipeline, and whether the follow-up SLA is holding. Target account tracking within HubSpot rounds out the build, giving the team a live view of where named accounts sit in the buying journey and what intent activity has occurred.

Free HubSpot Portal Audit

Unlock the Full Potential of Your HubSpot Portal

Request A Portal Audit arrow_forward

The Transformation

Before the engagement, reps were emailing everyone on a LinkedIn list the same way—no signal identifying who was in market, no routing logic getting hot accounts to the right rep, and no way for leadership to see what was happening in outbound without asking individually. Now, intent signals from G2, Clay, and LinkedIn Sales Navigator aggregate into an ICP-scored MQA model, accounts route automatically to the right rep with a pre-built brief and a 48-hour SLA enforced, and an executive dashboard tracks MQA conversion, SLA compliance, and attribution in real time.

There are no pipeline metrics to share here—this is a live engagement, and those numbers belong to the client to tell when they’re ready. What the build demonstrates is that the same HubSpot instance that started Phase 1 as a basic sequencing operation can run a full account-based marketing engine without a platform replacement or a stack rebuild.


Can HubSpot Run a Real ABM Operation? What This Build Shows

HubSpot can run a real ABM operation—the question is how you build it, not whether the platform is capable.

With the right integration architecture, HubSpot becomes the backbone of an account-based lead scoring system that competes with what most RevOps teams assume requires Marketo or 6sense. Factors.ai aggregates intent from G2, Clay, and LinkedIn Sales Navigator. ICP scoring gets reworked around live signals rather than static firmographics. Workflow routing enforces a follow-up SLA from the moment an account is tagged. None of that requires a new platform; it requires a deliberate build on the one you already have.

The three-phase progression here is also a practical roadmap. You don’t build this all at once, and you don’t need to. Start with the foundation—HubSpot, a sequencing tool, LinkedIn Sales Navigator—and get your reps active. When that’s solid, layer in intent data and rebuild your ICP scoring model around live signals. Then, when the team is ready, shift from contact-level MQL scoring to account-level MQA scoring and build the dashboards that give leadership real visibility. That’s HubSpot lead scoring best practices applied in sequence, with each phase building on the one before it.

The mistake most teams make is trying to jump to Phase 3 without the intent infrastructure in place. Account-based scoring without intent data is just relabeled lead scoring. The signal has to come first.

Ready To Move Past Phase 1?

If your outbound motion needs intent data, automated routing, and account scoring built on HubSpot, we can walk through what that architecture looks like for your team. Get in touch