Hi, everybody. Welcome on. Welcome to today's session on data monetization. We've hopefully got some great thought provoking content for you to, fill this in on today. So without further ado, let's get into it. Firstly, as is tradition, let's do some introductions, and I'll start. So I'm Max. Nice to see some familiar faces in the positioners menu. So if you know me, I won't take too long. And if not, then, yeah, I'm the solutions, team lead for EMEA InterWorks, and our team works with clients like yourselves, to understand, create, improve, optimize your data in analytics to stay in whatever that may entail. Think of us as your strategic data agony ants. If you're having difficulties with certain parts of your data stack or just general advice on how to optimize your existing solution, then please feel free to get in touch with anything that we discussed today in this session or anything that may be causing you some some issues outside of that as well. I've used Tableau as a significant part of my career so far. To date, I love it. I'm kinda bought and paid for Tableau. So it gives me great pleasure to, to welcome Zoe Mascarenhas from Tableau to walk you through some of the more important Tableau specific elements for our discussion today. Zoe. Hi, Alia. Thanks so much for having me. As Max has said, my name is Zoe Mascarenhas. I'm a Tableau account executive here. I look after mid market and predominantly work with, professional services. I can see a couple of, familiar names as well, so thanks for the team for joining. And, yeah, really looking forward to the session. Nice. Thanks, Zoe. So probably aware of InterWork so far. It's why you're here. A few of our partners, a few of our clients, familiar logos, hopefully, I'm sure to all, partners on the right hand side of the people with platforms that we believe are doing the best, out of the the various different tools that are in the industry. And if you have any interest in any of those and you're not using them already, then please feel free again to give us a shout, and we can give you a walk through of, those tools. Generally, we've received lots of lovely accolades from, those partner products. I won't bore you too much with those details, but we're well established in, various parts of the analytics industry. Today, we're gonna be talking about data monetization. And as such, we're not going to dive that deeply into some of the fun topics like data architecture, structural design. We're going to assume that some of your data is already able to be shared with your external, your whoever it is within your external network, be it clients or maybe even public, within your governed platform like Tableau. So we're gonna be discussing how Tableau and several other tools potentially can work together to provide you an offering for your clients where they can access their data. There's so many different directions that we could take this conversation, in terms of processes, platforms, architecture, branding, GTM strategies. So we've taken a subset of the most important to share, the ones that we believe are most important to share with you over the next hour. But as mentioned, if we need to go into more specific detail with you individually, then please give us a shout. Today's agenda, well, firstly, we're gonna introduce ourselves, which I think is a big tip. We've done that already. And then we're gonna discuss the agenda for today, which we're currently ticking, which is great. Next, Zoe is gonna discuss Tableau's embedding capabilities. So I find that often clients don't even realize that it's possible to embed Tableau sometimes. Although it's not essential for data monetization and sharing data externally, it certainly gives your organization more credit for, for your analytics platform that you're providing if it's kinda seamlessly integrated into kind of single platform for all your analytics data, your sort of knowledge and information and maybe help videos and all these sorts of things. So we're gonna be talking about how you can achieve that with embedding in Tableau. Then Then we're gonna dive into data monetization in more detail. So this is kind of a subset of embedding in my own list. Not all embedding opportunities or, embedding, solutions necessarily have to be selling that embedding to your clients, which is essentially what we're, what we're suggesting but, generally, if we are doing that, then there's certain other criteria that we we might want to, want to satisfy. So how does data monetization work? Where do almost all of us subscribe to data monetization in our day to day lives, kind of indirect versus direct data monetization? And how do other companies succeed here, in this area? And how should we think about data monetization from a sort of technical, point of view? Zoe's then gonna take us through usage based licensing. So in Tableau, this is a relatively new SKU. For certain use cases, this can enable you, to scale your offering by ensuring Tableau's, cost to your organization scales in line with the benefit that your customers are receiving. So if your customers use that platform a lot and get a lot of benefit from that, then the cost goes scales literally with that, with with that benefit, rather than the RBO role based licensing, which is a kind of flat fee per user per per month. Finally, we'll consider branding and styling of your platform using the InterWorks Curator product, and we'll kinda consider the kind of buy versus build, options that you have, available to you, when embedding Tableau in that kind of appealing website that we're envisaging. Curator allows you to do this without writing any code whatsoever, and gives us that styling and branding capabilities as mentioned. So get into embedding Tableau. So your customers need insights and you want to put that in an embedded platform. Obviously, use away. Perfect. Thanks. So I suppose just just to start with, I wanted to give a little bit of context as to what we're hearing in the market and what we're seeing kind of challenges being. So simply having data isn't enough. Businesses really do need to be turning that data into actionable insights to drive and derive value from it. Companies that fully embrace data with insights are significantly outperforming their competition. Forrester has reported that businesses with a really mature insight practice are eight times more likely to experience around twenty percent growth compared to their competitors. A key way they're achieving this is by turning their data into an asset and generating a new revenue stream. A powerful way to achieve this is by enhancing your current offerings with embedded analytics as Max has kind of alluded to before. So integrating analytics directly into an application not only helps you meet your customers' needs, but also significantly adds value to that product. By addressing new use cases with a data driven insight, you can then appeal to a broader audience and significantly grow your customer base. Additionally, another way to do this is also to unlock the full value of data by sharing it with your network and ecosystem. So this could be your partners, your suppliers, but also stakeholders as well. Just as your organization will use data to improve performance, by broadening your ecosystem and sharing your analytics with them, they can then tap into those insights and really help to streamline processes, identify efficiencies, and it also allows you to collaborate significantly more effectively. And having this data driven approach between both parties will help strengthen that relationship and ultimately drive mutual success. But as Max said, this these are just a couple of examples of how we could derive additional value by embedding analytics. But for the purposes of today's webinar, we'll focus predominantly on that data monetization opportunity. So back over to you. Thanks, Zoe. Great. So I suppose we've mentioned the various data monetization a few times at this point. It's probably worth clarifying what exactly do we mean. So data is valuable. We hear this all the time around data is getting more valuable than all of these sorts of phrases. And as organizations, we generally collect a lot of data to support us in order to create data driven decisions. And a lot of those data driven decisions can be useful to our clients and our, ecosystem, as Zoe mentioned there as well. So your clients can benefit from these exploratory insights in the same way that your organization does, and that's offers an opportunity for us to kind of upsell and create this data monetization platform. I wanted to go through a couple of very simple case studies that we have from some of our clients that, and and projects that we've been involved in, that allow us to, or allow our customers and our clients to to leverage data monetization, within their organizations. So the first one here that I've got is simply get results. These are one of our clients that have data monetization at the core of their business. So often, it might be that, data monetization could be a sort of separate SKU that you offer to some of your clients, maybe for one department, one of your projects that it could be, an idea. Sometimes businesses set themselves up in this in this way as their core offering. Their primary product could be data monetization, and that's certainly the case when it comes to Simplicate results. So they sell a data driven product, surfacing skills and development information, to staff at their customers' companies. So at InterWorks, it could be that, we feel like there's a gap, for instance, in in our employees and our consultants knowing where they should go next, what they should do, and what skills they would need to progress to that next level, become more employable in a certain area, and what areas are kind of more valid and profitable for them to to do that too. So kind of giving people not only a bit direction in terms of their career, but also understanding the requirements in order to move in that direction. So, simply, use a, a curator instance to surface this to their clients, make it nice and scalable, depending on, the relationship that they have with that client. It might be that they have their own instance, then maybe there's a separate one, or maybe some people are on a multitenant platform. Understanding that there are skill gaps and showing those organizations staff, that information allows them to prioritize their career checkers in that kind of ever changing world of tech and and otherwise. So, yeah, using Curator, simply have a kind of wonderful user friendly interface for their clients to to dig into that data and information, harnessing the power of really intricate and lovely Tableau dashboards that they use there as well to be able to compare two two different career paths together, for instance, and really kind of see the differences and expectations that they can have on each of those. They leverage usage based pricing usage based licensing that, that we'll we'll talk about shortly. And this allows them to be charged based on the value to their customers as mentioned. They pay more if their customers use the platform more, allowing them to, to charge more as a result because their platform kinda has more value in that case. The second, use case and, and case study I wanted to discuss here was Ocado retail as something that's been very publicly shared on, on on Tableau and and and Salesforce, documentation and and and public case studies as as well as within conferences. Ocado retail created the beat platform to to showcase data, to their suppliers. So if you're a large biscuit manufacturer, for instance, you may, log in to beat to see how your biscuits are selling, on the Akado platform. That comes with loads of capabilities and, and something we'll be discussing shortly is how you can have that in a kind of tiered approach where maybe, as a small manufacturer that doesn't have that kind of budget to really reinvest in that kind of marketing and understanding of where and how things are selling specifically within Ocado. Maybe they're on the free tier, the freemium tier, the the the the bronze tier, basic, whatever you want to call it. We can kind of help you with that structuring. Maybe if you're selling huge amount and you really want to make sure that you understand things around promotions like we have in the screenshot here, there's separate dashboards, a separate content that's gonna be, available to you. So we helped, the Ocado team with, not only, the Curator products and embedding our, their dashboards rather in the Curator product to offer that kind of single and unified front end for all of their content, not making them log in to Tableau, directly as a platform. They are logging into Tableau, but they don't realize they are because everything's embedded in that separate front end web user interface. So we also helped in this way, with the design of that tool. Our experienced consultants performed or or created a lot of different contents for, this project. So in terms of, the experience of people logging in, it's not just, you know, how does that login page look and what does the homepage look like. There's actually quite a lot more that that can be done there to create that kind of cohesive and intuitive platform. So we developed, content like site maps so that they understand where a user goes, when they go to each one, and how they navigate from one dashboard to the other, and how all of it fits together as a sort of collection that is intuitive for the end user to navigate. There's also kinda user experience guidance, which which can help there as well, and things like tutorials that might pop up in front of a dashboard, which might not be supported natively from the product and not our the Tableau products, and I'll I'll get to that shortly. Also, we help with design templates. So style guides, I'm a big fan of as someone tablet dashboard in my time. I love having kind of some of those style decisions taken out of my control because it just makes everything feel a lot more cohesive. It gives me more, or it gives me more direction and fewer decisions to make on a sort of click by click basis. What color should this be? What type of chart should that be? What sort of borders and access should I put on this chart? For a lot of that is already predefined, then you have some fantastic efficiencies that you can gain in development as well as the final product looking really cohesive and nice and everything fits together, in in a really kind of lovely way. On top of that, the experience team also developed things like loading GIFs and icons. And I remember with when we were developing this as as part of the, the Beat project, we were kind of talking about different names and things that the the the the product could be branded as and even introducing things like loading GIFs. And in this case, we did a few different examples of, of having a beat, a beat group that had a kind of a a heartbeat kinda going through it as well. So you're tying together the the product level information of fresh produce as well as that kinda heartbeat and the insight and and and tying all those things together, which was really effective. Do you remember on that project, actually, they were gonna maybe call it, rocket, and we had a a a a experienced designer in the US who really didn't understand the concept of of of rockets as as a kind of salad ingredient. And and we had to kind of explain after a couple of sessions that it's basically the equivalent of arugula, and then suddenly the penny dropped. It's like, oh, I get it so much more now. So it's interesting how I'm kind of looking at your demographics and the people that might be accessing the platform just from a sort of marketing and some graphic design experience, how that can, really affect the decisions you make when it comes to graphics and and that kind of thing. Learning curve for me for sure. Also, when, when when they mentioned that their product is based on Tableau, then people really start to look up or start to really pay attention. There's lots of these sorts of products in the market, lots of analytics tools in the market as well, but Tableau is still a differentiator in this place because people expect that sort of interactivity when it comes to Tableau. And they they expect the ability to get high quality information out of it because of the flexibility of how Tableau is designed. It's not just that kind of chart wizard where you say, I want a pie chart. It's gonna be different shades of blue. There's loads more in Tableau as I'm sure you're all aware, and that we can kinda leverage in order to create something that's interesting, engaging, and actually explores the data and analytics rather than just building reports of people. So, again, what can we monetize? What is data monetization? What options do we have here? So we're gonna split this into three sort of subdomains here. The first one being just kind of the raw data. This is not entirely useful, but it is a very common request when it comes to that kind of supplier, customer relationship. I just want the data. And that's something we hear a lot. And, this is kind of it kind of harmonizes with Tableau's kind of mission statement as well, in that you can just give somebody the data, but then what do they do with it? And for me, users are gonna probably take data from this platform. They're gonna download it. They're gonna put it into their own analytics tool. Commonly, that might be something like Excel. And they're gonna have a, they're gonna do some analytics on it after that point. They're gonna aggregate the data in certain ways, and they're gonna spend some time, which is really kind of a key, sort of metric here to pull that data, out of the system, on a regular basis, whether that's weekly or daily. And they're gonna put it in that platform, and then they're gonna create their analytics at the back of it. Now that analytics could be valuable for lots of different customers, They might be doing something very simple like putting it into pivot charts and creating bar charts from the back of it. So it's time intensive, and it's a great opportunity again to upsell this into, an analytics package that does a lot of that for them, saving them that that that time and effort. So this is where your kind of second tier comes in, your analytics tier. So this is gaining access to maybe basic trends, outliers, performance metrics, all within the tool without the need to download data at all. Perhaps in some more niche company specific analysis, they might still want to download that data because they do something that's maybe very specific to a particular meeting. So you can decide at that point whether you expose that or you don't. This is a benefit, this benefit of Tableau rather, saves customers time if you're preparing this analytics for them, and, and and can then be kind of shared across lots of different customers and can then, therefore, deliver more value. And, potentially, you can also sell that into a kind of a larger or a larger cost here essentially. The final one here might be your insights. So this is kind of going further with analytics to be fair. And this is kind of building more context around your data. And this is where your tool can be distinguished in provisioning content that your clients perhaps can't create on their own. So what do I mean by that? Well, in terms of, you know, something like an or a large retailer, they might be leveraging insights, but it's not necessarily just my data as someone who sells biscuits. It might be that I want to compare my biscuits against all the other biscuits that are being sold within the platform. And maybe I want to benchmark to say in certain months, some biscuits are selling better than other biscuits. And that benchmarking and comparison can be really interesting on that seasonal level. So you're leveraging maybe other data that you have and depending on your relationship with those clients or customers that you have within your tool, it might be that you have a premium tier where you're allowed to expose the fact that biscuit company a is doing better than biscuit company b specifically, or maybe you're just looking at an average over all of the biscuits or or or something like that. Your percentage of overall biscuit sales. I'll stop seeing biscuits at some point. So this is where value kinda goes from left to right here where you've got the raw data being pretty valuable. A lot of the time, it's a lot better than doing nothing in this in this, sort of area if you do have the opportunity to to to create a, data monetization product. But as we go through, we've we do have this opportunity to be able to create a opportunity to be able to create a much more valuable product that has, really, really interesting, repercussions for your clients and, therefore, as an opportunity for you to monetize. There's two different types of base monetization. And, the first one here, that I'll kinda want to look at was, indirect monetization. So there's three different platforms here that, I'm sure a lot of people are probably aware of, and check them in the chat if you know what this first one is. I'm sure people have seen this. It's kind of kind of all around us in direct monetization, and, apps that we use every day, subtly keep us coming back for more based on some of these extra value add sort of schemes and products that they have as part of those applications. Again, hopefully, you recognize some of these. The first one there, I don't know if anybody's mentioned in the chat what that is. No. They've not. Maybe it's maybe it's new to everybody who haven't seen this. I doubt that. There's no way everybody knows what this is. This is the, the Spotify wrapped, that, this is a scheme that comes out every year. If you're a Spotify user, I'm sure you've seen this. It's very difficult to to avoid. So every year around the Christmas time, it kinda wraps up your year. Right? And and I'm sure if your social sort of networks are anything like mine, you get bugged on WhatsApp by in several different groups by everybody sending in their Spotify rep screenshots and saying, look, look how much, you know, Siberian countries that I'm listening to. I don't care. But, anyway, so people definitely will be sharing this, and that's kind of a key component of, of, of of this this wraps opportunity. So, Spotify uses this not only to kinda show showcase to you what you're doing and and and kind of the diff the total amount of artists that you listen to, total amount of songs, different genres, your favorite artists, your favorite genres, all these kind of interesting, interesting pieces. But a core part of that is the branding that's on top of that. It's really exciting branding, and it encourages people to share it with other people. And that therefore, introduces a little bit of FOMO in people that maybe don't have Spotify. Maybe they're Apple Music, customers or they're on Tidal because they love the sound quality, something like that. So it shows people what they're missing essentially in in this core product, and it's delivered in a really engaging format. And style is is important here. As we can see, the color schemes are brave, shall we say. They're they're quite intense, and it definitely grabs the attention. It offers a mix of basic analysis, so your favorite artists as I mentioned, that kind of thing, as well as kind of more advanced machine learning, that might predict how many future listens they expect you to have on certain artists. Or, maybe you can rediscover forgotten favorites that you've had before or broaden your musical horizons to something that they think you would like based on some sort of a priority algorithm, kind of like market basket analysis or something like that. It also offers things like badges, like you're a tastemaker if you're listening to stuff before everybody else is or you're a pioneer, and and it kinda gamifies the experience for you to think and it'd be encouraged to use the platform more even something as simple as just listening to tunes. The second one, again, people are probably aware of so this one yeah. There we go. Animation. There we go. So the second one, you're probably well aware of what this is as well. This is your Google Maps feed where, it shows you a summary of kind of your all time data as collected by Google. And we're becoming kind of more and more aware that as we're using what is a fantastic product, let's be honest, Google Maps is brilliant. I use it when I'm traveling abroad, especially if I'm going somewhere for work and I need to know how to get from Zurich airport to customer site, and I need to know what bus to get, and I need to know when that bus leaves. This is this is a game changer. I don't know how people did it before. I might be aging myself there, but, do you get a map out and start reading it? Do you ask somebody? In this case, it's all in your pocket. It's brilliant. But, now we know that we're kind of more the product, of of those sorts of systems, and there's kind of a bit of shared benefit there. Let's be honest. So, that benefit, it gives you these summaries as well. They they're kind of expressing this data that they're collecting about you back to you, which is nice and transparent. We're collecting data about you, but also here's some cool information about where you've been and what you've been doing. So you could consider it creepy. You could consider it just really useful and kind of interesting information. I I think I'm on both sides of that. And then finally, you've got Apple screen time. So, this is whenever you're using iOS software, obviously, tracking what you're doing and when you're doing it. And, this is showing your usage of various different applications, throughout your day. And this can be framed as kinda combining screen addiction, which it kind of originally was, and then also it can be, you know, showcasing productivity. It's a really simple interface, and it showcases basic analytics here that's that's really useful. You can see in this case, I've been using tablet desktop for almost seven hours that day, which is, maybe not so common anymore, but sometimes I wish it was. So give customers, insights that are personal to them is kind of a fundamental of this indirect monetization, and it it creates that sort of sense of value and sense of loyalty from the products that you're selling. The second one here is that direct monetization that we kinda touched on before, when we're talking about Ocado or we're talking about, Simply. So direct monetization is where we're actively asking somebody as a separate SKU to pay for a service potentially. Maybe we have different pricing structures for each of these and and drones might be free. But, generally, there's a separate offering here, that that exists alongside your core application or your core product. And people can potentially opt in to a subscription based service, paying for functionality that benefits them. Potentially, they get certain discounts if they spend more on your core applications. Again, all of this is something that you can design as a kind of product, product designer. And as mentioned, this can be split into different tiers here. So we've used a medallion approach for simplicity, but but you could also have something like a basic advanced or premium or however you want to kind of structure this. It doesn't have to be three, could just be two, could be more. So we've kind of split that raw data dump into bronze, silver, and gold. Maybe that's something that all of your customers expect, the ability to download that CSV or Excel file for their data. And also, we've got, part of that bronze tier might be some very basic performance dashboards and some of that, analytics, the aggregation where maybe you can invoke some filters and parameters, but you almost deliberately don't go too deep on that layer because you won't be able to be encouraged to move to that second and third tier. When you get to that second tier, that silver tier, maybe you add some benchmarking dashboards, maybe at a, a kind of rolled up level. So, like, the biscuits before, I said I wouldn't say it again, but I'm gonna, then maybe you can see the average to you're you're you're higher than average. You sell more biscuits than most, but you're not as much as the top one. But maybe you remove that information of the top one, or even if it's, anonymized information. Maybe you remove that and you just give that average at the silver tier, and then you kind of expose that anonymized or not at the gold tier. So lots of different ways that we can kind of advance your, upselling methodology. And, actually, anything that you have as a sort of mechanism in Tableau, be it your extract refresh and something that's even as simple as that. And the bronze tier could be weekly, and at the gold tier, it could be daily or every half hour or even a live connection to see what's going on right now. So there's lots of different features that you can expose deliberately, at these incremental tiers in order to encourage and have that go to market strategy. So this offers business customers professional insights and analytics to enable them to make data informed decisions. So exactly the same way that that you leverage Tableau, hopefully, in your organization, you can apply this to your external use case as well. So there's a few things that you might want to consider as part of this approach. The first one being a data pipeline and something that means that you have a nice stable, governed, useful data infrastructure. Again, we're kind of assuming that that's already in place, and a lot of the time it might not be. But if you do have that infrastructure, then that makes everything after that point a lot easier. If you're going to market with a strategy that has something that's maybe not, as stable or as governed as you would like, then you're gonna run into problems later. The second part here is access to a portal to host analytics, and that could be your Tableau portal in this case. And we would certainly recommend in most instances that that is the case. Some clients use this native front end as their monetization platform generally. I worked in a previous company that did that. We were a workflow, software based in Cheltenham, and we had an analytic suite, which is where I first started cutting my teeth with Tableau and and and really fell in love with that as a product. And we didn't invest in development time to be fair to to set up that analytics portal to wrap it in an interface. We just said, you can log in to Tableau. It's part of the product. We upsell that as part of kind of an OEM strategy with Tableau, and people can access their data in there. And that's fine, but it doesn't necessarily give you that kind of credit for the platform that you would like. And that's where embedding the BI tool in another instance comes in. So you really want to kinda take away the fact that you are you kinda want this to make it look like you've created this yourself and this is something that you're really taking credit for as an organization. You don't necessarily want to expose the fact that we have created these dashboards in this particular tool. You want to make sure that it just feels like your brand and that you're responsible for creating all of this and you take the kind of products out of it really. Everything is still back onto Tableau, so all of your rules, permissions, your groups, and your access controls and governance is all still stored in Tableau, works in the exact same way. But you're saying dashboard x is gonna be available with this name in your branded embedded platform. And then finally, a modern UX. So everything wants to be wrapped in a seamless user friendly interface. And, again, there's obvious advantages of that. But the better you can go in that direction or the further you can go in that direction and the better the experience, the more likely people are obviously gonna come back and the more likely they're gonna drive more, more or have a better feeling about the product that you're providing them. So finally, kind of on the technical front here. I think this is very useful to understand exactly how, how how the architecture can fit together when it when it comes to maybe considering your internal instance versus how you can set up a data monetization structure or architecture. So if we have your existing hypothetical internal only Tableau cloud instance, We've got one database here symbolized from the green icon on the left. It could be, and there probably will be many. But for simplicity, just included one. And I've got role based licenses, that are available here on Tableau cloud with a with a double use of Tableau cloud site on there. This is kind of a standard set up that we see for, small medium sized businesses. So if we're moving into a data monetization world and we want to set up that separate SKU, that separate sort of work stream on top, then we would still keep everything as is in your current infrastructure. So you would still have Tableau Server, Tableau Cloud connecting to those same data sources on the same site and the same URL, so none of that changes. Everything's still the same. We're setting this up as a separate architecture. And if we're thinking about Tableau Cloud, somewhat this is this is still the same for Tableau Server. We would recommend splitting into a separate site. So you would have an external site as well as an internal site, and that has several advantages. One is it's probably true that you'll have different people administrating that, and you might have different roles and responsibilities on that second site. And it's gonna be probably a subset of the people that are responsible for your internal analytics. The second is you might want to imply different policies and government's controls on that second site like low level security, and you want to have that kind of multi box approach so that you make sure that nothing is from your external or none of your users from the external site can access your internal so that there's no slip of the mouse and you accidentally get so many permissions or something that you shouldn't see. So these are completely separate in this instance. And then the third benefit, one is that you might want to put curator or something similar to embed that into your, in into your customer portal. And it's much easier to keep those as separate sites again for the previously mentioned slip in the mouse reason. But also it allows you to have a separate site which can then have a different licensing model underpinning it. And that licensing model is our usage based licenses, which is a very separate use case that Zoey's gonna get into just now. So what is usage based licensing, Zoey? Great segue there, Max. Thanks. Thanks. If you could just play out the whole slide. So for anyone who's, looking at data monetization for the first time, this usage based licensing is a really great way of kind of starting that journey. The licensed model essentially lets you buy analytical impressions rather than licensing it on a per user base, which if you've got a high volume of low frequency users can be a really great way of starting that. Equally, this approach kinda helps you monetize your data, add that to your offerings, and scale without having to invest on unused licenses before you've started to take this to your customer base. So there are various different use cases, as Max has said, that this might be a good fit for. We do still very much support on, on premise instances as well as other role based cloud environments as well. But if you're starting out, usage based licensing could be a really great start to kinda dip your toe into that. It is. Yeah. And with the requirements for usage based licensing, this is only the one type of cloud. Is that what I say? Yes. It's only available on cloud, and it's solely for embedding externally to your environment. So yeah. Yeah. Absolutely. Okay. So it has to be embedded. It has to be external use cases, I. E. The domains of the users are not your internal customer domains. That kinda how that's established? Yes. A hundred percent. Yeah. Great. And a large number of parameters around the use cases for it. But yes. So as long as it's something that you're delivering through a portal, let's say, at to your external customers, that's where this will be a really great fit. Amazing. Yeah. I know certainly with some of my experience of of working in external use cases, there's, you you often maybe provision licenses for, say, one of your clients that might have twelve people that they won't have access to the the system. Now how you charge that company for those twelve people is completely up to you. But if maybe only ten of them ever log in, then, essentially, we're not paying anything to have those, those all all twelve of or do I say ten people log in? So two people are essentially you're not paying for because they've never logged in at all. So it derisks that from your perspective. Right? Yes. Exactly. And I think we've got, you know, various different customers who are externally using Tableau for different use cases. One of them if, say, for example, it's a consultancy organization that knows those users will log in without a doubt every month on the same days, etcetera, and it will be the same users, then role based might be the benefit because you are anticipating additional activity. But if, as I said, if you're starting out and also if it's a case where there will be seasonal spikes, so let's say it's a marketing activity and you know that there will be marketing events happening every quarter and you won't have a lot of that traction in between. That's where this will be, yeah, help you mitigate some of that financial upfront investment, to make sure that you can maximize benefits. Absolutely. So your goal based licenses are sort of like an all you can eat restaurant, and that's if you're if you're starving and you're going all the time, then that's that's probably a good model. If you're really not very hungry, then it's probably better to go to Greggs and and use the usage rates. I'm really good with analysis today. Yeah. And I think we should have found a way to bring it back to biscuits, but Yeah. Perfect. Hey. Thanks, Zoe. So when we talked about the the the different requirements that we have here, you've got your data pipeline, you've got your products, your your Tableau as a as a back end for your analytics. We also mentioned embedding. We mentioned that a few times, as being kind of core to allowing you to express graphically your brand, as as part of your product that you're going to market with. And this is really where Curator comes in, by by Intuorix as being a fantastic tool to allow you to do that without writing any code. We've kind of thought of this as as as kinda like a fast track to your data analytics. It could be that you use, Curator for a year while you potentially think about building your own product in in in, in line with that. Generally, one of the mistakes that we see people make is underestimating how much time and effort that cost and the expertise that are required in order to create those web based portals. This is where the fast track comes in for for data monetization and, and and embedding with Curator. So we can see in this lovely GIF that we have here, there is that back end administration panel where you can quickly create pages as people have done here, where you're embedding maybe videos, instructions for a home page, for instance, as well as a dashboard or the top five dashboards. All of that's baked into the Curator tool that we'll see very shortly. So, basically, Curator is gonna reduce the time to go to market for this first and foremost. And, for the cost, which is a very normal cost for for what Curator is, you can, you can create fantastic web portals, and maintain them very simply and easily, which is something that we'll we'll come back to shortly. So your challenge is that data monetization can be intimidating because of costs, and the need for an embedded solution to deliver analytics to your customers. And when we think about, you know, authentication integration, the JavaScript API, the different parameters of which there are many, the embedding Tableau is not the most difficult thing to do in the world. It's actually quite straightforward if you have, if you have web, web design and and and web developer knowledge. It's some of the extra things that come around that. So you want to limit the number of login screens that you might see or have, you know, one at the front and then nothing else afterwards. And that can sometimes be challenging when you're building your own. The solution here is that given the usage based licensing model that we just discussed, comparing that perfectly with Curator, the interested in reading embedded solution, it allows you to deliver analytics to your customers rapidly and reliably without extreme costs and the headache of custom development. And I always think about this as kind of like the tech data tech debt of your organization. We actually work with several companies, that, are currently maybe replacing the, the the portal or the platform that they've created themselves because somebody's left, and they actually don't know how to manage and maintain that. Maybe they had PHP, JavaScript, HTML, or expertise in the company previously, and that's not really the case anymore. And they don't anticipate that they're gonna be hiring someone else to do that, which is, again, another fantastic use case for Curator to be able to embed your Tableau dashboards in something that can be managed and maintained by a lot like myself who is, who's who's not someone who's experienced massively in, in these web developing programming languages. Oops. Here we go. So how does Curator help? So it's a flexible white labeling of your analytics. We can see three examples of different curator, publicly available curated sites that we can have a look at shortly. It's built for Tableau, which is a real differentiator for curator when it comes to the the product compared to some of the other products on the market where it's, you know, SharePoint or something like that. You can build these in other tools, but they're not necessarily built for this use case, which is where Curator become really simple in the back end because you're really focused we're really focused on having that as the primary use case of Curator, embedding analytics. So as much as we do have other wonderful supporting features of being able to embed other content that helps, the primary focus is analytics rather than the other platforms whose primary focus might be the other content and analytics is a kind of, sort of afterthought, essentially. So it provides extra functionality on top of the Tableau, interface, the Tableau, server, Tableau cloud platforms, things like PowerPoint scheduling. So in Curator, you can log on to a dashboard in Curator, and there's a little report builder button in the top right, which I'll then maybe I'll show shortly, where you can build a report. You can have your own template for your organization pushed into the back end of Curator, and you can make some selections on filters, and you can click save that as a slide to my report. You You can then go to a completely different dashboard on a completely different workbook, and you can click the button again after selecting some different, filter criteria, and it will save the logic of those, those saved selections. And you can export that now, or you can schedule that to export every Monday morning, for instance, send it to your boss and say, here's your report. I don't have to do anything anymore. So there's loads of extra cool features of Curator that make it useful for external use cases and internal use cases. And, again, with the external use case, you can expose more and more of these as you go up and progress into those tiers. We have very flexible hosting if you want to use software as a service where we host it as Interworks, or you can host it yourself. There's an AMI on AWS, for instance, that you can spin up really quickly and easily. And the main advantage for me is that it's quick and easy to administrate. You just have a a that back end capability where you can click on drop down lists that are all connected up to Tableau cloud to Tableau server, and you can say, I want to show dashboard a. You select it from a drop down list. You don't have to copy and paste any JavaScript code over and test the fact that you haven't missed some curly brackets somewhere. It's all just done through that interface, and, and and it's super simple and easy to create something. So then we come back to this build versus buy. And, again, the common mistake for me here is that we underestimate the development time and tech debt that you're gonna be, be be investing in when it comes to building something yourself. Again, I wouldn't necessarily not recommend somebody to do this, but I would consider both options here, and think about which one is, is is more beneficial to you based on kind of that return investment and and sort of value add proposition. So when we come to building something ourselves, we do require web development expertise, as well as maybe some back end integration expertise and platform knowledge of how different things are gonna be connected together, authentication. There's lots of skills that are gonna be required. Those obviously have the implication of a longer time to value. Realistically, it's gonna take you months in order to set that up, probably six months at minimum, depending on how deep you want to go into that development, and you need the expertise to do that, as I mentioned. With Curator, we can set you up a trial and you can get going tomorrow. It's very, very quick to connect up your Tableau instance. Obviously, there's a bit of a handshake that needs to be done between because it is secure, it is governed, and Tableau does have to say, yep. I'm allowing this thing to, embed me, essentially, as well as a curator saying, I want to be embedding this thing. So, there's lots of lots of different things that we have to add in there or a few different pieces that we have to kind of add in the back end. But, generally, in an hour's call, we can help you set that up. Some of the issues that you get with that building is authentication security, dashboard management in the long term because you're probably gonna be embedding direct links into that. If that dashboard name changes, what do you then do? How do who then manages and owns that? As well as the all the various different JavaScript API parameters. There's great knowledge and documentation from Tableau's perspective on this, to really list out and help you with I think it's developer dot tableau dot com. It's a really good interface for kinda elearning and understanding all the different capabilities of the embedded, functionality that Tableau has as part of the software. But it can be a little bit unwieldy if you're learning it for the first time. And then also there's design flexibility. So a lot of the design capabilities of Curator are out of the box. You can say, do I want top navigation or do I want side navigation? Those are two things that you just flip the drop down, and it will just shift. You then preview it in a little back end screen, and then you say, yep. I'm gonna commit that, and you just click okay. And then that will cascade to your end users, which is really, really useful and would take me a long time to actually code that into into a system if I would ever get there at all. No guarantees that I would ever make it. So the other option there is to buy something. In in this case, we recommend Curator, obviously. It's our product. So we, so this is something that can be owned by analysts first and foremost. It's something that if you can manage a Tableau server or Tableau cloud, application knowing about groups and projects and workbooks and worksheets and dashboards, you're you're already equipped to be able to manage your curator instance. Again, in an hour's call, you'll have the basics from from ourselves, and it's quick and easy to install. And then the app gives you more time to perfect that design, perfect the the graphical interface that you're then gonna be exposing to your end users. Native integrations for your solution, again, it's built for Tableau in this case, so everything there will be very straightforward and smooth out of the box. And our support team are fantastic. See Moe's there. So, yeah, big up, Moe. Incredible, support whenever you need it. So let's have a look at curator. Enough of me just kind of showing it or or talking about curator generally. Let's have a look at the Curator demonstrations here. So we've got curator dot InterWorks dot com forward slash demos. We make sure that we have that link. It's a very simple link. You type in curator demos into works that will definitely come up. And as part of this, you get a lovely little helpful video, where, our colleague Ben is gonna talk you through the, the the benefits of curator. And then we also have a huge number of a huge number. I think there's about fifteen different demonstration sites that you can click on here, and you can have a look at how that might appeal to you and the design for your sector, whether you're in health care or maybe you're in finance. We've got some excellent little demonstration sites that showcase some of the features the curator can provide to you. One that I'm gonna look at today is our data monetization, platform here. I do recommend looking at something like the retail platform as well, as a different use case. But this one is just looking at, you know, your generals of home pages and how you can embed a Tableau dashboard like the pardon me, the Flash store report for instance. And when that loads up with our custom loading gifts, again, none of this looks necessarily like it's coming from Tableau. But here, we can see everything inside that red box is Tableau, and everything outside of that red box is curated. So that's kind of the differentiator of where you would make adjustments to either of them. Inside the red box, you go into Tableau desktop, or Tableau cloud, Tableau server, and you would change the analytics, from the workbook perspective. And if you want to change, say, for instance, the icons of report builder up here, you would just go into the back end and you would upload a new icon and reference it there. A bit zoomed out. There we go. So data monetization. How does that work in Curator? So here we've got a less beautifully styled, I'll be quite honest, dashboard or or or interface portal here, but it gets some of the key components across that we've been talking about in the previous fifty minutes. So we're doing yeah. Ten minutes left. Good. So in this case, again, this is a public facing demonstration. So a lot of the capabilities and and the, the, the the functionality here is gonna be slightly different when when your clients would log in. They're not selecting the username from a drop down. They're typing in their username, and then they're typing in their password as well. But for this demonstration, I'm gonna log in as the basic user. It's a bit offensive, but, I'm gonna click on log in there as a basic user, and I'm gonna be granted here, something like a terms of service, for instance. Again, this is just an idea. It's not required here. But as the terms of service, you might want to say you're not gonna share any of this data with any of the competitors, blah blah blah. You can put whatever boilerplate you might want in there, and you can then say accept terms of service and require that as somebody who's logging in for the first time. And then they're granted this homepage, which after they've accepted that potentially, then they're always gonna come back to this, this this homepage after they've logged in. And on these home pages, we've got huge amount of different information and content that you can nest in here. You can have videos to show people exactly how to use the site. You can have dashboards embedded in that home page that they can use as navigation to click out. You can even, again, see things like the most most used dashboards or your favorite dashboards or any of these sorts of, ideas are probably baked in, from from a default standpoint. But when I go down here, I can see that I've got, a basic level dashboard, which I can click on. And, again, just to kind of highlight some of those kind of upselling features that we were talking about before, we've got things like custom loading gifts. We've got our instructions and tutorials that we can highlight at the top here to guide people conveniently through their dashboard. And then we've got this kind of somewhat uninspiring, pretty cool dashboard, but, you know, doesn't really give us a huge amount of information here. Then also all gray scale. It doesn't really encourage me to come back, but it does give me some useful content. So maybe I want to go in here and I want to download the data as a CSV, and I'm gonna do my own analysis on top of that as a as a basic user. I could also go in and I could, I could capture this dashboard, like I said before, as a, as a as an end user. And I'm gonna pop that out to PowerPoint as a as I as I described previously. Also some information icons and and generally the similar sorts of icons that you would see in Tableau server are gonna be exposed here. Just a bit of information. If I do click on one of these, generally, this is just a way of us calling that Tableau API that is then gonna go get the data from this dashboard. It's all being exposed by Tableau's gonna, embed its development team. So if I go back to my home page here oh, I've logged myself out somehow. Just make sure I log in again. There we go. If I go back to that home page, then I can see here that I've got some pro level dashboards, and I'm currently logged in as that basic user. So if I click on that, then I'll see that we're not hiding that information away. It's actually just a placeholder. It's not the dashboard itself because as someone who doesn't have access to see that dashboard, I can't get access to that dashboard. So I can put a placeholder in there that says, if I wasn't a basic user, if I was a pro user, then I would be able to, I would be able to, up up, what's the phrase? I'd be able to increase the permissions on my account. I would be able to, upgrade my account is probably the the the phrase I'm looking for. So I can upgrade my account to pro, and I can have a web form here that then sends an email, for instance, to a, a particular team within your organization that then approves that they're from the right email address, for instance, and approves that they've, you know, confirmed via email as something that they're happy to pay for this increased subscription every month. So I can add some more comments in here. I'm part of Bill's team, blah blah blah, and, then I can submit that and get that process rolling. Then if I, if I was to submit that, then I would previously mentioned I would get the ability to then log in, and I would then be a pro user. So as a pro user, I've then got some extra functionality. Maybe I've now exposed the ability to search across my data source, and have some, other embedded functionality in there. Maybe I've got these extra dashboards that I'm now able to see, like, for instance, my pro version of that full KPI dashboard. So I can click on that, and then I can see that I've got extra functionality that I can now break this down by country or maybe having benchmarks in other areas, for instance. Also, some cool functionality like feedback. You might want to be encouraging feedback that's not necessarily just here's an email link. Give us an email if you fancy. Maybe you want something in line that is then gonna say, look at this dashboard. Don't quite understand it. Don't think it's relevant for me or I don't understand this particular data point. And then you can, you can you can have a custom form here that's then gonna send an email to somebody within your team to, to to be able to to action that and respond to the user as part of your support agreement. So oops. I'll go ahead there. There you go. Pro user. There's lots of things that we can nest in here as well. I think finally, as a as a sort of final point, this isn't just Tableau dashboards. We can have, you know, links to external, systems in here like our demo page. You can also have PDF downloads of of different pieces of information as well as web forms as we've demonstrated previously. So, hopefully, that's a useful overview of the curator product. Again, lots of different curator links showcasing lots of different features in here, like, for instance, that report builder that we talked about previously. And, yeah, lots of things that you can kinda get your creative juices flowing as to how you can create an instance here that is then gonna be able to encourage your users to access their data, which is kind of the fundamental point here. We want people to be accessing their data here, and we think it uses or or gives us a lot of value, as an organization. And there's several ways that we can encourage people to do that around branding, around setting up that analytics package, that do those data flows that we talked about previously. So if any of that is interesting for you, if you enjoyed the session today, then let's stay in touch. Please feel free to reach out to myself or, inter works for dot com forward slash, contact. And, we can have a, we can have a discussion on on where you are as an organization and where you would like to get to, using, any of the tools that we talked about today or some other tools if you fancy. So we've discussed data monetization. We've discussed the usage based licensing as well as embedding capabilities. Hopefully, you found that interesting, and hopefully, we hear from you again soon.