The Extinction Risk Debate Is a Distraction for Operators

The AI existential risk debate matters enormously, just not for the reason most founders think it does. Burning your own limited attention on it instead of practical implementation is wasting a real competitive window.

Key takeaways

Existential risk is a genuine policy question, but it’s not an operator’s job to solve it
Founders who disengage from AI out of philosophical caution fall behind quietly
Practical governance inside your own company beats abstract debate every time
Frontier labs and regulators are the right owners of the extinction risk conversation
Attention spent on implementation discipline compounds; dread doesn’t

I’ve founded and exited two companies, Obby and Baluu, and I now run FirstMotion while advising founders and leadership teams through VAQA on how they actually implement AI inside their businesses. I say this a lot in board conversations: the founders wasting time debating whether AI will end civilisation are usually the same ones who haven’t set a basic AI usage policy for their own team yet. This piece is about why that trade off matters more than it sounds.

Why this debate is real, and why it’s not yours to solve

I want to be clear before saying anything critical: the AI safety and existential risk debate is not nonsense. Serious researchers, including people inside Anthropic and OpenAI, take frontier model risk seriously enough to build entire safety and alignment teams around it. That’s a legitimate, important conversation.

It’s a conversation for the labs building frontier models, and for the policymakers and regulators whose job is to set the rules those labs operate under. It is not, in any practical sense, a conversation that changes what a founder running a 30 person company should do on a Monday morning.

I think a lot of smart, well meaning operators conflate “this is an important societal question” with “this is a question I need to have a personal position on before I can act.” Those are different things, and confusing them costs real time.

The cost of philosophical disengagement

Every hour a founder spends genuinely anxious about long run existential risk is an hour not spent figuring out how their own team should actually use these tools today. That trade off is easy to miss because it doesn’t feel like a cost in the moment, it feels like thoughtfulness.

But it is a cost, and a compounding one. While one founder is working through where they land on AI risk philosophically, a competitor is quietly:

Rolling out clear internal guidelines for what AI tools staff can and can’t use
Redesigning workflows around what AI can already do reliably today
Building governance that manages real, near term risks like data handling and accuracy
Shipping product improvements that use AI capability competitors are still debating

None of that requires resolving the extinction risk question. It requires the much more boring discipline of practical implementation.

Practical governance beats philosophical hand wringing

Here’s the distinction I try to get founders to sit with. There’s a real difference between existential risk, the very long run, civilisation scale question, and operational risk, the near term, entirely manageable question of how your own company uses AI responsibly.

Operational AI risk is genuinely your job, and it’s far more tractable than the philosophical version. It includes things like:

Making sure sensitive customer data isn’t fed into tools without proper controls
Setting clear expectations for when AI output needs human review before it ships
Training your team on where these tools are reliable and where they still fail
Building accountability so nobody assumes “the AI did it” is an acceptable excuse

That’s the governance that actually protects a business today. It’s unglamorous compared to the extinction risk debate, but it’s the version you can actually act on this week, and it’s the version I help founders build through VAQA’s AI Implementation advisory work.

Where the attention actually pays off

I’ve seen this pattern repeatedly through FirstMotion’s work with B2B SaaS companies. The businesses pulling ahead aren’t the ones with the most sophisticated position on AI safety philosophy, they’re the ones that quietly built implementation discipline while others were still debating.

That discipline compounds. A team that’s spent six months genuinely learning where AI tools help and where they don’t builds institutional knowledge a competitor can’t shortcut. A founder who’s spent that same six months worried about long run civilisational risk, without changing anything operationally, has nothing to show for the time either way.

I’m not asking anyone to stop caring about the big picture question. I’m asking founders to be honest about which conversations actually move their business forward, and to spend their scarce attention accordingly.

A framework for where your attention should go

If you’re a founder or leadership team member trying to sort this out for yourself, I’d suggest a simple test before spending real time on an AI related question: can I actually act on the answer this quarter?

Existential risk debates rarely pass that test for an individual operator; you can have an opinion, but you can’t meaningfully change the outcome through your own actions. Implementation questions almost always pass it. Which tools should my team use, what should we automate first, how do we govern data handling, those are all questions where your attention directly produces a better outcome.

That test alone reallocates a surprising amount of time once founders actually apply it honestly.

Engagement, not disengagement, just pointed the right way

I want to be careful not to overcorrect into telling founders to ignore AI risk entirely, because that’s not my argument either. Disengaging from the conversation completely, treating AI as just another tool with no downside, is its own kind of mistake.

The point is precision about which risks are yours to manage. Existential risk belongs to the labs and the regulators. Operational risk, the version that actually determines whether your team uses these tools safely and effectively, belongs to you, starting today.

Get that allocation right and you free up real attention for the part of this transition you can actually influence, which is exactly where the competitive window I keep coming back to actually sits.

Where I can help with the practical side

This is precisely the ground I work on with founders through VAQA’s AI Implementation pillar, building the practical governance and rollout discipline that actually protects a business and speeds it up, rather than getting stuck on questions no individual operator can resolve alone. If you want a clear eyed look at where your own AI implementation gaps are, get in touch, or read more about what I advise on and my background.

Frequently Asked Questions

Is Tom saying AI existential risk isn’t a real concern?

No, it’s a legitimate and serious debate, taken seriously by researchers inside major labs and by policymakers working on AI regulation. The point is that it’s the wrong place for an individual founder to spend limited strategic attention, not that the concern itself is invalid.

What should a founder actually focus on instead?

Practical, near term operational governance: how your team uses AI tools, how sensitive data is handled, and where human review is required before AI output ships. Those are questions a founder can act on directly and see results from within a single quarter.

Does VAQA offer help specifically with AI governance and rollout?

Yes, this sits under my AI Implementation advisory pillar at VAQA, where I work with founders and leadership teams on building practical usage policies, governance, and rollout plans. It’s a distinct, more actionable conversation than the broader industry debate about AI safety.

How is this different from what FirstMotion does?

FirstMotion focuses specifically on AI search and GEO for B2B SaaS companies, helping brands show up accurately in AI driven research and answers. VAQA’s AI Implementation advisory work is broader, covering how a company actually adopts and governs AI tools across its operations.

Should leadership teams ignore AI safety news entirely?

Not entirely, staying broadly informed is reasonable, but I’d draw a hard line against letting that awareness turn into operational paralysis or prolonged anxiety that displaces practical work. Read enough to stay informed, then redirect the bulk of your attention to what you can actually implement.

What’s the biggest mistake Tom sees founders make with AI right now?

Treating AI adoption as something to resolve philosophically before acting, rather than something to govern practically while moving. The founders who wait for certainty, on either the safety debate or the capability curve, consistently lose ground to those building implementation discipline in the meantime.

Tom Batting is a Forbes 30 Under 30 entrepreneur, founder of Obby and Baluu, and founder of FirstMotion. He advises founders and leadership teams through VAQA on Board Advisory, Growth, Go-to-Market, AI Implementation, Operational Efficiency, and Finance and Fundraising.