A merger acquisition sales trigger is a public deal event at a target account, used as a reason to research it before outreach. It proves that two companies have agreed to combine, or have combined; not that anyone is buying anything. Read it in three gates (announced, closed, integrating), decide which side you are selling to, then verify each consequence, from systems to procurement, before you write a word.

Disclosure, date and method

Bob Generale is President of Percepture, which is related to Lead Seeker, the publisher of this page; Percepture's intent-data service, Prime AI Visibility and Pyra are each linked once below and labelled as related. This guide was researched on October 2, 2026 from the primary sources listed at the end: the SEC's Investor Bulletin on reading a Form 8-K, the Federal Trade Commission's pages on the premerger notification program, its 2026 jurisdictional thresholds and its staff guidance on pre-merger information sharing, the Department of Labor's WARN regulations at 20 CFR Part 639 and California's WARN reporting page, the Federal Acquisition Regulation on novation and change-of-name agreements, Sections 251 and 259 of the Delaware General Corporation Law, the USPTO's page on trademark ownership changes, the European Commission's 2018 Altice decision, and the SEC's EDGAR full-text search, which we queried ourselves for the filing counts in the data section.

We also read the pages we could retrieve from the results for this query and its close variants. They fall into three groups: general trigger-event lists in which a merger is one bullet among fifteen to thirty-five; a prompt template and an exit-planning page that use "trigger event" in a different sense; and one vendor page built around a "first 100 days" window and a six-month lock-in. None of them separates a signed deal from a closed one, names the legal reason the two companies cannot combine purchasing before close, or says which public record shows that a consequence has actually started. Several repeat conversion multiples without a dataset behind them; those figures are not repeated here. No outbound outcome on this page is a measurement.

Merger Acquisition Sales Trigger: The Short Answer

  • A deal is three events, not one. The announcement says two boards agreed. The close says ownership changed. Integration is when systems, vendors, facilities, brands and purchasing actually move. Each gate produces a different public record and supports a different research question. This guide calls them the Three Gates.
  • Before the close, the two companies are legally separate buyers. Under the Hart-Scott-Rodino Act, reportable deals wait 30 days (15 for a cash tender offer or a bankruptcy) after filing, or longer if the agencies issue a Second Request, and the FTC's staff guidance states that right up until consummation the parties "are still independent businesses and they must continue to operate independently." A consolidation pitch sent at announcement is addressed to a decision that cannot be made yet.
  • Which side you sell to changes the whole read. The acquirer, the acquired company, a merged entity and a carved-out unit face different consequences and hold different budgets. Pick the side before the persona.
  • Every consequence below is a hypothesis. Integration, consolidation, systems, vendors, facilities, branding and procurement each come with a possible implication, an alternative explanation, a verify-next step, the roles who hold the decision and a decay default. The defaults are a model to adjust against your own closed deals, not measurements.
  • Contracts do not end at close. When a Delaware merger becomes effective, the surviving corporation takes on the property, rights and debts of the constituent corporations. An acquired company's vendor agreements travel with it. "They will need to replace everything" is the alternative explanation to test, not the premise.

Which gate has the deal passed? Announcement, close and integration are three different signals

A merger acquisition sales trigger arrives as a headline, and the headline hides which of three events it describes. The Three Gates is the device this guide uses to separate them. Each gate is marked by a specific public record, proves a specific thing and leaves specific questions open.

Gate one: signing

At signing, two boards have approved a definitive agreement. For an SEC registrant, the agreement is a candidate for an 8-K under Item 1.01, which the SEC's Investor Bulletin describes as covering "certain material agreements not made in the ordinary course of business"; the accompanying press release is filed under Item 7.01 or Item 8.01. In the SEC's wording, companies are required to make most 8-K disclosures within four business days of the triggering event. The release text carries the stage markers: "entered into a definitive agreement", "subject to customary closing conditions, including regulatory approvals", "expected to close in" a named quarter.

What signing proves: intent to combine, the side that is buying, the headline price where disclosed, and the rationale where the release states one. What it cannot prove: that the deal will close, when, or what the combined company will run. Deals are terminated; the SEC lists that event too, under Item 1.02.

