EMEA | Domopalooza Unpacked 2026

Good morning, everybody. Good morning. Thank you for joining us. And apologies for the slight delay. Had a couple of technical issues, but we also thought it would help build up a little bit of suspense for today's live webinar — Domopalooza Unpacked.

As you can imagine from the name, we'll be going into all things Domopalooza. Everything from the latest and biggest product releases, some of which are available for you now. We'll be talking about the announcements made in terms of product development and where that's going. And we'll also be joined by one of our key customers, who'll be talking through his experience at the event as well. So super excited to be here today and to be guiding you through the session.

My name is Joe, and I'll be the host for the next hour. I'll be joined by Marius Kaiser, who is a senior solutions engineer here at Domo. His role will really be bringing a lot of the product development and new features to life, spotlighting how they solve challenges we're seeing amongst organizations, and taking part in the live demonstrations.

I also have the privilege of introducing Adam Leeder, who's a travel technology product manager at the Good Travel Collective. He'll be talking through his experience at Domo and his perspective on the event.

From an agenda perspective, quite a lot of things to go through, and we'll try to cover as much as we can over the next hour. We'll start with the Domopalooza experience with Adam — hearing his perspective on how he found the event, what he thought, what he took away, and what he left most excited about from a Domo perspective.

We'll then move into the core element of the webinar, which is three themes centered around key challenges we're hearing amongst our customers and within the market. Marius will be mapping a lot of the product features that were announced and released towards solving those challenges.

We'll then move on to a live Q&A. We'll be rejoined by Adam, so it gives you a good opportunity to ask as many questions as you can. Please put them in the chat and we'll make sure we get to them.

Quite a lot of today will be around AI and how organizations are using it, and what features and developments we've made within the product around that. We'll leave today with a little offer that will help you plan and start to prioritize some of the AI use cases you have. So stick around — if you can make it to the end, we'll be able to give you that offer.

Before we get into some of the key announcements, we thought what better way to bring these to life than hearing directly from a customer who was there at Domopalooza experiencing it firsthand. It was the first Domopalooza for Adam. So it gives me great pleasure to introduce Adam Leeder from the Good Travel Collective.

Adam, welcome. Thank you for joining us. Obviously always great to see you. Before we dive into everything Domopalooza, maybe set the scene for us a little bit. Can you give everyone a quick introduction — your role, your focus at the Good Travel Collective, what you guys do as an organization, and how the team is currently using Domo?

Absolutely. Thank you, Joe. Thank you for inviting me to take part in this. So hi, everyone. I'm Adam from the Good Travel Collective. My role as travel technology product manager is looking after all the pieces of technology that we have, whether it be our proprietary software or third-party solutions — anything from online booking tools, profile systems, reporting tools, etc.

As a travel management company, we look after our corporates and their travel programs, making sure they're getting to their destinations safely and in line with policies. One of the biggest things prevalent throughout the travel industry is the fragmentation of data. Everything is different — every different system does something different with their data, or the naming conventions are different.

That was one of the key things for us when we decided to become a customer and partner of Domo — we wanted to bring that fragmentation together, realign everything, and be able to deliver results and data visuals in real time for our clients that are actually meaningful, rather than trying to cobble something together with lots of manual processes.

For us, we've been using Domo for visualization for our clients and internal reporting, but we've also now moved into other areas within Domo, and it's so exciting what we can do with that data.

That's great. And you were obviously out with us in Utah earlier this year — your first time there. We're keen to get your perspective. What was your overall take on the event? What was maybe one of the main things you came away thinking about?

Well, one thing — it was certainly a lot warmer than it is here today, that's for sure. And I have to say thank you to everybody at Domo for the event. It was amazing. You certainly know how to put on a conference. Everything — the highlights from the product releases, the interaction, meeting the Domo CEO and having a really deep and meaningful conversation with him, through to the concerts and the celebratory aspect of it.

To answer your question, I think my biggest takeaway from the conference was this sense of community that Domo has built. It wasn't just about what Domo wanted to push out with their product releases — it was more about what people actually want, and what would work better for the end users.

It will make you laugh, but one of the biggest cheers of the event was the announcement that dark mode is coming, which was hilarious to watch — rapturous applause. But even things like people lobbying for the report builder for PDF — just to have something as simple as that is cool because that's what people actually want.

Exactly. I'm still trying to get my head around the dark mode applause. In terms of the product side of things, lots of announcements, lots going on — it was really jam-packed into quite a short time frame. What were some of the key ones for you and why were they important for you and the Good Travel Collective?

I've been racking my brain on this because there were quite a lot announced. I think for me personally, having worked with some of our legacy systems and platforms, some of the key things were the annotations — being able to put notes on a workflow as to what you're doing, as a reminder for yourself, but also if somebody else steps in, or if someone builds something and then leaves the business and you take over, you can clearly see what their intentions were and what the suggested outcome was.

But also the "run to here" piece. So if you've built a workflow and you want to stop it halfway and check where there's a break — now you can just run a specific section to understand what's happening. I think that's a really key thing when you're building up to scale. We need to be able to do things in bite-sized chunks and go: that bit's working, now we do the next bit. Is that now working and having the intended results?

There were so many other things, but for me, those were the key takeaways, just because of the legacy systems we're currently using. You look at it and you go, well, what actually was the intended outcome?

Yeah, I hear that from customers all the time. People leave the business or you've built something and weeks later you go back and can't remember exactly why you did certain things. And AI was obviously a big theme at Domopalooza. Was there anything in that space that got you thinking about what's possible for the team, and is there a particular AI agent you're quite excited to build?

I'd say we've got a long list of ideas, which we are slowly prioritizing and picking out key areas that don't just affect day-to-day operations for consultants and clients, but also internal teams. Like, is there something we can do with AI agents for the finance team — from a reconciliation perspective or credit control? Just bringing everybody into the fold of what we're trying to do.

We're currently working with you guys to get a podcast AI agent ready. That will produce up-to-date daily, weekly, and monthly results to our exec team, so they can literally have it delivered straight to their inbox, hit play on the way into the office, and just get live updates from the system.

Another one we're looking at is reconciliation. We have various different credit cards and finance packages, all doing different things but all integral to what we want to deliver to our clients. Trying to bring that together to speed up the month-end process and make things easier and better for everybody is a key one for us.

I love the executive podcast agent — it was definitely getting a lot of traction. For those of you on the call who haven't explored the agents, that would definitely be one we'd love to walk you through. Please contact your CSM and AE to explore that further.

Look, Adam, thank you for joining us this morning. We'd obviously love to see you there next year. You're not leaving us though — you'll be back towards the end for a live Q&A. So everybody please put your questions in the Q&A chat. Start thinking about any questions you have for Adam. Thank you, Adam. See you later on.

Perfect. So moving on to the three core themes of today, centered around the challenges we see and hear from organizations.

Typically, those would be: making life easier — things around navigation within Domo, the UI, how we can share and collaborate more with our users. Then the next two points are around AI — what are we doing to get the data in the right place to unlock the real value and potential of AI? What are some of the features discussed at Domopalooza that allow for that? And lastly, what are we doing to help you build AI solutions faster — how can you get these things up and running?

So I'm super excited for that. Moving on to the first theme — making life easier. A lot of customers will hopefully find this resonates: sometimes instances can get quite cluttered, it's difficult to find the content you need. A big ask was how can we collaborate better with teams within the organization? App Studio is great and we're using it a lot, but there are a few tweaks and navigation pieces around the UI we'd like to see improved. And as Adam mentioned, around that PDF report aspect — how can we start to share that with users?

I'll pass over to you, Marius. Keen to understand what some of the new things that came out of Domopalooza are that address those challenges we're hearing from our customers.

Marius: Yeah, absolutely. First of all, thank you very much, Joe and Adam, for setting the scene perfectly. A lot of the features and announcements Adam mentioned, I'm super excited about as well and really excited to show you guys live and in action.

Let's not waste any time and jump right into the Domo platform. As Joe mentioned, the first theme is really around collaboration — finding the data at the right time when you need it, plus the governance around content as well. Because these are actually quite small feature announcements, but they can have a really big impact when you know how to use them and where to find them.

So first of all, we're going to start with Workspaces. You can create workspaces for your teams and projects, and you'll find them in the Teams section of the Domo platform. So we see the workspaces I'm a part of. I can pin a couple of workspaces so I know exactly where to start and dive in straight away.

I wanted to be part of the marketing team, so let's see what those guys are up to. You can see we have a mix of content types — apps, dashboards, datasets, even data flows. Everything can be combined in workspaces. For some teams, that might be the one thing they need: all of the content in one place and good to go.

I can even further organize this with folders — creating more structure so I can group all my datasets and apps into specific folders. And when I'm part of the marketing team, I can share this workspace so everyone is able to jump straight into the key dashboards and apps they need for their day-to-day job.

This really goes hand in hand with the next capability, which is customizing the navigation for every user and user group. I love using the nav bar and customizing it to my needs in terms of features and content. The thing is, everyone has to set it up themselves and personalize it, and some users are keen to do that — but for some, there might be a little bit of friction when they first log into Domo.

So let me show you a new capability that helps everyone have the right navigation straight away when they log in. This is an admin feature found in the admin section. Domo admins can configure this within company settings under Navigation. We've got one set up for the marketing team — let's continue that theme. When we go to edit, we see a preview of how the navigation looks for any marketing group or team member. Key features like dashboards, alerts, and apps are going to be relevant for everyone, but also the marketing workspace, AI chat, and maybe approvals for the marketing workflows.

We can completely define and configure this — moving each feature and content type around, adding new ones. For instance, we might want a particular marketing app or dashboard to be part of this, or maybe add App Catalyst for the marketing team. You're completely free to customize it to the needs of particular teams and groups. Then we just assign people to it — directly or by team or group — and everyone with the marketing role can be added. When they log in, they see a completely personalized navigation bar straight out of the box.

Now let's jump into one of my favorite content types — apps. I'm going to look into one of my humble apps that I created as an example, looking at CRM, project management, and contract invoice data all in a single app. This will be a great example as we dive into how we're actually designing these apps.

You'll notice on the left is a new toolbar where we can access all of the key features straight away — new worksheets and tables, cards, visualization types, controls, and any sort of components, directly via drag and drop into my app. If I want to build something brand new, I can bring in a new chart, build a card, and connect a dataset. That already shows us the next big change: we can now completely build and customize these cards directly in App Studio. That's a massive efficiency gain for me personally because I don't need to go back into Analyzer — I can do everything directly here. I can change the chart type, design the card, set the x and y axis — just like that, I've got a new card added to my app, very, very quickly and easily.

We can also add the new worksheets and editable tables into App Studio now as well — that's currently in beta. This allows us to collaborate with teams and add data input directly in the app. For instance, we use this to manage our projects, and if I add time needed for a certain activity, it will populate directly in the chart below — super easy data entry with direct visualization capabilities.

Another feature that's in beta is the new PDF report builder, which got standing ovations at Domopalooza. We've always had the capability of sending out email reports, and now we can build PDF reports directly in App Studio. We get a preview, we can design our pages as needed, and it's really pixel-perfect reporting. You can add footer data, header data, and define the summary and analysis. Users can then export and generate their PDFs directly. In the next iteration, we'll be able to schedule this out as well to have the full burst reporting workflow supported directly in App Studio.

But for now, I'll pass it back over to Joe.

Joe: Thank you, Marius. Yeah, a lot of really cool updates, especially around App Studio — we've had that for the last couple of years and we're continuing to build it out and enhance it as much as possible.

I'd say the majority of the features around App Studio are now GA. There are a couple in beta, and we'll go through that in the documentation section — you can click and see a lot of the release notes and get more information.

Workspaces is a big thing. We've been using it ourselves within our teams, creating space to collaborate with different teams and making sure everything is well managed and organized in an easy way.

Worksheets is something else that came out of Domopalooza — for all the Excel enthusiasts who want to use and explore data in more of a spreadsheet format, that's definitely one to look into. Those three areas are generally available and you should have access to them.

The last one — the PDF report builder that Marius mentioned — I've had a lot of emails from customers looking to be able to send out PDFs out of App Studio to their users. That is now in beta, due to be released later this year. If you're keen to join the beta program, if you click on Docs, there'll be a form there to sign up. We'll also have a QR code at the end of the session and share the deck with links to join the beta program. I'd definitely recommend it — it gives you early access to a lot of the product features we're building and actually helps shape them as we go.

As Adam mentioned before, there's a sense of community we're trying to drive. If you're keen to be part of the product strategy and direction, definitely join the beta program. It's a great way to help us get feedback and build the product towards how you're looking to use it.

So really cool things there — lots of things that hopefully make your life easier, and lots of little things that, added up, make a big difference.

In terms of the next theme — getting data in the right state for AI. Adam mentioned a couple of use cases. Lots of organizations are looking to develop AI solutions, and many of you on the call today have already developed quite a few as well.

From working with customers and speaking to organizations, a lot of the research tells us that organizations not getting the results they need from AI often have data that hasn't been prepared in the right way. Inconsistent data limits the accuracy of the model and the outcome you're looking for. And often data prep can take a long time — it can be quite monotonous. Those are some of the key challenges we're hearing from organizations.

Keen to know from your perspective, Marius — what are some of the things discussed at Domopalooza that will help address some of those challenges?

Marius: Yeah, definitely. We definitely have to talk about Magic ETL and the new data models and the semantics around those two as well. Happy to showcase them directly here.

So let's jump into Magic ETL straight away. There are some really cool new capabilities I want to highlight. You can see straight away the different sections we can create to make things more structured and organized and easier to read, plus the annotations. If I go in, I didn't build this data flow, but I can see comments telling me what's going on. In this case, we're loading data from Salesforce, bringing it together, and transforming it — combining this with a sales territory mapping we do on the right side.

Let me quickly introduce you to loads of quality-of-life improvements that definitely made my life much easier when building Magic data flows. For instance, the typical workflow is finding an action tile on the left, then dragging it into the canvas — which is fine in most use cases. But when you build larger, more complex workflows, you might want to speed this up. Now you can simply right-click and add an action directly to the canvas where you right-clicked, and you'll see the most used tiles and actions straight at the top.

Fun fact: adding a formula is the top-used tile in all of Domo. So let's add one of those. And another small but really useful adjustment — we can now configure the style before we actually connect it into our data flow. That's going to save some time.

On top of that, if we have a more complex flow and want to focus on a particular part, we can now enable and disable certain sections and actions directly with a right-click — disabling them if we want to focus on a different part of the flow.

We've also added a couple of brand new actions and tiles which I absolutely love. First is a split filter — we can define how we want to filter data and then how to use those outputs. In terms of Salesforce, we might want to filter closed-won and closed-lost opportunities and use them in a different flow or even create an output. Similarly, with a split join, it tells us exactly what is joining and what is not joining. We stay in control of the data and how it's being transformed. We can see not just the data that has been joined but also the data that hasn't been joined, which is just as useful sometimes to troubleshoot and understand what's happening.

This is all GA already — you can use it directly within your instance. Now we jump into something coming soon, which will be in beta soon and released later today. And one hundred percent one of the most exciting features is dark mode. Let's switch it straight into dark mode. It's definitely great for your late-night ETL sessions, or anytime really. And you can now define and configure how you want the UI to look so it really works for your workflows.

We also see raw telemetry — what's actually happening to the data rows. We can see a thousand coming in, but we're filtering all of them out. That's something we need to directly adjust, otherwise we'll see it impacted downstream in our flow. Just a little sneak peek into what's coming soon.

When we have our data ready, we definitely have to talk about data models. We can now combine and create relationships between our datasets and tables. CRM data is very complex — loads of different tables. Now we can create one clean data model to use as a foundation for our cards, our apps, and particularly for AI. It's going to be very useful telling AI how the data is relating to each other.

We can add any sort of table or dataset within Domo as long as there's a relationship — like an ID field. That goes hand in hand with the new schema tab, where we can see what fields and columns we have in our data, and most importantly, the metadata around it — descriptions, and in the AI context, synonyms, which is going to be really useful. We can also enable and disable certain fields for AI. So we're merging AI readiness with the new schema viewer.

And one more feature I quickly want to show is the new worksheets. That's going to be the default for exploring data, especially if you work a lot in Excel — a very familiar user interface. It's GA now. You can group, create new columns and functions, and really dive deeper into your data with a very familiar interface.

Perfect. Now over to our third theme — back to you, Joe.

Joe: Thank you, Marius. Yeah, late-night ETL sessions — I love that. So in terms of what we went through — a big focus on Magic ETL and all the improvements we've made there. Certainly seems like quite a few people in the chat were pretty happy about those.

Data models — I can tell you that it will be released later this month, around next Wednesday the twentieth. Quite a few of these releases will be coming out as generally available then. That's been a big request from a lot of customers, so super excited for that.

And then around workflow updates and the AI solutions piece — we know from working with a lot of customers that some are looking to deploy AI and do it in a way that improves efficiencies and automates things. I would definitely look into Workflows to begin with. That's one of the big ways you can start and achieve a lot of automation across the business. Please contact your CSM and AE to explore that further.

In terms of the next and last theme — continuing around the AI space. You want to build AI solutions really quickly. There's sometimes a feeling of: how do I do this? I don't have the technical skills in house. I don't know how to code things. But the CEO is telling us we need to find ways to implement AI in the business. How do we do this?

A lot of companies and customers we work with have invested in AI assistants — things like Claude, Gemini, or ChatGPT — but there's this feeling of maybe Domo doesn't really integrate very well. We've invested in Claude, but how does that work with Domo?

And then the last point is our AI chat — how can we use that in the best way? How can we customize it more and really share it with our customers?

So Marius — what are some of the exciting new things coming that will help address and answer some of those challenges?

Marius: Yeah, a hundred percent. AI is obviously super exciting — we could probably have two or three webinars just on the AI capabilities. But as a quick highlight reel: we definitely have to mention App Catalyst. If you take one thing away from today's webinar, definitely try out App Catalyst, which is fully available.

Think of it as all the apps you always wanted to have and may have wanted to build in Domo, but couldn't quite find the right time for. Now is the time — App Catalyst will make this ten times or even a hundred times faster. I use it a lot for prototyping, but it can build complete production applications. It works like your AI assistant — you start typing, add a prompt, and there are even starter prompts to get a feeling for how it works and what kind of information App Catalyst needs.

I can quickly show you one of my more recent examples — a travel space account management dashboard. You can see it's very highly tailored to exactly what I needed, what I requested, and in terms of design, what I wanted. That's already a great starting point and I can further iterate on it. That's going to be a really important capability to try out and prototype certain AI use cases. We're going to come back to App Catalyst in just a moment.

But that's already available. Now we're going into something coming soon later this year — our new Domo AI library. That combines two things: on one hand, toolkits for agents to interact with the Domo environment — things like querying data, building cards, building apps, even building ETLs and workflows. You can combine these into toolkits to give those capabilities to your Domo agents. And in the future, your own AI assistants as well, which is super exciting.

To have a look into the new agent experience — you can build agents that interact with the Domo environment in all sorts of different ways using those toolkits. One of the very first use cases is like a Q&A chatbot to analyze structured and unstructured data. And you can see it's like the AI chat capabilities we already have in Domo, but much more personalizable and customizable.

I can go in and define the model I want to use, define a role, define instructions, and always have the agent right there in the panel where I can test it out and see how my changes are affecting it. Here are the toolkits — I can add toolkits to my agent. In this case it's quite simple; it just needs to query data. And really importantly, in terms of grounding the agent, I can add knowledge — datasets, unstructured documents, or file sets directly to my agent. I can even tailor the UI settings, like a welcome message or preview questions.

And for me, personally, really exciting — we can embed these agents anywhere. In other portals, products, websites — you can really take this wherever the agent is needed. We already see here a nice analysis of the data and really prescriptive recommendations on what we should do. So that's a bit of a preview into the new AI chat capabilities coming very soon.

And that leads us perfectly to the integration via MCP — to our AI chat agents and AI tools. I use Claude pretty much every day now, and it's really, really powerful. With the Domo MCP, we allow Claude to access and query data directly from our Domo instance. Let's bring Claude into the picture as well and see what we can do. Claude gives us a great overview of what's possible and key insights. Because Claude knows I'm part of the marketing team, it already gives me recommendations on what apps and cards I might want to look into. You can infuse Domo data directly into your AI assistant workflows.

Let's try out one more use case, where we're in the role of an admin. What are the datasets that need my attention right now? This is a high-value use case — I don't have to log into Domo or do the analysis myself. I can ask Claude to tell me what datasets need attention that power a lot of cards and are potentially stale or not refreshing correctly. This is a live workflow — Claude is accessing and querying Domo, getting the live data, and now giving us the response.

We see the top datasets that need our attention. This is our internal demo environment so I'm not too concerned, but in a real production environment, that would be something a data steward and admin would need to look into. And because Claude gets the data directly from Domo, it knows where to find all of that data. I can just click the link and I'm straight into Domo with the dataset, ready to start looking into the issues and solving them. Really powerful — infusing Domo data directly into your AI assistant workflows.

I'll pass it back over to Joe to wrap up and start the Q&A section.

Joe: Perfect. Thank you, Marius. Quite a lot to go through there. App Catalyst is available now — use it to build prototypes, use it to build really cool custom apps. That's definitely been a big game changer.

New models, the AI library, and agent builder are going to be huge. We've got a lot of customers looking at how they can build their own custom chat experience and share that with their customers — put it on their website, maybe even monetize it. Love to get into more details about that with you guys.

And MCP was probably one of the biggest themes of Domopalooza. That ability to integrate with your AI assistant makes a huge, huge difference.

I see a couple of comments in the chat — some people are quite keen on the MCP piece and instructions on how to link it. The release notes — if you scan the QR code or click on the Docs element — will have all of the documentation, which includes the MCP piece in terms of how to connect it. But we're also happy to set up time with you and guide you through that integration because I think it makes a big difference.

For those of you who weren't able to attend and are keen to watch back some of the sessions — click and scan the QR code, it was all on demand. The keynote was a particular highlight for me, so I'd definitely recommend watching that, and a lot of the product sessions will go into more detail on those features.

We mentioned quite a few times around the beta program — please sign up for that if you're interested in testing a lot of those features early. Scan the QR code or there's also a form in the Docs area.

And then quickly — Marius, before we go to Q&A — you know, I'm a customer sitting there with a lot of requests from the business. How do I best plan and prioritize for those AI use cases? Just a quick couple of minutes to show us how that works, and then we can welcome back Adam and go through the Q&A.

Marius: Perfect. Absolutely. Because that's something we hear a lot — there are a ton of ideas out there in terms of how to use AI, how to optimize certain processes and workflows. But customers need a bit of help with the strategy and prioritization around this. So we've built an AI Transformation Plan tool, which is super powerful for creating a bit of strategy and structure.

To give you a quick overview — this is generally the process: you map the processes you want to improve with AI, map them to the benefits and the effort it might take, assess whether the data is ready, whether we need to transform our data, and so on. Then you get a prioritization matrix — what are the big bets, what should we do today as number one priority (like a data quality agent, for instance), versus what's more of a nice-to-have or not super important right now.

You can click into these and see further context and information on what data is needed. There are a few sample entries to explore. This is a tool we can deploy directly in your instance so you can use it directly in your Domo environment. Please just reach out to us and we can get that set up and talk you through it in detail.

Because the outcome is that you can then create App Catalyst prompts that we can copy and paste into App Catalyst and already see a prototype of your top priority use cases — like the weekly podcast, for instance — and see how it works and iterate on top of that. Super exciting. Definitely worth checking out further — the AI Transformation Plan.

