Skip to main content

Signal key

acquired_signal

Category

Composite

Source

Composite of Parent Company Added with name or description change.
A company was acquired.

​
When it fires

Trigger condition

parent_company_added AND (name_change OR description_change_major) within a 60-day window.

​
Magnitude

Hyper, a confirmed acquisition.
For the full bucket definitions used across percentage-based signals, see Magnitude buckets.

​
Why it matters

That combination is a near-certain acquisition. A new parent appearing alongside a name or description change is the structural fingerprint of an acquisition, far more reliable than any single signal, and it reshapes who controls budget and vendor decisions.

​
How to use Acquired Signal?

Where you sit. You are an enterprise CSM at a data-integration platform. Wrenfield Data, a healthy seven-year account, mid-six figures annually, sits in your book. Renewal is in ten months. You have a good champion, solid usage, and, as of this morning, a problem you did not know about. The mission. Treat acquisitions of your customers as first-class renewal events, because an acquired customer is not the same customer anymore, whatever the logo says. The signal fires. acquired_signal fires for Wrenfield: the composite has detected the acquisition pattern, a new parent, Halcyon Group, plus the identity changes that follow. Your champion mentions it two days later, with the airy optimism of someone who has not yet met the integration team. Reading it. Every acquired account’s contracts enter a sorting process: keep, consolidate, or kill. Halcyon has its own preferred vendors, maybe a competing integration platform among them, and somewhere an integration office will eventually compare overlapping tools on a spreadsheet you will never see. Sitting still means letting that spreadsheet decide your renewal. The accounts that survive integrations are the ones that made themselves annoying to remove before the comparison started. The play.
  1. Reforecast honestly: flag the renewal as at-risk-by-structure regardless of current health, and tell your leadership why now.
  2. Deepen technical entrenchment immediately, more integrations live, more teams onboarded, more workflows dependent; usage is your only vote in the parent’s process.
  3. Ask your champion for the map: who at Halcyon owns vendor consolidation, and can you present the platform’s footprint to them proactively.
  4. Explore the upside path too, Halcyon has other subsidiaries with the same data problems, and a parent-level agreement turns your biggest risk into your biggest expansion.
Automate it. Run your whole book through the Company Signals API on acquired_signal weekly; every fire should open a renewal-risk play automatically, not after the QBR. Why it lands. Integration spreadsheets kill quietly and on schedule. This signal gives you two or three quarters to become unkillable.

​
How to read it

Confirmed M&A

The signal combination strongly confirms an acquisition.

Budget control shifts

The parent may centralize or release purchasing.

Stack consolidation

Acquirers often consolidate vendors post-deal.

​
Outreach playbook

Top-tier. Determine whether the parent controls budget; expect stack consolidation.

Parent Company Added

A parent company was set where there was none.

Name Change

The company name string changed.

Description Change Major

The company description was substantially rewritten.

Merger Signal

Two companies merged under a common new parent.

Subsidiary Status Change

The company became or stopped being a subsidiary.

Track this signal with CUFinder

Surface acquired_signal across millions of companies, enriched with verified emails, phones, and full firmographics. Start free, no credit card required.