Signing also starts the regulatory clock. For deals above the HSR size-of-transaction threshold, $133.9 million from February 17, 2026 under the FTC's adjusted figures, both parties file with the FTC and the Department of Justice and "must wait 30 days (15 days in the case of a cash tender offer or a bankruptcy) or until the agencies grant early termination of the waiting period before they can consummate the deal." A Second Request extends that. Deals in the European Union carry a parallel standstill obligation; in 2018 the European Commission fined Altice €124.5 million for implementing its acquisition of PT Portugal before notification or approval, and Commissioner Margrethe Vestager said that companies "that jump the gun and implement mergers before notification or clearance undermine the effectiveness of our merger control system."

That is the sales-relevant point of gate one. The FTC's guidance on pre-merger information sharing warns that conduct that lets the buyer gain "beneficial ownership of the seller prior to the close of the transaction" can be unlawful gun jumping, and cites a 2002 case in which the merger agreement required buyer pre-approval before the seller could offer customers discounts above 20 per cent off list. Companies operating under that guidance do not combine purchasing, migrate the target's systems or cancel the target's vendors before close. A message that assumes they are already doing so is wrong on the law as well as the timing.

Gate two: closing

Closing is the ownership change. For a registrant, the marker is an 8-K under Item 2.01, Completion of Acquisition or Disposition of Assets; the Investor Bulletin notes that Item 9.01 then requires the financial statements of the acquired business and pro forma results "that show what the company's financial results might have been if the transaction had been completed earlier." For a Delaware corporation, the merger takes effect through a filing with the Secretary of State, the agreement of merger or a certificate of merger in its place under Section 251, effective in accordance with Section 103, so a private deal leaves a record even when no press release follows.

Closing also changes who is responsible for what. Under 20 CFR 639.4(c), in a sale of part or all of a business "the seller is responsible for providing notice of any plant closing or mass layoff which takes place up to and including the effective date (time) of the sale, and the buyer is responsible for providing notice of any plant closing or mass layoff that takes place thereafter." Under FAR Subpart 42.12, a government contract does not simply follow the business: 41 U.S.C. 6305 prohibits transfer of government contracts to a third party, and the government "may, when in its interest, recognize a third party as the successor in interest" through a novation agreement when the transfer covers all the contractor's assets or the entire portion involved in performing the contract. Those two rules give you dated, public consequences to look for after close rather than guesses to make at announcement.

What closing proves: ownership has changed and the gun-jumping constraint has lifted. What it cannot prove: that any system, vendor, site or brand will change. Section 259 of the Delaware code is explicit that the surviving corporation holds "all property, real, personal and mixed, and all debts due to any of said constituent corporations"; the acquired company's existing contracts are now the acquirer's contracts.

Gate three: integration

Integration is the long tail in which consequences become visible, one record at a time: a transition services agreement filed as an exhibit, "integration costs" and "synergies" in the next quarterly report, a WARN notice on a state list, a name change at the Secretary of State, a trademark assignment recorded with the USPTO, a new domain on the email headers, a posted role titled "integration" or "ERP consolidation". There is no single gate-three filing. There is a sequence of smaller ones, and each is a verify-next step for one of the seven consequences below.

The Three Gates at a glance

Gate Public record that marks it What it can prove What it cannot prove Who to research first
Signing (announcement) Press release; 8-K Item 1.01, 7.01 or 8.01 with the agreement as an exhibit; HSR filing (not public, but the waiting period is) Two boards agreed; which side is buying; stated price and rationale That the deal closes; when; what the combined company will run Corporate development, strategy, the executive quoted in the release
Closing 8-K Item 2.01; certificate of merger at the Secretary of State; Item 9.01 financial statements of the business acquired Ownership changed; the legal constraint on joint operation lifted Any change to systems, vendors, sites or brands Integration lead or PMO, finance, legal, HR
Integration TSA exhibits; "integration costs" and "synergies" in 10-Q and 10-K; WARN notices; name changes; trademark assignments; domain and MX changes; integration-titled roles A specific consequence has started, with a date That the consequence touches your category, unless the record says so The operating owner of the function the record names

