... got the money, then found out the previous owner was a chainsmoker and a cadaver is decomposing in the trunk, then for some mysterious reason didn't want to buy it.
He did want to buy the car, signed a contract to buy the car that decided that he didn't want to buy it because it had a head gasket leak. Even though that was the whole reason he was buying the car, and he doesn't have any evidence for said leak anyway.
That’s precisely how acquisitions at my current and past company worked. Everyone signs NDAs, there’s a fee paid by the purchaser for the time should they decline the deal, and the audit commences.
I’ve been asked to do the evaluation a few times and it’s pretty straightforward. Even if you think the code is of poor quality, it may still make sense to complete the purchase because of the business case.
Not necessarily. It depends on the company acquiring. I've seen M&As focus solely on the relationships (ex, customers), so the tech DD was just checkboxes without deep dives.
Not necessarily… what? This is my actual professional experience. I’m sure people just buy things without any due diligence somewhere but I have never seen it.
In one case my judgement was that the customer list was all that there was of value. They opted to not buy that company.
Getting/giving access to the actual code/backend (especially as a competitor!) is a heavily negotiated diligence request.
The seller can simply refuse without even giving a reason.
ITT:
People are throwing around the phrase "audit" liberally. Audit will have a defined (and likely limited) scope and is typically more about compliance, e.g., Do you have the correct number of Microsoft Office licenses per accounting records?
Inspecting the source code is a condition of all deals I've been involved with. Most sensible people want to see what they buying, unless they are under pressure to close fast due to competition. It's a lot like buying a house.
I once read about an acquisition attempt by Google which eventually failed because Google found codebase less than impressive. So I guess this is normal to review codebase before a buyout.
A meaningful audit at Twitter would take months. This is but a stunt.