Whether you're looking for an angel investor, a growth advisor, or just want to connect — I'm always open to great ideas.
Get in TouchAI, startups & growth insights. No spam.
TL;DR: Every startup founder panics when they spot a competitor. Most panic responses — feature scrambles, price wars, pivot spirals — destroy more value than the competitor ever would have. This article is the playbook I wish I had ten years ago: how to map your competitive landscape clearly, position against giants honestly, and build structural advantages that don't evaporate the moment someone raises a Series B.
I remember the first time a prospective investor asked me, "Who are your competitors?" My instinct was to say "no one, really" — because I'd been reading too much Peter Thiel and had internalized the idea that competition is for losers and monopoly is the goal.
That was naive. And it cost me deals.
Here's what I've learned since: having no competitors is almost always a red flag, not a feature. It means one of three things — you're in a market so small that nobody bothered to address it, you've found something so new that the market doesn't exist yet (extremely rare), or you haven't looked hard enough. None of these scenarios are automatically good.
When Notion launched, they were competing against Evernote, Google Docs, Confluence, Roam Research, and a dozen other tools. That wasn't a problem. It was market validation. People desperately wanted a better way to organize their work and thinking. The competition proved it. Notion's job wasn't to be in an empty room — it was to be meaningfully different in a crowded one.
Thiel's monopoly thesis is correct at the endgame level — you want to eventually dominate a niche so completely that competition becomes irrelevant. But in the early game, competition is fuel. Competitors are spending money on ads that educate the market you're targeting. They're publishing blog posts that rank for keywords you want. They're having sales calls with prospects who might then look for alternatives — and find you. They're building category awareness so you don't have to.
The real question isn't "do we have competitors?" It's "do we have a defensible reason to exist alongside or instead of them?"
When you tell an investor you have no competitors, one of two things happens:
Experienced investors know that every market has competition — if not direct competition, then status quo competition. The biggest competitor for most B2B SaaS products isn't another SaaS tool. It's Excel. It's email. It's "we'll just do it manually." You're not competing in a vacuum. You're competing against inertia, existing habits, and the human brain's default preference for keeping things the same.
Acknowledging competition, mapping it clearly, and explaining your differentiated position is a sign of market understanding, not weakness. I've pitched rooms full of investors and gotten far more traction saying "Here's a crowded market, here's where everyone has made the same mistake, and here's why our approach is different" than I ever got from trying to claim empty sky.
The founders who treat competition as fuel — who study it, learn from it, and use it to sharpen their positioning — consistently outperform founders who either ignore it or obsess over it anxiously. The goal is informed clarity, not avoidance or paranoia.
Every founder who has watched Google, Microsoft, or a VC-backed juggernaut enter their space has felt the cold dread of "we're done." I've felt it. The instinct is to see only the disadvantages: more money, more engineers, more brand recognition, more distribution.
But the analysis is incomplete. Big companies have enormous structural disadvantages that small startups can exploit ruthlessly.
A startup with five engineers can ship a feature in three days. A company with 500 engineers ships it in three quarters — after it's been through roadmap planning, design review, legal sign-off, engineering grooming, sprint cycles, QA, and a staged rollout. By the time they've shipped, you've iterated four times.
Linear is a masterclass in this. They entered a market dominated by Jira, Asana, and Monday.com — all heavily funded, deeply entrenched. Their advantage wasn't budget. It was that they could make opinionated product decisions fast and ship them without fourteen layers of consensus. Their changelog became a marketing asset. Every week, something new shipped. That velocity communicates confidence, momentum, and care in a way that press releases never do.
Speed also compounds. Faster shipping means faster learning. Faster learning means faster product-market fit refinement. The startup that ships every week collects more signal in a year than the enterprise product that ships quarterly collects in a decade. At scale, this information advantage becomes moat-level.
Big companies run portfolios. They have dozens of products, hundreds of use cases, and thousands of edge cases to maintain. A small startup has one job. That's not a weakness — it's laser precision.
Superhuman didn't try to build a platform. They built the fastest email client on earth, for one type of user: high-output professionals who live in their inbox. That singular focus let them go deeper than Gmail ever would on speed, keyboard shortcuts, and the felt experience of email. Google can't justify making Gmail 50ms faster for power users because that doesn't move the needle for their 1.8 billion users. Superhuman can — because that is their entire product.
When you're competing against a giant, the fastest path to defensibility is narrowing scope to a point where the giant would feel embarrassed to follow you. The narrower your niche, the harder it is for a large company to justify the reallocation of engineering resources to compete there.
I've taken hundreds of customer calls personally. Not delegated to a customer success rep — me, on the call, listening, asking follow-ups, sometimes spending an hour with a single user understanding their exact workflow. That's not scalable. It's also the single greatest competitive advantage I've ever had.
When the CEO of Salesforce gets feedback, it travels through four layers of organizational hierarchy before it reaches any product decision. When I get feedback, I can ship a response by Thursday. That speed of the feedback loop is transformative.
The founders who stay close to users longest — who don't outsource the customer learning early — build better products. Paul Graham's advice to "do things that don't scale" isn't just about growth hacks. It's about the information advantage you build when you talk to every single customer personally.
A startup can make a bet that a public company literally cannot make. If it works, you win the category. If it fails, the company dies — but that's a bet you're willing to make because the upside justifies it. A public company's management team can't make that same call without triggering shareholder litigation.
Dropbox bet everything on a consumer-grade file sync product when enterprise IT departments said it was a security nightmare. They were right. Slack bet on replacing email with a chat interface that enterprise IT buyers considered frivolous. Both bets paid off enormously — and both were bets that an incumbent, protecting quarterly earnings, couldn't have made.
Your size is your permission structure. Use it.
There's a failure mode I've watched kill startup momentum more effectively than any competitor: obsessive competitive monitoring. I've seen founders who spend more time on competitor Twitter accounts than on customer interviews. That's a version of losing before the battle starts.
Competitive intelligence is valuable in controlled doses. The framework I use: map quarterly, monitor signals monthly, act on insights only when they touch your roadmap.
Not all competition is equal. I think about it in three tiers:
Tier 1 — Direct competitors. Same customer, same problem, similar solution. If your prospect is choosing between you and them, you need to know their product deeply. These are the competitors you monitor most actively.
Tier 2 — Indirect competitors. Same customer, related problem, different solution. A project management tool competes indirectly with a communication tool — both want the same workflow attention. Less urgency, but worth understanding.
Tier 3 — Status quo alternatives. Spreadsheets, email, manual processes. Often the most dangerous competitor because there's no clear comparative pitch. Switching from an explicit competitor is a product decision. Switching from "we'll just keep doing it in Excel" is a behavior change — much harder to trigger.
Rather than listing competitors in a table, I map them on two axes that reveal strategic white space:
Most incumbents cluster in the upper-right quadrant: broad functionality, complex implementation. Most new entrants try to go upper-left (broad and simple — the hardest quadrant to defend because it's a quality race). The strategic opportunity for a startup is usually lower-left: focused functionality, simple implementation — a position that incumbents find hard to occupy because simplicity kills their upsell surface area.
Draw this matrix with honest placements. The empty quadrant is your wedge.
The three competitive signals worth monitoring:
What not to track: their social media follower counts, Hacker News comments about their product, or anything that creates anxiety without informing action.
The most counterintuitive competitive move I've seen work consistently is defining your product by what it's not.
This is anti-positioning, and it works because it does two things simultaneously: it tells your target customer exactly what frustrations you've rejected, and it immediately disqualifies customers who want the thing you're not.
Linear built their entire early brand on not being Jira. Their tagline might as well have been "software project management that doesn't make you want to quit." They didn't need to explain every feature they had. They just needed engineers to feel seen — understood in their specific frustration with the incumbent — and the product sold itself.
Basecamp has made an art form of this. Their whole brand is built on not being "enterprise project management." They explicitly reject the complexity, the integrations, the customization, and the feature bloat that Salesforce and Microsoft Teams embrace. For some customers, this is a dealbreaker. For their target customer — small teams who want clarity — it's the sale.
Hey, their email product, came out with an explicit manifesto against Gmail: no tracking pixels, no promotions tab, no auto-categorization you didn't choose. They didn't compete on features. They competed on philosophy. And their customers paid a premium for it.
Start with the frustrations your target customers have with the category leader. Not all frustrations — the core frustrations that represent a genuine design trade-off, not a bug they're fixing.
Then ask: would we ever build that thing they're frustrated with? If the answer is genuinely "no, and here's why," you have an anti-position.
The test: your anti-position should make some people angry. If everyone agrees with it, it's not a real differentiation — it's just saying "we're better." Real anti-positioning means rejecting something valuable. Basecamp rejects integrations that many teams actually want. Linear rejects the flexibility that enterprise teams need. Hey rejects the free tier that most email users expect. Those rejections cost them customers. They're also what make them credible to the customers they actually want.
Write your anti-position statement as a "we don't" or "we believe X is wrong":
Post this on your website. Mean it. Let it filter your customers before your sales team has to.
Feature parity is the trap that kills startups. It feels rational: a customer asks "does it have X?" you say no, you lose the deal, so you build X. Repeat until you've built everything the competitor has — but slower, with less polish, and without the integrations they've spent years developing. You've now entered a race you cannot win.
The startups that beat incumbents don't do it by matching features. They do it by owning a different way of working.
Here's the economics of feature parity: the incumbent has a 5-year head start and 50 engineers. You have 2 years and 8 engineers. Every feature you build to match them is a feature you're not building to differentiate from them. The treadmill accelerates. You stay in the same relative position, exhausted.
Meanwhile, the incumbent isn't standing still. They're shipping too. So the gap never closes — you just run faster to stay in place.
The only escape is to stop running their race and start running yours.
Figma didn't beat Adobe Sketch by having more features. It beat it by being collaborative by default — real-time multiplayer design, in the browser, shareable by link. Adobe's product was technically superior in many areas. But Figma understood that design was increasingly a team activity, not a solo one, and they built the workflow for that world. The feature battle was irrelevant once they won the workflow argument.
Airtable competes in the database/spreadsheet space against Excel, Google Sheets, and full relational databases. They didn't win by having more formulas or better charting. They won by making databases feel like spreadsheets — a workflow affordance that made non-technical users feel powerful rather than intimidated. Same data, entirely different relationship.
Opinionated products are hard to build — they require you to make enemies of some users. But they create the deepest loyalty with the users who agree with your philosophy.
An opinionated product says: "This is the right way to do this thing. We've thought about it deeply, and we've made choices. If you trust our judgment, this will be the best tool you've ever used. If you want to do it differently, this isn't your tool."
That's terrifying to ship. It's also defensible in ways that flexible, configurable products are not. Because the customer who bought your opinionated product didn't just buy features — they bought your judgment. And your judgment, consistently expressed over years in how you build, is a moat that can't be cloned.
One underrated competitive strategy: be the connective tissue. If your product sits in the middle of a user's workflow — pulling data in from five places, pushing outputs to three more — leaving you is extraordinarily painful. Not because your product is great (though it should be), but because removing it means rebuilding the entire plumbing.
Zapier is the extreme version of this: they're literally the connective tissue. But any SaaS product can pursue a version of this strategy. Build integrations aggressively and early. Make your product the hub, not the spoke. The more workflows depend on you, the higher the switching cost — not because you've trapped anyone, but because you've genuinely become part of how they work.
In 2016, Slack was growing explosively. Then Microsoft announced Teams. Every pundit declared Slack dead. In 2019, Slack went public at a $23B valuation. In 2020, Salesforce acquired it for $27.7B.
The narrative that "Big Tech entering your market = game over" is mostly wrong, because it misunderstands how big companies operate. They don't enter markets — they announce entries into markets, ship MVPs that check the checkbox, and then move on to the next announcement.
When Google launched Google Drive, Dropbox was declared dead. Dropbox now has 700 million registered users. When Apple launched Apple Maps, every navigation startup was supposed to shut down. Waze sold to Google for over $1B and still operates independently. When AWS launched their queue service, SQS, it was supposed to kill RabbitMQ and every message broker startup. Confluent was founded after AWS SQS existed and built a multi-billion dollar company on Kafka.
Big Tech's entries into startup markets consistently underperform because:
When Big Tech enters your space, here's what I'd do:
Days 1–30: Don't panic, assess honestly. Read everything they've shipped. What did they actually build versus what they announced? Build a feature comparison that's honest. Most times you'll find their entry is shallow — they've built 20% of your product and called it the same name.
Days 31–60: Go deeper into your niche. They've entered the broad market. Go narrower. If you were serving "project management," go to "software project management for remote-first teams under 50 people." The narrower you go, the less economically interesting you are to them, and the more valuable you are to your specific customer.
Days 61–90: Lock in your existing customers. Send them a direct communication. Not a defensive one — a confident one. "You've heard the news. Here's what it means for you: nothing changes in your workflow, and here's what we're shipping next that they won't build." Get your most loyal customers to talk publicly about why they're sticking. Every case study of a customer who considered switching and didn't is a competitive asset.
The one scenario where Big Tech entry is genuinely lethal: if they can bundle your product for free into something your customers already pay for. Microsoft Teams didn't beat Slack by being better — they beat Slack in the mid-market by being included in Office 365. If you're facing that dynamic, you need to either move up-market (where purchasing decisions are made on merit, not bundling) or find the customer segment where the free bundle doesn't reach.
Professional competitive intelligence tools exist — Crayon, Klue, Kompyte — and they're useful at scale. But in the early stages, you can run a thorough competitive intelligence operation with free and near-free tools, customer conversations, and a disciplined quarterly process.
G2 and Capterra reviews. This is one of the most underused competitive research tools in existence. Your competitors' most recent negative reviews are a direct line to what customers hate about them — which is a map of your messaging opportunities. Filter for 3-star reviews of your competitors and read every single one. Group the complaints by theme. Those themes are your positioning.
Glassdoor reviews for competitors. Employee reviews reveal culture, execution quality, and internal dysfunction that would never appear in a press release. A competitor with 2.8 stars and dozens of reviews saying "product roadmap changes every quarter" is a competitor with execution problems. A competitor with dozens of reviews saying "we're losing to X startup in every deal" is telling you who your real competition is.
Job postings. A competitor hiring five data engineers signals an investment in data infrastructure. A competitor opening a London office signals geographic expansion. A competitor posting for "Head of Self-Serve" signals a motion change from enterprise to PLG. Job boards are a 12–18 month roadmap preview, published publicly.
Twitter/X and LinkedIn social listening. Search your competitors' names on Twitter and sort by "latest." You'll find real-time customer complaints, press coverage, and sometimes product announcements before they hit the blog. LinkedIn shows you who's leaving and joining competitors — a personnel signal that often precedes strategy changes.
Customer win/loss interviews. The single highest-signal intelligence source. After every lost deal and every won deal, do a 15-minute call with the prospect or customer to understand the decision. Why did they choose you or the alternative? What almost made them go the other way? This information is direct, contextual, and immediately actionable. Record it systematically (a Notion database works fine), look for patterns quarterly.
I recommend a 90-minute session every quarter with your leadership team:
Output: one page of positioning updates, one page of roadmap implications. That's it. Don't over-engineer this. The goal is informed judgment, not paralysis.
The best time to build switching costs is before you need them. Most startups think about retention as a customer success problem — churn happens when customers are unhappy, and the solution is making them happier. That's true but incomplete.
Switching cost is a structural property of your product. You can engineer it deliberately, not as a trap for customers, but as a natural consequence of how deeply integrated your product becomes in their workflow.
I think of this as a ladder — each rung adds friction to leaving, in a way that also adds value to staying.
The first and most basic switching cost: you have data that lives in the product. Transaction history, customer records, project archives, conversation logs. The longer someone uses your product, the more historical data they have — and the more painful it is to migrate or recreate that data elsewhere.
This isn't lock-in through data hostage-taking. Good products make data exportable. But the practical reality is that migrating years of historical data is painful, and the mere existence of that data creates inertia.
Design for data accumulation early. Think about what longitudinal data your product generates that becomes more valuable over time. For a CRM, it's deal history and customer notes. For an analytics tool, it's baseline metrics that make current performance meaningful. For a project management tool, it's the entire record of how your team makes decisions.
At this rung, the product isn't just where data lives — it's how work gets done. The daily standup happens in the tool. The sprint review happens in the tool. Onboarding new employees includes "here's how we use this tool."
When a product is embedded in workflow, switching isn't a product decision anymore. It's an organizational change management project. The person who would advocate for switching has to convince their team to change how they work, not just which software they log into. That's a much higher bar.
Build for workflow embedding by making your product the place where decisions happen, not just where information is stored. Decisions leave a trail. That trail creates narrative and organizational memory that's extremely hard to move.
Every user who becomes expert in your tool is a switching cost node. They've invested time learning your system, built mental models around your interface, and developed workflows that are product-specific. Asking them to switch is asking them to give up that investment.
Scale this across a team of 20 people and you're not talking about one person's time investment — you're talking about hundreds of hours of collective expertise. The economic argument for switching has to overcome that collective investment.
This is why free training, certifications, and power-user programs are secretly competitive moats. They feel like customer success investments. They're also structural switching costs.
Every integration your product has with another system in the customer's stack creates a dependency. If your tool pushes to Salesforce, pulls from GitHub, sends to Slack, and syncs with HubSpot, removing your tool means rebuilding all four of those integrations in whatever replaces you. And finding a replacement that integrates with all the same systems in the same ways is often impossible — leaving gaps in the workflow.
Build integrations as fast as you can, as early as you can. Every integration is a retention investment disguised as a product feature.
The top of the ladder: the customer has built custom workflows inside your product. Custom fields, automation rules, reporting templates, API integrations they built themselves. This isn't your product anymore — it's their product, built on your platform.
At this rung, switching doesn't just mean leaving your product. It means leaving the product they've built. That's a fundamentally different ask. The switching cost isn't "find an alternative to this vendor" — it's "rebuild this custom system we've spent 18 months developing."
If your product supports customization, configuration, and extensibility, encourage it. The more customers build on top of your platform, the more the platform belongs to them — and the harder it is to leave.
The most counterintuitive move in competitive strategy: partner with your competition.
This isn't naive. It's a calculated recognition that in most markets, the question isn't "will your tool win?" — it's "will this category of tools be adopted by mainstream users?" In the growth phase of a market, the biggest enemy isn't your direct competitor. It's the inertia of non-adoption.
Co-opetition works when:
The market is still being created. If you're both trying to convince people that they need this type of product, you're better off as allies against inertia than as enemies against each other. Two small voices in the same direction are louder than one.
You're in different sub-segments. If your competitor serves enterprise and you serve SMB, you're not actually competing for the same customer — you're just in the same category. An integration partnership that makes it easy for SMB customers to graduate to the enterprise product (and enterprise buyers to offload smaller accounts to you) benefits both parties.
You're complementary, not substitutable. If a customer plausibly uses both of you in their workflow, an integration that connects your products is a competitive advantage for both of you against any third party who doesn't play well with either.
HubSpot built their ecosystem by partnering aggressively with tools their customers used — even tools that competed with parts of the HubSpot platform. A HubSpot-Salesforce integration that let customers use both was "cannibalistic" only in the short term. In the long term, HubSpot's willingness to play well with others made them the hub that customers organized their stack around.
Build an open API early, publish it publicly, make it good, and actively recruit integration partners — including competitors who serve adjacent segments. Every integration partnership is a referral channel, a retention mechanism, and a signal to prospects that you play well in the ecosystem they already have.
The risk in co-opetition is giving a competitor access to your customer data or distribution. Integration partnerships should be designed so that you remain the system of record for your core data, and the integration enriches the partner's data without giving them a strategic foothold in your account.
The other risk: being used as a stepping stone. If a larger competitor integrates with you specifically to understand your product and customer base, the integration can become a due diligence process for acquisition or a blueprint for a competing feature. This is rare, but it's worth structuring integration agreements carefully — especially around data access and competitive use.
I want to close with something that doesn't get said enough in the competitive strategy conversation: the best competitive advantage isn't a feature, a price point, a partnership, or a positioning statement. It's the rate at which you learn.
The companies that win long-term in competitive markets aren't the ones who made the best decisions at year one. They're the ones who built systems to learn faster than their competitors — who could be wrong in January and right in March, because they closed the loop faster.
That means talking to customers continuously, not just at the start. It means looking at churn signals before they become churn. It means running experiments rather than making commitments. It means having the organizational humility to kill features that aren't working and double down on the ones that are, regardless of who originally advocated for them.
The startups I've watched beat better-funded competitors consistently shared one trait: they were better at updating their beliefs. They had better feedback loops, shorter iteration cycles, and less political resistance to changing course when evidence pointed another way.
If I had to reduce this entire article to a single sentence: The startup that learns fastest wins, regardless of the competitive landscape around it.
Your competitors will make mistakes. You will make mistakes. The question is who corrects faster.
Q: Should I mention competitors on my website?
A: It depends on your category maturity. In a well-established category, comparison pages ("us vs. [competitor]") rank well for high-intent search traffic and convert effectively — the person searching "[your category] vs. [competitor]" is already in buying mode. In a new category, mentioning competitors can confuse prospects who don't know the landscape yet. My rule: if the category is mature enough that a comparison page would rank, build it. Make it honest — include areas where the competitor is genuinely better, then explain why those areas don't matter to your target customer.
Q: How do I handle a prospect who says "the big company does this for free"?
A: First, validate the feeling — "That's worth exploring." Then ask what free actually includes. Most "free" tiers of enterprise products are feature-stripped in ways that matter for their specific workflow. Second, reframe the conversation from price to cost: what does it cost in time, reliability, and capability to use the free version versus the purpose-built solution? Free software that creates three hours of workarounds per week is more expensive than paid software that doesn't. Third, be honest about the trade-offs. If the free tier genuinely does everything they need, help them figure that out — they're probably not your customer right now, and that's okay.
Q: When should a startup actually compete on price?
A: Almost never in the early stages. Price competition is a race to the bottom, and startups almost always lose it to better-capitalized competitors. The one scenario where price is a legitimate weapon: if the incumbent is significantly over-charging for a product that's become commoditized, and you can profitably undercut them while maintaining a comparable experience. Even then, use price as an entry wedge, not a permanent positioning strategy. Land on price, expand on value.
Q: How do I stop my team from being demoralized by competitor announcements?
A: The best antidote to competitor anxiety is customer momentum. When your team sees evidence that customers love what you're building — case studies, NPS scores, renewal conversations, enthusiastic feature requests — the competitor announcement feels less existential. Create systems that surface customer love regularly: share positive testimonials in the team Slack, read good G2 reviews in all-hands, celebrate customer milestones publicly. The team that's hearing "this product changed how we work" every week is much harder to demoralize than one that only hears about competitors.
Q: Should I track every competitor move?
A: No. Track tier 1 direct competitors closely (quarterly deep-dives, monthly signal monitoring). Track tier 2 indirect competitors occasionally (semi-annual review). Ignore competitor social media and Hacker News threads entirely — they're almost entirely noise. The signal-to-noise ratio in competitive intelligence drops precipitously as you go from "product announcements and pricing changes" to "Twitter commentary."
Q: What's the best way to learn from companies who successfully competed against Big Tech?
A: Case studies worth reading in depth: Slack vs. Microsoft Teams, Zoom vs. Google Meet and Microsoft Teams, Figma vs. Adobe, Notion vs. Google Docs, and Airtable vs. Excel/Google Sheets. In each case, the winner didn't match features — they owned a workflow or a user segment so specifically that the incumbent couldn't follow without cannibalizing their own product. The common thread: they were more opinionated, moved faster, and stayed closer to a specific user type. Read their founder interviews, not just their launch announcements. The strategy is usually more visible in hindsight than it appeared at the time.
Q: How do I handle a competitor who's spreading misinformation about our product?
A: Document it, don't panic about it. If a competitor is saying your product doesn't have a feature that you do have, the appropriate response is a clear, public, factual clarification — ideally in a format that ranks for "[competitor] vs. [you]" searches. If it's genuinely defamatory, consult a lawyer. In most cases, the best response to misinformation is evidence: case studies, public documentation, customer testimonials that speak to the specific capability being misrepresented. Getting into a Twitter war with a competitor is almost always a bad trade — it amplifies both of you and makes the category look petty.
Q: At what stage should a startup start thinking seriously about competitive strategy?
A: Day one. Not obsessively, but clearly. Before you write a line of code, you should know who else is trying to solve this problem, why your approach is different, and what would make a target customer choose you over them. That doesn't require a competitive intelligence stack or quarterly reviews — it requires a conversation with 20 potential customers about what else they've tried and why it fell short. Competitive positioning is a product decision, not a marketing decision. The earlier you treat it that way, the more coherent your product will be.
I write about building products, growing startups, and competing in markets that are already crowded. If this was useful, subscribe to get new essays in your inbox.
Mark Zuckerberg cuts 20% of Meta's workforce in a sweeping AI restructuring, redirecting billions from traditional engineering roles to AI infrastructure, research, and autonomous agent development.
Meta pushes back its next-gen Avocado model to May after underperforming rivals, and its AI leaders are now discussing temporarily licensing Gemini from Google — putting the $135 billion AI bet under scrutiny.
VCs are discounting feature-based moats. AI replicates complex features in weeks. Here's where real SaaS defensibility comes from now — and how to build it.