Two cautions apply to the table. First, the 8-K items exist for SEC registrants; a private acquirer leaves a release, a Secretary of State filing and whatever its counterparties disclose. Second, the records are dated by their filing, not by the decision; an Item 2.01 filed on a Thursday reports a close that happened within the previous four business days, and a 10-Q sentence about integration costs describes a quarter that has already ended.

Which side are you selling to: the acquirer, the target or the combined company?

Google's own AI answer for this query asks the reader whether they are targeting the acquiring company or the acquired company, and it is the right first question. The Side Selector below is this guide's second device. Four sides, four different consequence patterns.

Side What the deal changes for it What it keeps by default Decision owners after close
Acquirer Adds users, sites, contracts and data to systems it already runs; its procurement function inherits the target's vendor list Its own platforms and vendors, in the absence of a stated decision otherwise Acquirer's functional leaders; integration lead; procurement
Acquired company (target) Pre-close, nothing by law beyond planning; post-close, its vendors are reviewed against the acquirer's, its leaders may change role, its brand may be retired Contracts in force, which pass to the acquirer The acquirer's owner for each function, with the target's manager as the operating contact
Merged entity (merger of equals, new name) Two of everything with no incumbent; a new brand, domain and legal entity Little by default; the TSA and integration plan decide Newly appointed combined leadership; the integration office
Carved-out or divested unit Loses the parent's systems, contracts and shared services on a stated schedule; must stand up its own The staff and customers it took with it The unit's new management and, if a sponsor bought it, the sponsor's operating team

Three consequences of the table are worth stating plainly.

The acquirer is the side with an incumbent for every category. When your category is one of them, the research question is whether the acquirer's incumbent scales to the combined footprint, and the alternative explanation is that it does. When your category is one the target ran and the acquirer did not, the question is whether the acquirer adopts it, retires it or leaves it alone; two of those three outcomes end the target's contract.

The target, before close, is frozen in a specific way. Its managers can plan, and the integration workstreams are being staffed, but the FTC guidance quoted above means the companies safeguard competitively sensitive information and operate independently until consummation. A target-side champion who tells you "nothing is decided" is describing the law, not stalling.

The carve-out is the one side for which "they need to buy everything" can be literally true. A divested unit operating under a transition services agreement has a stated date on which the parent stops providing finance, HR, IT or procurement services. The TSA term, when it is filed as an exhibit, is the only decay clock on this page that is written down by the buyer itself.

What does the deal change? Seven consequences, each as a hypothesis

The brief for a merger acquisition sales trigger is to map what the deal does to integration, consolidation, systems, vendors, facilities, branding and procurement. Each row below states the consequence as a hypothesis to test, the alternative explanation that fits the same evidence, the record that settles it, the roles who hold the decision and a decay default. The table's heading is deliberate: these are hypotheses, not meanings.

