# When your prospect gets acquired mid-deal: what to re-qualify and what to record in Pipedrive

https://salesbond.app/blog/prospect-acquired-mid-deal-pipedrive/
Published: 2026-10-07 · Updated: 2026-10-07

If your prospect gets acquired while your deal is open, treat the deal as one you have to qualify again. Within a week, find out who decides now, whose budget pays, and what happens to the project you were selling into. Move the deal back to the stage you can honestly defend with what you know today. Then record the new structure in Pipedrive by linking the two companies through Related organizations, not by merging them, because a merge cannot be undone.

## The press release came on a Friday, and the deal still says “Proposal sent”

A made-up example, so no real names. Radomir sells for an equipment distributor. His deal is with a regional retail chain: eleven stores, a proposal for new in-store equipment sent on February 27, a little over $40,000 in the pipeline, close date set for March 31. His contact is Isidore, the chain’s head of operations, who asked for the proposal in the first place and has answered every email within a day.

On Friday, March 20, a press release goes around: a national holding has bought the chain. Isidore’s last reply was eight days ago. The deal in Pipedrive still sits in “Proposal sent”, 60 percent probability, close date eleven days out.

Nothing in the record is false, but who decides, who pays and when are now unknown. Pipedrive doesn’t know the buyer changed hands.

## Three questions to ask after the acquisition news

