SpaceX’s Cursor Buy is an AI Compute Play

Kison Patel
Founder of M&A Science | 10 years, 400+ practitioner interviews

In mid-June, SpaceX agreed to buy Anysphere, the company behind the Cursor coding tool, in an all-stock deal that values Cursor at $60 billion. The companies expect the deal to close in the third quarter, subject to regulatory approvals.

‍

‍

The two had been circling each other for a while. Back in April, SpaceX publicly floated two options: acquire Cursor outright, or pay $10 billion for collaborative work. By then, Cursor had already used tens of thousands of xAI chips to train its newest model. The June agreement settled which of those paths they would take.

Why a rocket company wants a coding tool

At first glance, SpaceX buying a software tool for developers looks like an odd fit. It makes more sense when you look at what each side brings.

SpaceX has access to enormous amounts of computing power. Cursor has a product that developers pay for, a large and loyal user base, and a team that knows how to turn computing power into features people actually use. In AI, those two things need each other. Models get better with more compute, and compute is only valuable if there’s a product that turns it into something customers want.

So while the headline says “SpaceX buys a coding tool,” I’d describe this as a compute deal. SpaceX is buying a way to put its infrastructure to work, and Cursor is getting the resources to compete with much larger AI companies.

Working together before buying

One detail I like about this deal is the order in which things happened. Cursor was already training on xAI’s chips before anyone signed a merger agreement. That kind of hands-on relationship tells both sides far more about how the other operates than any data room can: how decisions get made, how fast teams move, and whether the people actually work well together.

More acquirers should consider this path, especially in technology. A commercial partnership, a joint project or a licensing deal can be a lower-risk way to test the fit before committing billions. If it works, the acquisition becomes a confirmation rather than a leap of faith. If it doesn’t, you’ve learned something important for a fraction of the cost.

The risk of slowing them down

What SpaceX is really paying for is speed. Cursor competes in a market where products change month to month and new competitors appear constantly. If the integration slows the team down, the $60 billion stops making sense.

The challenge is that large acquirers tend to add process almost by reflex. A new approval step, a new security review, a new reporting line, a new set of planning meetings. Each of those changes is reasonable on its own, and each might be required by the larger company’s policies. But stack enough of them on top of a small, fast-moving team and you can turn a group that ships every week into one that ships every quarter.

What I’d put in the integration plan

For a deal like this, I’d start the integration plan with a list of things not to change, and then work outward from there.

First, be explicit about decision rights. The product team should know which decisions it still owns, from roadmap priorities to release timing, and which now need approval from the parent company.

Second, integrate where there’s clear value. In this case, that’s access to computing power and the shared infrastructure behind it. Other areas, such as HR systems or internal tools, can usually wait.

Third, plan retention for the builders before close. The engineers and researchers who built Cursor are a big part of why it’s worth $60 billion. They also have plenty of other options, so their incentives and their role in the combined company need to be clear early.

Tying the deal back to strategy

Baljit Singh, a corporate development leader, made a point in an M&A Science interview that applies here: “M&A is not something that is done artificially.” Every deal should tie back to the company’s overall strategy. In this case, the strategic logic is clear: SpaceX wants its compute to power products people use. The integration plan should follow that logic too, focusing on what supports the strategy and leaving the rest alone.

The fastest way to lose value in an AI acquisition is to treat it like any other integration. When you buy a team for its speed, the integration plan should be built to protect it.

Sources

Definition
Pros
Cons
No items found.