SpaceX looked at an AI capability gap last week and reached for a checkbook. That instinct is everywhere right now, and it is costing founders more than they realize.

Bloomberg reported this week that SpaceX attempted to acquire Cursor, an AI coding startup, in a deal that would have valued it at $60 billion. Whether or not that deal closes, what it reveals is worth sitting with. A company with serious engineering resources, serious internal talent, and a founder-driven culture saw a capability it wanted and moved to buy it rather than build it.

The acquisition is not the problem. The pressure is.

Boards are pushing hard on AI right now. That is not surprising and it is not entirely wrong. AI is genuinely reshaping how work gets done, how fast teams can move, how much leverage a small group of people can create. The pressure to adopt, integrate, and demonstrate AI capability is real, and founders are feeling it from every direction.

But here is what is actually happening in most of those boardrooms. The conversation sounds like it is about AI. What it is really exposing is something that was already there before any of this became urgent. The board is asking why the business cannot move faster. Why decisions keep stacking up. Why the team cannot absorb new tools and run with them independently. Why every significant capability shift seems to require either a massive hire or a massive acquisition.

Those are not AI questions. Those are leadership structure questions. And they have been sitting there, unanswered, for a while.

What you are actually solving when you buy instead of build

Acquisitions make sense in specific situations: when the capability genuinely does not exist internally, when the market window is narrow, when you are buying a customer base or a distribution channel that would take years to replicate. Those are real justifications.

But a lot of what is being framed as AI acquisition right now is something else. It is founders trying to solve a permission problem by bringing in an external answer. The logic goes: if we have the right tool, the right platform, the right acquisition, then the team can finally move without needing me in every loop.

That does not work. The tool lands in an organization where people still do not feel equipped to make judgment calls, still do not have clear enough scope to act independently, still route everything upward because that is the pattern that exists. A $60 billion acquisition does not fix that. A $60 software subscription does not fix it either.

The permission problem is what you actually need to solve

What most founders are sitting on, without necessarily naming it this way, is a system where their team needs permission to act. Not because the team is incapable; usually the opposite. The team has been conditioned over time to wait, to check in, to defer. Sometimes because the founder moved fast and made unilateral calls early on. Sometimes because there were no clear frameworks for what decisions live at what level. Sometimes because being wrong once had visible consequences and being cautious never did.

The result is a business that is structurally dependent on the founder's bandwidth. Every time the environment changes, whether that is a new technology wave, a new competitive pressure, or a new board mandate, the team waits for the founder to interpret it and tell them what to do. That is not a team problem. That is a leadership architecture problem.

It shows up most clearly when something moves fast. AI is moving fast. So the permission problem is showing up everywhere, all at once, and boards are watching it happen in real time.

What actually needs to change

Before you go looking for something to acquire, run a different audit. Ask yourself three honest questions about how your team operates.

  • When something new lands on their desk, do they have enough context about your priorities to make a reasonable call without you? Not a perfect call. A reasonable one.
  • When they make a call and it is wrong, is the response a conversation or a correction? One builds confidence. The other builds hesitation.
  • Do they know what they are optimizing for well enough to evaluate a new tool on their own terms, or do they need you to tell them whether it matters?

If the honest answers are uncomfortable, no acquisition changes that. What changes it is building the internal scaffolding that lets people lead in their own lanes: clear decision rights, documented thinking on what the business is actually trying to accomplish and why, and a culture where moving and being slightly wrong is more valued than waiting and being safe.

That scaffolding is also what allows AI tools to actually get used well. A team that cannot make independent judgment calls will not know how to evaluate, adopt, or iterate on AI capabilities without constant hand-holding. You will spend the acquisition budget and still be in the same meeting six months from now wondering why nothing is moving.

The real cost of waiting

Every month your team waits for permission instead of acting is a month your competitors who have solved this are compounding faster. They are iterating on AI tools while your team is still waiting to find out if AI is a priority. They are absorbing new capabilities into existing workflows while yours are asking what the workflow should even be.

The board pressure you are feeling is not going to ease. It is going to get louder. And the more you respond to it with external solutions, the longer you delay confronting the internal one. The founders who move through this moment well are not the ones who find the best acquisition target. They are the ones who stop being the ceiling.

If you want to work through what that internal architecture looks like for your business, reach out to us at A&A. We work with founders who are ready to build something that moves without them.

Source: bloomberg.com