HubSpot ABM Lifecycle Stage Rules — Best Practices

The Core Pattern

When building ABM email automation in HubSpot, gate email suppression on the contact's lifecycle stage, not on whether the associated company has an open deal. Specifically: stop marketing emails only when a contact reaches Sales Qualified Lead (SQL) status — not when an Opportunity or Deal is created.

The Problem This Solves

A common automation pattern is to suppress ABM emails for any contact whose company has an active deal. This breaks down when the client uses deals liberally — creating Opportunities for nearly every contact as a tracking mechanism rather than as a signal of serious sales engagement.

The result: emails get canceled en masse for contacts who are still early in the funnel and should be receiving marketing.

"He's making deals for everybody who's got a pulse. So it's not that it's wrong, it's just a different way of doing it. But you have to have different rules if that's what you're going to do."
— Mark Hope, 2026-03-24 weekly call

In the ^[1] ABM campaign, this misconfiguration caused the majority of queued emails to be canceled, with only 264 emails sent and an 11% open rate — far below expected volume.

The Fix

Change the suppression rule to evaluate the contact record's lifecycle stage directly, rather than checking for deal existence at the company level.

Recommended Rule Logic

Why SQL Is the Right Gate

The SQL stage signals that a contact has entered a serious sales conversation — a proposal is being prepared, pricing is being discussed, or a formal evaluation is underway. This is the appropriate moment to hand off fully to sales and pause marketing outreach.

Creating a Deal or Opportunity, by contrast, often happens much earlier and means different things to different sales teams. It is not a reliable suppression trigger.

Implementation Notes

• HubSpot lifecycle stages (in typical order): Subscriber → Lead → Marketing Qualified Lead → Sales Qualified Lead → Opportunity → Customer
• The SQL stage must be actively set by the sales rep — it does not advance automatically when a Deal is created
• Before changing the rule, confirm with the client that they understand marketing will continue until they manually mark a contact as SQL
• After updating the rule, canceled emails can be backfilled: queue up previously suppressed sends and re-dispatch them

Client Confirmation Required

This rule change requires explicit client sign-off. The client must agree to:

1. Marketing emails continuing even when a Deal/Opportunity exists for the contact's company
2. Taking responsibility for marking contacts as SQL when a serious sales conversation begins

Without this agreement, the automation change could result in marketing contacts who the sales team considers "in play."

Related Patterns

• ^[2] — companion cleanup process run alongside this fix for Aviary
• ^[3] — how to segment contacts between personalized ABM sequences and cold drip campaigns

Seen In

• ^[1] — ABM campaign, March 2026. Bulk email cancellations traced to company-level deal suppression rule. Fix pending client approval from Justin (Aviary contact).