Play: SaaS replacing their CRM in the next 60 days

The signal

A B2B SaaS quietly removes their CRM from job descriptions, integrations pages, or status pages. New RevOps roles mention "CRM evaluation" or "system migration." Tech stack scrapers stop seeing the old CRM in their JS bundle.

Satellyte stitches all three together: job posts, public stack changes, and changelog mentions. When the pattern fires, the account has roughly 60 days before they pick the next system.

What it means

They are between vendors right now. The next pick is being decided in slack threads, founder dinners, and one or two reference calls. By the time it hits G2, the contract is signed.

This is the cheapest deal-cycle window of the year for any CRM, RevOps, or migration vendor.

The play

1. Open with the failure mode, not the pitch

Reference what their old CRM stopped doing as they grew, not what your CRM does. Founders trust diagnoses, not demos.

2. Send a buyer's frame, not a deck

A one-pager that walks through which CRM fits which stage of B2B SaaS. Even if they pick a competitor, you become the trusted second opinion.

3. Offer a migration scoping call

Not a sales call. A working session to scope data, integrations, and rollout. The team running the migration will lean on whoever shows up first.

Sample first message

When to skip this play

If they just raised and the new VP Sales has not landed yet, wait two weeks. The decision will not be made by anyone you can reach today.

Where to go next

Pair this with the Leadership Change signal to catch new RevOps and VP Sales hires inside the same accounts.