Joe: Perfect. Thank you, Marius. So as he mentioned, please contact your AE or CSM to get access to that. For all non-customers who are looking to come on board, reach out to me — I'll put my email in the chat, please keep it work-related — and I'll happily get back to you and give you access to that.

Now we'll finish off with a bit of a live Q&A. So we'll welcome back Adam to the stage. We've got quite a lot of questions to go through. So I'll try to pick the hardest ones first.

The first one is from Diogo: after deploying an application from App Catalyst, can you use it again to make changes? Do you want to take that one, Marius?

Marius: Yes, absolutely. You can iterate on it completely. I showed you one of my apps and I just went into my history — we can pick it up from there and iterate further, add further instructions, and make changes. That's one option. Or what I also like to do: you get the code directly — the HTML and JavaScript that App Catalyst creates — and you can pull that out and use it in your AI tool of choice to help you redesign it and bring it to the next level. So there are two ways to address this.

Joe: Perfect. Thank you, Marius. One for you, Adam: with the work you're doing on AI agents, you mentioned quite a long list. How are you approaching engaging with the different teams and people in the organization and bringing them on that journey? And are there any particular challenges you've faced?

Adam: Wow. Thanks, Joe. I mean, we've had quite interesting twelve months. We've effectively brought two travel management firms together to form the Good Travel Collective, so we've had two if not three of everything within the business.

For us, it's kind of going and focusing on one department at a time. Go to finance and say, hey — what are you guys doing? What are your manual processes right now? Really trying to understand their pain points. The reconciliation piece I mentioned earlier — at the moment some of that is done completely manually. But with using App Catalyst — which I absolutely love, and my boss absolutely loves it too (I will restrict her access at some point if she keeps at it) — just being able to put your thoughts down as to what you want it to achieve, and then work with the tool as it asks you questions, to then effectively deliver something that could be game-changing.

It's just literally listening to people, going there, asking them questions, and showing them what you can do in Domo.

Joe: Perfect. Yeah, thank you, Adam. And shout out to Kelly if you're on the call.

The next question: as we integrate Domo data into Claude, how do we manage GDPR, particularly regarding PII data? Marius, do you want to touch on that?

Marius: Yeah, a hundred percent. It's a big question, but as a summary: Claude will query the data live from Domo. So all of the security and permissions that you've set up on the Domo side will be respected by Claude as well. There are things like personal data permissions — PDPs, column PDPs for PII data. All of that will be reflected. So if your Domo environment is GDPR compliant, the use of MCPs shouldn't change any of that.

Joe: Thanks, Marius. And another question: what's the difference between App Catalyst and MCP? Maybe share some example use cases for both.

Marius: Yeah, a hundred percent. It's a very valid question because we interact with these tools very similarly — through prompts and natural language. Maybe I'll share my workflow a little bit, because these tools interact and collaborate really well with each other.

For instance, you might want to start in Claude — which has access to Domo data via MCP — with an explanation of what kind of app you want to build, your plan and objectives, the audience, maybe some design inspiration. Then Claude can actually generate an App Catalyst prompt for you. We bring that into App Catalyst, copy-paste the prompt, and App Catalyst goes to work building that app. Then we already have a really powerful version one of our app ready to go. We can iterate directly there, or bring it further and back into Claude. That's one of the workflows I use — really useful for getting the best initial version directly in Domo with App Catalyst and Claude working in conjunction.

Joe: Perfect. Thank you, Marius. And I think we've got about one minute left, so we'll close things off. Thank you for your time today, Marius — guiding us through the product and bringing it to life.

To all the customers, non-customers, and people on the call — reach out to your AE, reach out to your CSM, reach out to me. We'd love to explore a lot of these tools further with you. Thank you, Adam, for joining us — I really appreciate you going through your experience and helping answer some of the questions from our customers.

And also, shout out to Jasmine, Hannah, and Ria from our marketing team — a lot of time and effort went into this, so I really appreciate your patience and everything you set up for us. We hope this is the first of many more webinars. That's it from us — thank you and goodbye.

Adam: Thank you all. Take care.