I Was That CEO

When I read Mark Cuban’s tweet this morning, my first reaction wasn’t “he’s right.”

It was “I lived that.”

Cuban wrote something that should make every CEO with running systems uncomfortable:

“Every entrepreneur that knows how to use AI is trying to find ways to build AI native companies that completely displace incumbents. For the incumbents, it’s the ‘Innovator’s AI Dilemma’.”

He then offered what he called a “hint”: ask your AI models for the best path from where you are now to an AI-native version that achieves the same economics.

Good advice. Except for one thing.

Most CEOs can’t ask that question. They’re missing something more basic than the answer — they’re missing the map that makes the question possible.

Cuban Gave the Answer. But the Question Is the Hard Part.

“Ask your AI models for the best path to becoming AI-native.” Sounds straightforward. In practice, this question falls apart because it demands information almost nobody has organized.

You need a genuine map of what you actually have today. I’m talking about architecture, workflows, unit economics per process, technical dependencies — not the org chart or the board deck. Most companies I work with have a general sense of their systems, enough to run day-to-day operations but nowhere near enough to redesign from scratch.

You also need to answer a question that few directors face honestly: if you built your company today with agents, automation, and language models, what would it actually look like? What cost structure, what headcount, which processes would vanish? Most executives skip this step because the results are uncomfortable.

The part where everyone stalls — and I mean literally, the conversation dies — is modeling the transition with real numbers. Getting from your current operation to that blank-slate version requires a concrete plan: the costs, the sequencing so the business keeps running while you rebuild, the explicit risk tolerance from your board. Almost nobody has attempted this exercise because it forces you to confront the full scale of what “becoming AI-native” actually means.

I know this because I lived it. At Word Magic — the translation software company I co-founded at age 15 with my father — Google Translate didn’t beat us with better technology. It beat us by making translation free and instant while we kept shipping boxed software. We had a great product. The market had moved on, and we were too busy optimizing to notice.

Cuban is describing the exact dynamic that killed my first company. And most CEOs are in that same position today, telling themselves they still have time.

Everyone Agrees AI Matters. Almost Nobody Knows What to Do About It.

Ask any executive team whether AI will affect their business and you’ll get unanimous agreement. Ask them what their AI-native version would look like — with specific cost structures and headcount — and nobody has a real answer. That silence has a cause, and it’s not lack of interest or budget.

The numbers make this concrete. According to BCG, roughly 75% of global CEOs are the primary decision-makers on AI in their companies. Three out of four say AI will materially impact their business model. Yet fewer than 30% report measurable ROI from their AI investments. That gap tells you something specific: companies are spending money and building teams around AI while skipping the diagnostic work that would tell them where to aim.

A Harvard Business Review survey from early 2026 confirms what I hear in my own conversations with technology directors. Enthusiasm is everywhere. Budget exists. Some companies even set up an “AI committee.” But try getting them to describe their AI-native version in economic terms — cost per transaction, required headcount, which departments shrink — and you hit a wall. Nobody has a detailed map of current systems. Nobody has modeled what the transition would cost. They’re buying tools before drawing the blueprint.

BCG identified five barriers CEOs must clear to get real impact from AI. The first one is the most telling: executive teams don’t share a concrete definition of what “being an AI company” means for their specific business. I’ve been in those meetings. The CFO shows up with a spreadsheet where AI is a line item for cost savings. The CTO wants to talk about which tools to pilot next quarter. The CEO keeps saying “competitiveness” without anyone in the room knowing what that means operationally. They’re all answering different questions, and the meeting ends without a decision because nobody agreed on what they were deciding.

When the people around the table can’t even agree on what they’re trying to decide, the quality of the answer doesn’t matter much.

The Dual Lawsuit Paradox Proves There’s No Framework

Cuban describes a scenario that sounds absurd but is economically inevitable:

“You will know AI is having a huge impact on public companies when there are two types of lawsuits: shareholders that sue the company for tearing down the company and crushing the stock price — and shareholders that sue the company for NOT tearing down the company and crushing the stock price.”

Both lawsuits are valid. That’s the point.

If a CEO could walk into the boardroom with a real diagnostic — here’s what we have, here’s what the AI-native version would cost, here are the risks of moving versus staying — the conversation would be hard but informed. Instead, what most have is gut feeling, conflicting opinions, and a market that’s moving faster than their internal decision-making process.

I know that paralysis. I lived it. At Word Magic, we could see that something was changing. The signs were there. But while the product worked and customers kept paying, it was more comfortable to optimize what we had than to ask the uncomfortable question: what happens if all of this stops working?

Success makes you blind. You tell yourself “that doesn’t apply to my market,” “my customers are loyal,” “our product quality protects us.” And while you’re saying all that, someone is building the replacement from scratch.

If you ran a video rental business in 2005, you didn’t need anyone to explain Netflix. You knew. You just thought you had more time.

What “Ask Your AI” Actually Means

Cuban is right about the direction. But his advice needs grounding.

“Ask your AI models for the best path” isn’t a ChatGPT session. It’s a process that requires serious preparatory work most companies haven’t done.

I’ve spent over 35 years in technology and seen at least six major cycles: DOS to Windows, client-server to web, on-premise to cloud, waterfall to agile, web to mobile, and now AI replacing entire workflows. In every cycle, the companies that survived weren’t the ones with the biggest budgets. They were the ones that asked the uncomfortable question before the answer became obvious.

What Cuban calls “ask your models” breaks down into three pieces of homework that most companies have been skipping.

Start with what you actually have — and I mean really have. How many systems, what talks to what, where business logic hides in undocumented processes, what the actual unit costs are per workflow. This is boring, unglamorous inventory work. IBM charged millions for it on COBOL systems for decades, until AI brought the cost down. Most companies skipped it even when it was the only option. And you can’t delegate it to IT alone — it requires someone who knows the actual business processes, the shortcuts, the exceptions, and can translate all of that into something AI models can work with. That’s what we call the AI maestro — the person who bridges business reality and AI capability.

Once you have that map, you can run what I call the blank-slate exercise: if you started your company today with agents, automation, and language models — no legacy to maintain, no existing headcount to justify — what would it look like? I’ve seen this exercise stop board conversations cold. The answer usually points to a much smaller team, completely different workflows, and economics that make the current setup look bloated. You can’t present those findings without serious data backing them up.

The last piece is the one that kills momentum: modeling the actual transition. What does it cost to get from here to there? How do you keep the business running while you rebuild underneath it? What level of risk has your board explicitly agreed to tolerate? This isn’t an exercise most companies have attempted — which is why the CEO ends up stuck between pressure to act and fear of breaking what works.

Companies that handle technology cycles well — the ones that build their competitive advantage on deep industry knowledge instead of generic tooling — run these three exercises before the market forces their hand. They do it because they’d rather face uncomfortable answers while they still control the timeline.

The Gap Between the Tweet and the Action

Cuban closed his tweet with a line that reads like a warning: “If asking your models questions doesn’t make sense to you, you are in deep shit.”

He’s right. But there’s a follow-up he didn’t mention: most CEOs understand they should be asking their AI about strategy. What they don’t have is the structured input that makes the question answerable. And that gap is where companies get stuck — sometimes for years.

At IQ Source, we do the work that comes before Cuban’s question. That means mapping your actual architecture (not the version from the last board presentation), modeling what an AI-native version of your operation would look like with real economic projections, and building a transition roadmap your board can evaluate with numbers instead of gut feelings.

If your company knows AI is reshaping the playing field but can’t articulate what that means for your operations — the bottleneck is almost certainly diagnostic, not technological. And that gets solved before you buy another tool. Let’s talk about where you stand.