It’s been a while since we launched Above Trends, Beyond Insights. What began as an experiment in editorial positioning has gradually become a method: looking past headlines to understand how technology actually behaves inside organisations.

The Claude vs ChatGPT moment is about consent

Over the last couple of weeks, a niche debate turned into something mainstream:

On February 27, Anthropic’s CEO publicly pushed back against what he described as a Pentagon request for looser access and fewer safeguards;
On February 28, OpenAI’s CEO announced an agreement to deploy its models inside classified US military networks;
By March 2, the backlash had a name, “Cancel ChatGPT” or “QuitGPT”, and the narrative shifted from product preference to political pressure. Over the next days, major outlets amplified the boycott framing, calling for users to cancel subscriptions as a form of consumer leverage.

At surface level, people are swapping tools, but a deeper read shows something else happening: public consent is being renegotiated.

When a general-purpose assistant becomes entangled with defense and security infrastructure, users start asking a question that sounds simple and lands heavy:

“Did I sign up for this?”

That is why this wave feels different from previous tech controversies. It is not only about privacy or model quality. It is about moral distance. People want a buffer between their daily workflows and systems that can scale surveillance, automate targeting, or accelerate conflict dynamics, even indirectly.

This is where the Claude vs ChatGPT “discourse” becomes a proxy war for a bigger cultural shift: a public increasingly exhausted by permanent conflict framing, constant escalation rhetoric, and the normalization of militarized tech. The boycott energy reads like a refusal to keep funding the next step in that normalization, especially when the switch cost is low and alternatives exist.

Even the metrics are being used as persuasion. NDTV reports claims of over 2.5 million boycott pledges tied to the QuitGPT website and points to a spike in uninstalls following the Pentagon deal. Euronews reports the movement claiming over 1.5 million actions of different kinds (cancellations, sharing, signups). Whether those numbers are perfectly precise matters less than what they reveal: the boycott is being narrated as a democratic act, a way to reassert agency in a market where “defaults” quietly become infrastructure.

My take is blunt: the real product is governance. If an AI assistant is becoming part of contested state power, “which chatbot is better” turns into “which governance model do I accept”, and that decision has ethical weight.

TREND TRACKER

The return of industrial policy in tech

For years, tech supply chains were optimised for efficiency. Now they are being redesigned around sovereignty.

In the US, the CHIPS and Science Act channels $52.7B over five years into semiconductor manufacturing, R&D, and workforce programs.
In Europe, the European Chips Act explicitly aims to boost resilience and “double” the EU’s global chip market share to 20%.

This shift is spreading beyond chips. In late February and early March 2026, the Commission’s push for “Buy European/Buy EU” procurement rules brought industrial policy back into the headlines, framing public spending as a tool to reshape strategic supply chains.

Want to learn more?

• NIST, CHIPS for America fact sheet

• European Chips Act

• The EU wants to buy European. But can it? - Euronews

• The European Commission proposes ‘Buy EU’ plan to compete against China - The Guardian

QUICK INSIGHT

The paradox of digital infrastructure: a 5-step approach to de-risk your stack

Digital feels intangible, yet it depends on physical chokepoints: cables, data centres, grids, and chips. Here’s a short method you can run with IT + procurement + risk.

1) Map what is physical (not what is branded)
List cloud regions, data-centre locations, network paths, and critical hardware dependencies for your top services.

2) Identify your real chokepoints
Pick the top 3 “single points of failure” that could stop operations: one region, one provider, one connectivity dependency, one chip class.

3) Classify workloads by portability
Portable (move fast), semi-portable (needs refactoring), anchored (legacy, compliance, hardware-tied). Be strict.

4) Define a fallback per critical service
For each service, write: minimum viable alternative, switch trigger, owner, and a degraded mode that keeps the business alive.

5) Test one switch path
Run a tabletop exercise or a controlled failover. If it’s never rehearsed, it’s not a fallback, it’s hope.

WHO IS BABINI MAZZARI

Our Value Proposition

Babini Mazzari is the strategic IT partner for European companies looking to navigate digital transformation in a structured, pragmatic, and sustainable way.
We don’t just deliver technical solutions - we work as an extension of your internal team, helping you integrate systems, optimize processes, and lead change with clarity and competence.

Our approach is built on listening, transparency, and a strong results-driven culture. Whether you're scaling, modernizing, or rethinking your operating model, we support every client with the right tools, clear methodology, and long-term vision.
Above Technology. Beyond Solutions.

📎 [Our services]
📎 [Our Manifesto]