📝 官方博客Databricks BlogDoubao · 实盘不做把握 8/10不做原因:无可交易标的
北京时间·🕒 发布 08:01:41(美西 10-19 17:01)时区推断·⟳ 抓取 08:23:06·⚡ 决策 10-20 08:24:43 +1m37s·7.5 天前
Databricks 官博发布 HP 采用 CustomerLake/Genie 建营销数据底座的客户案例,无合同金额、双方均无可交易催化
这是一篇供应商官博的客户成功营销文:发布方 Databricks 仍是私有公司(2026 年明确不上市),被宣传客户 HP 只是分享内部数据平台使用体验,全文无合同金额、无收入/指引变化、无产品 GA 或竞争格局改变,TCO 降 40% 等为早期自述且落在营销 IT 开支层面,对 HPQ 不构成可交易的基本面增量,也没有可坐实的产业链映射标的。
📄 原文Databricks Blog↗ 原文
How HP Is Building an AI-Ready CDP with Databricks CustomerLake
At Data + AI Summit 2026, Luis Alonso, Global Head of Data Strategy & Engineering for MarTech & AI Enablement at HP, sh…
不做 HP Inc.(HPQ.US)
HP 仅作为 Databricks 客户案例出现,无订单金额、无业绩/指引变化,营销 IT 效率轶事相对其营收规模不具 materiality,不构成可交易催化
不做 Databricks(私有,无公开证券)(N/A)
发布方 Databricks 2026 年明确不 IPO、仍为私有公司,仅私募市场可转让,无可公开交易的股票或单股杠杆产品
展开详情(成交明细 / 研究档案 / 原文全文 / 决策记录链)
研究档案
结论摘要
Databricks 官博借 HP 之口宣传 CustomerLake/Genie,属品牌性客户案例,无商业金额与业绩指引;Databricks 未上市、HPQ 仅为被引用客户且影响微不足道,故无正期望可交易标的,回避。
消息传播链
- Databricks 官博发布 HP 采用 CustomerLake/Genie 的客户案例,时间仅精确到日期,无第三方转载或市场反应可确认,属供应商自发营销内容
关键理由
- 事件性质为供应商官方营销案例,不构成任何上市主体的新增合同、订单、业绩或指引信息
主要风险
- 文中“TCO 降 40%”“两小时受众就绪”等为 HP 个人陈述的早期/潜在结果,未经独立验证,也不能外推为 HP 利润或 Databricks 收入
反向证据
- 做多前查反向 · 来源 web · 日期 2026-10-20 · 影响 invalidates
全文及检索均无采购金额、收入贡献或 HP 指引调整,仅为内部效率叙事,无支撑 HPQ 做多的基本面增量
检索:HP Databricks CustomerLake 合同金额 订单 业绩 指引 原文 ↗
先例如何影响了这次决策
对本次决策的影响:未据此下任何交易腿;无可交易标的与无 materiality 的判断由事件性质与上市状态直接得出
方向:无可比交易类事件:供应商官博客户成功故事对被引用客户股价通常无可测向的增量影响
涨幅量级:无高相似对齐先例,且本案不产生订单/业绩数字,无法也无需校准幅度
形态:不适用
工具执行结果 · 成功 2 · 降级 0 · 失败 0 · 取消 0
- search_processed_events 成功 stock_tools HTTP · 12 ms
{"result": "search_processed_events:agent query=`data + ai summit 2026 hp martech ai-ready cdp | databricks hp customerlake genie marketing lakehouse case study | hp databricks cdp customerlake 数据湖 案例`;结构化索引覆盖完整 72 小时;旧记录兼容扫描近 0.0/72 小时、0 条本臂决策(完整),返回 0 条候选。未命中只表示这些 agent query 表达式没有召回候选,不能据此证明消息首发或 - web_search 成功 doubao_search · 1,457 ms
豆包搜索结果(原始查询:Databricks IPO 2026 publicly traded ticker listing status;API SearchType:web)
原文全文
展开原文 · 6,116 字
At Data + AI Summit 2026, Luis Alonso, Global Head of Data Strategy & Engineering for MarTech & AI Enablement at HP, shared how the company is building an AI-ready go-to-market data foundation on Databricks.
HP has spent extensive time and effort unifying customer data and third-party signals in their Marketing Lakehouse, and now Genie and CustomerLake make that trusted context available to marketers making daily decisions about audiences, channels, and customer journeys.
HP’s early work highlights three ways this approach can reduce costs, expand available customer context, and accelerate activation:
For HP, a CDP isn't one product or a narrow set of activation features. It's a collection of capabilities built around the needs of the business:
As HP consolidated more governed data and business logic on Databricks, maintaining a separate CDP increasingly meant duplicating pipelines, data and operational overhead. Composable architectures reduced some data movement, but the activation layer still lacked the business definitions, context, and governance already available in the data platform.
That context is essential for self-service analytics and AI agents. Without it, an agent may be able to access data but still lack the definitions, relationships, metrics and governance needed to use it correctly.
HP's broader data transformation consolidated hundreds of data lakes and repositories into a small number of Databricks lakehouses. The company uses central standards with federated execution, allowing domain experts to retain ownership and stewardship while sharing governed data products across the business.
This gave marketing governed access to previously fragmented sources, including media performance, market-share, technographic and intent data, along with propensity models.
The change has materially changed how HP teams work together.
Alonso described a 2024 request to share data with a sales partner that required three months, roughly 15 email exchanges and three escalations, without a reliable outcome. Today, a comparable request can result in a governed Delta Sharing asset within 48 hours.
That improvement gives marketing faster access to the data it needs for planning, targeting, reporting and measurement, while preserving domain ownership and governance.
Creating a strong technical foundation doesn't automatically make data usable for marketers. The next step is enabling executives, marketing users, media teams and analysts to use that foundation without relying on engineering for every question or task.
HP is using AI/BI Genie and agent-based capabilities to help bridge that gap across three layers of work:
Business context is a core part of that strategy. HP is developing semantic layers that help Genie understand what the company's data means, including domains, metric views, instructions and reusable skills.
For example, HP created a media metric view covering 26 dimensions and 10 measures. This centralizes definitions for media-spend and performance KPIs so dashboards, business users and AI systems can work from the same source of truth.
HP has also expanded its intent-data ingestion from 75 topics to approximately 20,000 topics. Genie Code helps the team plan how to cluster those signals at scale and use them for richer account profiles.
HP is also rethinking where identity resolution should live. Historically, companies often sent customer data to an external identity provider and kept the resulting identity layer outside their core data environment.
HP plans to bring identity signals back into its Databricks environment. That creates a governed foundation for measurement, audience activation and model improvement. Data can flow through the same identity service on its way to media platforms and on the return path, helping HP build a more complete view of performance and continuously improve its models.
Alonso noted that reaching even 10% of HP's consumer customer base through this consent-preserving approach could create a substantial new opportunity for the commercial business.
HP's early experience with CustomerLake illustrates the potential of bringing marketing capabilities directly to the governed data foundation.
Based on the team's prior CDP implementations, Alonso expected a long setup process involving extensive meetings, documentation, data-model configuration, and privacy and security reviews.
The initial experience was dramatically simpler.
“We had our data models in place, we had attributes published, and we were ready to build audiences — work that might have previously required two or three months to complete.”
Because CustomerLake is native to Databricks and Unity Catalog, HP's team could work directly with their schemas, tables, definitions, and governance, instead of recreating context in a separate platform.
The architecture also supports a significant B2C-to-B2B opportunity. HP has hundreds of millions of consumer customers, but a much smaller known population of business contacts. CustomerLake makes it possible for HP to work across both their B2C and B2B data models and systems in one environment through a shared identity layer. HP can also incorporate data from other platforms using Lakehouse Federation.
Across the go-to-market roadmap, HP is evaluating value in three areas:
HP’s work with Genie and CustomerLake suggests potential to address all three areas together. Their journey offers four practical takeaways for other enterprises modernizing their marketing stack:
HP’s journey shows that modernizing marketing activation and applying AI at scale both depend on bringing data, intelligence, and action together on the same foundation. With CustomerLake and Genie on its governed Marketing Lakehouse, HP is giving marketers and agents direct access to trusted context without recreating it across disconnected systems. The early results include becoming audience-ready in two hours instead of months, with the potential to reduce CDP TCO by up to 40%. Together, these gains lay the foundation for faster, more intelligent and more personalized customer engagement at scale.
HP has spent extensive time and effort unifying customer data and third-party signals in their Marketing Lakehouse, and now Genie and CustomerLake make that trusted context available to marketers making daily decisions about audiences, channels, and customer journeys.
HP’s early work highlights three ways this approach can reduce costs, expand available customer context, and accelerate activation:
For HP, a CDP isn't one product or a narrow set of activation features. It's a collection of capabilities built around the needs of the business:
As HP consolidated more governed data and business logic on Databricks, maintaining a separate CDP increasingly meant duplicating pipelines, data and operational overhead. Composable architectures reduced some data movement, but the activation layer still lacked the business definitions, context, and governance already available in the data platform.
That context is essential for self-service analytics and AI agents. Without it, an agent may be able to access data but still lack the definitions, relationships, metrics and governance needed to use it correctly.
HP's broader data transformation consolidated hundreds of data lakes and repositories into a small number of Databricks lakehouses. The company uses central standards with federated execution, allowing domain experts to retain ownership and stewardship while sharing governed data products across the business.
This gave marketing governed access to previously fragmented sources, including media performance, market-share, technographic and intent data, along with propensity models.
The change has materially changed how HP teams work together.
Alonso described a 2024 request to share data with a sales partner that required three months, roughly 15 email exchanges and three escalations, without a reliable outcome. Today, a comparable request can result in a governed Delta Sharing asset within 48 hours.
That improvement gives marketing faster access to the data it needs for planning, targeting, reporting and measurement, while preserving domain ownership and governance.
Creating a strong technical foundation doesn't automatically make data usable for marketers. The next step is enabling executives, marketing users, media teams and analysts to use that foundation without relying on engineering for every question or task.
HP is using AI/BI Genie and agent-based capabilities to help bridge that gap across three layers of work:
Business context is a core part of that strategy. HP is developing semantic layers that help Genie understand what the company's data means, including domains, metric views, instructions and reusable skills.
For example, HP created a media metric view covering 26 dimensions and 10 measures. This centralizes definitions for media-spend and performance KPIs so dashboards, business users and AI systems can work from the same source of truth.
HP has also expanded its intent-data ingestion from 75 topics to approximately 20,000 topics. Genie Code helps the team plan how to cluster those signals at scale and use them for richer account profiles.
HP is also rethinking where identity resolution should live. Historically, companies often sent customer data to an external identity provider and kept the resulting identity layer outside their core data environment.
HP plans to bring identity signals back into its Databricks environment. That creates a governed foundation for measurement, audience activation and model improvement. Data can flow through the same identity service on its way to media platforms and on the return path, helping HP build a more complete view of performance and continuously improve its models.
Alonso noted that reaching even 10% of HP's consumer customer base through this consent-preserving approach could create a substantial new opportunity for the commercial business.
HP's early experience with CustomerLake illustrates the potential of bringing marketing capabilities directly to the governed data foundation.
Based on the team's prior CDP implementations, Alonso expected a long setup process involving extensive meetings, documentation, data-model configuration, and privacy and security reviews.
The initial experience was dramatically simpler.
“We had our data models in place, we had attributes published, and we were ready to build audiences — work that might have previously required two or three months to complete.”
Because CustomerLake is native to Databricks and Unity Catalog, HP's team could work directly with their schemas, tables, definitions, and governance, instead of recreating context in a separate platform.
The architecture also supports a significant B2C-to-B2B opportunity. HP has hundreds of millions of consumer customers, but a much smaller known population of business contacts. CustomerLake makes it possible for HP to work across both their B2C and B2B data models and systems in one environment through a shared identity layer. HP can also incorporate data from other platforms using Lakehouse Federation.
Across the go-to-market roadmap, HP is evaluating value in three areas:
HP’s work with Genie and CustomerLake suggests potential to address all three areas together. Their journey offers four practical takeaways for other enterprises modernizing their marketing stack:
HP’s journey shows that modernizing marketing activation and applying AI at scale both depend on bringing data, intelligence, and action together on the same foundation. With CustomerLake and Genie on its governed Marketing Lakehouse, HP is giving marketers and agents direct access to trusted context without recreating it across disconnected systems. The early results include becoming audience-ready in two hours instead of months, with the potential to reduce CDP TCO by up to 40%. Together, these gains lay the foundation for faster, more intelligent and more personalized customer engagement at scale.
决策记录链 · 只追加
每次领取产生一条记录,重新决策追加一条并以 supersedes 指向被替代的记录(ADR 0014)。
a9cfdeef05· 2026-10-20 08:24 · doubao / doubao-seed-evolving-latest-version · 策略包658c0c1e2ba5当前