“更好”并不总是足够。为什么聪明的领导者使用这种隐藏的曲线来决定谁获胜
来自 Maksym Misichenko · Yahoo Finance ·
来自 Maksym Misichenko · Yahoo Finance ·
AI智能体对这条新闻的看法
The panel generally agreed that market substitution is not linear but follows a curved path due to high switching costs, integration challenges, and other frictions. However, they also noted that this curve can be compressed or accelerated by technological advancements, regulatory changes, or other external factors.
风险: Human risk aversion and the fear of catastrophic migrations can act as a significant barrier to market substitution, even when technical costs and integration times are reduced.
机会: Technological advancements, such as AI-driven modularity and LLM-based API orchestration, can compress the substitution curve and lead to sudden, non-linear displacement of incumbents.
本分析由 StockScreener 管道生成——四个领先的 LLM(Claude、GPT、Gemini、Grok)接收相同的提示,并内置反幻觉防护。 阅读方法论 →
“更好”并不总是足够。为什么聪明的领导者使用这种隐藏的曲线来决定谁获胜
尼尔·索马尼
5 分钟阅读
Entrepreneur Media LLC 和 Yahoo Finance LLC 可能通过以下链接中的产品和服务赚取佣金或收入。
关键要点
“更好”并不意味着“被取代”——真正的约束会减缓你认为显而易见的每一个转变。
现有企业能够维持是因为离开它们的成本比任何电子表格显示的还要复杂。
不要争论哪一方获胜——而是弄清楚实际需要什么才能实现转变。
如果你从足够远的地方看,替代总是听起来很干净。
煤炭是旧的。天然气是新的。所以人们说:“这些是更高效的天然气发电机。让我们把所有的煤炭从电网中移除,然后把这些天然气单元放进去。”
如果你曾经在真正的系统中工作过,你已经知道接下来会发生什么:它不会像那样运作。
看起来像一个简单的升级通常是一种权衡。这是一种在约束下的替代。我关心这一点,因为领导者在商业中经常犯同样的错误,尤其是在资本和注意力移动速度超过人们预期的速度时。他们将替代视为一场头对头比较,但实际上,它是一种曲线。
问题在于,领导者倾向于将替代建模为仅仅是美元:我们现在支付多少,我们另支付多少?
但替代成本不仅仅是美元。存在粘性市场效应。一些约束使得“显而易见的”转变实际上并不显而易见。如果你不考虑这一点,你就会根据一种叙述而不是你实际运行的曲线做出决定。
燃料转换是约束下的替代
当我谈到“天然气与煤炭”时,我不是在进行辩论。我是在谈论一种替代曲线。
在某些时候,系统会燃烧更多的天然气并将煤炭排出。在另一些时候,系统会依赖煤炭。而且不是因为人们突然改变了主意。而是因为相对的权衡发生了变化,约束使得在那个时刻更容易或更难进行转换。
这就是领导者的观点:市场不会以一种干净、线性的方式进行替代,仅仅因为出现了一种新的选择。它们在权衡对实际约束有意义时才会进行替代。
这表现为一种非常常见的业务失败模式。你查看一个替代选项,查看“更好的”产品,并假设旧的东西即将被清除。然后它没有发生。然后你决定市场是不理性的。
大多数时候,这并不不理性。大多数时候,你忽略了替代曲线。
煤炭就像 SAP:旧的不代表消失
我发现向商业受众解释这种方式的最简单方法是使用与电力无关的例子。煤炭就像那些存在的旧企业公司,比如 SAP。即使其他公司轮换到“最有价值”的位置,SAP 仍然值很多钱,并且仍然在欧洲高端市场中占有一席之地。
你可能会想象 SAP 会被 Palantir 和这些能够解决许多相同问题的新公司所清除,但事实并非如此。这是因为替代成本不仅仅是“我们为 SAP 支付多少美元与我们为 Palantir 或 Salesforce 支付多少美元?”存在粘性市场效应和其他因素导致 SAP 的持久性。
而且这是因为替代成本不仅仅是“我们为 SAP 支付多少美元与我们为 Palantir 或 Salesforce 支付多少美元?”存在粘性市场效应和其他因素导致 SAP 的持久性。
这就是领导者在关注“更好的”故事时所误读的内容。他们将替代视为功能比较或价格比较,并假设市场会像电子表格一样表现。
但现有企业在转换很麻烦时会持续存在。
即使替代方案确实很强大,人们也希望故事是干净的。领导者希望它是干净的,因为这会让规划感觉干净。但如果你实际上试图实现转换,你需要像你在曲线上的那样思考,而不是像在仲裁辩论那样思考。
因为在真正的市场中,你可以拥有一个看起来明显“更好”的产品,但仍然看不到转换以你想要的速度发生。
领导者可以实际使用的替代清单
那么,你如何实际使用这个?
如果你试图理解竞争动态,或者你试图在自己的公司中替换某物,你需要一个替代清单。而不是一张说“新的是好的,旧的是坏的”的幻灯片。一张清单,迫使你命名权衡和约束。
我用来的是:
替代品有哪些?不要只列出你最喜欢的。列出人们实际上使用的替代品。
什么触发了转换?为了使转换变得合理,必须有什么是真的?
替代成本是什么?不仅仅是美元。在实践中出现的其他成本。
粘性市场效应是什么?现有企业即使存在替代品也能持续存在的理由。
什么约束阻止了转换,即使替代品看起来更好?使“显而易见的”举动不显而易见的因素。
如果你诚实地做到这一点,许多“令人惊讶”的结果就不再令人惊讶了。
领导者的错误是查看较新的选项并假设替代是自动的。领导者的错误是专注于叙述而不是曲线。在电力领域,你看到的是燃料转换。在企业软件中,你看到的是即使替代故事很有说服力,现有企业仍然持续存在。
停止争论故事,开始绘制曲线
如果你试图在竞争性转变中发挥领导作用,那么问题不是“哪一方是对的?”问题是,“权衡是什么,什么约束塑造了替代曲线?”
这就是为什么天然气与煤炭是一个有用的视角。它训练你停止以二元方式思考。它训练你停止假设“更好”意味着“被取代”。它训练你问的是,为了使转换发生,实际上需要什么。
如果你想在一个市场或公司中做出良好的决策,你不需要辩论。你需要一个替代清单,并且你需要认真对待粘性市场效应。
订阅 Entrepreneur Daily 电子报,以获取今天帮助你更好地建设业务所需的新闻和资源。
四大领先AI模型讨论这篇文章
"Sticky switching costs will keep SAP's installed base and margins intact longer than Palantir-led disruption models price in."
The article frames market substitution as a constrained curve rather than linear replacement, using coal-to-gas and SAP examples to show why incumbents endure despite superior alternatives. For investors this implies legacy enterprise software names can sustain cash flows and multiples longer than disruption narratives assume, especially where integration, compliance, and data-migration costs dominate. Capital allocators should therefore stress-test revenue forecasts against explicit switching triggers rather than feature comparisons alone. Overlooking these frictions risks mispricing both defenders and attackers in sectors with high switching inertia.
Generative-AI tooling is already compressing integration timelines and data-mapping costs, which could flatten the substitution curve faster than historical energy or ERP precedents suggest and accelerate displacement.
"Substitution curves are real and matter, but the article provides a diagnostic framework, not a predictive model—and conflates 'slow adoption' with 'rational persistence,' which are not the same thing."
This is a framework essay, not financial news—it's about decision-making under constraints, not a market call. The core insight is sound: substitution rarely follows clean narratives. SAP persisting despite 'better' competitors (Salesforce, Palantir) is real; switching costs—integration, retraining, organizational risk—are genuinely sticky. But the article conflates two different problems: (1) why incumbents survive when cheaper alternatives exist (valid), and (2) whether they survive when fundamentally superior AND cheaper alternatives exist. Those are different curves. The article also assumes 'better' is subjective or hard to measure, when in many markets it's brutally objective—cloud beat on-prem not through narrative but through measurable economics.
The article's framework could rationalize any outcome as 'the curve is just complex'—a tautology that explains everything and predicts nothing. If SAP persists, it's 'sticky effects.' If SAP collapses, it's 'the tradeoff finally shifted.' Without quantifying what those constraints actually are (switching cost in dollars? time? risk premium?), this is sophisticated hand-waving, not actionable analysis.
"The 'substitution curve' is not static; it is being rapidly compressed by AI, turning legacy technical debt from a defensive moat into a terminal liability."
The article correctly identifies that 'better' is not a proxy for adoption, but it dangerously undersells the role of technical debt and regulatory capture in enterprise software. While SAP remains dominant due to high switching costs and deep integration, the 'substitution curve' is increasingly being compressed by AI-driven modularity. Investors often mistake persistence for moat strength; in reality, companies like SAP or legacy utilities are often just beneficiaries of inertia. When the cost of integration drops—as we are seeing with LLM-based API orchestration—that 'messy' substitution cost collapses, leading to a sudden, non-linear displacement that the author’s model might miss.
The author assumes that 'sticky market effects' are a permanent feature, potentially ignoring that technological disruption eventually reaches a tipping point where the cost of maintaining the legacy system exceeds the cost of a total platform rip-and-replace.
"Substitution is a curve shaped by constraints; the decisive signals are policy, financing, and grid/capital costs that bend the curve, not simple 'better' narratives."
Short take: the article nails a real risk in strategy and investing—substitution is curved, not a clean 'better replaces worse' switch. Leaders misprice the timing by fixating on the new option's efficiency and ignoring switching costs, incumbents' ecosystems, and sticky market effects. The strongest risk to this view is when policy, regulation, or financing collapses the cost of adoption or imposes penalties for keeping old tech, accelerating the curve far faster than the narrative suggests. Missing context includes network effects, supplier lock-in, and capital cycles; in energy, grid upgrades and carbon pricing can compress the curve dramatically.
Policy tailwinds and rapid cost declines have disrupted sectors faster than expected in the past. If you discount that, you risk underpricing upside in early-stage disruption.
"AI-driven integration cost cuts give the substitution curve testable numbers instead of remaining descriptive."
Claude flags the framework as potentially tautological without dollar or time metrics, yet Gemini's LLM orchestration example supplies one: migration pilots now cut ERP integration from 18 to 9 months. That measurable compression directly tests the article's sticky-effects claim for SAP and utilities, turning vague constraints into forecast inputs rather than post-hoc explanations, especially when paired with carbon-pricing deadlines.
"Pilot-stage migration speedups don't prove the substitution curve has fundamentally shifted at enterprise scale."
Grok's 18-to-9-month compression is concrete, but it's a pilot metric—not yet production-scaled across thousands of legacy SAP installations. The real test: does that 50% speedup hold when you're migrating a $2B global finance operation with 15 years of custom code? Gemini assumes LLM orchestration scales linearly; I'd want to see failure rates and hidden costs before declaring the substitution curve actually flattened. Pilots compress; production deployments often don't.
"The substitution curve is constrained more by organizational risk aversion than by the technical speed of migration."
Claude is right to demand production-scale data, but both Grok and Gemini miss the real bottleneck: human risk aversion. Even if LLMs halve migration time, CIOs aren't incentivized to rip out stable SAP backbones for a 50% efficiency gain if the failure risk is catastrophic. The substitution curve isn't just about technical cost or integration speed; it’s about the career-ending risk of a failed core ERP migration. That's the 'sticky' variable that won't compress.
"Production-scale economics and governance/compliance risks will dominate, so migration speed alone won't flatten the substitution curve."
Gemini overplays the 'human risk' blocker as the sole limiter. Yes, CIOs fear catastrophic migrations, but the bigger gating factor is architectural debt and data governance risk across multi-tenant, regulated environments. Pilot cost and user adoption matter, but production-scale economics--total cost of ownership, auditability, and regulatory penalties for outages--will often trump migration speed. Without quantifying those, the 18->9 months metric risks overstating the curve flattening.
The panel generally agreed that market substitution is not linear but follows a curved path due to high switching costs, integration challenges, and other frictions. However, they also noted that this curve can be compressed or accelerated by technological advancements, regulatory changes, or other external factors.
Technological advancements, such as AI-driven modularity and LLM-based API orchestration, can compress the substitution curve and lead to sudden, non-linear displacement of incumbents.
Human risk aversion and the fear of catastrophic migrations can act as a significant barrier to market substitution, even when technical costs and integration times are reduced.