Skip to content

Cross-sell recommendation task from complementary product match

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.

Company11 stepsUpdated for HubSpot seat pricing
OutcomeAn account owner gets a specific, named cross-sell recommendation the moment an account's product mix matches a known complementary pairing, instead of a generic "consider upsell" nudge with no product attached.
Workflow maprenewal-expansion-029
Active Products known, no cross-sell task yet leads to Has A, not B?; Has C, not D?. Has A, not B? leads to Yes: Recommend Product B, create task; No: Any match found?. Has C, not D? leads to Yes: Recommend Product D, create task; No: Any match found?. Any match found? leads to No: Set recommendation = None. Yes Yes No No No Active Products known, no cross-sell task yet Has A, not B? Has C, not D? Recommend Product B, create task Recommend Product D, create task Any match found? Set recommendation = None
Active Products known, no cross-sell task yet leads to Has A, not B?; Has C, not D?. Has A, not B? leads to Yes: Recommend Product B, create task; No: Any match found?. Has C, not D? leads to Yes: Recommend Product D, create task; No: Any match found?. Any match found? leads to No: Set recommendation = None. Yes Yes No No No Active Products known, no cross-sell task yet Has A, not B? Has C, not D? Recommend Product B, create task Recommend Product D, create task Any match found? Set recommendation = None

When to use it, when not to

Use it

  • Use it when the product catalog has known, fixed pairings (owning Product A makes Product B a natural next purchase, for example) and those pairings are stable enough to encode as a small set of branches.
  • Use it as a more specific companion to renewal-expansion-010, which only detects single-product accounts in general; this fiche matches an actual product combination to a specific recommended add-on.
Read more on when to use itShow less

Skip it

  • Do not use it for a large or frequently changing product catalog. A catalog with many products and shifting pairing logic needs a lookup table outside standard workflow branching, which is a custom object or custom code concern at a higher tier.
  • Do not use it on accounts that already own the complementary product; the branches below check for that explicitly.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 11 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 5

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 10 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Renewal and expansion spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library