How Tech Acquisitions Work: A Complete Guide
M&A Intelligence · The CODEW Intelligence
The complete guide to technology acquisitions — deal types, buyer motivations, the step-by-step process, valuation methods, deal structures, and what actually happens to founders, employees, and products after the close.
Every week, The CODEW covers another tech acquisition — a startup absorbed into a giant, two rivals merging, a founder cashing out after a decade of grinding. But behind every headline ("Company X acquires Company Y for $Z billion") sits a process that usually takes months, involves dozens of specialists, and follows a fairly consistent playbook regardless of deal size.
This guide breaks down how tech acquisitions actually work, from the first conversation to the day the acquired company's logo disappears from its own website.
What Counts as a Tech Acquisition?
A tech acquisition happens when one company buys a controlling stake — usually all of it — in another. In the tech industry, this takes a few common forms:
Full Acquisitions — The buyer purchases the entire company, including its product, team, IP, and customer base.
Acquihires — The buyer is primarily interested in the team, not the product. The startup's product is often shut down shortly after.
Asset Purchases — The buyer takes specific assets — a patent portfolio, a codebase, a customer list — without absorbing the whole company or its liabilities.
Mergers — Two companies combine into a new or surviving entity, more common between similarly sized players than in the classic "Big Tech buys startup" pattern.
The distinction matters because it shapes everything downstream: valuation, deal structure, and what happens to employees.
The CODEW Lens: The form of the acquisition is often the clearest signal of the buyer's real motivation. A full acquisition says "we want the business." An acquihire says "we want the team." An asset purchase says "we want one thing and nothing else."
Why Companies Acquire Other Companies
Acquisitions are rarely just about revenue. The most common motivations in tech:
Talent — Acquiring a strong engineering or research team faster than hiring individually (common with AI labs and specialized infrastructure teams).
Technology — Buying IP, patents, or a product that would take years to build in-house.
Market Access — Gaining customers, distribution, or entry into a new geography or vertical.
Eliminating Competition — Removing a rival before it scales into a real threat.
Defensive Positioning — Preventing a competitor from acquiring the same target first.
Understanding the why behind a deal is usually the fastest way to predict what happens to the acquired company afterward — whether it is integrated, shut down, or left to operate independently.
The CODEW Lens: The motivation determines the outcome. A talent-driven acquisition rarely preserves the product. A technology-driven acquisition rarely preserves the team. A market-access acquisition rarely preserves independence.
The Acquisition Process, Step by Step
Sourcing → NDA → LOI → Due Diligence → Valuation & Structure → Definitive Agreement → Regulatory Review → Closing & Integration
1. Sourcing and Initial Contact
Deals start in one of three ways: the buyer's corporate development team proactively identifies a target, a banker or advisor shops the target around, or the startup itself signals it's open to being acquired (often after a tough fundraising environment).
2. Preliminary Discussions and NDA
Before any real numbers are exchanged, both sides sign a non-disclosure agreement. Early conversations focus on strategic fit — does this make sense at all — before diving into financials.
3. Letter of Intent (LOI) / Term Sheet
Once there's mutual interest, the buyer issues a non-binding LOI outlining the proposed price, structure, and key terms. This isn't final, but it sets the framework everyone negotiates against.
4. Due Diligence
This is the longest and most intensive phase, often taking 4–12 weeks. The buyer's teams — legal, finance, engineering, security — dig into:
Financial statements and revenue quality
Customer contracts and churn
Codebase quality, technical debt, and IP ownership
Cap table, outstanding equity, and any litigation risk
Compliance, data privacy, and security posture
Due diligence is where deals die. A messy cap table, undisclosed litigation, or a codebase full of unlicensed dependencies can tank a deal even after an LOI is signed.
The CODEW Lens: Due diligence is not a formality. It is where the deal is actually tested. A signed LOI means the buyer is interested. A clean data room means the buyer can close.
5. Valuation and Deal Structure
Valuation in tech M&A rarely uses a single method. Buyers typically triangulate between:
Revenue multiples — Common for SaaS (e.g., 5–10x ARR depending on growth rate)
Comparable transactions — What similar companies sold for recently
Strategic premium — How much extra the buyer pays for talent, IP, or competitive removal, which can override pure financial logic entirely
Deal structure also matters as much as headline price: how much is cash versus stock, whether there's an earnout tied to future performance, and how founder/employee equity vests post-acquisition.
The CODEW Lens: A high headline valuation with a heavy earnout component is a very different outcome than an all-cash deal. The structure is often the real story.
6. Definitive Agreement
Lawyers draft the binding purchase agreement covering price, representations and warranties, indemnification, and closing conditions. This is where most of the legal risk gets allocated between buyer and seller.
7. Regulatory Review
Depending on deal size and market, the transaction may need clearance from antitrust regulators — the FTC and DOJ in the U.S., the European Commission in the EU, or equivalent bodies elsewhere.
Most tech deals clear quickly, but large or competitively sensitive ones can face extended review or blocks.
8. Closing and Integration
Once conditions are met, the deal closes and ownership transfers. What follows — full integration, independent operation, or wind-down — depends entirely on the original motivation for the deal.
The CODEW Lens: The close is not the end of the story. For many acquisitions, the close is when the real changes begin — layoffs, product sunsets, and integration decisions that affect everyone who stayed.
What Happens to Employees and Founders
This is often the part people care about most, and it varies widely:
Retention Packages — Key employees are frequently offered bonuses or accelerated vesting to stay for a defined period (commonly 1–4 years).
Earnouts — Founders may receive additional payment tied to hitting post-acquisition milestones — revenue targets, product launches, or retention goals.
Layoffs — Redundant roles (especially in sales, marketing, and support) are often cut once the acquirer's existing teams absorb those functions.
Product Sunset — If the deal was acquihire-driven, the original product is frequently discontinued within 12–18 months.
The CODEW Lens: Retention packages are a signal. The length and size of the retention package tell you how badly the buyer wants those specific people to stay — and how much the deal depends on them.
Common Deal Structures in Tech M&A
All-Cash
How it works: Buyer pays entirely in cash at closing.
When it's used: Smaller deals, or when the buyer has strong cash reserves.
All-Stock
How it works: Sellers receive the acquirer's equity.
When it's used: Large strategic mergers, tax-efficient for sellers.
Cash + Stock
How it works: Blend of both.
When it's used: Most common structure for mid-to-large deals.
Earnout
How it works: Portion of payment tied to future performance.
When it's used: Deals with uncertain near-term revenue or high founder dependency.
The CODEW Lens: Earnouts are a mechanism for bridging the gap between what the buyer will pay today and what the seller believes the business is worth tomorrow. They transfer risk from the buyer to the seller.
Why This Matters If You're Not a Dealmaker
Even if you're not negotiating M&A deals yourself, understanding this process helps you read the news more critically:
A high headline valuation with a heavy earnout component is a very different outcome than an all-cash deal.
Regulatory scrutiny on a deal often signals how the acquirer's market power is being perceived, not just the deal itself.
Rapid product shutdowns after acquisition are usually a sign the deal was acquihire-driven, not product-driven — worth knowing before you build on a startup's platform.
Understanding the mechanics of tech acquisitions turns headlines into signals. The deal tells you what the buyer wanted. The structure tells you what they were willing to pay for it. The integration tells you whether it worked.
Tech Acquisition Process Checklist
Before a tech acquisition closes, every deal generally moves through these phases:
☐ Sourcing and initial contact
☐ NDA signed
☐ Strategic fit discussion
☐ Letter of Intent (LOI) / Term Sheet issued
☐ Due diligence — financial, legal, technical, security
☐ Valuation and deal structure negotiated
☐ Definitive purchase agreement drafted
☐ Regulatory review (if required)
☐ Closing conditions satisfied
☐ Ownership transfer
☐ Integration, independent operation, or wind-down
Deals can die at any stage — most commonly during due diligence or regulatory review.
The CODEW Stat
8 phases · 4 deal structures · 4 outcomes Every tech acquisition moves through eight phases — from sourcing to integration. Deals use one of four common structures: all-cash, all-stock, cash + stock, or earnout. And the acquired company ends up in one of four states: integrated, independent, partially absorbed, or wound down. The headline is the number. The process is the story.
No comments: