Best of 2024: Data & AI Trends in 2024, with Tom Tunguz, General Partner at Theory Ventures

Hi, I'm Maggie, VP of Curriculum at datacamp, and I know firsthand how overwhelming it can be to keep up with the rapid changes in data and AI. But staying ahead doesn't have to be hard. That's why our curriculum team has curated the best learning content to help you and your team stay ahead, covering everything from data and AI literacy for busy executives to cutting edge generative AI for developers, and everything in between. Whether you're upskilling yourself or your team, we make learning practical, engaging and flexible. It just works. Power your data and AI transformation journey on datacamp.com.

Well, I think the productivity expectations of every white collar worker will now go through the roof. I think everyone will be expected to be 50 to, I don't know, 250% more productive than they have been in the past because they have these tools at their disposal and so being familiar with all these different systems and understanding when to use them will be absolutely essential.

Foreign.

Welcome to Data Framed. This is Ritchie. Since the data and AI ecosystem of tools is changing rapidly, it can be tricky to keep up with what is available and what the most important ideas are. Fortunately, it's the job of venture capitalists to stay on top of such things, so I've invited Juan to share his thoughts. I want to know what he considers to be the most important data and AI trends and how you can go about taking advantage of them. That guest is Tom Tungus, a general partner at Theory Ventures. Tom was a longtime VC at Redpoint Ventures, rising to become a Managing director before leaving to found his own fund focusing on early stage data and machine learning companies. He's also a prolific writer@tomtungos.com and since he's not shy about prognosticating on the future of the data space, I'm very excited to hear his opinions. Hi Tom, thank you for joining me.

Pleasure to be here, Richie. Thanks for inviting me.

Excellent. So we're going to talk a bit about trends. We'll start with the big one. So generative AI has obviously been the big story of the last few years and it seems to be changing pretty fast. So what trends are you seeing at the moment?

I think you're right. I mean, it feels like crypto did maybe two or three years ago, where every morning you'd wake up and there'd be a new paper and the world would have changed. And I definitely feel that way. I think we're all waiting with bated breath for the next generation of the models, the ones that Facebook Meta has promised that GPT5, which seem like they'll be able to work on much longer duration tasks. So until we know what that looks like. But in the meantime, I think there's definitely been a shift, I would say last year to this year, from preferring co pilots which complete your sentences, to agents which will fully automate work or at least some fraction of the rote work.

Okay, no, that's very interesting because yeah, there's been a big refrain over the last year or2 like AI is not going to take your job, it's going to augment it. But agents sort of promise to just like automate things and completely take away that human from the loop. So yeah, tell me more about that.

Yeah, for sure. So I mean, I think what we see, we've seen some of the productivity stats on copilots, which are about 50 to 75%. That's Microsoft in service. Now the other way around, Microsoft has 75. If the LLM agents are anything like mechanical robots, the promise is to increase productivity by about 250%. So one robot would take the place of two and a half humans, which is what's happened on automotive manufacturing lines. We're still really early there. I would say we're starting to see the very first applications of this and security automation or customer support, where Klarna cut two thirds of their customer support staff. And we can debate the relative effectiveness of the bots, but they did it and they saved a lot of money doing it. And so I think what we're seeing across, people are really excited about this trend and the nature of like entry level tasks will change. There was a really interesting Twitter thread about this where they were talking about, okay, so where robots have taken off in the last 10 years is robotic surgery, particularly like urology or areas in the body where there's just a very difficult weight, a very difficult space to navigate. And as a result, robots, they can move in ways that humans can't because their fingers, so to speak, are much narrower. There's now this training gap where the, the senior surgeons are no longer teaching the junior surgeons side by side. The junior surgeons are now just watching the robot operate. And so as a result there'll be this generation of surgeons or security analysts or customer support reps who are experts in the domain and then the younger ones don't receive the benefit of the training. And so that's an interesting dynamic that we're sort of paying attention to. But in terms of like the technology itself, we're looking for tasks where there's a lot of summarization Maybe some initial customization. Some of these agents are actually starting to write their own queries to hit external databases to enrich and then produce a summary output. And then that goes to a classifier that says is this worth a human's attention or not?

So on the other side of AI, so what about non generative AI? Are you seeing any changes there?

