Win M&A Deals

Training target CEO mind... (~10 min)

Based on Lisa's values, priorities, and decision-making:
Lisa's Bidder Ranking:
PREFERRED: Bidder A (Us - Strategic Buyer)
ACCEPTABLE: Bidder B (PE Firm)
WILL REJECT: Bidder C (Competitor)
Why Lisa Prefers Bidder A (Despite Lower Price):
Reason 1: Team Retention is Her Top Priority
- Lisa built this company with her team for 10 years
- Feels deep responsibility to 200 employees
- $30M retention pool shows we care about people
- PE's $10M is minimal, Competitor has none
Her thought: "I can't sell my team out for $30M more.
These people believed in me. Bidder A will take care of them."
Reason 2: Product Legacy Matters
- DataFlow is her life's work
- Wants product to thrive long-term, not be killed
- Bidder A: keeps brand independent (preserves legacy)
- Competitor: kills brand, makes it a feature (unacceptable)
Her thought: "I didn't spend 10 years building this to
watch it disappear into someone's feature set."
Reason 3: Personal Role and Respect
- GM role reporting to CEO = real authority
- SVP role at Competitor = being "managed out"
- Wants to lead, not be window dressing
Her thought: "GM with real authority is better than
fake SVP title with no team."
Reason 4: Cultural Fit
- Has met our CEO, respects leadership
- Trusts our vision and values
- Competitor has reputation for harsh integration
- PE is fine but transactional
Her thought: "I've talked to their former founders.
The ones who sold to Competitor all regret it."
Why She'd Accept PE (Bidder B) as Backup:
- $30M more in cash is meaningful
- She stays CEO = respect and control
- But: worried PE will cut her team after 12 months
- And: no strategic synergies, just financial engineering
Her thought: "PE is fine. More money, I stay CEO. But
it feels mercenary. And they'll cut my team eventually."
Why She'll Reject Competitor (Bidder C):
DEALBREAKERS:
✗ Product becomes feature (kills her legacy)
✗ Brand disappears (unacceptable)
✗ Team becomes redundant (she won't do this to them)
✗ Fake SVP role (no real authority)
Her thought: "Even at $500M, I won't destroy what we built.
My team will hate me. The product will die. Not worth it."
What Wins Lisa (How We Beat PE's Higher Price):
Current situation:
- We're at $450M, PE at $480M ($30M gap)
- Lisa prefers us but has fiduciary duty to board
- Board will push her to take PE's higher offer
How to win:
Option 1: Match PE on Economics
- Increase to $480M ($320M cash + $160M stock)
- Cost to us: $30M more
- Result: Lisa has no reason to pick PE, chooses us
Option 2: Address Her True Priorities
- Stay at $450M but enhance team retention to $40M
- Commit to 3-year product independence (in writing)
- Give Lisa real 3-year GM role with board seat
- Cost to us: $10M more retention
- Result: Lisa champions us to board despite PE's higher price
Option 3: Get Her to Champion Us
- Go to $470M (split the difference)
- Enhance retention to $35M
- Add board seat for Lisa
- Formal product independence commitment
- Cost to us: $20M + board seat
- Result: Lisa becomes our advocate to board
What Lisa Will Say to Her Board:
If we stay at $450M:
"PE is offering $30M more. I prefer Bidder A for team
and product reasons, but we have fiduciary duty. I
recommend we take PE unless Bidder A improves."
If we go to $470M + better terms:
"Bidder A is only $10M behind PE but treats our team
better, keeps our product independent, and gives us
board seat. The strategic value is worth more than
$10M. I strongly recommend Bidder A."
Bottom Line - How to Win:
✓ Close the price gap to $10-20M (not $30M)
✓ Enhance team retention (show we care about people)
✓ Formalize product independence commitment
✓ Give Lisa real role (GM + board seat = respect)
✓ Emphasize strategic value vs. PE's financial engineering
Don't try to win at $450M. You need $470M+ or exceptional terms.
At $470M with strong retention and product commitment,
Lisa will champion us and we'll win despite PE's higher price.

Training 3 executive minds... (~10 min each)

ALEX KIM (CTO) - Response:
Will Alex stay? NO - 80% likelihood he leaves
Why he'll leave:
Dealbreaker 1: Reporting Structure
- Alex is CTO, reports to CEO today
- Reporting to VP Engineering = demotion
- He's 15 years experience, this is disrespectful
- Feels like being managed out
His thought: "I built this tech org from 0 to 50 people.
Now I report to someone junior to me? I'm being pushed out."
Dealbreaker 2: Location Requirement
- Alex has family in Austin (kids in school)
- Wife has job she loves
- SF move = family disruption
- No remote = inflexible
His thought: "I'm not uprooting my family for a demotion.
This is a non-starter."
Concern 3: Tech Stack Migration
- 12-month migration is aggressive
- Team will burn out
- Will cause attrition in his org
- Feels like we don't trust their tech decisions
Retention Package: INSUFFICIENT
- $500K over 2 years = $250K/year
- Alex makes $300K base + equity worth $200K/year
- Retention is only 50% of his current comp
- Not enough to offset career regression
When Alex will leave:
- Month 3-6 post-close (after retention cliff)
- Will start interviewing immediately
- Has strong network, will get CTO offers easily
What would make Alex stay:
✓ Reports directly to CEO (not VP Eng)
✓ Remote work from Austin (come to SF 1 week/month)
✓ Real CTO role with autonomy
✓ $1M retention (2-year vest) + equity refresh
✓ Longer tech migration timeline (18-24 months)
---
MARIA RODRIGUEZ (VP Engineering) - Response:
Will Maria stay? MAYBE - 50/50
Her concerns:
Concern 1: Career Growth
- VP Eng today, reports to CTO
- After: Reports to your VP Eng, less authority
- Lateral move at best, maybe regression
- Where's her path to CTO?
Her thought: "I'm VP Eng at a successful company. What's
my growth path here? Feels like a lateral move."
Concern 2: Team Retention
- Worried about her team leaving
- Tech migration will cause attrition
- Office move will lose remote engineers
- She'll be blamed for attrition
Her thought: "If my team leaves, I'll look bad and get
blamed. This integration plan sets me up to fail."
Concern 3: Culture Clash
- DataFlow has strong engineering culture
- Worried about losing autonomy
- Process changes feel like micromanagement
Retention: ACCEPTABLE BUT NOT EXCITING
- $500K is decent
- But career concerns outweigh money
What makes Maria stay:
✓ Clear path to CTO or equivalent
✓ Autonomy to retain her team (flexible on location)
✓ Phased integration (prove value before big changes)
✓ $750K retention + equity refresh
✓ Success metrics tied to outcomes, not processes
What makes Maria leave:
✗ No career growth path
✗ Her team has mass exodus (she'll follow)
✗ Micromanagement and loss of autonomy
Timeline: Will decide in first 6 months
---
JAMES LIU (VP Product) - Response:
Will James stay? YES - 70% likelihood
Why James will likely stay:
Positive 1: Product Opportunity
- Excited about bigger product scope
- Access to your customer base (10x larger)
- More resources and budget
- This is career growth for him
His thought: "This is my chance to work on product at
scale. I've been waiting for this opportunity."
Positive 2: Retention Package
- $500K is meaningful to him
- Early in career (5 years experience)
- Needs financial security
His concerns (but not dealbreakers):
Concern 1: Reporting Structure
- Reports to CEO today
- Will report to your VP Product
- Ego hit but accepts it's normal post-M&A
Concern 2: Product Vision
- Wants to preserve DataFlow product identity
- Worried about becoming feature team
- Needs commitment to product investment
Concern 3: Location
- Prefers remote but willing to relocate
- Young, no kids, flexible
- SF is expensive but manageable
What makes James thrive:
✓ Clear product roadmap (DataFlow stays independent product)
✓ Access to your resources and customers
✓ Mentorship from your VP Product (sees it as learning)
✓ Commitment to product investment (not just integration)
What would make James leave:
✗ DataFlow becomes feature, not product
✗ No resources or investment post-close
✗ Toxic management from your VP Product
Timeline: Will stay 2+ years if product thrives
---
INTEGRATION RECOMMENDATIONS:
CRITICAL: You will lose Alex (CTO) with this plan
- 80% chance he leaves in 3-6 months
- This is your biggest retention risk
- Losing CTO = cascading attrition
MODERATE RISK: Maria (VP Eng) is 50/50
- Needs career path and autonomy
- Will leave if her team has mass exodus
LIKELY STAYS: James (VP Product) is excited
- Product opportunity outweighs concerns
- Early career, flexible, growth-minded
Revised Integration Plan:
For Alex (CTO) - MUST CHANGE:
✓ Direct report to CEO (not VP Eng)
✓ Remote from Austin (1 week/month in SF)
✓ Real CTO role with autonomy over tech migration
✓ $1M retention (2-year vest)
✓ 18-24 month tech migration (not 12 months)
For Maria (VP Eng) - IMPROVE:
✓ Path to CTO when Alex exits (give her 2-year runway)
✓ Autonomy to retain her team (flexible policies)
✓ $750K retention + equity refresh
✓ Success metrics on outcomes, not compliance
For James (VP Product) - MAINTAIN:
✓ Current plan is fine
✓ Add: formal product independence commitment
✓ Add: quarterly investment reviews (show commitment)
Cost: $250K more retention + remote policy flexibility
Result: Retain all 3 key executives, protect $450M deal value