Panic with an AI Roadmap
AI-native and AI-powered are both legitimate. The mistake is not knowing which one you are — and panicking into the wrong answer.
One of my board members brought up an AI-native company last quarter. Wanted to know how I saw them as a competitor.
My honest answer: I hadn’t heard their name from a single customer or prospect in our pipeline. Not once.
When I looked them up, I understood why. They’re a horizontal platform — their model is to integrate data from every system at an enterprise, layer AI on top, and sell the output. No deep vertical. No embedded workflow. No domain expertise built over years in a specific industry. Just data aggregation and an intelligence layer.
We’re something different. Deeply verticalized. Intelligence is an add-on to the core value we deliver to a specific customer in a specific workflow. That distinction matters. And not just for us.
Every market narrative right now is pushing SaaS CEOs toward a binary that isn’t real. AI-native platforms command premium multiples. AI-powered is the consolation tier. Get with the program or get left behind.
Notion didn’t get that memo. Neither did Atlassian, Monday.com, Canva, or Adobe — which added Firefly on top of Creative Cloud and didn’t apologize for it. These are not companies in retreat. They’re some of the most valuable software businesses on the planet, and AI makes them better without defining them.
There is a real category of AI-native software. Cursor is an AI-native code editor — remove the AI and the product doesn’t exist. Harvey built a legal reasoning engine where the intelligence is the product. Glean is enterprise search built entirely on models trained on your company’s data. These companies exist because AI created a category that didn’t exist before.
Real, valuable, and smaller than the narrative implies.
Trying to become it when your business is something else — burning 18 months rearchitecting a platform that works, chasing a multiple before validating whether your data can actually support what you’re building — is not strategy. It’s panic with a roadmap attached.
ChatGPT can write a blog post in 30 seconds. People are still writing their own. Our world doesn’t operate in binaries. It operates in grey.
So the real question isn’t AI-native or AI-powered. It’s: which one are you, and do you know why?
Most CEOs don’t. Not because they haven’t thought about it — they have, constantly — but because they’ve been thinking under pressure without a clean framework for the decision. So they do what people under pressure do: they copy the most expensive-looking option.
Here’s the audit I ran on our platform. Four questions, in order.
1. What data do you actually own?
Not what you have access to. What is proprietary, rights-secured, and unique to your platform? Public data doesn’t compound. Semi-proprietary data doesn’t compound. Only signals that exist because customers use your platform — and only yours — build a flywheel. Map every data asset. Classify each one honestly. Most CEOs find less in the proprietary column than they expected.
2. Where do your customers seek value you can monetize?
Not where they use your product. Where they would pay more if the product were better. Find two or three workflows where your proprietary data makes AI materially better than any generic alternative. Name them specifically — if you can’t, you’re not ready to build.
3. Can you deliver that value better than the alternatives?
Your customers have options. They can wait for a horizontal platform to solve the same problem. They can build something themselves. Your moat question is whether your data, domain knowledge, or workflow depth gives you a durable edge. Speed erodes. Data compounds. Relationships compound. Vertical depth compounds.
4. What does it actually take to build it?
Before committing, prototype. One workflow. One agent. Real customers. Measure whether the outcome actually improves. Companies I’ve watched burn capital on AI transformation mostly skipped this step — they modeled the destination before validating the path.
Run those four questions honestly and the call usually makes itself.
If your data is so central to the product that removing the AI removes the product — and every customer interaction generates a training signal that makes the system smarter — you may be building toward AI-native. Real destination. Real architectural commitment. Real price tag.
If your platform delivers genuine value independent of AI, and AI makes that value better, faster, or more defensible — you’re AI-powered. Own it. Your moat is the embedded workflow, the vertical expertise, the customer trust built over years. AI sharpens it. The platform is still the platform.
We ran the audit. We came out AI-powered. Our platform has real value to customers whether or not AI is in the picture. That’s not a concession. It’s a foundation most AI-native startups are still trying to build.
Before you make the call
Have you mapped your data assets and classified them — public, semi-proprietary, or uniquely yours?
Can you name two workflows where your proprietary data makes AI better than any generic alternative?
Have you stress-tested your moat against horizontal platforms building toward the same problem?
Have you prototyped one AI feature with real customers — not planned it, built it?
Does your platform deliver value when AI is off?
Are you pricing AI tied to measurable customer outcomes, or bundling it in and hoping?
Is your advantage vertical depth and domain expertise — or is it the AI itself? One of those is a moat. The other is a feature.
Most CEOs can work through those questions. Fewer do it before the fear arrives.
The fear is real. FOMO hits SaaS businesses the same way it hits the stock market — it makes disciplined operators do things they’d never do in a calm room. Chase a multiple before validating a moat. Build for the narrative instead of the customer.
Two questions cut through the noise: does what you’re building create surplus value your customers couldn’t get elsewhere? And is that value durable — compounding, deepening, harder to replace over time?
That board member’s AI-native competitor hadn’t shown up once in our pipeline. Not because they weren’t real. Because they weren’t solving a problem our customers had.
Our world doesn’t operate in binaries. Your strategy shouldn’t either.