Events

How to find the true ROI of the modern data stack | Census

Nicole Mitich
Nicole Mitich May 11, 2023

Nicole Mitich is the content marketing manager @ Census. She's carried a love for reading and writing since childhood, but her particular focus is on streamlining technical communication through writing. She loves seeing (and helping) technical folks share their wisdom. San Diego, California, United States

With more data flowing through companies than ever before, and competitors scrambling to be the best and fastest at operationalizing it, the modern data stack is increasingly seen as a must-have – at least among data folks.

But implementing these tools still requires buy-in from the business side. So, the burning question is, “How do we measure the ROI of the modern data stack?”

This was the main topic of discussion in our recent webinar, Proving the Value of Your Modern Data Stack with Google and Montreal Analytics. It featured some folks who do a lot of thinking about the impact your data stack has on ROI.

To kick things off, they all agreed: When making the case for data investment, you have to communicate the costs and value of both the tools and the people who run them. ⚒️➕😀

ROI = Goals achieved ✅

“It starts with the capital expenses – moving into a modern data stack or modernizing the tools you have,” said Jobin George, staff solutions architect at Google. “Once the migration is done, then comes the operating expenses. Who is going to run the show?”

Many stacks are a blend of first-party services, cloud providers, and third-party tools. Cost calculations should include the cost of the tool, consultants who help with migration, and ongoing use and support. With all those moving parts, it’s tricky to figure out where to attribute value.

“It’s difficult to pinpoint what is good across all companies,” agreed Yoni Hazan, lead analytics consultant at Montreal Analytics. “Tooling and personnel are line items that impact the finances of companies really differently. A small company and a large company are going to have different needs and require different skill sets.”

What you need from your data stack is likely to grow over time. You’ll eventually need more computation, more headcount, and more consultants. 

But that might seem alarming to finance folks. 😱 To ease their anxieties, they have to see the return the company can expect from its modern data stack investment.

“Costs can be directly proportional to how much your team wants to achieve,” Jobin said. “Thoroughly research what your deliverables are so you don’t implement things you don’t really need. First, be sure you understand the problem, then invest only in the necessary areas to solve it.”

Beware of falling down the rabbit hole of marketing hype and buying tools that solve problems you don’t have. Because once you have the tool, you have to invent “problems” for it to solve just so you can justify the expense – and that’s a waste of time and money.

Ultimately, choosing which problems to tackle all ties back to company goals. Data teams tend to be pretty good at setting objectives for themselves, but often forget to set goals that will move the entire business forward. ⏩ 

The elements of your modern data stack should directly connect to business objectives. So, if your company is really focused on reducing costs, you might turn up the heat on improving processes and automation. If you’re focused on revenue growth, you should concentrate on embedded analytics, data shares, and data clean rooms.

But even once all objectives are aligned and data folks take on more of a consultant role in their own organizations, they often struggle to connect business team results back to the data team’s contributions.

“The data team takes the costs and experiences few of the benefits,” said Paul David, director of sales at Census. “You don’t see sales teams proving the data team’s ROI by saying, ‘Hey, the data made this measurable impact in ROAS.’”

One way to combat this is to borrow the agile approach from engineering: You tackle specific, small goals to show value on a simple cadence. This framework is scalable, measurable, and helps stakeholders see the ROI. 💡

“It helps people understand what we’re trying to achieve and the value,” Yoni said. “What’s beautiful about the modern data stack is, within clicks, you can start generating value.”

Getting buy-in for the modern data stack

The biggest obstacle a lot of data teams face when making the case for modern data stack investment is sunk costs. Especially in a tough economy, it’s hard to convince the C-suite to fund a shift away from the systems and processes they’ve already invested in – even if everyone knows it’s the right move in the long run.

Many legacy data stacks are built on "value” versions of open-source software self-supported by a team of smart data engineers. Jobin said he’s seeing a lot of companies migrating these stacks into fully-managed or semi-managed versions that let the data team hand off day-to-day management and focus on generating revenue.

“The call is between employing a bunch of really smart people on a mediocre platform or a small team of smart people on an awesome platform,” he said. “You have to choose the option that’s right for you.”

Investing in more managed systems can create stability in the entire data ecosystem. Paul said he’s seen plenty of instances where companies build processes that are cheap from a software perspective, but rely on one or two superhero engineers who wrote the custom script that runs everything. 🦸🦸‍♀️

“From a cost perspective, it’s particularly expensive to invest in getting a stack up and running when a single person leaving their role can bring the whole thing crashing down,” he said.

And when it comes to investing in tooling, ROI is often calculated on time to value. But since the value of the modern data stack relies on both tooling and personnel, companies also need to factor in onboarding time. That starts with the simple question, How long will it take a reasonably talented new hire to learn all the tools and processes so they can function as well as the rest of the team?

Making a case for a modern data stack means you have to frame the conversation so it doesn’t begin and end with the initial capital expense. Paint a picture of what can happen if you don’t modernize – if your data heroes leave and there’s no one to fill the gap.

“The beauty of the modern data stack is you don’t have to depend on somebody for their specific skill set,” Yoni explained. “When you have something broader, the team is scalable, and that makes the business scalable. The majority of value comes from documented processes and enabling the data team.”

Easing into investments

Before you start pitching decision-makers on your dream data stack, make sure every element can pull its weight. Here are some of the panel’s top tips:

  1. Painstakingly research the company’s objectives and the data team deliverables required to achieve them. 
  2. Focus on the tools that make those deliverables possible with the least amount of manual intervention from the data team.
  3. When talking to business units about their goals, make sure everyone has a shared understanding of what terms mean. Different definitions of things like “activated customer,” “segment,” or “real-time” can have far-reaching impacts on how the data team does its job.

