Skip to main content

Signal key

merger_signal

Category

Composite

Source

Composite across two companies’ parent relationships.
Two companies merged under a common new parent.

​
When it fires

Trigger condition

Two distinct companies acquire the same new parent_id within 60 days of each other. Emits once on the second company.

​
Stored fields

This signal persists the following metadata you can read downstream:

​
Magnitude

Hyper, mergers are major consolidation events.
For the full bucket definitions used across percentage-based signals, see Magnitude buckets.

​
Why it matters

Mergers create massive consolidation and re-evaluation of vendors. When two companies come under one new parent, overlapping tools get cut and surviving vendors get scrutinized, a high-stakes moment for both incumbents and challengers.

​
How to use Merger Signal?

The scenario. You run an HR-systems consultancy specializing in consolidation: taking two companies’ payroll, HRIS, and benefits stacks and making them one. Your projects are born in exactly one kind of event, and the event announces itself: two companies becoming one company, with two of everything. The goal. Reach merged organizations in the window between deal close and systems decision, when both legacy stacks still run in parallel and the pain of duplication grows weekly. The signal fires. merger_signal fires: Beaumont Logistics and Carver Freight, two regional carriers of similar size, have merged under a new common parent. Composite confirmation, structure changes plus the identity pattern, not just rumor. Reading it. A merger of equals is the hardest systems scenario and the best consulting scenario: neither side’s stack is the obvious winner, both HR teams are defending their own, and every payroll cycle runs twice. This standoff has a natural clock, duplicated systems cost real money monthly, and the first combined benefits enrollment is a hard deadline, but no natural referee. Your entire value is being the referee with a method. The play.
  1. Time the approach four to eight weeks post-close, after the executive dust settles, before either HR team wins by attrition.
  2. Approach the combined entity’s CHRO, or the deal’s integration lead, with neutrality as the pitch: an objective assessment of both stacks against the merged company’s needs, with a migration plan either way.
  3. Lead with the enrollment deadline; naming the immovable date that makes deferral impossible is half the close.
  4. Fix the payroll consolidation first, the workstream with a monthly cost makes your fee self-justifying, then expand into the full roadmap.
Automate it. A monthly Company Signals API check on merger_signal in your regions produces a handful of qualified events a year, and each one is a six-month engagement. Why it lands. Merged companies do not need convincing that the duplication hurts. They need a referee neither side can accuse of picking favorites, which is precisely what an outsider is for.

​
How to read it

Consolidation

Mergers eliminate redundant tools and vendors.

Vendor scrutiny

Surviving systems face re-evaluation.

Both sides

meta.merged_with references both companies.

​
Outreach playbook

High-stakes. Position as the consolidation winner; map both entities’ stacks.

Acquired Signal

A company was acquired.

Parent Company Added

A parent company was set where there was none.

Name Change Drastic

A name change with almost no overlap to the old name.

Track this signal with CUFinder

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