The first move is one email to Isidore, sent the same day. Not a “congratulations on the news” email with nothing in it, and not a renewed pitch. A short note that says: we saw the announcement, we assume some things change for the equipment project, can you tell us three things. He is the right first reader: the one person on the account who already wanted this to happen. If you are not sure he is that person, the test is in [how to tell a sales champion from a friendly contact](https://salesbond.app/blog/sales-champion-pipedrive-deals/).

Here they are:

1. Who signs now? Does the decision stay at the chain, or does it move to the holding’s purchasing team? If it moves, who there, and has Isidore met them? Often the honest answer is “I don’t know yet”, and that is useful too: it tells you the decision date is not March 31.
2. Whose budget is it? The proposal was priced against the chain’s budget. After an acquisition that budget may be frozen, folded into the group’s, or left alone for the year. You are not asking for a commitment, only which pot of money the project is attached to now.
3. Is the project still alive? Is new in-store equipment a priority for a chain that just got bought, or does the holding already have a supplier and a standard? People avoid this question because the answer might be “it’s dead”. Ask it anyway. A dead project you learn about in March costs you one email. One you learn about in June costs you a quarter of pipeline.

Five working days is our own limit, not the buyer’s. After a week of silence you have to decide what this deal is, and we would rather decide with information than without.

If Isidore answers all three, you have a deal to re-qualify. If he says “ask me in a month”, you have a date. If he goes quiet, you have a single-threaded deal in the worst week to be single-threaded, and the next step is [finding a second person on the account](https://salesbond.app/blog/single-threaded-deals/).

## Where to move the deal, and what to write in the note

We move the deal back. Usually to the qualification stage, sometimes to discovery if the project itself is in doubt. We do it the day the news lands, not after the answers come in.

That feels wrong to most reps: “Proposal sent” is true, and nothing has been lost yet. But a stage should say what you know about the buyer, not what you have done, a point we make at more length in [what not to automate in your sales process](https://salesbond.app/blog/what-not-to-automate-sales-process/). On March 20 Radomir doesn’t know who decides or who pays, so the deal goes to Qualification.

The probability moves with it. The close date gets cleared or pushed to a date Radomir can name a reason for. In the example he sets it to April 30 with the reason “awaiting Isidore’s answer on who signs after the holding takeover”.

The note matters more than the stage. Written the same day, in the deal’s notes, something like:

> March 20. Chain acquired by [holding] (press release today). Decider, budget and project priority unknown. Emailed Isidore with three questions. Moved from Proposal sent to Qualification. Original proposal of February 27 stands until we hear otherwise. Next check: March 27.

A few lines. Anyone who opens this deal in a month, including Radomir’s manager, sees why a deal that was at 60 percent is now at the front of the pipeline, and what was done about it. Without the note, a deal that moved backwards looks like a rep covering for a mistake. With it, it looks like what it is. Keep the note about who decides, who pays and when; if the takeover raises questions about the contract itself, that’s a question for a lawyer, not for the deal record.

One more reason to move it now: a forecast built on a deal at “Proposal sent” with an eleven-day close date is counting that money for teh quarter. Better it drops in March, while there is time to do something about it.

## What to record: Related organizations, participants, a new decision date

Now the CRM side. The goal: when the holding’s purchasing manager finally emails Radomir in two months, the deal, the chain, the holding and every person involved can be found from one another, not scattered across three records and someone’s inbox.

In Pipedrive the tool for this is Related organizations ( [Pipedrive: related organizations](https://support.pipedrive.com/en/article/related-organizations)). On the chain’s organization record, in the Related organizations section, you click the plus, add the holding and choose Parent as the relationship type. There are three types: Related, which carries no hierarchy, Parent, and Daughter. Other chains the holding owns show up as sister organizations automatically once each is linked as a daughter of the same parent. One thing to know before you click: a relationship cannot be edited afterwards. Link the holding as Related when you meant Parent, and the fix is to open the relationship’s details, delete it and add it again. Not a disaster, but it is why we write the structure in the note first and click second.

Short steps for the example:

1. Create the holding as a new organization if it does not exist yet. Do not rename the chain’s record to the holding’s name. The chain still exists, your deal is with it, and the proposal names it.
2. On the chain’s organization page, add the holding with the Parent relationship type. The deal stays attached to the chain.
3. Add new people to the deal as participants ( [Pipedrive: participants](https://support.pipedrive.com/en/article/participants) ); Isidore stays the linked person for now. If the center of the deal later moves to the holding’s purchasing manager, switch the linked person to them. Pipedrive keeps the previous linked person as a participant, so Isidore does not drop off the deal.
4. Set the new expected close date and write the reason for it in the note, as above.

![Diagram: a holding as parent, a regional chain as daughter with the deal and its people, and a sister chain linked automatically](https://salesbond.app/wp-content/uploads/2026/10/prospect-acquired-mid-deal-pipedrive-2.png)

That is the whole setup: two organizations linked, the right people on the deal, a date with a reason. If your team keeps [a key account plan](https://salesbond.app/blog/key-account-plan-small-sales-team/) for this account, redraw it the same day, because the people on it just changed.

## Three things we have seen go wrong, and one of them is permanent

**Merging the two organizations.** Merge Duplicates in Pipedrive is for two records that are the same company entered twice ( [Pipedrive: merge duplicates](https://support.pipedrive.com/en/article/merge-duplicates)). The primary record’s data wins on conflicts, and merged records cannot be split back apart. A chain and the holding that bought it are two companies with a relationship, which is what Related organizations is for. The day may come when the chain is dissolved into the holding, its stores rebranded, and then merging is honest. Until that day, link. Why merging deserves care even with real duplicates is in [duplicate records in Pipedrive](https://salesbond.app/blog/duplicate-records-in-pipedrive/); merging two deals is a different operation, covered in [merging two deals in Pipedrive](https://salesbond.app/blog/pipedrive-merge-two-deals-primary-deal/).

**Cloning the deal onto the holding.** Some reps create a fresh deal against the holding “to start clean” and leave the old one open. Now one piece of revenue sits in two deals, one with the history and one with the new contact, and the pipeline double-counts. Keep one deal, on the chain, with the holding linked as parent and it’s people as participants. Open a second deal only if a genuinely second opportunity appears, such as the holding asking for a group-wide quote, and say so in both notes.

**Waiting for things to settle.** The quietest mistake, and the one we have run into most. The rep decides the buyer is busy, that calling now would be tactless, that in a month the picture will be clearer. A month later the the holding’s purchasing team has had a month of conversations with suppliers, and Radomir’s distributor was not in any of them. Some patience is really avoidance. An email with three questions is exactly what a supplier who cares about the project sends.

## Keep it open, or close it as lost?

After the week, there are three outcomes we see.

Isidore comes back with a name at the holding, or a date, or both. The deal stays open, re-qualified against the new decider, and works like a new deal with one advantage: a proposal already exists and someone inside already wanted it. In the deals we have seen this good case is not a rare one: a holding that just bought eleven stores has every reason to want them equipped properly.

Isidore comes back with “the group has a supplier, we have to use them”. Close it as lost the same week. If you use the list from [lost reasons in Pipedrive](https://salesbond.app/blog/pipedrive-lost-reasons/), that is “Chose a competitor”: the buyer told you who they picked, even if the group picked for them. A takeover that only shelves the project belongs under “Timing moved”. Whatever your labels, keep these losses apart from losses on price or product, because a loss review that lumps them together teaches the team the wrong lesson. Why acquisitions belong in the “outside the rep’s control” pile is in [debriefing a lost deal with your rep](https://salesbond.app/blog/lost-deal-debrief-rep/).

Isidore does not come back at all, and nobody at the holding is reachable. We hold the deal open in Qualification for one more cycle, with a check-in activity every two weeks and a close date we actually believe. If after two cycles there is still no decider, nobody decides, and we close it the way we close [no-decision deals](https://salesbond.app/blog/no-decision-deals-pipedrive/). A deal with no decider and no next activity is not a deal. It is a reminder to feel bad on Mondays.

A deal that moved back to Qualification on March 20 belongs on the manager’s list on March 27 and April 10 with one question: did we find the decider? We build SalesBond, a sales management layer on top of the CRM a team already uses, and its Deal Health checks every open deal against more than 20 rules, including activity and progression rules, and explains what pulled a deal’s score down. It will not tell you who the new decider is. It makes sure the question gets asked on time. To see which of your open deals look like Radomir’s did on March 19, [check your CRM with SalesBond](https://salesbond.app/).