Hello, everybody. I hope you can all hear and see us. Welcome to today's webinar. I'm going to give people one more minute just to join, and then we'll kick off at about one or two minutes past. Okay. So we're gonna get started, and don't worry. Any late joiners will receive the recording afterwards. So welcome, everybody. I hope you're having a good day today, whether it's a good morning, good afternoon, or a good evening We have people joining in from all across the world. You're all welcome here today. Welcome to this presentation on Paligo's annual customer insights report. This is our second ever edition. A little bit of housekeeping is that on the right of your screen, you should see a Q and A panel. So if there are any questions you have throughout this webinar, please submit your questions there. And if we have time, we will address them at the end. If not, don't worry. We will address them to you one to one by email after the presentation. Daniel, if you can go to the next slide. So my name is Andrea Francis. I'm the principal marketing manager at Paligo, and I will be here just to help the audience out today. So if anything's going wrong, either submit something in the q and a or email me at contact at paligo dot net. And without further ado, I will hand you over to the team. Yes. So my name is Christoph Norberg. I'm a management consultant at Harper and focusing mainly on transforming data into business insights. Looking forward to present these results that we have been looking at from the survey. I will hand over to Gustav who will tell you a bit more about Harper. Thank you, Chris. So my name is Gustav. I'm a partner at Harper and we've been around since twenty twenty one aiming to become the most loved management consultant company and we focus a lot on product development across the various industries and both how to position future future products, but also how to really develop them. And we really like to collaborate with both scale ups and global companies trying to make products we all love in different industries. Handing over to to Daniel then. Thank you, Gustav. Thank you, Christopher. And thanks, Andy. So I'm Daniel Nyberg. I'm the VP of marketing at Polygo. Been working together with this lovely team for the past five months, pulling together the data and the insights required to deliver the report as it is in its current form. So super happy to present these insights to you. And handing over to the always lovely Nicholas. Thank you, Daniel. Hi, everybody. My name is Nicholas Kolestetz. I am the chief operating officer here at Paligo since a year a year back. I'm super excited about this report. As Andy and all the rest of you said, we're very happy about the report, and we really look forward to to present back to you and and showcase all the the findings we have done throughout this process. But before that, I would just like to take the opportunity to say a couple of words about Polygo. I suppose the majority of you tuning in are aware about what we do. But for for the rest of you, I would just like to explain a little bit. Polygo is an organization that helps organization, large companies, small companies, midsized companies to transform how they manage product documentation, like manuals, portals, and help systems that keeps their product running and get the customers informed. Today, most companies are handling the this content manually in separate tools and formats. Polygo replaces that chaos with one intelligent cloud based platform where you author once, reuse everywhere, and govern centrally. That structured foundation reduces error, speeds compliance, and lower localization costs. And it's, of course, AI ready, meaning you approve proof content can safely be safely power search and both search and chat. So in short, Polygon turns documentations into an engine for business performance, making complex information clear, consistent, and scalable. Now I think we should jump into the actual report. What do you think, guys? Yes. Let's do it. So I'm going to start with this slide, and we're going to talk a bit about it. But first, there are a lot of current legal customers in this call or in this webinar, but there are also, we noted, a large portion of you who are not current customers. So we'll try to explain concepts and abbreviations as we go, so bear that in mind. But the the very first piece of information here, I mean, we won't be able to cover everything in the report. It's thirty two pages, and we have some forty five minutes on ourselves now, but we selected some of the most important insights from the report. And what you have in front of you on screen is that very first question we asked our respondents or that selection of customers and users that we made. The question was, is using Paligo helping you or your team to be more efficient or productive? Ninety four percent of the respondents say yes to that question. So ninety four percent of our users actually experience return on investment from using Polygo. Outstanding testament from Polygo's users on how worthwhile the switch to Polygo has been for them. Now I'm going hand over to Gustafar to talk a bit about who we asked and why we believe they actually represent all of the legal users. Yes, thank you. Let's dive into the responders or the users. We can move to the next slide maybe. Yeah. So for this twenty twenty five customer insights report, we have based it on the survey that we sent out and we got data from two forty plus authors or users around the system from about thirty two different countries and one hundred and forty different organisations. We have both looked at data points fetched through this survey. And we have combined that also with usage data from the Paliga platform in order to slice data and identify patterns. And looking at this just under forty seven percent of our customers are mid market organisations between two hundred and two thousand employees, but adoption spans all the way from small businesses to large enterprises. And by industry sixty percent are within software, although seventeen percent are in manufacturing and eleven percent in life sciences, showing adaptability beyond only the tech industry. Good. So I that insight from here is that structured content with Paligo, that's at the core of what we do, structured content, that translates into a positive business outcomes for a wide variety of industries and organizational sizes. So it is actually a structured content platform for everybody. And just moving on. Now, Christopher, do you want to introduce the numbers here? Yes. So we conducted this survey in order to understand what drives ROI within CCMS. And to understand that we asked the responders how much time they save in terms of decreasing the number of updates and combine that with the decrease in time per update. So we're looking at two different values. And if we're looking at the decrease in number of updates, we could see a twenty four percent decrease. But we can also see a thirty one percent decrease in time per update. So a lot of different here, but I'll leave it to you, Daniel, to dig deeper into these data points. Yes. So as Christopher mentioned, the the chars chart you have in front of you, the bars represent that first piece of the the dark chart the bar dark bar represents that decrease in documentation updates, and the light purple one decrease in time per update. And that combined leads us to the total time savings on everyday tasks as an average in that line at the top. So combining this, we actually end up in, on average, forty three percent of users' time is saved on everyday tasks, on average, simply by using Paligo compared to what they were using before Paligo. We really believe that these strong findings confirm, once again, structured single source content deliver strong and repeatable ROI by enabling teams to really perform at best, making life easier for those authors. I think, you know, forty three percent in on average of the respondents, that representation of users is very much worth carrying with us. And moving on to the next piece. So, of course, we asked a lot of questions. We broke down the insights for you. Content reuse is one of the core capabilities of Paligo, and and that alone represent represents thirty three percent of saved time per assignment for our authors. And Paligo, as a platform, enables our users to spend fifty one percent less time on actual authoring. So documentation teams really can free up time to do and complete important work or simply to get more work done. And just a commentary from me, at least working a lot with large global companies and also scale ups that documentation teams have increased pressure on them to actually produce more. So I think it's quite fascinating this facts that you present. It's a lot of a lot of waste that goes into normally to to create an update content. If whatever you can improve there, it is is saves a lot of a lot of value not only for for the documentation team as as such, but also for the rest of the organization to actually be able to move on with their with their projects. So I think that's quite quite fascinating. It is. It is. Because time saved for authors means faster time to market, better quality, increased confidence, etcetera. We'll and actually, we'll dive into some of the points that Gustaf made here in a few later slides. So a lot of numbers and we'll keep on digging and next up, we'll go a bit deeper into content reuse. Like I said, this is really one of the main capabilities of Polygo and one of those identified challenges that our founders, they founded Polygo ten years ago, set out to solve. Like, how can we stop copy pasting so much? So what we have here in front of us on screen is once again a representation of industries, software, manufacturing, finance, and life sciences, and then all the other industries that use Paleo, but software manufacturing and life sciences are the strongest one for us. That's where we have the most of our customers. And on the graph, we have reused images, that's the dark bar. That means an image in Paligo is used more than once. It could be used five times, it could be used two times. We'll get that breakdown for you in next year's customer insights report, but just carry with you that an image is used more than once. That's a reused image. So that's time saved. And the middle bar here, the light blue one, reused topics, that's the same. That means a topic, a snippet of text, has been used more than once throughout the documentation. So in total, we combine that with an estimate of time saved through content reuse, estimated by our users. And we can clearly see some of the differences here. Like, in finance industry, the savings are a bit lower when sort of self assessed, about twenty nine percent. But when you look at life sciences, the savings the estimated savings are much higher. It's actually above fifty percent of time saved through content reuse alone. And as you can see in the chart here, life sciences have a almost sixty percent amount of reused topics. So that's the same goes for finance industry, but maybe the time saving isn't as significant for finance as it is for life sciences. But this is once again a strong testament, and just to elaborate this a bit more, what does these numbers mean in real life, real numbers? So we asked our survey respondents, how much time, how many hours per week do you save with Paligo? That content reuse is part of that savings, and the response is plus two thousand hours per week. Two thousand hours per week, that's just a survey respondents. But as a collective with Polygo, all our authors, they would then save almost fourteen thousand hours per week with That's some staggering numbers and of course, there's a very large amount of authors in Polygo, But just to let you know, these numbers are in the report, so go ahead and dig through it. And before moving on, is there anybody else who would like to to comment on this? I mean, Gustav, you touched upon it, like, that time saving is faster information delivery, it's accelerated product time to market, it's a better customer experience, etcetera. I think it's also interesting to elaborate a little bit around different industries and how you use Allegro in different industries, of course, and what it's used for. I think that's also when you mentioned the life science case here, I think it tells you something, right, that but also a lot of opportunities manufacturing, for example, with I I think I think it seems like it seems like it's it's pretty much the same what I call the same not the same numbers, but the same difference between between between the different questions and different different industries. I think that's I I think you have to think about it from your industry that you work on as a user. How do you actually use the Paligo product, and and how can you apply it in the best way when you're when you're thinking about how to evolve it further or or even to to buy it? Yeah. That's a good point then. And using Paligo is could be easier. It's not super easy, but it's not super difficult to get there. We'll actually talk a bit about time to proficiency in later slide. But just as you say, goes by, like, finding your optimal use case for your industry, for your company, how should we use Polygo and and how should we deploy content reuse? It's sort of a strategy very well worth considering deeply as you embark on your journey. But let's let's let's move on. And, Christopher, I I saw you had some network challenges, but are you still with us? I'm with you. Keep my my video off now, so it's a little shake, as you said. But let's leave the survey for a while and look at as as I said earlier, we're combining both the survey data and the usage data. So what we're looking at here is the usage data in the platform. Daniel explained to you topic reuse or reuse in itself is a really important aspect of the Paligo product. And we can see variations by company sizes, for example, and in this case, it's the number of employees where the largest companies reuse the most. Sometimes that often means a lot of content in an imagery of course, they have a lot of stuff written down. And if we look at the industry, as Gustaf said, there is differences between those as well. We can see that life science are top of the class with a sixty two percent reuse. And if you were to look at all instances within Paligo, it's still a pretty high forty two percent reuse. So a lot of people or a lot of of authors reuse very much of their content. Yeah. Indeed. And, I mean, just to emphasize what Christopher said right now, these are every single the averages for every single production instance of Polygo, including the ones that are still onboarding, including the ones that's been with us for the last eight years. So we feel quite confident in saying that using Polygo, you should, on average, attain a topic reuse at about forty plus percent because that's what the data shows us. So that's it it is really super interesting, and like Christophe has said as well, like, there's a a bit of a a shift or a change, like, lower smaller companies would have probably less topic reuse as they would have less content and less sort of variations of publications and outputs but where the larger companies, you know, the five thousand employees that you have at the bottom of the left hand chart with forty nine percent content reuse, that's where you probably have a very sort of high economists of scale, you know, single teams managing global products, etcetera, and probably information architecture, resources helping you optimize and maximize how you get leverage from Paligo. But it is truly interesting, and this is, I'm gonna be transparent here, this is the first time that we actually pull all this production data. So this is actually the first time we expose to a global audience what it actually looks like behind the scenes. And in the report, there's a few more slices of this production data. So you'll have the number of publications, the number of languages, etcetera, etcetera. It's all in that afternoon read of thirty two pages for you. Yes. Could we move on? Let's do that. Okay. So, you know, what about actually changing to Polygo? Now the headline says beating the competition on efficiency and productivity, but this actually means we asked our users what were you using before Polygou, and then we combined that with their experienced efficiency savings in hours. So what you have in front of you is simply a categorization of the savings depending on where you came from when you started using Polygo. And the chart the scale is actually number of hours per author per week saved. Docs as code is at the top. This is quite interesting. Docs as code, you know, using GitHub or Markdown is is really a preferred method among developers. But potentially, a hypothesis here could be that that's actually not a very time efficient way of of building your documentation when you scale. But the second one, online document workplaces, that's where most of us come from. Google Docs, Microsoft Word, working in SharePoint, working in Google Drive, that's where you get that ten hour time saving. So like I said, like, many organizations, they begin with these unstructured tools like Word or Google Docs and maybe simpler help authoring tools like Madcap Flare, and they all have that their place, but, you know, as scalability becomes a challenge, content libraries grow, it becomes more complex. So and, Chris, offer sorry. I may have jumped a bit on your thunder. No problem. I always get a bit excited about these slides, but you wanna add something here? Yeah. I think you you covered most, but I think it's really interesting that no matter where you came from before, before going into the Paligo platform, you save time moving. And whether it's, as you said, Daniel, from working in Microsoft Word or in actually really advanced tool before. And if you want to look deeper into this in the report, have also divided this into the different type of work as in translation, etc. Etcetera. So they they can look even deeper into where you find most savings from the different tools as well. Yep. Just to be a bit balanced here at the the bottom part of the slider is you have SDL Trillion docs and you have Shima s c four, which are both very competent, very customizable, high end CCMSs, component and content management systems, just like But still, the customers we have who move from them still make life more efficient using Paligo. And you also have on that at the second one from the bottom, you have your Confluence documentation management the Wiki based solutions. So that's that's also maybe kind of interesting to contrast, you know, if you use a Wiki compared to using Google Docs or Microsoft Word, you're probably better at running your documentation on a Wiki than using Word. So there's a lot of sort of aspects of it. In the middle here, you have your help authoring tools like our friends at Madcap Flair or Document three sixty, etcetera. And they come in sort of at the middle because that's, you know, kind of semi structured authoring. But this is super interesting, and like Christopher said, there's much more to dig into with if you wanna compare and contrast, if you're not a company a customer of Polygo today, like, how what can I expect moving to Polygo? That, you know, in the reports, there's a few really good clues to that expectation. We think we yep. I just think it's a really interesting to reflect where you come from. What situation are you in right now? And this this really helps some and guides you forward, how how you can apply, I believe, in a good way to show it from a time perspective. I'm just curious if this before you before you embark on the Polygon journey, how how much have you thought about these different cases and this different how you apply it in the best possible way? I think that's that's something that you really need to think of about and also discuss with your management as well to really show where can the savings be made here from a time perspective, where can we be more efficient. So it's important to reflect upon that, how to apply it in the best possible way. It is. It is. Alright. But so we genuinely believe that Palego is almost always a cost efficient alternative to what you're using right now. At least looking at this chart, there's some proof for that. Alright. So let's talk more about some of the more challenging things. You know, getting a new platform like Polygo means you need to become proficient on that platform. And on average, our users report one hundred and eighteen hours on average to become proficient in Polygo. So that's about three working weeks to start delivering value, to be able to navigate the platform. So we believe it's a rather rapid ramp up time, But then of course, there's gonna be differences depending on what you're used to. Like we saw on the previous slide, if you come from a markdown or a docsis code or a environment of using Microsoft Word, it's probably gonna be those one hundred and eighteen hours for you before you become proficient because the way of creating your documentation is gonna be different, like quite a lot different. But if you used a CCMS or a semi structured help authoring tool in the past, it's gonna be significantly less than a hundred and eighteen hours. So bear that in mind. But the average in the survey is a hundred and eighteen hours. So then, how many if if you're if you just if you don't have that previous experience and and you need those three weeks, well, what's your recommendation? How to how to shorten that time? Running as fast as possible. That that's a super interesting question. I I think the first piece that most of our customers go through in ramping up is getting a hold of how the architect what's the structure of their current content? Because just shifting in documentation from wherever you have it, it's just gonna create a very complicated mess. Right? So you need to spend your time creating effect first. Like, what is my content? How is it structured? Identifying reuse potential preferably by using AI, for example, before you start migrating. So at least you have a plan on how to structure your content. I think that's the key, right, and sort of technical implementation or migration is something we have a team of professional services to help you with, But that first planning of how to migrate and how to structure content is key. That's that's that's the first tip. Sorry, Daniel. But I also think it's depends a lot on where you're coming from, what as Daniel alluded to, meaning how how big sets of documentation you have, multiple products or not, and also the majority of of your, your current team, meaning where you're coming from, or where you've handled your documentation earlier. So it's a big difference if you have done documentation in Confluence or Word, compared to another CCMS tool or something, maybe Homebrew. So that, course, impacts this as well quite quite a bit. Yep. Very good point. Thanks. Thank you, Chris. Really Really a recommendation to to think through that before you embark on a journey and and to have that plan. Absolutely. And that's what our professional services team and our, also our sales engineers, and, solution architects are helping our customers with, prior to, the onboarding, but also even in discovery phases where our, clients are looking into, a product like like ours, we can guide and help and and consult, if that's needed. We have a lot of, best practices. We have a customer base over, or around five hundred global, customers that we serve. So we have gathered over the last ten years a lot of knowledge in this space, and the migration part is a very important and critical part to really spend time on to get a successful outcome. Good. All right. So we're up at the first half hour of the webinar, and we've reached sort of a pivot point now, and we're gonna spend a few a couple of slides here on those of you who might not be Polygo customers today, and then we'll go back in for a wrap up of the entire webinar with some sort of closing additional super interesting findings and comments from the survey. So, know, assuming out of it, like, do you get results like this? With a CCMS, like Polygon, like, component content management system, that content is created once and then delivered consistency consistent across channels and languages. Compare that to how you would create a document or a Wiki page in Word or Confluence, you would create all content every time through copy pasting. Here, the reuse comes into play, the structure comes into play, and all the other sort of language management capabilities of Allego, the publication capabilities of Allego, etcetera. So this all reduces that or brings down duplication to zero. It accelerates releases, we've seen that previously with time to market going very rapidly, we improve findability in the content, and we provide a governed single source of truth for either if you're a product team or a support team, a customer experience team, or a compliance team. And even more interestingly, structured content is AI ready in every single aspect. Providing content from Paligo to an AI agent works like a charm. So for product teams, Paligo sets that govern single source of truth, enabling worker control and collaborative workflow as you develop and release your product. For these support organizations, Paligo centralizes knowledge creation. We use metadata, we use governance to improve findability and accuracy on those knowledge bases and support help blocks. For customer experience, Pollegio single sources that multilingual content. We keep the languages synchronized as the products evolve and as you create new content, new topics, etcetera. And for legal and compliance, Helio provides that role based permissions, the audit trails, and the reuse of approved language that reduces compliance risk and really accelerates audit readiness. So there's something here for every single team using Filigo. And shifting up, like I said earlier, structured content really shortens the time to value for AI. We resolve those disconnected inconsistent pieces of content across multiple sources of what could be truths. So making the product knowledge reusable, AI knowledge based on that content becomes more accurate, more reliable. And the Polygos CCMS becomes almost like a governance AI layer, keeping knowledge correct, ensuring that AI responses also are correct. Centralizing all that documentation under one model and one platform creates that dependable source of truth for both humans and machines. As just a proof point, if you haven't tested yet on docs. Paligo dot net, Paligo's own product documentation and knowledge base. There is an AI assistant answering questions on our documentation and how to use Paligo. And of course, our documentation is built and created through our own product. So test it out, do talk to us more about how structured content gets your content AI ready. So we're on pretty good time, and it's time to wrap up the webinar and open up for questions. And I'm gonna set this last slide on screen. I'm not gonna read out the commentary here. These are actual inputs from the survey, and we started off this webinar forty minutes ago by showing that ninety four percent of authors in Paligo report ROI from using Paligo. With structured authoring and an easy to learn solution like Paligo, customers from basically all kinds of alternative documentation solutions have found success with us. Now if it's access code, if it's Microsoft Word, or if it's a HAT tool, or even another CCMS. And whether you're a high growth SMB or a established enterprise company, organizations experience consistent time and cost savings almost regardless of their industry or company size. So and what's even best here is that you don't need to learn any complex standards like data used by some of our competitors on the CCMS market. You don't need to know that to get started. You can experience that rapid ROI together with us and dive deeper and go into the details of the XML as you go and when you need it. The time to value is at hand immediately. Great. And that's with that, we open up for q and a from the audience. Andy, welcome back. Hi. I'm back, and thank you, everybody, for sticking with us. We do have some questions to get through, and I will just start with this one, which is by email. Why did you create this report, and will it be used for Polygou's future planning in some way? So I don't know if Nicholas or Daniel, either of you have some thoughts on that. Maybe I can start. We will absolutely use all the input and feedback that we have gathered throughout this creating creating this report when it comes to our future road map and the the the future development we are doing of Polygo. It's very important for us to understand how our user community see the savings time wise and efficiency wise when using the product. So it helped us tremendously. It's also a way for us to showcase and communicate the benefits that our customer sees to to other today non Polygo customers or companies out there. There there are actually quite quite a few left that is still not using Polygo, but more and more come every day. Great. Hey, Candy. You know, since it comes like, when we originally set out to do this report last year, it was also built out of curiosity. Like, how do our customers actually, like, from word-of-mouth, experience the product? And sort of a will from us or an interest from us to share that knowledge with a larger audience and with our customers. So that's a that's a twofold or or, like, multiple reasons for why like, that first question, like, why did you create this report? It's all those things that Nick said to get insights, to understand the like, how our users use our product better, and just that we would like to share this. To honestly, to demystify CCMSs, it's it is not that complex, and it brings loads of value. I think it's also interesting for the community to, as you said, to understand how how how you use and apply the product in a in a good way, find inspiration for different use cases, and also, of course, help to improve the product as such. I think that's curiosity you mentioned is really important. Yeah, Gustaf, you're touching on a very important part. We know we have a lot of interactions with our customers that have some struggles internally to really showcase the bigger value of what they actually create within Polygo or other CCMSS to that point, to to to other stakeholders within the organization. And we have, based on the feedback we gathered for the when we published the first, inside report last year, got a lot of feedback that it was has been used internally, to, to really showcase the efficiency gains that the the technical author and technical writing teams, actually are are producing. So that's also an aspect of this. That's it. So we'll we'll keep going to the next question. So this is slightly more technical, and I actually will pass it on to this person's customer success manager just for a further debate. But since we rarely in our little industry have benchmark reports, we kind of are flying the flag here. And perhaps, I don't know if one of you guys have a comment to make on this. With regarding the percentage of reuse text, what measures would you recommend for organizations that fall below the average to increase the reuse rate? So I don't know if this falls into case by case basis. It really depends on your because we saw such variation over industries, or is it something that maybe you could discuss further with your own team and with your with our professional services as to how you can apply more reuse. Open question to the floor. Nick, do you have any input? Or No. I think we we could probably look at it case by case, and we're more than happy to to gather resources from from our point of view to to look at it. There if we look at our customer base, we have very small teams and also really large ones. So it and yeah. So the the the how to measure them, there's a lot of dependencies, but we're more than happy to look into it. Yeah. And I think, like, an average number means that there's numbers above than below that average. Yeah. So there will always be below, but not being a technical writer in my background, but what I've learned is as much of the reuse in Paligo comes from knowing your content, like identifying reuse potential. So that would be, you know, my sort of first steps. I think one of our sales engineers or information architects would have probably phrased it differently, but go go hunting for reuse potential is probably how I would approach it. Alright. But, Ricardo, we'll pass your your question on to our our smarter people inside. And if they have more to pointers for you, we'll pass it along. Was there anything in the findings that really surprised any of you here? Anything that was a curveball or a shocking learning? Hey, Topher, do you want to say something or should I was surprised by a lot of things, but Yeah. So so was that. But let let me go first. So I was very surprised by that slide where you showed, like, what you come from when migrating to Polygo. Markdown was a huge surprise for me that it's always something that I've like, if you do your documentation docs as code, it's supposed to be super efficient, but that's actually the ones that saved the most time. That was I shouldn't say it rocked my world, but but almost my sort of understanding of Polygos and our market really sort of took a big shake on it. And also the fact that some of the various other complex high end CCMSs on the market actually experienced time savings when they moved to us. Those were some big shockers. And the fact that our topic reuse on average in all production was forty two percent across all customer instances. I actually would have guessed it was lower, like, at around thirty percent, but forty two percent of this was surprise to me. Yeah. And I think, like, I've been digging this data for for quite some time and the more you kind of scrape on on the surface, the the more interesting things you find. Do do you guys hear me or maybe it's just my Yeah. Are. Yep. Okay. Good. So for example, like drilling down into what the specific kind of translation or reviews, etc. How much that affects the savings and also like when you kind of cluster different aspects in terms of repetitive work that those kind of work can save you three point five hours, for example. And you can drill down a lot more about that in the report, but there's there's a lot of nice findings and I think we could find even more if we drilled even more into the usage data and combine more and more survey questions. Absolutely. I was just digging through the questions here. So we're gonna move on to another one. Does Paligo use our own LLM or the documentation is sent to LLMs like OpenAI? So let's just go on a kind of a high level here. Well, we are not the technical team. If anyone has highly technical questions, I will be assigning them to to our team internally. But just since AI is a hot topic, I thought I'd put this up. Yeah. I mean, that's super interesting. I mean, first off, no. We do not have our own LLM. Not yet. I'm not sure what our product team has in their back pocket. So documentation created by Falego, you know, like, for example, for our own product documentation on docs paligo dot net, we make sure that that it's scrapeable by bots from AI agents. So OpenAI can scrape out that website and sort of ingest the documentation, and if you actually if if you use ChatGPT and ask it a very sort of, you know, complex question on how to use Perleo, it actually answers really well because it has ingested that knowledge. Yeah. And I think that's that's a quick response to that question. So we don't send the data, but our customers, as they create it, it it's public knowledge. They may should make sure that it's, you know, available and ingestible by a AI agents or use tools like Kappa dot ai that we use on docs our own docs. Yeah. Just one comment. I've been working with with with with quite a few AI initiatives in in in other companies. Right, when you start to dig into use cases and you look around the organization, what you can optimize through AI and so on. This the foundation of having a structured information is really key to get those use cases become as good as possible. So I think the foundation there, what you mentioned in your slide, is a real key for an organization to utilize in a best possible way. That's just the that's the finding. But Absolutely. Less challenging question. Was it just authors in the survey, or was it other user roles as well? So even I can answer this one. We specifically spoke to Polygou authors simply because they are the everyday users that are deep into the tool that will use most of the aspects rather than the contributors or the reviewers. And then I believe we've come to the end of the questions, but a very nice way to end it is when you were speaking about migrations and the wonderful Anna agreed with you and said, helped our company transition our content into Paligo, having the structure for our help center in place already helped immensely. So Anna, thank you very much. This is an example of a of a great experience where someone arrived, understood the work to be done, but also understood the ROI to be experienced at the other end. Brilliant. Fantastic. So on that positive note, thank you to our lovely speakers, Daniel, Nicholas, Christopher, Gustaf. We at Palego, it's been a pleasure to work with Harper on this report. If anybody on the webinar has not yet seen the full report, we will be sending it to you with a follow-up email with a link to this recording afterwards. And if that goes missing, you can always go to our website, paligo dot net, to our knowledge resources reports and if you would like to find it again. On that note, I will close it down for today. Thank you all so much for being here, and have a wonderful rest of your day. Thank you, everybody. Thank you, Andy. Thank you. Bye bye. Thanks, guys. Bye bye.