返回
原文
Tomer Tunguz 博客（VC 分析）
52AI 编辑部评分，满分 100

应用层公司：护城河是赢得的，并非与生俱来

2026-06-26 08:00· 46天前· Tomasz Tunguz
AI 导读

应用层公司创立时通常没有护城河。护城河分两种：先发护城河（技术差异、专有数据集、新颖架构，多见于基础设施层）和滞后护城河（规模经济、品牌、渠道关系，需长期积累）。Salesforce 凭借销售能力、品牌和十年先发优势胜过技术更好的 Siebel；Snowflake 以存储计算分离架构赢得先发护城河，再建设滞后护城河。基于 7 Powers 框架，规模经济、品牌和转换成本天然是滞后的。应用层创业公司可以坦诚回答：我们正在建造护城河。

原文 · 未翻译

In short : At the application layer, moats are lagging, earned through scale & brand. At infrastructure, capital intensity demands a leading moat at founding.

Every founder receives the question on slide three. What is your moat? They answer with technical differentiation. A model, a dataset, an architecture. At the application layer, that answer dissolves in a year.

What if there is no immediate moat? What if the moat is earned?

Leading moats exist at founding. Technical differentiation, a novel architecture, a proprietary dataset. You can point to them in the seed deck. They are most common at the infrastructure layer, where the product is the technology.

Lagging moats are earned through years of execution. Economies of scale, brand, channel relationships, embedded workflows. They cannot be drawn on a competitive landscape matrix because they are not built yet.

Application companies win with lagging moats. Infrastructure companies need leading moats to get off the ground because they require more research & capital to develop.

Salesforce never had a leading moat. Siebel had better technology in 1999. Salesforce won on sales muscle, brand, & a ten-year head start on the cloud-CRM category. Every moat that defends Salesforce today was earned, not engineered.

Snowflake took the other path. The company separated storage from compute when no one else had. That is a leading moat, & it bought the company the runway to build the lagging ones. Marketplace distribution through the hyperscalers. Brand recognition with CIOs. Switching costs embedded in every data pipeline.

Hamilton Helmer’s 7 Powers1 framework helps separate the two. Scale economies, brand, & switching costs are lagging by construction. They require volume, time, & embedded customers. Counter-positioning, cornered resources, & process power can be leading if you have them at founding, but most app-layer startups do not.

Network economies are earned. Slack, Figma, & GitHub got big before clones could catch them.

Application companies earn their moats over time. Focus, execution, & a market moving faster than incumbents can defend are enough. The moat shows up later. It is no less real.

The honest answer at the app layer : we are building one.

  1. Hamilton Helmer, 7 Powers : The Foundations of Business Strategy (Deep Strategy LLC, 2016). https://www.7powers.com/ ↩︎

大佬观点现象/趋势

来源：Tomer Tunguz 博客（VC 分析） · tomtunguz.com

导出 Markdown
返回
52打开原文
导出 Markdown

应用层公司：护城河是赢得的，并非与生俱来

Tomer Tunguz 博客（VC 分析）·2026-06-26 08:00·46天前·Tomasz Tunguz
AI 导读

应用层公司创立时通常没有护城河。护城河分两种：先发护城河（技术差异、专有数据集、新颖架构，多见于基础设施层）和滞后护城河（规模经济、品牌、渠道关系，需长期积累）。Salesforce 凭借销售能力、品牌和十年先发优势胜过技术更好的 Siebel；Snowflake 以存储计算分离架构赢得先发护城河，再建设滞后护城河。基于 7 Powers 框架，规模经济、品牌和转换成本天然是滞后的。应用层创业公司可以坦诚回答：我们正在建造护城河。

原文 · 保持原样，未翻译

In short : At the application layer, moats are lagging, earned through scale & brand. At infrastructure, capital intensity demands a leading moat at founding.

Every founder receives the question on slide three. What is your moat? They answer with technical differentiation. A model, a dataset, an architecture. At the application layer, that answer dissolves in a year.

What if there is no immediate moat? What if the moat is earned?

Leading moats exist at founding. Technical differentiation, a novel architecture, a proprietary dataset. You can point to them in the seed deck. They are most common at the infrastructure layer, where the product is the technology.

Lagging moats are earned through years of execution. Economies of scale, brand, channel relationships, embedded workflows. They cannot be drawn on a competitive landscape matrix because they are not built yet.

Application companies win with lagging moats. Infrastructure companies need leading moats to get off the ground because they require more research & capital to develop.

Salesforce never had a leading moat. Siebel had better technology in 1999. Salesforce won on sales muscle, brand, & a ten-year head start on the cloud-CRM category. Every moat that defends Salesforce today was earned, not engineered.

Snowflake took the other path. The company separated storage from compute when no one else had. That is a leading moat, & it bought the company the runway to build the lagging ones. Marketplace distribution through the hyperscalers. Brand recognition with CIOs. Switching costs embedded in every data pipeline.

Hamilton Helmer’s 7 Powers1 framework helps separate the two. Scale economies, brand, & switching costs are lagging by construction. They require volume, time, & embedded customers. Counter-positioning, cornered resources, & process power can be leading if you have them at founding, but most app-layer startups do not.

Network economies are earned. Slack, Figma, & GitHub got big before clones could catch them.

Application companies earn their moats over time. Focus, execution, & a market moving faster than incumbents can defend are enough. The moat shows up later. It is no less real.

The honest answer at the app layer : we are building one.

  1. Hamilton Helmer, 7 Powers : The Foundations of Business Strategy (Deep Strategy LLC, 2016). https://www.7powers.com/ ↩︎

来源：Tomer Tunguz 博客（VC 分析）· tomtunguz.com

大佬观点现象/趋势