Consequence Hypothesis to test Alternative explanation Verify-next Roles who hold it Recency and decay
Integration (programme) An integration office exists, has a budget and a plan with workstreams for your category The acquirer runs small deals through the acquiring business unit with no programme; a "tuck-in" has no PMO Integration-titled roles posted; an "integration" or "PMO" leader named in the release or on LinkedIn; "integration costs" quantified in the next 10-Q Chief integration officer or VP integration where one exists; otherwise the sponsoring executive and the CFO Opens at signing as planning; actionable after close; the programme winds down on its own stated horizon, visible when integration cost guidance stops
Consolidation (two of everything) Duplicate functions, teams and tools will be reduced, and the survivors chosen Stated "synergies" are revenue-side (cross-selling), not cost-side; or the target is kept as a standalone subsidiary The release's synergy language (cost vs revenue); 8-K Item 2.05 restructuring charges; headcount language in the 10-Q; WARN notices CFO, COO, the functional leader whose two teams overlap Starts after close; decisions on tools follow decisions on people, so the tool window opens after the org chart settles, not before
Systems (ERP, CRM, identity, data) The target will be migrated onto the acquirer's platforms, or both onto a new one The target keeps its stack as a subsidiary; the acquirer is itself mid-migration and freezes change; the TSA keeps the parent's systems running for a stated term Posted roles naming the platform and the word "migration" or "consolidation"; "enterprise resource planning" in filings; the target's domain and MX records changing; the method in how to read a technology change sales signal CIO, CFO for ERP, CRO or RevOps for CRM, CISO for identity Default: the platform decision is taken in the first integration planning cycle after close; once a migration is announced that decision is closed and the open question moves to what connects to the new platform
Vendors (contracts and renewals) Overlapping vendors will be reviewed and one dropped per category Contracts have terms; the acquired contracts passed to the acquirer at close and run to their renewal date; the acquirer rationalises on renewal, not on close Renewal timing where public (government contracts, filed material agreements); procurement roles posted; supplier-portal notices to vendors Procurement or sourcing lead; the budget owner for the category Keyed to each contract's renewal date rather than the deal date; a vendor review can sit twelve to twenty-four months after close for a long-term agreement
Facilities (sites, leases, plants) Sites will close, relocate or combine Both companies keep their footprints; the deal was about customers or product, not sites; a lease has years to run WARN notices (the DOL regulation assigns notice to the buyer for post-sale actions); 8-K Item 2.05 charges for exit activities; local permit and lease filings; "consolidation of facilities" language in filings COO, head of real estate or workplace, plant or site leadership, HR A WARN notice gives at least 60 days before a covered closing or mass layoff; default: facility decisions follow the systems and people decisions, and a lease term sets the horizon
Branding (name, domain, marks) The target's brand, domain and email identity will be retired The acquirer keeps the target as an endorsed or house brand; the new brand is the target's; the rename is legal-entity only Name change at the Secretary of State; trademark assignment or change-of-name recorded with the USPTO; new domain in email headers and on the careers site; "rebranding" in filings CMO, general counsel for the marks, IT for domains and identity A legal rename is a point in time; a customer-facing rebrand is a project with its own dated milestones; the window for brand, web and identity vendors opens when the new name is chosen, which may be months after close
Procurement (how the combined company buys) Vendor master data, purchasing systems and policies will be unified; small-company vendors face enterprise onboarding The target keeps its own purchasing as a subsidiary; the acquirer has no central procurement; government contracts need novation and may stay with the selling entity Supplier registration portals and vendor onboarding requirements; FAR Subpart 42.12 novation or change-of-name agreements for federal contracts; procurement roles posted; the acquirer's published supplier code CPO or head of procurement; accounts payable; contracts for government work Default: late; it decides how you are paid and onboarded, not whether you are chosen, so it changes your process rather than your timing

Three reading rules keep the table honest.

The alternative explanation is the default, not the exception. For every row, the no-change outcome is one the public record supports in a large share of deals: a kept subsidiary, a running contract, an endorsed brand, an unfinished migration. You are looking for the record that rules the default out.

The verify-next step produces a date. A posted role, a filed exhibit, a WARN notice, a trademark assignment and an MX change each carry a date. Your research log should record the date the record was created, the date you read it and the date the consequence it describes is expected to land, in the manner described in public signal prospect research.

Roles are hypotheses too. A deal moves people. The leader named in the acquired company's last org chart may now report into the acquirer, hold an interim title or have left; the SEC's Item 5.02 captures officer departures and appointments for registrants, and the method for reading a leadership change is in how to read a new executive hire sales trigger. Verify the person's current role on the day you write, not the day the deal was announced.

What the public record shows: an original count of deal-stage language in filings

To test whether the Three Gates are visible in filings, we ran the SEC's EDGAR full-text search on October 2, 2026 for exact phrases that mark each gate and each consequence, over the twelve months from October 1, 2025 to October 1, 2026, in two filing groups: current reports (Form 8-K) and periodic reports (Forms 10-K and 10-Q). The unit is documents containing the phrase, not deals and not companies; one deal produces several filings, and several of these phrases have uses outside deals.

Phrase searched 8-K documents 10-K and 10-Q documents Gate or consequence it marks
"Agreement and Plan of Merger" 4,852 3,758 Signing
"regulatory approvals" 7,226 6,568 Waiting period
"Hart-Scott-Rodino" 1,583 603 Waiting period
"completed the acquisition" 872 2,753 Closing
"completed its previously announced acquisition" 236 148 Closing
"transition services agreement" 746 970 Closing into integration
"integration costs" 2,013 1,845 Integration
"synergies" 6,058 5,711 Consolidation
"enterprise resource planning" 490 1,583 Systems
"rebranding" 348 525 Branding
"consolidation of facilities" 226 116 Facilities
"facility consolidation" 136 107 Facilities
"WARN Act" 589 191 Facilities and people
"novation agreement" 75 109 Procurement
"vendor consolidation" 56 68 Vendors

