Skip to content

Surface a competitive battlecard task when a competitor name is logged in a deal note

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

Enterprise

Seat pricing: Enterprise 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 Enterprise.

Deal5 stepsUpdated for HubSpot seat pricing
OutcomeThe moment a rep logs a note mentioning a known competitor, they get a task with a direct link to that competitor's battlecard, instead of digging through a shared drive mid-deal.
Workflow mapsales-ops-033
Note logged on deal leads to Custom code: scan note text against Competitors list. Custom code: scan note text against Competitors list leads to Competitor match found?. Competitor match found? leads to Yes: Set Competitor mentioned; No: End, no action. Set Competitor mentioned leads to Create battlecard review task for deal owner. Yes No Note logged on deal Custom code: scan note text against Competitors list Competitor match found? Set Competitor mentioned End, no action Create battlecard review task for deal owner
Note logged on deal leads to Custom code: scan note text against Competitors list. Custom code: scan note text against Competitors list leads to Competitor match found?. Competitor match found? leads to Yes: Set Competitor mentioned; No: End, no action. Set Competitor mentioned leads to Create battlecard review task for deal owner. Yes No Note logged on deal Custom code: scan note text against Competitors list Competitor match found? Set Competitor mentioned End, no action Create battlecard review task for deal owner

When to use it, when not to

Use it

  • Use it when your team maintains a maintained list of competitors with a battlecard link for each, and reps log discovery and call notes on the deal record.
  • Use it when the current process is "ask in Slack if anyone has faced this competitor," which is slow and inconsistent.
Read more on when to use itShow less

Skip it

  • Do not use it if competitor mentions mostly happen in call transcripts or emails rather than typed notes; this fiche only scans note text, not other engagement types (see Variants).
  • Do not use it without an Enterprise-tier subscription; this fiche depends on a custom object to hold the competitor list and battlecard links, and custom objects require Sales Hub, Service Hub, or Data Hub Enterprise (https://knowledge.hubspot.com/object-settings/create-custom-objects).
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 5 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 · 5 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 · 2 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, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

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 Sales ops 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