ABM Email Automation Fix — Lifecycle Stage Rule

Overview

Aviary's ABM email sequences were being silently canceled at scale due to a misconfigured suppression rule. The rule was gating on company-level deal existence rather than contact-level lifecycle stage — causing nearly all outbound marketing to halt prematurely. The fix is to change the suppression trigger to the Sales Qualified Lead (SQL) lifecycle stage on the contact record.

As of the 2026-03-24 weekly call, the fix is pending client confirmation before implementation.

Problem

The ABM automation contained a rule that stopped email sequences whenever the contact's associated company had an active deal (Opportunity) in HubSpot.

Why this caused mass cancellations: Aviary's client (Justin) creates Opportunities very liberally — essentially for any contact with a pulse — as a pipeline tracking habit. This is a valid CRM workflow, but it's incompatible with a suppression rule that treats any deal as a signal to halt marketing.

Result: The vast majority of queued ABM emails were being canceled. During the call, Mark shared his screen showing nearly every email in the queue marked as canceled, with only ~34 scheduled to send the following day. Total sent to date was only 264 emails at an 11% open rate — far below expected volume.

"Every bloody email is being canceled... the numbers are just not going up because, like right now, today, we didn't send any."
— Mark Hope

Root Cause

The suppression rule evaluated two conditions:

Contact lifecycle stage (correct signal)
Whether the company associated with the contact has an active deal (incorrect signal for this client)

Because condition 2 was triggering for nearly all contacts, condition 1 was effectively irrelevant. A contact could be sitting at lifecycle stage "Lead" and still have their emails canceled because their employer had a deal record attached.

Solution

Change the suppression rule to gate only on the contact's lifecycle stage, specifically:

Stop sending emails when a contact's lifecycle stage is set to "Sales Qualified Lead" (SQL).

All other lifecycle stages — subscriber, lead, marketing qualified lead — should continue to receive marketing emails. Customers should also be excluded from marketing, but the critical new gate is SQL.

Rationale: SQL is the appropriate signal that a serious sales conversation is underway (e.g., a proposal is being sent, pricing is being discussed). At that point, pausing marketing makes sense. Simply having an Opportunity record does not carry the same meaning for this client.

The SQL lifecycle stage already exists in Aviary's HubSpot instance (confirmed during the call: subscriber → lead → marketing qualified lead → sales qualified lead → opportunity).

Implementation Notes

Pending: Sebastian needs to confirm with Justin (Aviary) that marketing should continue for all contacts until they are explicitly marked SQL.
On approval: Mark will update the suppression rule in the automation system.
Backfill: Once the rule is corrected, Mark can re-queue all previously canceled emails and send them. This will significantly increase campaign volume.

Action Items

[ ] Sebastian — Email Justin to confirm: marketing continues until contact is marked SQL; opportunity creation alone does not suppress emails.
[ ] Mark — Once confirmed, update the ABM suppression rule to trigger on SQL lifecycle stage (remove company deal condition).
[ ] Mark — Backfill and re-queue all canceled email sends after rule is updated.

^[1] — Aviary client overview
^[2] — Concurrent cleanup work affecting contact data quality
^[3] — Generic nurture sequence for contacts outside ABM