Workday Plans to Buy Honeydew: What You Need to Know

Workday plans to acquire Honeydew to bring shared business definitions to AI and analytics. Here’s what IT teams should check before planning an integration.

Written By
Matt Gonzales
Matt Gonzales
Nov 19, 2026
Workday Plans to Buy Honeydew: What You Need to Know

Workday logo displayed on a laptop in an office. Image: Generated via OpenAI/ChatGPT

An AI answer is not much help if the dashboard beside it tells a different story.

Workday announced plans on Nov. 18 to acquire Honeydew, a semantic-layer company whose technology gives analytics tools and AI agents shared business definitions. Announced at Workday Rising EMEA in Barcelona, the proposed deal targets a practical problem for HR, finance, and IT teams: getting different systems to calculate business metrics consistently.

For buyers, the question is whether the organization can explain how a number was calculated, who was allowed to request it, and whether another tool would produce the same result.

What Workday plans to add

Workday intends to combine Honeydew’s semantic compiler with Workday Data Cloud. The compiler translates business definitions into governed queries, rather than leaving each application to interpret a metric independently.

The transaction is expected to close during Workday’s fiscal fourth quarter, which ends Jan. 31, 2027, subject to customary closing conditions. The announcement does not disclose a purchase price or a customer availability date for the integration.

Advertisement

That makes this an acquisition plan, not a feature rollout customers can schedule today. Workday’s promised benefits will need to be tested against actual implementations.

How a semantic layer changes the calculation

A semantic layer describes what business data means. Instead of making every dashboard or assistant maintain its own calculation, teams establish definitions that multiple applications can reuse.

In its modeling documentation, Honeydew describes how to define business objects, their relationships, and metrics such as revenue or retention. Its compiler uses those definitions to construct SQL, the language used to query databases.

Teams can also build narrower versions of a shared model. Honeydew says those versions can apply regional filters, exclude personally identifiable information, or specify a warehouse role while retaining common definitions.

This distinction matters: Consistent answers do not necessarily mean identical answers for every employee. Different access rights or business contexts may legitimately produce different results. The important part is making those differences deliberate and explainable.

Advertisement

That is a data-governance challenge for AI systems, not just a question of choosing a more capable model.

Consistency does not replace quality or security

A shared calculation can still operate on incomplete or outdated records. Businesses should separate data quality from data governance: Agreeing on a formula does not establish that every underlying record is correct.

Access controls need their own scrutiny. Honeydew’s interface documentation describes connections through Model Context Protocol, SQL, and GraphQL. It also describes per-agent identities with configurable permissions and lifetimes.

Those are descriptions of Honeydew’s current product, not confirmation that every capability will appear unchanged inside Workday.

For security teams, a useful evaluation should examine the connection between data governance, security, and privacy. Can an agent retrieve only the information its task requires? Can administrators reconstruct the query behind an answer? What happens when an employee changes roles, or an agent’s access expires?

Advertisement

What IT teams should ask before committing

For organizations evaluating the proposed integration, start with a small set of consequential metrics rather than a broad demonstration.

Choose questions that already produce disagreements across reports. Document the approved calculation, reporting period, source records, and authorized audience. Then ask a prospective implementation to reproduce those answers through different interfaces.

Include failure cases. Test a restricted account, a missing record, a changed definition, and a question that is too ambiguous to answer safely. A system that requests clarification may be more useful than one that returns a confident but unjustified number.

Buyers should also request clear answers on licensing, supported data sources, migration work, and availability before including the integration in a project budget.

The immediate task is preparation, not migration. Identify which definitions the business trusts now and who owns them. That gives IT teams something concrete to test when Workday provides integration details.

Advertisement

Related reading: Why AI agents are creating insider-security blind spots.

Matt Gonzales

Matt Gonzales is a technology journalist, editor, and content strategist with more than a decade of experience covering emerging technologies, enterprise IT, cybersecurity, artificial intelligence, and workplace innovation. As Managing Editor for eWeek and TechRepublic, he leads editorial strategy and newsroom operations while helping business and IT leaders navigate an evolving technology landscape. Throughout his career, Matt has held leadership roles overseeing content development, editorial planning, and newsroom operations across digital publications and enterprise media organizations. Before joining TechnologyAdvice, he served as an editor at SHRM, where he covered workplace trends and emerging technologies, and as Lead Writer and Editor for Marine Corps Systems Command, where he reported on defense technologies, innovation initiatives, and government technology programs. Matt's expertise spans cybersecurity, enterprise technology, AI, B2B software, technical writing, and digital publishing. He has reported on major technology developments, including the rapid evolution of generative AI, helping readers understand both the opportunities and risks associated with emerging technologies. His work combines deep research, editorial rigor, and practical business insights to make complex technical topics accessible to a broad audience. An award-winning journalist, Matt has earned recognition for excellence in reporting and editorial leadership. He holds a Bachelor of Science in Communication with a concentration in Journalism from East Carolina University and continues to focus on delivering trusted analysis and actionable insights for technology, cybersecurity, and business professionals.