I think it's not moving as fast. It's not to say that it's not important. We're starting to see combinations of generative AI and we'll call them classical methods. One reason for this is that generative AI mechanisms tend to be chaotic and non deterministic. If I ask how do I reset my password period? And I ask the question how do I reset my password space period? That's a different question that will elicit a different answer from a generative AI model. And if you start to chain these inputs and outputs across generative AI steps, you might have error that explodes. And so one of the, and this is very early on, but we're starting to see companies take the output of a generative AI step and then apply a classical machine learning method to it to classify it or just to kind of constrain the error and then pass it on to the next step. Pass it on to the next step. We've met a company recently where there's three or four different kinds of machine learning that are being used all in one system. Generative AI is really good at two different things. It's really good at generating ideas. So four to five great titles for this blog post that I wrote right now. And then deterministic methods or the classical methods are the ones that are really good at picking. And so I think you'll see this nice marriage between the two where most generative AI applications will not be entirely gen AI, they won't just be the wrappers. And as we get to the next step, you'll see we call them constellation of models. And so there's just to kind of talk about it in one level more detail. Input from the user comes in. There's a classifier that could be a classical classifier or Genai classifier that says what kind of query is this? Have I seen this before? And then given that output, it passes it either to a small language genai model that knows what it's talking about, or if it's like a completely new query, it goes to something like a ChatGPT4 is it going to handle a whole universe? Or if you go to a classical.

Okay, so that hybrid approach is really interesting. So it's maybe like using the generative AI stuff as like the human interface because human, human slide chatting and then you've got something more deterministic underneath so you've not got the error propagation problems. Okay. Actually one trend I've seen just from going to a lot of data conferences last year, everyone was like, hey, you must build stuff with generative AI. It's going to be amazing. And then just in the last few months it's changed to all those generative AI prototypes you built last year failed because your data quality sucks. And now you need to think about like data governance and how you improve your data quality. So are there any things interesting you're seeing in that space?

Well, yeah, there's, I mean there's a lot around data security. So we've, I think the big fear with generative AI. You have two different kinds of problems with generative AI security. The first is what happened with the Canadian National Airline when a passenger asked about a bereavement policy. And the generative AI created a bereavement policy that the Canadian airline was forced to to adhere to even though it had nothing to do with the real policy. So there's this like hallucination problem, but there are other challenges with it. Give you. A friend of mine started running a company. One of his employees installed an LLM on top of the cloud data warehouse and he asked what is this employee Social Security number? And I'll pop the Social Security number. So you have data security issues. So we've identified like five different kinds of security that will be needed around large language models. Whether it's ensuring the developer's environment that they're building. A large language model is secure, ensuring that there's no data loss like Social Security issue. There's the right access permissions to the database. Are you hitting the right snowflake connections? Do they have the right user account? There are data poisoning attempts. So if I'm downloading an open source model, am I downloading the right one? Has it been tampered with? That's sort of software supply chain and there are others. But this whole space is new and the challenge is historically the ciso, the chief information security officer has been predominantly responsible for securing data. The average tenure there is about 14 months out of breaches. So it's a very challenging job because the surface area continues to increase. But now the data pers, the head of data is now basically responsible, maybe even the head of engineering are responsible for building the systems that use those data in Generative AI. And so there's a sort of both of these roles have to unite in terms of securing and making a hermetic seal around the data. And those workflows have not yet been created. Our sense is that for many of the largest companies in the world who might have hundreds of thousands of LLM enabled applications on their roadmaps, security is the single biggest blocking feature because nobody wants to be fired for the week. But there's no playbook yet, there's no sort of standard tools and that's really slowing a lot of the enterprise adoption.

Okay, so it seems like making LLMs or making generative AI applications more secure, that could be a big growth area in the next few months or years then. Okay, I like to hear example of the Canadian airline. I believe the courts ruled that they had to uphold that bereavement policy that the AI told them about. Yeah, and I heard like another example of this where someone was chatting with like a car dealership and it was an AI sales rep and they persuaded the AI to sell my car for a dollar. And I have no idea whether that's been upheld or not. But like that seems like a good wheeze if you can pull it off. Okay, so related to this, it seems like a lot of the cloud data warehouses, your snowflakes and databricks and all this, they're rapidly adding AI features. And so how do you see data warehouses changing at the moment with this rise of AI?

They're at the core. Right. A lot of the data that's being fed into these large language models comes from the cloud data warehouses themselves. And so typically in the pre Genai era, the map of the modern data stack was you'd have a source system, an ETL platform, the cloud data warehouse, and then you would have three different consumers, you'd have bi exploratory analytics and then machine learning. But machine learning was always post hoc, it was never past the production. It was always customer segmentation, churn prediction, revenue maximization exercises. Now what's happening is the cloud data warehouse is basically now in the path of production, so to speak, where extracts of that data is, are being fed into a machine learning pipeline that's cutting up all the data, calculating the different vectors, potentially storing it in a vector database. And then at inference time, the query plus the documents and the vectors are all going into the vectors are leading to the documents, that's going to the large language model. And so these cloud data warehouses suddenly have to rethink where they sit in the stack. Many of the historical ones have not been architected to serve as production databases. So what's happening is that these new pipelines, right, so there's spark that's being pushed into to calculate the different vectors, particularly large scale. And then you have this category of vector databases which do a lot of calculations on similarity search. There's a strategic question about how much of the vector database should be a standalone database and how much of the vector database can actually exist within a cloud data warehouse. Core functions there are relatively straightforward. It's clustering with K. Means are another form of clustering and then cosine similarity. How similar are two vectors or three vectors or four vectors? And so I think we'll start to see some of the bigger database companies have announced vector database initiatives. So that's an important competitive dynamic that we'll see play out and that'll be really critical. I think the other dynamic within the all of cloud data warehousing is the separation of compute storage, but not in the way that Snowflake takes talks about. It literally mean like the separation of the query engine from where the data is stored. And you saw that in Snowflake's most recent earnings, where a lot of the bigger customers are asking for the data to be stored in iceberg tables in S3. And so it's very possible that that core centralized data may actually be hit by a different query engine in order to power a generative AI pipeline.

Okay. So you might be skirting around the data warehouse entirely. So you go straight from your cloud storage in S3 or whatever, and that's going straight to the LLM and then or into your vector database and just like cutting out that middle part. Is that right?

Yeah, it could be. You may need to, I mean it depends on the sizes of the data. And again, like one of the challenges is formatting the data in the right way. A lot of the times, like if anybody has used LangChain and you're trying to process documents, how you chunk the documents, how you cut them up, how you structure them in order to feed the model is really critical. Or the sequencing is also really important. And so you may need to pre process using a data warehouse or some other tool and then write to iceberg tables with arrow files underneath and then that will be consumed. But there's no, at least our perception is there's no real standard design pattern quite yet for how everybody's building these flows in a very customized way today and two, three years from now, they'll be, I mean, just where we had in the modern data stack, right. It's source system 5 trans snowflake looker. There was your stack. We don't have that yet.

Okay, that's really interesting. And it seemed like there are a lot of new companies in this area and they're all doing overlapping parts of the puzzle. So there's probably lots of different ways to get your complete flow at the moment. But you think we're going to end up with like these companies becoming bigger and they'll sort of overlap each other to converge on something or is it just going to be there'll be like one winner somewhere that does everything.

I don't think there'll be one winner. I mean the modern data stack had many different approaches and you know, I mean you could look at like Databricks versus Snowflake, you can look at 5chan versus Airbyte looker versus I mean any number of the BI products. So I think there will be many different approaches. What's different within the world of AI is that unlike business intelligence where everybody wanted a dashboard, the output is different. A company might want to build a gen AI pipeline to summarize text. Another company might want to build a recommendation system that combines both textual information about like a video, but also statistics about how long user is watching those videos in order to show the right next video. So that's a different, the different kind of pipeline where you're computing multimodal vectors. On the multimodal topic, you may have a third company that's trying to build TV production, production grade video generation. That's a third completely different kind of pipeline. You might have like legal documents or let's say you were looking to analyze the financials of a company, take a look at an income statement. You might want a classical method there to understand exactly what's going on inside of the P and L. Because you can't take any, you can't accept any error. Then there's another. The way that a venture capitalist looks at a P and L is very different than the way that an auditor would look at a P and L. Anyway, so my point is there's so many different outputs that are necessary that you may actually see a much broader diversity of different data pipelines and data pipeline vendors to support all these different use cases.

Okay, so I guess like once we get a modern AI stack, it's going to be a lot more rich and complex compared to the modern data stack that was talked about a few years ago.

I think so.

So going back to the idea of data quality, I know One of the buzziest terms at the moment is the idea of data contracts. Can you just talk me through, like what are these and when would you need one?

Sure, yeah. Data quality. So you can imagine data is like a manufacturing line, right? We talked about that. You have raw ingredients that then go through a processing facility and then they're packaged up. And data quality, Monte Carlo is the leader here, is really about understanding how effectively the data is coming through. Are there changes in the upstream sources and is the distribution of the data changing? Is the volume of the data changing? Is the shape of the data changing? And if there are that, everybody should be alerted because that's very likely a problem. And so that's what data, the data quality movement is about. And so you have a company like Monte Carlo which is doing, using machine learning to understand exactly what's happening. And then you also have a test based approach where you assert different conditions about there should never be a zero in this particular column or it should always be numeric. For example, once a data pipeline is working and you have an observability layer, kind of like a datadog, through that you're in a really good place. The next sort of theme within the modern data stack world is this idea of a data contract. And it's part of this broader theme that parallels what's happened in software engineering. So let's take a step back. So the way that we used to build software is we used to build on one very large code base, all the engineers who work on one really large code base at the same time. And there are some advantages to that. But what we found is by cutting it up into small pieces and having small teams of engineers build on all those different microservices we call them, it was much easier for everybody to collaborate. The one requirement was that each team had declared to the rest of the world that these are the kinds of inputs my system expects and these are the kind of outputs that my system will produce. And these are the guarantees that I'll give you about how fast it will do that and how often we'll update it. And so this is exactly what's happening in the data world. Twenty years ago, MicroStrategy and business objects and cognos, they were all controlled by a centralized data team. And the access to data was, was really limited in order to make sure that it was highly controlled and the data was good, accurate. And now what's happened is we've had a democratization of data where the marketing team has its own analyst, it might have its Own cloud data warehouse. The same for the sales team. Finance might have the same thing. And so now it's been distributed just in the way microservices and what data contracts promise is buts and code, the inputs, the outputs and then the sla, the expectations around performance into software so that we can manage all of this effectively. Today, for many of the largest companies, this doesn't exist. And so having a software platform or the change management associated with encoding that so that if the marketing team is consuming product data and the product team doesn't just change the format of the data without alerting the marketing team. Breaking downstream systems.

Okay, so this sounds like a really effective way for different teams who are working on either similar bits of data or one bit of data where it's downstream from another team. They can work together more effectively because they're essentially guaranteed like what they're getting from the other team.

That's right, yeah. It feeds in this idea of data mesh, which is data is distributed all throughout the organization. People are each consuming and producing data for each other as opposed to to from a centralized node.

So I'd also like to talk a bit about cloud computing. So it seems like moving everything from working locally to moving to working in the cloud, that's been a big trend over the last, well, more than a decade. Is this something you see continuing or is the pendulum going to swing the other way?

So it's absolutely true. Everyone was moving from on prem to the cloud. Now what we're starting to see is hybrid execution. And there's two different parts to hybrid execution. The first is the customers want to hold on to their own data. And so we talked a little bit about Snowflake and Iceberg before. Many of the largest companies are the privacy centric companies. They want their own data stored on their S3 buckets or whatever buckets they have. And what they want to do is they want to bring the software and the compute to that data as opposed to sending that data to Salesforce or sending it to Marketo and then having the output stay there and then somehow have to pay a third party vendor. So just bring all the data here, bring your software in, we'll compute and then the software can leave. If ever we decide to change it, that is becoming much, much more important than it has been in the past. The other part of hybrid execution is actually so this is why it's a little bit overloaded. There's a new wave of building applications where some of the processing is done in the cloud, maybe through that architecture and some of the processing is done in the browser. And so if we look at technologies like DubDB, you can run a DuckDB instance inside of a wasm container, webassembly container. And so let's say you have this really huge dataset, like a hundred gigabyte dataset, pre process some of it to the cloud, take 2 gigabytes, put it locally, and then all of the analysis of the visualization that's done on that 2 gigabyte dataset is actually done on the user's computer. And so as a result, it's much faster, it's much more capital efficient. You actually offload. If you're a vendor with this kind of architecture, you're able to operate with significantly better margins because you don't pay for as much computers as you used to in the past.