As you add tools to your data stack, Jobin also recommends sticking to pay-as-you-go licenses or licenses that last no longer than a year so you can test out a tool’s effectiveness before making a big commitment. Start with one project, he said. If that goes well, slowly start onboarding other workloads onto the platform, making sure it lives up to its hype.

Check out the full webinar with Jobin, Yoni, and Paul, where they talk more in-depth about establishing the ROI of the modern data stack here. 👇

‎💰 Want to see how Census can help you maximize the ROI of your data stack? Book a demo with a product specialist.

Related articles

Customer Stories
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native
Built With Census Embedded: Labelbox Becomes Data Warehouse-Native

Every business’s best source of truth is in their cloud data warehouse. If you’re a SaaS provider, your customer’s best data is in their cloud data warehouse, too.

Best Practices
Keeping Data Private with the Composable CDP
Keeping Data Private with the Composable CDP

One of the benefits of composing your Customer Data Platform on your data warehouse is enforcing and maintaining strong controls over how, where, and to whom your data is exposed.

Product News
Sync data 100x faster on Snowflake with Census Live Syncs
Sync data 100x faster on Snowflake with Census Live Syncs

For years, working with high-quality data in real time was an elusive goal for data teams. Two hurdles blocked real-time data activation on Snowflake from becoming a reality: Lack of low-latency data flows and transformation pipelines The compute cost of running queries at high frequency in order to provide real-time insights Today, we’re solving both of those challenges by partnering with Snowflake to support our real-time Live Syncs, which can be 100 times faster and 100 times cheaper to operate than traditional Reverse ETL. You can create a Live Sync using any Snowflake table (including Dynamic Tables) as a source, and sync data to over 200 business tools within seconds. We’re proud to offer the fastest Reverse ETL platform on the planet, and the only one capable of real-time activation with Snowflake. 👉 Luke Ambrosetti discusses Live Sync architecture in-depth on Snowflake’s Medium blog here. Real-Time Composable CDP with Snowflake Developed alongside Snowflake’s product team, we’re excited to enable the fastest-ever data activation on Snowflake. Today marks a massive paradigm shift in how quickly companies can leverage their first-party data to stay ahead of their competition. In the past, businesses had to implement their real-time use cases outside their Data Cloud by building a separate fast path, through hosted custom infrastructure and event buses, or piles of if-this-then-that no-code hacks — all with painful limitations such as lack of scalability, data silos, and low adaptability. Census Live Syncs were born to tear down the latency barrier that previously prevented companies from centralizing these integrations with all of their others. Census Live Syncs and Snowflake now combine to offer real-time CDP capabilities without having to abandon the Data Cloud. This Composable CDP approach transforms the Data Cloud infrastructure that companies already have into an engine that drives business growth and revenue, delivering huge cost savings and data-driven decisions without complex engineering. Together we’re enabling marketing and business teams to interact with customers at the moment of intent, deliver the most personalized recommendations, and update AI models with the freshest insights. Doing the Math: 100x Faster and 100x Cheaper There are two primary ways to use Census Live Syncs — through Snowflake Dynamic Tables, or directly through Snowflake Streams. Near real time: Dynamic Tables have a target lag of minimum 1 minute (as of March 2024). Real time: Live Syncs can operate off a Snowflake Stream directly to achieve true real-time activation in single-digit seconds. Using a real-world example, one of our customers was looking for real-time activation to personalize in-app content immediately. They replaced their previous hourly process with Census Live Syncs, achieving an end-to-end latency of <1 minute. They observed that Live Syncs are 144 times cheaper and 150 times faster than their previous Reverse ETL process. It’s rare to offer customers multiple orders of magnitude of improvement as part of a product release, but we did the math. Continuous Syncs (traditional Reverse ETL) Census Live Syncs Improvement Cost 24 hours = 24 Snowflake credits. 24 * $2 * 30 = $1440/month ⅙ of a credit per day. ⅙ * $2 * 30 = $10/month 144x Speed Transformation hourly job + 15 minutes for ETL = 75 minutes on average 30 seconds on average 150x Cost The previous method of lowest latency Reverse ETL, called Continuous Syncs, required a Snowflake compute platform to be live 24/7 in order to continuously detect changes. This was expensive and also wasteful for datasets that don’t change often. Assuming that one Snowflake credit is on average $2, traditional Reverse ETL costs 24 credits * $2 * 30 days = $1440 per month. Using Snowflake’s Streams to detect changes offers a huge saving in credits to detect changes, just 1/6th of a single credit in equivalent cost, lowering the cost to $10 per month. Speed Real-time activation also requires ETL and transformation workflows to be low latency. In this example, our customer needed real-time activation of an event that occurs 10 times per day. First, we reduced their ETL processing time to 1 second with our HTTP Request source. On the activation side, Live Syncs activate data with subsecond latency. 1 second HTTP Live Sync + 1 minute Dynamic Table refresh + 1 second Census Snowflake Live Sync = 1 minute end-to-end latency. This process can be even faster when using Live Syncs with a Snowflake Stream. For this customer, using Census Live Syncs on Snowflake was 144x cheaper and 150x faster than their previous Reverse ETL process How Live Syncs work It’s easy to set up a real-time workflow with Snowflake as a source in three steps: