Supabase could have positioned themselves as a modern backend platform for developers. They could have used buzzwords about speed and performance and developer experience, like every other infrastructure startup in the space. Instead, the top of their homepage said: “Open source Firebase alternative.” They kept that positioning from 2021 through mid-2025, reaching a $5 billion valuation along the way.
First to Market documents the framework that made it work, and the logic is counterintuitive. Most startups avoid naming the industry giant because it makes them look small. But buyers are already thinking about the incumbent. “People get awkward talking about their biggest competitor,” writes Andrew Garberson. “We do not acknowledge their size because it would make us look small. We do not accept their feature breadth because it would make us look behind.” Pretending the comparison does not exist makes the product harder to understand, not easier.
“Alternative positioning works best when there is a single default choice that your buyers already know,” Garberson explains. “Fragmented markets with lots of feature overlap and complicated consideration criteria are not a fit here. But if there is one name everyone thinks of, you can use it as a reference point rather than competing against it indirectly.”
Name the giant, then claim the wedge
The Supabase playbook has four moves. Name the giant explicitly and with confidence. Claim a wedge that matters deeply to a specific disgruntled segment of the incumbent’s audience. Prove the difference through tangible, independently verifiable proof. Then lower the switching costs so the default choice feels less like a trap.
For Supabase, the wedge was ownership and control. Developers who valued open source and SQL, two things Firebase did not offer, had permission to choose Supabase. The wedge was not a nice-to-have feature. As Garberson puts it: “A good wedge needs to fuel a fire that is already burning.” Supabase did not need to convert every Firebase user. They just needed the segment that was already frustrated.
The proof was visible across everything Supabase did. “From day one, Supabase was built on community trust,” said investor Aaron Cort. “It grew into one of the most starred open-source projects on GitHub, scaling from early Hacker News buzz to powering millions of databases.” The wedge was not just claimed in marketing copy. It was embedded in how the company operated: open source code, public documentation, community governance.
What this looks like in Web3
The same logic applies to Web3 projects, with one important difference: the wedge has to survive on-chain scrutiny. In Web3, transparency beats polish. Token distribution, wallet activity, and smart contract interactions are visible to anyone. As EAK Wire puts it: “Spin does not survive that level of scrutiny. On-chain activity is public. Token distribution, wallet activity, and smart contract interactions are visible to anyone.”
A Web3 alternative positioning playbook follows the same four steps but with crypto-specific wedges. If your competitor dominates general-purpose DeFi lending, your wedge might be institutional-grade compliance and audited smart contracts. If they own the high-TVL narrative, your wedge might be sustainable yield that does not depend on token subsidies. If they are the default for experienced traders, your wedge might be the onboarding experience for first-time DeFi users.
The wedge must be something the incumbent either cannot or will not offer. Stratup’s asymmetric warfare framework names the same principle: “Instead of attacking where incumbents are strongest, identify adjacent markets they have neglected. Target their non-consumers. Serve their worst customers. Build for the job they will not do.” In Web3 terms, this means finding the specific protocol pain point that the bigger competitor dismisses as a niche concern and turning that niche into your core audience.
AP Collective adds a useful framing: “If your project does not fit an active narrative, connect your product to the narrative naturally.” If you do not fit the dominant narrative, claim an adjacent one. The bigger competitor is fighting for the centre of the category. You want the edge where the growth comes from.
Spend your limited budget where trust compounds
A bigger competitor will outspend you on paid acquisition every single time, and chasing them in their channel is a losing game. GrowthChain recommends putting 50 to 60 percent of your early marketing budget into community building and content. “Nurture 100 to 200 highly invested community members rather than chasing 10,000 passive followers,” they advise. “A small core of believers will outperform a massive audience of tourists every time. They create user-generated content, refer new users, defend the project, and stick around through volatility.”
The compounding channels are SEO and community. Monolit’s guide to competing with funded competitors makes the same point: incumbents can outspend you on ads, but they cannot out-earn you on content that ranks and accumulates authority over time. Most well-funded competitors prioritise brand campaigns and paid distribution over SEO, which means the organic channel is wide open for projects willing to invest the time.
FORKOFF’s Web3 Growth Loop provides the sequence: grant leverage for initial distribution, founder-voice CT signal for thesis building, quest surfaces to convert attention into on-chain action, community trust to retain filtered users, then product conversion. Each lever feeds the next. “Web3 GTM fails when founders treat levers as one-shot campaigns instead of a compounding system,” they write. The loop compounds in a way that a one-off paid campaign never can.
The free unlocks matter too. List your project on CoinMarketCap, CoinGecko, and CoinMarketCal. GrowthChain calls this “the most underrated zero-cost move in crypto marketing.” The credibility boost is real, and most projects skip it because it does not feel like a campaign. A fractional marketing lead can help you identify and execute these high-leverage, low-cost plays that compound over time.
Make speed your structural advantage
Stratup calls this the 10x speed advantage: “While incumbents take 18 months to ship, you can launch in 6 weeks.” Big projects have layers of approval, compliance reviews, and communication sign-offs. You can publish a blog post, ship a feature, or respond to market feedback in hours.
That speed advantage is most effective when paired with narrow focus. Incumbents serve everyone poorly; you serve one segment perfectly. Figma initially focused only on web designers, ignoring print and mobile. Supabase focused only on developers who valued SQL and open source. The narrower the segment, the faster you can iterate on their specific needs and the harder it is for the bigger competitor to respond without diluting their own product.
FORKOFF’s operator interview captures this perfectly: “We spent $180K on KOL pushes over 4 months. Zero retained users. The tweet that actually converted came from the founder’s own account, a 200-word thread, about a bug he fixed.” The bigger competitor cannot match founder-level speed and authenticity. They have committees and approval workflows. You have a founder who can tweet at 2am.
Lower their switching costs
The most effective wedge in the Supabase playbook might be the least glamorous. Supabase put energy into eliminating the binary choice between staying with Firebase or switching completely. Developers were encouraged to start new projects on Supabase with generous free tiers rather than migrate existing work. Support documentation covered partial migrations and running both platforms in parallel. The community developed migration tools that reduced the fear of the unknown.
Status quo bias means it is always easier for users to do nothing. Any friction in the form of time, risk, or complexity compounds the cost to switch. Make it easy to start small. Make it easy to run your solution alongside the incumbent. Make it easy to leave if it does not work. The bigger competitor does not need to offer this flexibility because they are the default, but you do, and that optionality is a structural advantage you should not waste.
Run a small experiment alongside your competitor and let users discover the difference on their own terms. Cross-chain compatibility, pilot programs, testnet access, and documentation that directly compares your approach to the incumbent without being hostile. The goal is to make the comparison inevitable and favourable by being present in the places users already go, rather than forcing a hard migration.
If you would like help positioning your Web3 project against a better-funded competitor, get in touch.
Leave a Reply