---
title: "Why HelloFresh chose Atlan"
url: "https://atlan.com/why-hellofresh-chose-atlan/"
description: "Why HelloFresh chose Atlan as its data catalog: what the team needed solved and what tipped the decision."
keywords: "DataOps Platform, Platform Demo, Atlan Demo, Atlan Platform"
---

> Atlan is hosting Context Conference, bringing together the leaders and builders at the frontier of giving AI the context it needs to understand their business. It runs online on October 28, 2026, from 11:00 AM to 2:00 PM ET. Atlan co-founder Prukalpa Sankar opens and closes the day. Leaders from AstraZeneca, BNY and Verizon share why they invest in context and what they get from it. Registrants get early access to The AI Context Gap, a new study from MIT Technology Review Insights. Register: https://atlan.com/context-conference/

# Why HelloFresh chose Atlan

Videos / On demand / Recorded October 20, 2023 / 2:31

Watch: https://atlan.com/why-hellofresh-chose-atlan/

Natalie Hallak of HelloFresh on what decided it: column-level lineage from first point of entry to the dashboard, found during a POC that turned up 10 to 15 different names for customer name.

## Speakers

- Natalie Hallak, Director of Global Data Management, HelloFresh

## Related videos

- [HelloFresh on Atlan's data impact analysis](https://atlan.com/why-atlan-s-data-impact-analysis-was-a-game-changer-for-hellofresh/) (1 min)
- [HelloFresh's migration to Atlan in weeks](https://atlan.com/migrating-to-atlan-in-weeks-with-minimal-engineering-effort/) (1 min)
- [How Atlan reverse-engineers column-level lineage](https://atlan.com/know/enterprise-context-layer/videos/column-level-lineage-reverse-engineering/) (3 min)
- [The context layer, live (product demos)](https://atlan.com/context-layer-demo/) (62 min)

## Transcript

**Natalie Hallak**

[0:05] So like, like I mentioned at the beginning, for us the, the key, the main big thing was the data lineage, right? But not from like a, a high level, but all the way to the column details. And then one of the things that we saw during the POC is we had more than 10, if not 15 different ways of calling customer name, right? So we realized that the way we were standardizing even columns was completely different from, from team to team. But the data lineage was one of the biggest winner compared to the other data catalog we saw even during our POC, right?

[0:45] The data lineage was the most important, just to have that understanding of where's the first point of entry of the data all the way down to which dashboard it's, it's being used. And you know, just having the, the right owner and the right understanding of description was quite key for us. So I would say this is one of the biggest differentiator. I mean, I, I... There's a lot more, but yeah, this was a key thing for us. Initially, we, we had quite a bit of resistance because we actually had two previous data catalog before moving to Atlan.

[1:22] So a lot of the initial thought is, "Okay, here we go with another data catalog, which I might never use." But one of the things that we've done during our POC was to engage with different personas across different data domains team, right? To, to really understand the use cases, the pain points in order to bring that into, into the POC. And this started to excite quite a lot of, of people, right? And that facilitate a lot of the choice for us to go with Atlan compared to, for example, other data catalog where we've done also a POC for.

[2:05] So really, I would say really understanding the different pain points of the different personas because a data engineer will have different problems than, you know, from what the business is looking for. We used to get quite a lot of Slack messages saying, "When can I use Atlan?" Or some people were already seeing the value of Atlan during the POC itself.