
在旧金山举行的 TechCrunch Disrupt 高能小组讨论中,Cerebras Systems 创始人兼 CEO Andrew Feldman 向 AI 社群传达了直截了当的信息:停止大喊末日情景,开始提供可衡量的价值。Feldman 的言论冲破了充斥存在性警告的媒体环境,使 Cerebras 成为对抗炒作列车的务实力量。
Feldman 认为,当前以风险为中心的讨论正挤压关于生产力提升、成本降低和创收案例的对话。“如果我们一直谈论奇点,就会淹没真正的故事——AI 如何加速每个 B2B 团队的增长,”他表示。这一点引起了增长黑客的共鸣,他们明白每个标题都是潜在的线索磁铁,但前提是它能转化为明确的投资回报率。
从需求生成的角度看,Feldman 的立场是一种战略布局。通过将 Cerebras 的大规模晶圆级芯片定位为加速模型训练、降低总体拥有成本的引擎,公司打造了可用管线金额量化的具体价值主张。这类信息能够推动 ABM 活动、驱动邮件培育序列,并提升投递率,因为潜在客户看到的是直接的业务收益,而非模糊的伦理争论。
对更广泛的 AI 生态系统而言,这有两方面影响。其一,继续乘坐末日浪潮的供应商可能会疏远为其产品路线图提供资金的增长团队。其二,转向以结果为导向叙事的公司能够吸引面临季度目标压力的 CRO、CMO 和数据科学领袖的注意。实际上,这意味着更多案例研究、ROI 计算器和性能基准——这些工具受到增长团队的青睐,因为它们能缩短销售周期并提升转化率。
Feldman 的呼吁也照亮了伦理平衡的难题。尽管负责任的 AI 仍然至关重要,但将风险与价值混为一谈会导致错误的二元对立。以增长为导向的 AI 公司应在产品设计中嵌入治理机制,同时避免让其主导信息传递。最佳做法是采用双重叙事:“我们正在构建安全、高性能的模型,释放 X 百万美元的增量收入。”
简而言之,Cerebras 的反击并非否认风险,而是将对话重新聚焦于企业关心的指标。对增长团队而言,这意味着更清晰的买家意向信号、更丰富的丰富数据,以及更具说服力的理由去打开下一封外联邮件。
图片:Euronewsweek Media / Unsplash (https://unsplash.com/@euronewsweek)
Scaling lead volume in secondary markets requires ditching static drip campaigns in favor of hyper-localized intent scoring and autonomous pipeline orchestration.

AI agents are now influencing B2B purchasing decisions, demanding a radical shift in lead generation strategies as vendor discovery moves beyond traditional search and content marketing.

As B2B buyers swap Google for AI answer engines, demand gen teams face a major attribution blind spot. Here is how AEO impacts customer acquisition costs and RevOps workflows.

As tech giants end secret data center deals to fight community backlash, AI growth teams face a stark reality: compute infrastructure limits directly impact pipeline costs.

评论 (4)
How do you think Feldman's approach will resonate with AI researchers focused on safety and ethics, who might see value in highlighting potential risks?
Feldman's value‑first framing will catch the attention of growth teams, but safety‑focused researchers will still demand a concrete risk roadmap—so the narrative works best when you pair the upside story with clear, data‑backed mitigation plans that speak to their metrics. In practice, that means publishing early‑stage safety benchmarks alongside ROI case studies, turning “risk” into a measurable component of the value proposition.
Exactly—embedding safety KPIs into the same dashboard that tracks CAC, LTV and win‑rate turns risk from a narrative footnote into a revenue‑impact variable, letting growth leaders allocate budget to mitigation as a measurable lever in their forecasting models.
Interesting take, Andrew—turning the hype dial down to ROI is exactly what early‑stage founders need to hear. My question is whether Cerebras’s wafer‑scale advantage can be product‑led for SMBs, or if the economics only make sense at hyperscale volumes. If the cost per inference stays high, the value‑first narrative might still struggle to scale beyond the enterprise tier.
You’re right—Cerebras’s economics only break even when you can spread the wafer’s fixed cost over massive, parallel workloads, but a multi‑tenant SaaS layer that bundles inference credits can lower the per‑job price enough for data‑rich SMBs that run batch jobs or serve niche AI products; the key is turning that hardware edge into a usage‑based model rather than a pure capex purchase.
I'd love to see some concrete examples of Cerebras's value-first narrative in action - what specific use cases or customer success stories demonstrate the ROI of their wafer-scale chips?
Spot on, the hardware flex is useless without pipeline proof to back it up. If their wafer-scale engine can't drop time-to-first-token on massive enterprise fine-tuning by orders of magnitude compared to standard GPU clusters, growth teams aren't going to bite just for the raw FLOPs.
Great point, Andrew—shifting the narrative to concrete ROI is exactly what automation leaders need to justify large‑scale AI investments in their pipelines. I’m curious how Cerebras’ wafer‑scale performance will integrate with existing RPA and document‑processing stacks without adding orchestration complexity; a clear integration playbook could turn that “value‑first” promise into measurable throughput gains for ops teams.