So certainly saving money sounds like a good idea. And it sounds like. So you've got raw data sets are generally bigger, so they're going to be somewhere centralized and then by the time you got something processed, that's going to be much smaller. So that may arguably makes more sense to be done locally.

Okay.

I suppose the trick is just to be able to move fluidly from local to cloud and back again. So you're not worrying too much about that.

That's right. That's the hard part.

Okay. All right. And so another big trend is business intelligence. Platforms have been conquering everything, certainly the data analytics space over the last few years. And you mentioned Looker, and then there's others like Power BI and Tableau and all the rest. Do you see these BI platforms changing at all or are they mature?

I do think, I mean, these BI platforms will change, I think the way that we think about BI over the last 20 years, and we talked a bit about this, but in the early 2000s, BI was really centralized and controlled by a small number of people in order to ensure the accuracy. That was like in the year 2000, let's say. And then during Tableau was formed in 2004 and really hit its stride over the next five to 10 years. That was about enabling an analyst to take control and analyze their own data completely. Bottoms up strategy, no centralized control at the beginning. And so he had a huge pendulum swing from the center to the edge. Then Looker came and said, well, there's these next generation cloud databases, these cloud data warehouses like Snowflake and BigQuery, why don't we try to exact some more control on giving some flexibility? And they deployed a modeling language called LookML, which allowed the Data team to define a metric and then everyone in the organization to use that definition of revenue. And now I think where we're going is continuing to sort of like go back to the pendulum. So the next generation of companies like Omni, what they're trying to do is allow the metrics definitions to be helped created at the edge and then promoted all the way through with the right kinds of workflow. The big question, you know, the one that you asked is, well, where does AI fit into this? There's a challenge with AI, I think, at least in the BI world, AI has a role. With SQL, query completion seems to be a great use case. I may not know exactly the right syntax to do a windowing function, or I may not know exactly the right syntax for beautiful union across two different tables or cte. And so I can complete the code, complete the query using AI. The big question is whether or not people will trust these AI systems in order to answer questions like what is the company's revenue broken up by region and territory, by region and product? Because if I ask that question in a slightly different way, if I flip the group, effectively the group buys, I might get a different answer. And so until we really solve that problem, the lack of trust, I think will be a pretty significant barrier to entry to full automated. Just ask a question and trust that the data is correct. And then talking to different data teams. There's another nuance here which is the interpretation of the data. Even if you have the right data, the interpretation of the data is still the really hard part. Is there a statistically significant difference between two averages? And then how does that impact what the business ultimately makes? So there I'm a little more cautious because of some of the chaotic nature of the AI.

Let's say there's two parts then. So you've got the helping you write the code in order to actually do the analysis and then the interpretation separately. And it seems like, I think the simple queries, it's certainly like the SQL generation is pretty good. And I agree with you that it's impossible to remember the syntax of a window function. So yeah, better to get the AI to write that. But yeah, for more complex queries I can certainly see how to be some trust issues there. So in that case, do you think we're going to need to have humans in the loop there like for a long time in order to just sanity check the SQL?

I think our bet is that the number of people working in data will actually increase by a big, big number multiple because so many, many Many more functions and many more businesses will now become reliant on data because they need it. And so what will change is the kinds of tasks that analysts are doing. But we'll need many, many more of them.

And on the subject of like BI and AI, obviously like the biggest generative AI application is ChatGPT. And do you think that chat interface is going to replace the BI point and click interface or are the two things complimentary?

I think so. There's BI and then there's exploratory analytics. My sense is in the BI landscape it probably won't have that much of an impact. I mean, maybe it will help you find a dashboard or might point you to a data point. I think in the exploratory use case there's a much greater value there because let's imagine I'm Coca Cola, which one of the bottlers has seen the greatest amount of volume growth in the last 12 months. And then you might want to dig into that in a bunch of different dimensions. Like let's say we wanted to tie that to contract structures. And so we would jump from the world of structured data, which is what's going on, what's happening in the core dashboards. And we want to tie it to. Is there a particular provision within the contract terms associated with these kinds of bottlers There I could see generative AI being really helpful because its ability to classify and its ability to retrieve different kinds of information that might be written differently across different contracts would be really useful. And so I think it might have, and it's still early, so I might be completely wrong, but I think it'll probably have more of an impact on the exploratory analytics than it will on core dashboarding and reporting of business metrics.

