Play: Catching pipeline-tool installs after HubSpot churn

The signal

A team installs a lighter pipeline-first tool while HubSpot mentions stay live in their public footprint. The new install shows up in changelogs, eng blogs, or careers page mentions. HubSpot stays in their robots.txt and integrations list, but it is on borrowed time.

Satellyte flags the dual-state: incumbent still present, challenger just installed.

What it means

They are quietly running a pilot. The all-in-one suite is on the chopping block before quarter-end. The decision is mostly made, but no contract has moved. Politically, this is the cheapest window for any vendor adjacent to the new pick.

The play

1. Skip the head-to-head pitch

Do not lead with feature comparisons. They have already done that math. Lead with the migration math: data, dashboards, automations, integrations.

2. Frame the pilot honestly

Walk through where the lighter pipeline tool wins (speed, founder workflows, low TCO) and where the suite still earns its seat (marketing automation, lifecycle, reporting). Honest framing builds trust faster than feature dumps.

3. Offer a 30-day pilot scope

A tight scope: pipeline migration, three reports, one integration. Founders sign these in days, not weeks.

Sample first message

When to skip this play

If the founder is running sales solo and there is no AE yet, the pipeline tool will win on its own. No play needed.

Where to go next

Pair with the Leadership Change signal: a new VP Sales lands at this kind of account roughly 60% of the time within a quarter of the install.