Four observations, stated as what the counts show rather than what they mean.

  1. The signing vocabulary dominates current reports: 4,852 8-K documents contain "Agreement and Plan of Merger", against 236 that contain "completed its previously announced acquisition" and 872 that contain "completed the acquisition". Announcements are filed as events; completions are filed as events less distinctively and described again later in periodic reports, where "completed the acquisition" appears 2,753 times.
  2. The consequence vocabulary is small in current reports and larger, in relative terms, in periodic ones. "Enterprise resource planning" appears in 490 8-K documents and 1,583 10-K and 10-Q documents; "rebranding" in 348 and 525. The consequences a seller cares about are disclosed after the fact, in quarterly and annual narrative, not as dated events.
  3. The vendor decision is barely a filing event at all. "Vendor consolidation" appears in 56 8-K documents and 68 periodic ones across a year of filings by every registrant. The decision that matters to a vendor is made below the disclosure threshold, which is why the verify-next steps in the table above point at roles, portals and contract dates rather than at filings.
  4. "Synergies" (6,058 and 5,711) and "regulatory approvals" (7,226 and 6,568) are too broad to count deals; both phrases appear in earnings commentary, risk factors and guidance that have nothing to do with a specific transaction. They are included to show the ceiling of what a phrase count can tell you.

Anyone can reproduce the table: open EDGAR full-text search, enter the phrase in quotation marks, set the form type and a custom date range, and read the document total. Re-running it on a later date will produce different numbers because filings continue to arrive and the window moves.

How fast does a merger acquisition sales trigger decay?

The dedicated vendor page ranking for this query, and Google's AI answer built partly on it, give a "first 100 days" window and a six-month lock-in. Neither cites a source for either figure, and this guide does not adopt them. The clocks below are the ones that are written down somewhere public.

Clock Length Where it is written What it tells a seller
8-K filing deadline Four business days from the triggering event for most items SEC Investor Bulletin on Form 8-K The filing date is at most four business days after the signing or the close; use the event date in the filing, not the filing date, as the signal date
HSR initial waiting period 30 days after filing; 15 for a cash tender offer or a bankruptcy; longer under a Second Request; shorter with early termination FTC, premerger notification and merger review process The earliest a reportable deal can close; before it, the parties operate independently
Stated expected close As written in the release ("expected to close in the second quarter") The parties' own announcement The parties' own forecast of gate two; slippage against it is itself a signal of regulatory or financing friction
WARN notice period At least 60 days before a covered plant closing or mass layoff 20 CFR Part 639 A dated facilities or headcount consequence, assigned to the buyer for post-sale actions
Transition services agreement term As written in the agreement, where filed as an exhibit EDGAR exhibits to the 8-K or the next 10-Q The date by which a carved-out unit must stand on its own systems and services
Contract renewal dates Per contract; public for government contracts, otherwise private Award records; filed material agreements The date on which a vendor review can take effect, as distinct from the date it is discussed

A decay default follows from the clocks. At signing, the trigger is fresh for research and stale for pitching; the only decisions being made are deal decisions. At close, the trigger is fresh for the consequences that are planned first; the defaults in the table put systems and people before facilities and brand. In integration, the trigger does not decay as a whole; each consequence decays on its own clock, and a facilities consequence can be live two years after a systems consequence has closed. Treat "the deal was eighteen months ago" as a reason to check which consequences remain open rather than as a reason to drop the account.

Which deals are noise for you?