Yeah, so if you're trying to ask lots of questions quickly like you do in eda, then you probably want a chat interface. If you know what you want to build, then just build the dashboard using the traditional tools and then, yeah, you're done. All right, so this leads to, I mean you said that data scientists like and data analysts, the skills or their job is going to change. Like what new skills do they need in order to be able to cope with this new world?

Well, I think the product of the expectations of every white collar worker will now go through the roof. I think everyone will be expected to be 50 to, I don't know, 250% more productive than they have been in the past because they have these tools at their disposal. And so being familiar with all these different systems and understanding when to use them will be absolutely essential. I think we'll look at even there's this professor at Duke who requires all his English students to use ChatGPT when they write. And it's a bit of a divisive perspective, but very much in agreement with it. The reason is when those students graduate, there'll be a huge advantage if they understand how to use ChatGPT in a very sophisticated way to write. The trade that he makes with his students is if there's a single grammatical error, you fail. And so just as much as the student can benefit from the technology, also, you know, need to assume some responsibility for it. So I think the role will become less data, like munging data, movement, data management, and much more understanding. Is the data correct? What is the right interpretation? How does this apply to the business? Which I think we would all agree that it's a far more interesting part of the job than modifying a data frame from being wide to long, for example.

That's definitely a task that I think GNOD data analyst or data science appreciates.

It was always a pain in the.

Data being in the wrong shape. Okay, so we talked about changes in skills at the level like whole roles or jobs. Have you seen any roles becoming more popular or less popular? Like, is your job title going to change?

I don't think the job titles will change. We haven't seen the impact broadly yet. I think that the main difference here is the structure of the organizations where a lot of the core, like machine learning, data scientist functions are now being pushed to fuse with the core engineering teams. And this is because the machine learning system, the AI systems are now being put into production. And so that's a very different place than where the data team used to live, which was downstream analytics, post hoc, not in the path of production. And so one of the broader themes that we're wondering is, does the data team actually start to live underneath engineering?

Ah, interesting. Have you seen any companies where that's actually happened yet?

It's starting to happen, particularly in the smaller companies where AI is a core part of the feature and just there's an output from a cloud data warehouse or some kind of aggregation that's then being funneled into production. Because all of a sudden then if you think about the classic modern data stack, that whole tool chain or the whole value chain to deliver that data needs to be production grade. In the definition of a site reliability engineer working on a core website, it needs to have three or four nines of uptime reliability. There needs to be the alerting and monitoring around those core systems. And so there's this cultural fusion that I think will need to happen between the classic AI data science machine learning teams and the core engineering teams. That is definitely, we're seeing that broadly today, but it will take time.

What sort of culture clashes are you expecting there between data and engineering teams?

Well, the engineering teams, like I said, they're accustomed to carry, I mean, many of them will carry pagers. So these systems break. They're accustomed to using libraries. They think about shipping the product really fast. They code in a very particular way. So if you look, if we were to compare the Python of a web application engineer and the python in an IPython notebook of a data scientist, one has nothing to do with the other. Right? In fact, the core software engineering team looks at an IPython notebook, it's is like, what is this? I can't, I can't take that code and put it into production. I need to actually reimplement it or write it into a different language that goes into the cicd, which is the, sorry, integration, continuous integration, continuous development flow and the code path of production. It's completely different than the way the data science has been accustomed to building. And so just like even the core workflows of like, how to commit the code, what does the code format look like? Is it packages, the library? How do I make sure it has tests and checks and it performs in a similar way to the other kinds of Python code within the code base that that needs to come together.

Okay, so it sounds like a lot of your data scientists think need to, like, be able to write a great function, create great packages, just learn about style guides and like, how to structure their code. Are there any other skills along those lines that you think are going to be important for data people?

No, I think that's it. I mean, there's another function or another. Well, actually another skill is this idea of a data product. So I was a product manager at Google and what we would do before deciding to build a product was we would create a product requirements document, prd, which described exactly what it is that we were going to build. We would socialize it within the rest of the company, we would understand the dependencies, and then once that was complete, it would pass to the engineering team for implementation, obviously to be back and forth. What we're starting to see in some of the more sophisticated data engineering organizations and AI organizations is they're starting to create data PRDs and they're starting to think about tables or APIs as data products, just the way that like a regular API or a production grade API would be. And so they're starting to look like their own sort of engineering teams with the data product manager, data tech lead, and then a bunch of data engineers who are building this and maintaining it. So I think that formal way of building products will come to data.

