Lead qualification guides · Disqualifying evidence
When a lead acquires a company that sells what you sell, most of the time the answer is no for a year or two. Here is how to confirm what they bought and why, where the exceptions hide, and what LeadSmarts does with the evidence.
AI does the research. Your reps own the relationship.
No credit card. No automatic sending. Review every result before using it.
An acquisition is the most expensive way a company can answer the question you were going to ask. It looked at the problem, decided to own the solution rather than rent it, and paid for a team, a product, and its customers. Everyone involved now has a reason to make that bet look right. The integration project will absorb the engineers, the budget, and the attention of the very people you would sell to, and anyone proposing an outside vendor for the same job is arguing against the board's decision.
That is why this is usually a hard stop. Product fit drops where it counts: the company now runs a competing product, so your tool no longer fits its operating context, and the problem you solve has an owner inside the building. Buying intent goes quiet too. There is plenty of change underway, but all of it points toward the acquired product. The window is not shut for a quarter, as it is after a freeze. It is shut until the integration lands or fails, which is commonly a year or two.
The exceptions are real, though, and the announcement usually tells you whether you are looking at one. Companies buy rivals for their customers, a region, or a team as often as for the product, and a product bought for its customer list is often retired within a year. The acquired tool may serve a segment your contact does not run: domestic fleets, not cross-border lanes, or small accounts, not enterprise ones. And if you sell something adjacent rather than the same thing, the integration itself creates needs. Read why they bought, then decide.
The deal is public; what it means for your contact takes five more checks.
LeadSmarts finds acquisition news during live research and scores it under fixed rules, with a source link on every item. The model has no negative points, so a rival acquisition shows up as points that are not awarded. On product fit, a company that now owns a competing product reads as a mismatch on technology or operating-context fit (0 of 10), and problem and use-case fit (25 points) drops to a partial or no match when the acquired product covers the same job. Recency does not apply to fit, so a deal from two years ago counts as fully as last month's while the product is still in use. On buying intent, the integration is a vendor or technology change (20 points), but it runs toward the rival, so there is nothing to award unless the evidence names a gap you fill. An official press release is the top source quality, so confidence usually stays high: the verdict is low because the evidence is clear, not because it is thin.
An acquisition is not a hard disqualifier by itself. Hard disqualifiers come from your own business context, and any active one makes the verdict Cold whatever the scores say. If you wrote a rule such as 'no companies that own a competing product', a matching lead is Cold. If you did not, the lead is scored on what remains, which for a direct overlap usually means a weak fit score and a Cold or low Warm verdict, with the reasoning shown per criterion so you can see exactly which part of the fit the acquisition took.
Acquirers walk the expo floor more than you would expect, and not to buy. A product manager from a company that just bought your rival is often doing competitive homework, asking sharp questions about your roadmap and pricing. That is a good conversation and a bad lead. Note on the badge scan who they are and what they asked, and do not let the energy of the chat put them at the top of the follow-up list. The opposite case is worth listening for too: 'the acquisition only covers our domestic side' is a sentence that reopens the account, and you will rarely find it written anywhere.
Before the event, qualify the attendee list for acquisitions so nobody spends booth time pitching a company that owns your competitor. After it, sort the scan list by fit first, then read the acquisition evidence on any lead that dropped. Each one gets a dated reminder tied to a milestone you can check: the sunset date, the end of the earn-out, the first anniversary of the deal. The acquired company's own customers, if any of them visited your booth, are a different story: they are facing a migration they did not choose, and they belong near the top.
Do not argue with the acquisition. Telling a director that the product their company just paid for is weaker than yours asks them to say the board made a mistake, and they will not. Congratulate them, take the deal as settled, and look for what it leaves out: the segment the acquired product does not serve, the region it does not cover, the work the integration has pushed down the queue.
If the overlap is total, ask for nothing. A short note that acknowledges the deal and offers a conversation once the integration has landed keeps you in the room for the day it stalls, and keeps you in touch with a contact who may move to another company.
"Good to meet you at Logistics Tech Summit. Congratulations on Routewise: owning route planning makes sense at your scale. You mentioned the integration covers the domestic fleets first, and that cross-border lanes still run on spreadsheets. That gap is most of what we do. Worth twenty minutes on just that piece, or should I check back once the integration lands?"
It accepts the deal, names the gap in the contact's own words, and offers two answers that both keep the door open.
No. It lowers product fit where the acquired product overlaps yours and leaves nothing to award on vendor or technology change, but a verdict only becomes Cold through low scores or a hard disqualifier, and hard disqualifiers come from your own business context. If you want a competing product to disqualify outright, write that rule into your context and the model enforces it.
At a milestone, not a fixed interval. Watch for the acquired product's sunset announcement, the founders leaving when the earn-out ends, or the integration running long past its stated date. Any of those is fresh, dated evidence, and intent evidence under 90 days old counts in full when you research the lead again.
They are a separate list and often a better one. A customer told to migrate onto the acquirer's platform is facing a vendor change it did not ask for, which is scored under vendor or technology change, and many of them will run a fresh evaluation instead. Find them through the acquired product's case studies, G2 reviews, and logo wall.
Live web research per lead: the acquirer's press page, the acquired company's announcement, reputable trade coverage, filings where they are public, and the careers and people pages that show how the integration is staffed. Each item carries a source link and a date, and the result page shows how it moved fit, intent, and confidence, so you can check the reading before you decide.
Evidence rarely arrives alone. If you are seeing this, check for these too.
Companies switch when something failed. A visible stack change means an open budget line, an active evaluation, and a short window.
Read the guide →Cuts freeze most new spend, but a restructuring sometimes creates the exact problem you solve. The announcement tells you which, if you read it properly.
Read the guide →New leaders audit everything they inherit and spend their honeymoon budget early. Their first two quarters are the buying window.
Read the guide →Upload the list and get the high-fit leads back first, with every acquisition found, dated, and sourced.
Qualify 5 leads freeNo credit card. No automatic sending. Review every result before using it.