Not every merger acquisition sales trigger deserves a Deal Card. Five filters remove the ones that will not change anything in your category.

  1. Relative size. A deal that is small relative to the acquirer is absorbed into an existing business unit with the acquirer's existing tools. The release gives you the price where disclosed and the acquired company's headcount or revenue where stated; a target that is a low single-digit percentage of the acquirer is a tuck-in, and the consequences table above shrinks to the "acquired company" row.
  2. Deal form. An asset purchase moves specified assets and contracts; a stock purchase or merger moves the entity. The release and the 8-K exhibit say which. For a vendor, the difference is whether your contract with the target was assigned or simply came along.
  3. Sponsor involvement. A private equity add-on is an integration into a platform company the sponsor already owns, run by the sponsor's operating team and the platform's management. The consequence pattern is the acquirer pattern, with the platform's incumbents as the default winners.
  4. Minority stakes, investments and partnerships labelled as deals. A strategic investment, a joint venture or a "partnership" headline is not a change of control. None of the Three Gates applies; read it as a funding or partnership signal instead, in the manner of a funding round sales trigger.
  5. Deals that touch your customers rather than your prospects. When your own customer is the target, the trigger is a retention event: your contract now belongs to the acquirer, your champion's role is in question, and the acquirer's incumbent is your competitor. The same Three Gates apply with the roles reversed.

Pre-outreach checklist: the Deal Card

The Deal Card is a one-page record you complete before any message goes to an account surfaced by a merger acquisition sales trigger. Copy the fields into your CRM or a sheet; an account with blank fields in the first block is not ready.

Block one: the deal (complete before close)

  1. Buyer, seller and deal form (merger, stock purchase, asset purchase, carve-out), with the release URL and date.
  2. Gate passed today, with the record that proves it (release only; 8-K item number; certificate of merger; Item 2.01).
  3. Stated expected close and any regulatory references (HSR, EU, sector regulator) in the release.
  4. Side you are selling to (acquirer, target, merged entity, carve-out) and why.
  5. Relative size: the target's stated revenue or headcount as a share of the acquirer's, with the source.

Block two: the consequences (complete after close, revisit monthly)

  1. For your category, which of the seven consequences is in play, the hypothesis in one line, and the alternative explanation in one line.
  2. The verify-next record you found, its date, and the date you read it.
  3. The decision owner by name and current title, verified on the day of writing, and the operating contact at the acquired company if different.
  4. The clock that governs this consequence (TSA term, renewal date, WARN date, migration date) and its source.

Block three: the message (complete last)

  1. The one verified fact your first sentence will state, with its source.
  2. What you are asking for (a comparison, a baseline review, a working session) and why the timing fits the clock in field 9.
  3. What you will not claim: no reference to internal plans you have not seen, no "I know you're consolidating", no personal data beyond business role and public work history.

Compliance sits around the card rather than inside it. Keep business contact data only, prefer company roles over personal detail, and treat the rules in the jurisdiction of the person you are writing to as the constraint. Lead Seeker's published data boundaries and sources are set out on its trust page; this guide is not legal advice.

A synthetic example: one announced acquisition read through the Three Gates

The companies, people and figures below are invented to show the method; any resemblance to a real deal is accidental.

The release. On a Tuesday, Marlowe Fabrication Holdings, a listed industrial-components maker with 6,200 employees, announces a definitive agreement to acquire Ridgefern Sensor Systems, a private firm with 410 employees and two plants, for an undisclosed sum, "subject to customary closing conditions, including regulatory approvals," with closing "expected in the first quarter." An 8-K is filed under Item 1.01 two days later with the merger agreement as an exhibit. You sell a quality-management platform that Ridgefern runs and Marlowe does not.