Okay, so going from that sort of scrappy, I'll just do my analysis notebook to okay, actually you have to think about like, who else is reading the code, who else is consuming this and make sure it's good for public consumption. So for companies who are thinking, okay, there are all these new tools available, what do you need to do to take advantage of them?

I think today it's all about experimentation and really understanding where they work and where they don't. The ecosystem is changing really fast. I think the leaders of the next wave will be conversant in AI. They will know how to speak to their leaders and educate them on where the company should be spending time, where the company should be investing in terms of software. Because the reality is like every board and every C suite is saying, we need AI, we need AI. We're starting to see the productivity improvements from our competitors. They're looking to the leaders within each individual team and department to educate themselves and then ultimately develop the strategy on how to leverage this technology internally. And so being an expert in that domain, I think will will lead to lots of promotions. Because if you can cut 2/3 of a workforce or if you can increase revenue by a third by making sales team that just that much more effective through automation, there's a lot of value to be created.

Absolutely. So you take advantage of this, you could be like the real hero of heroine of your company then.

Absolutely.

And are there any particular areas where you think data teams should be focusing their attention or companies should be focusing their attention to improve their data capabilities?

I mean, I think the first is the data pipelines that are going to be necessary to power sales optimization and customer support optimization. Those seem to be the two areas across companies where, for example, we're starting to see startups that are building fully automated sales development reps. So instead of sending a human sending 10 emails per day, these systems are sending a thousand emails a week or 2,000 emails a week. In order for those programs to be effective, the data pipelines to inform those outbound campaigns will need to be there. Same on customer support. So those chatbots that are able to deflect 2/3 or more of the inbound customer support queries, the richer the context is. The more data those robots have about the customer in particular or the FAQs or the new product features, the better and more effective they'll be. And so I think that's where you'll see a lot of effort and energy because those are the two. One is a revenue center. In order to make a lot of money in software, they increase the revenue of your customer, you materially reduce the cost still, that's where you're going to increase revenue. And then the customer support team, typically that's where pretty significant cost comes from. So I would expect focusing on those data pipelines, enabling that to happen will be great. The third order priority is around marketing because there's a technique in marketing, it's called account based marketing. Building a website for a particular buyer like a Coca Cola, Procter Gamble. And historically that's been really difficult to scale, just as you can imagine, need a lot of data to be able to do that. Now we're starting to see the next generation account based marketing companies do this for every single customer in a universe because they're just automating machines. And there again the data pipeline is the context of the report.

Okay, that's really interesting. So start the stuff that is really going to have a direct impact on your revenue or your costs and then go towards like personalization and think about better marketing through personalization. Okay, those seem like pretty strong areas to target. Just before we wrap up, are there any companies that you are particularly excited right about right now?

Yeah, within the data ecosystem, you know, Mother Duck we talked about, I think that they have a potential to really change the cloud data warehouse ecosystem with their unique hybrid architecture. And Jordan, who's The founder and CEO there, he was the tech lead at BigQuery, clearly understands the domain. The other realization that we've had as a company is that more than 80% of the cloud data warehouse workloads are small enough to be able to process on a modern Mac. And so having this hybrid architecture allows companies to do that. The other one is Omni. So this is the xlooker team, the key part of them and who got together with one of the Chris Merritt, who was one of the architects of dbt. They're building a modern BI system that balances centralized control and metrics definition with enabling individual, an individual marketer to create a metric around cost, customer acquisition and building the workflow to have that move all the way up to centralized, the centralized data team. And they're having a lot of success. Those are the two I'd like to highlight today. Okay.

Mother Duck and Omni.

Yeah.

Companies to watch out for then. And do you have any final advice for companies wanting to make better use of data? Keep going.

It can be hard and there tends to be a lot of resistance associated with it. But what I've seen in my career time and time again is the company has moved really fast and experiment with the next generation technologies, are often able to find a lot of alpha and develop competitive advantage through it.

All right, super great advice there. Thank you so much, Tom.

Pleasure was mine. Thank you, Richie.