Engineering brief
The M&A route to AI deployment: buy the customer, own the outcome
At a glance
The brief is enough
- Relevance
- Practical value
- Radar
- Time horizon
- This year
- Warnings
- High hype
- Vendor pitch
Long Lake is spending $7.5B to buy services firms and deploy AI from the inside. The pitch is coherent, but the talk offers no measured P&L results, so treat the compounding story as a thesis, not evidence.
If M&A becomes an AI distribution model, enterprises may face competitors who own the outcome instead of selling tools.
Watch if you are evaluating how to get AI into a services-heavy business or wondering whether M&A is part of your strategy.
Summary
The acquisition play. Prathik Naidu, founding partner at Long Lake, argues the hardest part of enterprise AI is the vendor-customer wall, not the model. Security reviews, legacy integrations, training, pricing, and value capture drain outside vendors. His answer is to buy the customer. Long Lake, an applied AI holding company with $7.5B from Elad Gil, General Catalyst, Alpha Wave, and D1, has acquired 40 services businesses and embeds AI inside them. Its $6.3B Amex GBT take-private shows the scale.
Why services. Naidu contrasts software and services. Software keeps about $80 of every $100 of new revenue; services keeps about $20 because delivery and overhead scale with headcount. AI breaks that link, so labor costs stop rising in lockstep with revenue. The examples are concrete: an HOA community manager can run only so many associations; an architect, only so many hospitals. AI is meant to give these businesses software-like margins, instead of growth that only scales with headcount.
Ownership effects. Buying the firm instead of selling to it gives the AI team direct access to people with decades of judgment, real tasks and edge cases for evaluation, aligned incentives, and customer trust. Naidu calls this a compounding flywheel. The argument is coherent, but it renames the classic M&A integration problem. Tacit knowledge and internal politics do not disappear; ownership means absorbing them into the P&L instead of negotiating across a contract.
The J-curve. The talk describes a familiar pattern: invest in platform, workflows, and training; hit a valley of hard work; then usage climbs and capacity appears. The next step is the one most AI projects skip. Capacity must be converted into growth, client or employee NPS, and higher revenue per employee. That is where management teams and incentives matter. None of this is measured for the 40 companies.
Missing evidence. No deployment timelines, revenue per employee changes, client retention numbers, or margin figures appear in the talk. The most cited number is the fund's own capital. That makes this an investment thesis, not an engineering case study. The J-curve is promised, not shown. Engineering leaders should treat the compounding language as a hypothesis and ask for the same evidence they would demand from any vendor.
What to watch. The real signal is market structure. If M&A becomes a credible way to deploy AI at scale, enterprises will face competitors that own the outcome end to end rather than vendors that sell a tool. Teams should watch whether Long Lake's portfolio publishes comparable results. If it does, the buy-versus-build decision around AI changes. If it does not, this remains a capital story.
My take
The ownership thesis is logical, and I think it is genuinely different from the usual agent pitch. Buying the firm removes the two walls that kill most enterprise AI projects: access to tacit knowledge and the incentive to drive adoption. But the talk overreaches when it turns a structural advantage into a compounding guarantee. Long Lake names 40 businesses and one huge deal, yet gives no deployment time, no revenue per employee change, no client retention numbers. A J-curve is not evidence.
I would treat this as an investment strategy more than an engineering playbook. For teams that cannot buy the customer, the transferable lesson is smaller: find the people with twenty years of judgment and let them define what good looks like before you build anything.
What to do with this
- Map the workflow areas where tacit knowledge lives in your organization before starting any AI project, and name the experts who hold it.
- Ask your finance team to model what a 20% and 40% labor-cost reduction would do to service margins before commissioning new AI work.
- Spend one session with a portfolio company or acquisition target to see whether ownership changes adoption incentives more than product features do.
Watch the video
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
Model Choice Barely Matters: Fix Engineering Culture, Not AI Tools
AI model choice explains under 1% of developer output variance, per Jellyfish's 50,000-engineer dataset. The levers leaders control matter more.
Stop evaluating models. Start evaluating the risk around them.
1,368 AI failures later: deployment controls, not model quality, determine real-world harm. Failure-driven evals follow. No production proof yet.
Testing AI Agents: Plant the Defect, Then Find It
No benchmark for your AI agent? Air Canada generated 275 contracts with planted violations, cut expert grading from weekly to daily, and warns against LLM…
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.