Gate one read. Side: target, with the acquirer as the decision owner after close. Relative size: 410 of 6,610 combined employees, so roughly six per cent; a tuck-in by headcount, but a product-line acquisition rather than a geographic one, which keeps the systems consequence open. Consequences in play for your category: systems (does Marlowe adopt, retire or leave Ridgefern's quality platform?) and vendors (your Ridgefern contract passes to Marlowe at close and runs to its renewal). Alternative explanation: Marlowe keeps Ridgefern as an operating subsidiary with its own systems, which the release's language about "preserving Ridgefern's engineering culture" leaves open. Decision today: no message. The gun-jumping constraint means nobody at Marlowe can review Ridgefern's vendors yet, and your Ridgefern champion cannot share what Marlowe intends. Action: open the Deal Card, log the expected close, set a watch on Marlowe's 8-Ks and both careers pages.

Gate two read. Eleven weeks later, Marlowe files an 8-K under Item 2.01 stating the acquisition was completed on the prior Friday. The same week Marlowe posts a "Manager, Quality Systems Integration" role in the city of Ridgefern's larger plant, and Ridgefern's careers page begins redirecting to Marlowe's. Verify-next records now exist for two consequences: systems (the role's text names "harmonising quality processes across sites" without naming a platform) and branding (the redirect, dated by an archived copy). The vendor consequence is unchanged: your contract has eighteen months to run. Decision owner: Marlowe's VP Quality, confirmed in role on LinkedIn that day; your Ridgefern contact now carries a "Director, Quality, Ridgefern (a Marlowe company)" title. Action: one message to the VP Quality that states what you verified, the completed acquisition and the posted integration role, and asks for a comparison of how both sites' quality data is structured today, before any harmonisation decision. No claim that Marlowe is consolidating platforms, because no record says so.

Gate three read. Three months after close, Marlowe's 10-Q discloses integration costs for the quarter and says the company "expects to complete the migration of acquired operations to its enterprise systems over the next eighteen months." That sentence closes one hypothesis and opens another: the ERP decision is made and is not yours to influence; the question for your category becomes whether the quality platform is in scope of "enterprise systems" or is a plant-level system that survives. Field 9 on the Deal Card now reads: migration horizon eighteen months from the 10-Q date; contract renewal fifteen months out. The two clocks nearly coincide, which is the timing argument for a working session now rather than a renewal conversation later.

Nothing in the example tells you that Marlowe buys. It tells you which gate was passed, which consequences had a record behind them, who held the decision on the day and which clock governed it. That is what the trigger is for.

Writing the first message without pretending

The temptation after a deal is to write as if you have read the integration plan. You have not. A first message that survives scrutiny on the other side does four things. It states the public fact you verified, with its date: the completed acquisition and the posted role, not "your consolidation". It names the side and the consequence you are writing about, so the reader knows you understand that the acquirer, not the acquired company, holds the decision. It asks for something proportionate to the gate: a comparison or a baseline before close, a working session after it. And it leaves out what you do not know, which includes whether any vendor review is planned and what the reader thinks of their incumbent.

Two phrases to delete from every draft: "now that you're integrating" when no record shows integration has started, and "I know you'll be consolidating vendors" at any time. The counts above put "vendor consolidation" in 56 current reports across a year of filings by every registrant; it is not something you know.

Where this fits in a signal programme

A merger acquisition sales trigger belongs to the public business signal class: an observed event with a date in the record, as distinct from topic intent inferred from browsing or first-party behaviour on your own site. It is worth more than its headline when combined with a second, independent record, a posted integration role, a WARN notice, a domain change, that confirms a specific consequence has started. The combination rule and the eight-stage workflow from signal to meeting are set out in signal based prospecting, and the wider library is on the intent data insights hub.

Where Lead Seeker fits is narrow and stated in its own product pages. Trigger Signals group "M&A activity" with funding and financial events, draw on public sources only, including regulatory filings and press releases, and every signal in the feed links back to its original source so a rep can read the underlying event before reaching out; the catalogue is described in how to read Trigger Signals. The Prospect Dossier attaches the verified contact, the public signal that surfaced the person and the public source behind each claim where available, which is the form a completed Deal Card takes when it reaches a rep; see how the prospect dossier works. What Lead Seeker does not do is read the integration plan for you; the gate, the side and the hypothesis are judgments the Deal Card asks you to make.

Three related companies are mentioned once each, for the workflows where they fit. Percepture, which is related to Lead Seeker, offers a B2B intent data service for teams that want the signal programme run for them. Prime AI Visibility, also related, measures how AI answer engines describe a company; after a rebrand, the combined company's own name is the thing to check in those answers, see Prime AI Visibility. Pyra, also related, builds AI agents; monitoring 8-K feeds, careers pages and state WARN lists for a watchlist of deals and assembling the first block of the Deal Card is the kind of repetitive, source-linked task an agent is suited to, see Pyra. None of the three is evaluated or ranked on this page.

Frequently Asked Questions

Is a merger or acquisition a buying signal or intent data?

It is a buying signal in the public-business-signal sense: an observed event, with a date, recorded by the companies themselves or a regulator. It is not intent data, which is an inference about research behaviour. The distinction matters because a deal tells you something happened at the account; it tells you nothing about whether anyone there is researching your category. The Three Gates and the consequences table turn the event into hypotheses that intent data, first-party behaviour or a posted role can then corroborate or rule out.

Should I contact the acquired company before the deal closes?

Contact for research, not for a consolidation pitch. Until the deal is consummated the two companies are independent businesses that must operate independently, under the FTC's reading of the HSR Act and Rules, and in the EU under the Merger Regulation's standstill obligation. Nobody at the target can commit to a post-close vendor decision, and nobody at the acquirer can direct the target's purchasing. A pre-close conversation that asks how the target's processes and data are structured today, with no reference to what the acquirer might do, is appropriate; a message that assumes a combined purchasing decision is not.

How do I find out whether a deal has closed?

For an SEC registrant on either side, look for an 8-K under Item 2.01, Completion of Acquisition or Disposition of Assets, filed within four business days of the close; the item text gives the completion date. For a Delaware corporation, the merger becomes effective when the agreement or a certificate of merger is filed with the Secretary of State under Section 251. For private deals with no filing on either side, the parties' own completion release, a change in the target's legal name on its site and contracts, and the start of consequences such as a careers-page redirect are the available records. Absent any of them, treat the deal as announced, not closed.

How long after an acquisition is the trigger still useful?

Each consequence has its own clock, so the trigger does not expire on one date. Systems and people decisions are planned first after close; facilities and brand decisions trail them; vendor reviews take effect on contract renewal dates that can sit a year or more after close. The clocks that are written down are the 8-K deadline, the HSR waiting period, the parties' stated expected close, the WARN notice period, a filed transition services agreement's term and any public contract renewal date. The "100 days" and "six months" figures on other pages for this query are not sourced and are not used here.

Which side of the deal should I prospect, the acquirer or the acquired company?

Decide by where the decision for your category will sit after close. When the acquirer runs an incumbent in your category, the acquirer's functional leader owns the decision and the acquired company's manager is the operating contact. When the acquired company ran your category and the acquirer did not, the acquirer still decides whether to adopt, retire or leave it. When the deal is a merger of equals with a new name, the combined leadership and the integration office decide, and there is no incumbent by default. When the deal is a carve-out, the divested unit's new management must stand up its own services by the date in the transition services agreement, and that is the one case in which the acquired side is the buyer of record.

What does an M&A trigger event mean to a business broker?

In exit planning and M&A advisory, a "trigger event" is a catalyst that pushes an owner to sell a business: a market shock, a family transition, a growth plateau, interest-rate conditions or owner burnout. One of the pages ranking for this query is written from that perspective. This guide uses the sales-prospecting meaning, in which a completed or announced deal at a target account is the event and the question is what it changes for a vendor. If you arrived here looking for the exit-planning meaning, the advisory pages address it.

What if my own customer is the one being acquired?

Run the same Three Gates with the roles reversed. At signing, your contract is unaffected and your champion cannot share the acquirer's intentions. At close, your contract passes to the acquirer, whose incumbent in your category is now your competitor and whose functional leader is your new decision owner. In integration, the consequences table tells you which records to watch: a posted migration role or a disclosed systems consolidation is a retention risk with a date on it. The Deal Card fields are identical; the message asks for a baseline of what your product does across the combined footprint rather than a comparison against an incumbent.

Sources

About the Author

Bob Generale is President of Percepture. He works across SEO, AI search, digital PR, sales intelligence and AI-powered revenue systems, with a focus on connecting visibility, buyer intent and sales action.

Disclosure: Lead Seeker is related to Percepture, Prime AI Visibility and Pyra. The links to the three on this page are labelled as related, and no vendor, data provider or agency named here was tested or engaged in the course of writing it.

Next Steps

Take the last five deals your team acted on and write the gate, the side and the consequence next to each one, then look for the record that proved the consequence had started. The ones with a filing, a posted role or a notice behind them are the pattern to build the watchlist around. Then claim 5 free verified leads to see what a dated, source-linked record for one of those accounts looks like beside your own Deal Card.