How We Build Cross-Sell Workflows

The right next product, at the right time

A cross-sell workflow introduces a specific product to a specific member segment based on what they already have. The build is shaped by your priorities — what you want to grow and who's most likely to say yes.

Why it matters: Cross-sell is where member relationships deepen and lifetime value grows. A well-targeted workflow beats a blanket promotion, and with datestamps on both ends, you can show exactly which products it moved.

How the workflow is built

Every cross-sell workflow is custom to your goals, so we start by answering three questions with you:

Who's the segment? (What do they have, or not have?)
What's the offer? (Which product or service are we introducing?)
What counts as success? (Opening the product, applying, or adding a feature?)

Example: indirect auto members. Members who joined through a dealer-originated auto loan often don't realize they're credit union members. A cross-sell workflow introduces them to the credit union and offers checking, direct deposit, and other products.

Enrollment trigger — Based on your segment. For the indirect auto example: an associated auto loan with a channel of "indirect," and no checking account.

Suppression — The standard non-marketing groups (hard bounces, unsubscribes, core "do not market"), plus:

Members who already hold the product being offered
Members currently in onboarding or another active cross-sell (to avoid overlap)

Re-enrollment — Depends on the offer. Usually off, or time-limited.

Goal — The member opens or adds the offered product (e.g., an associated checking deal or a "Date Checking Opened" value). This stops the emails once they've converted.

Workflow steps:

Optional delay — For example, wait 30 days after an indirect loan funds so the first touch isn't too early.
Set enrollment datestamp — Set "Date Enrolled in [Cross-Sell Workflow Name]" to the current date.
Email series — Typically 3–5 emails building awareness, then making the offer.

Data requirements

Required:

Product holdings — Deals for each product, associated to the member, with product type and status. This is how we define the segment and suppress existing holders.
Segment-defining fields — Whatever the targeting depends on. For indirect auto: loan channel (direct vs. indirect) or dealer indicator.
Membership status and marketing eligibility flag from your core.

Required for reporting:

Enrollment datestamp — "Date Enrolled in [Cross-Sell Workflow Name]" (date picker, member object).
Outcome datestamp — The date the member added the offered product or feature, from one of two sources:
- Your core integration — An open date on the product record (preferred).
- A HubSpot tracking workflow — Watches for the product or flag to appear and sets a "Date [Product] Added" property.

Helpful:

Loan funding date — For timing the first touch.
Branch or region — For segmented reporting and localized messaging.

Pre-launch checklist

Segment, offer, and success measure agreed with your team
Segment-defining data confirmed in HubSpot (e.g., indirect channel flag)
Product holdings syncing and associated to members
Trigger built and tested against sample members
Suppression in place: bounces, unsubscribes, core "do not market," existing product holders, overlapping workflows
Re-enrollment rule decided
Goal set to the offered product
Enrollment datestamp action placed before the first email
Outcome datestamp available — from the core, or a HubSpot tracking workflow built and turned on before launch
Emails reviewed, approved, and links tested
Attribution window agreed

How we report on it

What we compare: "Date Enrolled in [Cross-Sell Workflow Name]" vs. the outcome datestamp.

How it's built: A formula field checks whether the outcome date falls after the enrollment date and within the attribution window. Members who pass count as attributed cross-sells.

Typical dashboard tiles:

Members enrolled (by month)
Cross-sell conversion rate (attributed conversions ÷ enrolled)
Products opened after enrollment, by product type
Email engagement by step

Important Notes & Limitations

Every cross-sell is custom — Segments and offers vary by credit union, so data requirements do too. We confirm the data exists before we build.
Clean product data is a must — If product type or channel data is missing or inconsistent, targeting and suppression won't be reliable.
No backfill — Enrollment and HubSpot-set outcome datestamps only capture activity from the day they go live.
Watch for overlap — Members can qualify for several cross-sells at once. We set priority rules so no one gets competing offers.