You Can't Out-Punch Domino's. So Don't Try.

Ilir Sela started Slice from a single pizzeria in Staten Island. By the time I joined, we had a few hundred independent shops on the platform. Every owner conversation started the same way: stop trying to be Domino's. Not because Domino's is unbeatable. Because the fight they're having with Domino's isn't the one that matters.

Domino's spends over a billion dollars annually on marketing. Their tech infrastructure is thirty years deep. Their supply chain, franchise operations, and delivery logistics have been compounding since 1960. You are not out-resourcing that. You are not out-advertising it. The race was over before you registered.

But there is something the franchise system structurally prevents Domino's from doing. The same efficiency machine that makes them dominant makes them incapable of knowing that the Morales family orders a large pepperoni every Friday, that the guy in 4B always pays cash and tips well, that the woman who's been coming since 1987 just had her daughter get into college. A corporate operator runs a system. An independent owner runs on quality and relationships. Given the right technology, they can far surpass the chains. That asymmetry is the entire business case.

What Christensen Got Right About This Market

Clayton Christensen spent his career studying why good companies fail when attackers arrive. His central insight in The Innovator's Dilemma was that incumbents are almost always rational when they ignore disruption. Their best customers don't want what the disruptor is selling, so they rationally ignore it, and they lose anyway.

What's less discussed is the flip side: attackers are also often irrational when they aim at the incumbent's core. They build for the incumbent's customers, at the incumbent's price points, competing on the incumbent's terms. They're fighting on terrain designed to favor the other side.

At Slice, we made a deliberate choice to do the opposite. We weren't building for Domino's customer. We were building for the customer Domino's had written out of their business model entirely. The 20,000+ independent pizzerias that together represented more market share than any single chain. The platform we built was never going to be used by a Domino's franchisee, and that was correct. We weren't trying to compete with Domino's. We were building something for a customer they had structurally abandoned.

Peter Thiel makes a related point in Zero to One: competition is for losers. The best strategy is often to find the market where competition hasn't shown up yet, dominate it completely, then expand from a position of strength. Slice's market wasn't "pizza delivery apps." It was "technology partner for independent pizzerias," a category that essentially didn't exist before we defined it.

The Jobs-to-Be-Done Lens

Christensen's later work on Jobs to Be Done adds another layer. The framework asks: what job is the customer actually hiring your product to do? Not the feature list. The underlying outcome they're trying to achieve.

The independent pizzeria owner wasn't hiring us to "manage online ordering." She was hiring us to compete. To stay viable against chains with technology budgets she could never match. To give her regulars a reason to order direct instead of through DoorDash, where she was losing 30% of the ticket price and had no access to the customer relationship.

When you understand the job that way, the product decisions become obvious. Every feature we built had to pass one test: does this help the independent shop compete on the dimension they can win? Relationship, community, specificity. Features that made the shop look like a chain failed that test. Features that amplified what was already special about them passed.

What SinglePlatform Taught Me About Changing the Question

Before Slice, I ran strategy and business development at SinglePlatform. Google and Yelp dominated local search. We had no realistic path to out-investing either of them in SEO, in product, in brand. The instinct was to compete directly. The right move was to change what we were competing on.

The problem we solved wasn't "be better than Google." It was "be everywhere Google can't take you." Accurate, consistent business information syndicated to hundreds of publishers simultaneously. Not one platform. All of them. Google could own Google. We owned the distribution layer across the rest of the web.

That framing opened a distribution channel our competitors couldn't touch. Publishers wanted to offer local business customers something Google wasn't providing. We were that thing. The network effect compounded as we added publishers: each new distribution partner made the product more valuable to every business already on it. That's not a feature. That's a structural advantage.

We sold to Constant Contact for $100M in 22 months. The strategic logic had nothing to do with competing with Google. It had everything to do with serving a customer the incumbents had decided wasn't worth their attention, and building a network around that customer that became defensible over time.

The best competitive strategy is often not competition at all. Find the customer the market leader structurally cannot serve. Build something so specific to that customer that the incumbent can't follow without dismantling what made them big. Then build a moat around the relationship before they figure out you're there.

The Three Questions I Ask Every Founding Team

Before I let anyone write product spec, I push on three things. The answers change what gets built more often than not:

• Who is the incumbent structurally incapable of serving? Not who they've ignored. Who their business model, unit economics, or org structure makes it genuinely impossible to serve well. The franchise constraint at Domino's is a real answer. "They haven't gotten there yet" is not.
• What do you know about this customer that the incumbent doesn't and can't learn? Asymmetric customer intimacy is a durable moat. If you've embedded yourself with the operator and your competitor sends sales reps, that gap is structural and compounds.
• What job is the customer trying to do that the incumbent's product actively prevents? Not a gap in features. A job the incumbent's model makes it impossible for them to enable. At Slice, that job was "keep my customer relationship." DoorDash structurally had to own that relationship. We could give it back.

The answers are the company. Not the deck.

The Math Behind the Moat

Slice reached a $1B valuation serving customers who were too small, too distributed, and too high-touch for any corporate operator to want. Those exact characteristics created the moat. High-touch means the relationship is real. Distributed means it's hard to replicate at scale without the infrastructure we had already built. Too small for Domino's means no competitive pressure from the people with the largest war chests.

The pizzeria owner in Jackson Heights didn't need to out-punch Domino's. She needed a partner who understood that her advantages were fundamentally different from a chain's, and built tools that made those advantages more durable instead of trying to paper over them with features she'd never use.

That market is always adjacent to the crowded one. The crowded one is where everyone is looking. Go find the other one.