Strategic M&A from the acquirer’s perspective

Start relationships long before any intent to sell.

80 % of Adobe’s conversations begin with simple intros or coffee chats; only 20 % are reactive inbound driven by competitive interest or auction processes.

Why: Trust and context accumulate over time, making later strategic alignment and valuation discussions smoother and more informed.

"it's very relationship oriented... oftentimes it's as simple as that. We get introduced... not looking for funding, not looking to sell. But we'd love to grab coffee and just talk about what we're doing."

Treat early meetings as mutual diligence, not sales pitches.

Entrepreneurs should use early contact to assess whether Adobe can accelerate their vision and whether they want to work with the people inside.

Why: The eventual success of the acquisition depends on post-close collaboration; early cultural fit checks reduce later integration risk.

"is it a place where you think your vision can not just sort of go and get parked but hopefully can be accelerated... are they the type of people that you want to work with?"

Use a five-dimension adjacency test to quantify strategic risk.

Adobe scores deals by how many of customer, channel, geography, business model, and product differ from the core; >2 steps drops success odds to ~10 %.

Why: Disciplined adjacency mapping prevents undisciplined diversification and focuses capital on moves with highest probability of payoff.

"once you change one of those five things, you're like a one-step adjacency further from the core... once you got out like three or four of those things changed, you dropped off to like 10 percent chance of success."

Walk away from financially attractive deals if culture mis-aligns.

Adobe has passed on billion-dollar+ targets when the team or ethos felt incompatible.

Why: Execution, not strategy, creates value; misaligned cultures erode execution and destroy long-term returns.

"we've walked away from extremely large deals north of a billion dollar because we didn't feel like the culture fit was there."

Make Corp Dev the entrepreneur’s concierge, not gatekeeper.

Corp Dev guides navigation of the 15,000-person company, frames the story for execs, and protects the startup from bureaucratic overload.

Why: Reduces friction, speeds trust-building, and ensures the startup’s narrative is accurately translated to decision-makers.

"we oftentimes act as sort of a concierge into this wildly complex 15,000 person company... treat the corp dev person and the business owner as people that are your partners to figure out whether this makes sense."

Sequence conversations: business owner first, senior execs later.

Premature CEO meetings can kill momentum if the exec lacks context; Corp Dev and the product GM must frame value before escalation.

Why: Prevents “one-and-done” rejections and keeps the process collaborative rather than adversarial.

"if you get in front of them too early... they might take one meeting and be like, eh, I was not interested. Then it creates this uphill battle."

View LOI as the moment of truth; include no-shop and 45-60 day exclusivity.

After the LOI, diligence circles expand, legal drafts appear, and momentum shifts toward close; exclusivity protects both sides’ investment of time.

Why: Establishes clear expectations and mirrors venture term-sheet discipline, reducing re-trading risk.

"the biggest milestone... is kind of the LOI or the term sheet... almost always includes a no-shop provision of some period of time."

Embed integration planning inside Corp Dev from day one.

Adobe’s Corp Dev team owns integration, retention package design, and quarterly post-mortems for two years post-close.

Why: Ensures dealmakers remain accountable for value realization and prevents “throw-it-over-the-wall” behavior.

"our team is responsible for... the M&A integration function... I always myself have thought of the job as a growth job... not kind of a deal function."