- So, hi, everybody. Welcome to today's webinar. And let's just start with some basic housekeeping. Now, there is a Q&A box for you viewers to submit your questions during the webinar. So feel free to use that box. We will do our best to answer all your questions at the end of the webinar, and there will be plenty of time for questions, so don't worry. And there is a audience chat box for you to have conversations with each other. Or let us know if you're having any of technical problems. So go ahead, use the audience chat, and use the Q&A. Now, today, we have a hard stop at 15:55. That's 5 minutes to 4:00 or in 53 minutes from now. So if there's any questions that we are unable to answer, we promise to get right back to you using the email address that you provided. So let's go. So first of all, who am I? Well, I'm Daniel Nyberg. I'm the vice president of marketing at Paligo. And for the past 2 and 1/2 years that I've been with the company, I've had the pleasure of interviewing and talking to many of our customers. But this is actually the first time I'm able to introduce you to our first ever customer survey on Paligo, and how our users use it, and get value from it. Now, we were supposed to be joined by Rasmus, who is our VP of product, but unfortunately, Rasmus has fallen ill today, and is replaced by Nermin, who is one of our product managers. Now, Nermin, I see you're still muted, but if you go unmute and introduce yourself. Thank you. - Yes, hello. As Daniel pointed out, I am not Rasmus, but hopefully, I can cover his parts. And as Daniel mentioned, I work as a product manager for Paligo. I have been doing so for about two years, and hopefully, I'll bring you up to speed with the interesting statistics and the features and examples that we have in the material today. - Therese, do you want to take over? - Yeah, thank you. Hi, everyone. I'm Therese Mucherie. I'm the director of customer success here at Paligo, and I've had the pleasure of working here with amazing teams for almost two years now. My background is in knowledge management. So coming to a tool as powerful, really, as Paligo was incredibly exciting for me. It's a platform that really aligns perfectly with my passion for driving innovative customer experience. And I truly believe in the power of communication, innovation, problem-solving, and also collaboration to bring real value to our customers. And so I'm thrilled to share some of those insights with you all today. - Brilliant. Thank you, Therese and Nermin. So let's get going. So here's what we're going to cover today. In the next 15 minutes, we're going to kick off with talking about the cost effectiveness and ROI of Paligo. Because after all, it is a productivity and efficiency tool. We're going to talk about productivity gains and some of the streamlining of workflows. And in the middle, talk a bit about how easy structured authoring can be for all. Now, this is really what Paligo is about, and we'll round up and finish off with future proofing with Paligo, how to scale and expand with Paligo. So with that, let's get going. And Therese-- - Yeah. - --how about Paligo's customers? Who are they? - Well, I love to speak about our customers and being in the customer success field. That's obviously what we're here for. And we're very proud to support a really diverse range of organizations, from tech startups to really established global enterprises who really all trust us to manage and deliver their content efficiently. Our customer base spends through various industries with unique needs for content management, documentation, and also seamless collaboration. Some of our well-known customers. You can see some of them on the screen. So, Allianz, we've got Palo Alto, 3M, HBO, who really leverage Paligo to streamline complex content workflows, improve documentation, and enhance their customer experience. So these organizations really value our product to be robust, cloud-based, and allow their teams to work collaboratively across departments, ensuring accuracy, consistency, and scalability. So it really is an exciting range of customers. And what's really exciting here as well is that global technology giants or specialized industry leaders all have that one same common goal, which is making content a competitive advantage within their organizations. And for us at Paligo to be the backbone of that is just truly, truly exciting for us. - Good. Thank you, Therese, for that intro to Paligo's customers. So, Nermin, let's talk about a bit more on the details who our customers are. - Yes, well, Therese brought up some of our key customers. And what can be said about this slide is that we have a diverse and global customer base, as Therese mentioned. And if we look into the numbers that prove this, and if we look at the number of employees by customers, now, there are 20% that have more than 1,000 employees, and 15% are not 18% have less than 50. So there's a wide range there. And what can also be said is that we have a strong representation in Europe and North America. But also what is not in this slide is that we have translated our UI in German. So we're seeing an increase in the Dutch region. In terms of industries, finance, insurance, life science, manufacturing within other, we've placed a couple of industries, but software is the most popular one. - Good. Thank you, Nermin. - All right. So let's dive into the data that is on the screen at the moment. You can see from the slide, we asked our users in this report that we're going to dissect, so to speak. We asked did your company switch to Paligo from another CCMS software. And the results are quite telling. So we've got 46% of the respondents that said yes, indicating that they had experienced with another CCMS before transitioning to Paligo. And then on the other hand, 48% said no, meaning that their first introduction to a component content management system was Paligo. Now, we've got those 6% who responded, I don't know. And usually, those are users who weren't involved in the vendor selection process and joined Paligo when it was already established in their organization. Now, what really is interesting here is that nearly half of our customers choose Paligo as their first CCMS. And this really speaks highly about our, or the ease of use of our products, and comprehensive onboarding process, also, that we offer. So whether they're migrating from traditional tools like HATs, so help authoring tools, and other CCMSs or starting fresh with Paligo, the consistent feedback that we get, especially within my team, the customer success team, is that our customers are able to quickly find their rhythm, and achieve the goals that they initially brought them to us. So our success with customers, regardless of their prior experience, really comes down to tailored onboarding process, I would say. And so we've got dedicated professional services and solution engineering team that step in from day one to support their onboarding, adoption and migration journey. But we'll talk about that a little bit more down in this webinar. But ultimately, what the data demonstrates is that our customers are achieving success, whether they are CCMS veterans or first time users. And our team is here to help every step of the way, making sure that the transition to Paligo is smooth and impactful. - Good. Now, I think we've talked about this in the past, but I think one of my reflections from this data point as well is that there's so many of our customers that actually come from an environment where they did not use a CCMS in the past, which means that they were actually doing or managing very complex documentation or content without a CCMS. And I think that's probably some of the most intriguing pieces about CCMS, is like how well kept a secret they are. But let's move on. I think this is super interesting. We're getting into the data here. So, of course, the business side of things comes into play always. And we know that any of our economic buyers or leadership will have a look at the ROI. Now, implementing a piece of software just because it's fun, never happens. But implementing a SaaS product because it delivers ROI, well, that's more interesting. So let's move on to those findings. Does Paligo find our solution to be worth it? Now, this is a collection of conclusions from the survey data. And I'm just going to kick off with the most obvious one. So Paligo was actually founded on the very fundamental idea or premise that there is a better and more efficient way of doing technical documentation. Now, that's the foundational idea of our founders. And obviously, Paligo hit some of those buttons very well, because 75% agree or strongly agree of our users that Paligo delivers ROI to their organization. Now, bear in mind that interpretation of ROI in this case is better efficient resource use, better time to market, et cetera. It's an open question as to our users about, do you find that Paligo delivers return on investment? But yes, the very vast majority do believe so. - That's a good number. That's a really good number. - It is. It's an incredibly good number. And Nermin, there's some more interesting facts here as well. - Yes, in terms of the 90%, this is a number that we take great pride in, and we take it very seriously also. And what the number says is that 90% agree or strongly agree that Paligo is a reliable source platform. And what's in the word reliable? Well, we have based it on minimal downtime, reliable updates, trustworthy data, but also privacy and security. All very important things when dealing with sensitive content, and content in general. These are the things that you want to have in place, and the general trust in the platform that you choose. - And then we've got the 50% there. And I'm going to try to enlarge my screen to see what it actually says, but I can't. So I'll look at it on the other screen. But 50% of the respondents are actually saying that they're saving 25% of their time during creation, or updating or even maintaining their documentation because or thanks to some of our features in there, which is versioning, branching, and variable features. What's really interesting in that is putting into perspective. So what does 25% mean while 10 hours saved over the course of a week? That's huge. That's more than a working day. So it really shows that our features are really designed to streamline different workflows and eliminate repetitive tasks, and allowing our users to focus on higher value activities. So this is a really exciting number as well. And my team and I are working to get an even higher number of that in the future for sure. - Good. Thank you, Therese and Nermin. So moving on to the Paligo content pipeline, and Nermin. - Yes, the famous content pipeline. Yes, or as I like to call it, the value chain. And now, if you have been in contact with one of our salespeople, I am sure that you have seen this before. We can talk about this picture for hours as it is powerful, and a lot is hidden behind these numbers. So each of these, this whole value chain from authoring to publishing, we take great pride in this as we have a seamless connection between all of these areas, and so from authoring to publishing. And what I can say about Paligo is that in short, is that it's based out of XML, which means Extensive Markup Language. And what can be said about this then? Well, it's an industry standard to encode both human readable and machine readable content. And we also throw words at as topic-based authoring. Now, if you have not heard this before, it is a more efficient way of managing and producing documentation. So if I'm to define topic-based authoring, let's say that it's a way of writing content in small modular chunks of information. And these chunks, we have chosen or it is called topics. Now, these topics are independent from each other, and you can mix and match them however you want. Now, as I am one out of three product managers, I can give you some cliffhangers in the coming slides. One is in regards to versioning, but I have been working with the collaboration workflow, but also our Salesforce integration. So I'll be speaking a bit about that in the coming slides. - Good, thank you. And I think for you who are listening, our valued viewers, I think this slide is something to just keep at the back of your head because this is really the fast overview of what Paligo does-- author reuse, versioning, collaboration, translation, management, and publishing your content. So that's why we tend to call this the content pipeline or value chain. Thank you. So shifting over a bit of talking a bit more about return on investment. And for us, we've learned over the years that the use case of our customers is super important-- having the right fit, having the right needs for it, having the right use case. And our customers usually go through a very rigorous pre-sales process. We assess. Usually, we do a free trial for our customers, where both parties agree that there is a good fit between the needs of our customer or potential customer, their use case, and what Paligo can do. And part of that journey is also to discuss and set a bit of shared expectations on the ROI, or return on investment by discussing cost versus benefits. And I think this leaves an impact on the quotes and statements we get from our customers as they go live and over the years work with Paligo. And now, Therese, do you want to add something here? - Yeah, I mean, I'm very glad that the pricing is being brought up. And just like you say, Daniel, it's not only about the price, because it is a major asset when you compare to other tools on the market. But what truly sets us at Paligo apart isn't just the affordability or the functionality, it's our genuine commitment to our customers success. So from day one, and even before the customer actually becomes a Paligo customer, we prioritize setting our customers up for success. It starts with, I talked about it before, the onboarding, where our teams work alongside our customers to ensure that each setup is tailored to their unique needs. We guide them through implementation, migration, so that they don't just have a tool, they have a solution that feels made for them, really. And beyond the setup and once everything is good to go, we're here to support them every step of the way as well. We've got an incredible support team that's always available to help with technical needs. And then our customer success team, which I can't speak highly enough about. Not that I'm biased, but we serve our customers, and we are the customer's internal advocate. So the CCMSs, they're not just checking in. They're actively supporting the customer's goals-- what do they want to achieve with Paligo, and looking out for their best interest and offer proactive insights to really maximize the platform's value. So having dedicated teams make really a tremendous difference in how our customers experience Paligo. And it's central as to why we achieve such great results, in my opinion. I think that really is what makes Paligo truly unique. - OK, thank you, Therese. So I think it's a bit about that initial phase before you actually acquire a legal instance, and the ending piece where you tie them all together, tie the loop in, and work with the onboarding, the support side of things, the training side of things. So moving on, what about productivity gains, and how Paligo helps streamline workflows? Now, there are some quite remarkable productivity improvements. And we'll have a look at that. How that saves money and foremost time for our customers in the long run. So shifting again back to the customer survey. And Nermin will give us a bit more insight about how Paligo helps deliver more content than in the past. - Yes, thank you, Daniel. So looking at this slide and the statistics shown here, what can be said is that 50% of customers deliver 26% more content now they're in Paligo than previously. Although, I'd like to bring up the tricky part of this question. As we take pride and value in these numbers, it's not always about delivering more value. It's a question of demand. Higher demand, more products, you need to produce more documentation. And then the numbers speak for themselves. But, in many cases, there is the need to deliver the same amount of documentation, or even less maybe, but more efficiently. So I would say that efficiency comes in many forms. And Paligo we have seen with our customers. And this is just one way to look at it if there is a need to produce more content. And that's why, and that's one of the reasons with going with Paligo. - Daniel, I don't think we can hear you. - Sorry, just mute button. Thank you, Nermin, so much. And moving on to a bit more of a real world examples of our actual customers. Therese, how about Hiab? - So I love speaking to our customers, but I also love speaking about our customers. So Daniel time if I take too much time you need to stop me. But let's take a look at Hiab, and how we help them solve complex challenges with their documentation. First, let's figure out who Hiab is for those of you that don't know. They're a leading provider and a smart, sustainable load-handling solution. They're part of cargotec corporation if that rings more of a bell. And they have sales in 2022 that total approximately 4 billion euros. So quite a big organization for sure. This goes without saying that their customer base is spread out all over the world, meaning that there are documentation needs to be not only accurate and compliant, but also available in many different languages to meet local regulations, and also support their customers queries and understanding. So before Paligo, Hiab struggled with the time-consuming process of manually managing and translating their content as well, which slowed down their documentation workflows, and really created inconsistencies. Now, when they adopted Paligo combined with Phrase, which is one of our partners for translation management, everything changed. They were able to streamline their content creation and translation processes, publishing in multiple places, and cutting down on time and minimizing errors. It's really interesting to hear what they've been doing. And if you jump on our website, you'll be able to read even more about that if you want to. But one of the standout features for Hiab was, obviously, our structured content management, which allows Hiab to reuse content efficiently across different versions and different languages. So instead of duplicating work for each region or each language, they can make updates in one place and apply all of those changes globally, and really significantly reducing their maintenance workload. I could talk a lot about Hiab, but it, really, is a great example of how Paligo doesn't just provide a platform for the content, but it provides a comprehensive solution to support complex, multilingual content needs, allowing teams to really focus more on creating quality documentation, and less on the time-consuming manual tasks. So it's really an inspiring case of how technology can simplify even the most demanding content challenges, I would say. - Indeed. Well, thank you. I think Hiab, it's a super interesting case, and a really good example of how Paligo makes a difference. - Yeah, definitely. - And moving on to another super interesting survey result. And Nermin, how about content reuse here? How does that impact our users? - Yeah, exactly. So this is another one of those fantastic statistics slides that we have. And firstly, what can be said about the numbers that we see is that, roughly, around 60%, 58.8%, to be precise, of our customers have increased their content reuse by at least 25% since implementing Paligo. Now, this is interesting and important, especially with the type of platform that we are. But I would like to highlight three other things besides the obvious benefits of not having to copy and paste and duplicate info, but it's also improving on the content quality, ensuring a consistency with the content, but also a better content governance which this implies. So that's everything that I would like to say about this slide. - True, thank you. And I think coming up next is a bit more of a deep dive on what content reuse actually is in Paligo. - Exactly, so this is the slide. Yeah, sorry. I have a hard time seeing the slides here. One moment. So a bit of an example. So a bit of a deep dive into what I mentioned here. So on the left, let's say that these are our Paligo's tools for reusing in combination with version management. It's really powerful. But let's stop at reuse for a moment. So the example use case we have here is that there's a company that has five different products that are, say, roughly, 80% similar. Now, there's more types of reuses that you can make use of here. But for the sake of the example, the relevant features would be structure reuse. And to just stop here. What does structure reuse actually mean? Well, we like to call, I think we have dropped the word, publication. If I have not, then let me define publications. It's kind of a container and obtainer for structure for all the topics or chunks, as I referred to it previously. So the structure reuse and the publication that is formed, you can actually reuse the structure there to multiple products. Now, what might differ, it might be that you keep all of the topics that are the same, but you need to create new ones for the deltas for the differences. And so then you don't need to change every single topic. You keep what is similar or even take it to the next level. Text fragments, you can reuse text fragments which are basically paragraphs or sentences, if I should say it in a sloppy way. And so the business benefits are basically that you save a lot of time by reusing and making use of the tool set that is to the left. And basically, what you see there is to not go into detail, but its a variety on different levels of what you can reuse in Paligo. - Good. And I think the important message here is, like, content reuse in Paligo is not one thing. It's not one single set of feature. It's a whole portfolio of features and capabilities and methods. We will not go into deeper detail here, because that would require a whole webinar on itself. But just for you who do not know Paligo well, who are listening, I think it's important to explain what content reuse is in Paligo, at least on a high level. So moving on to another case, Tonkean. Is that correctly pronounced, Therese? - It is, from what I've heard at least. So we spoke about Hiab a couple of minutes ago. And they were obviously quite a big organization. And let's move to quite the opposite, so to speak. So Tonkean, they are an intake orchestration platform used by internal service teams in the sectors like procurement and legal sectors. So their headquarter is in Palo Alto, and they are having customers that are within the Fortune 500 companies. So they have really high expectations put on themselves. And especially when it comes to the documentation, they need to keep things efficient, manageable. But they're quite a small team. They're quite a small team themselves. So they needed that efficiency. And we can talk about reuse. We can talk about a lot of things. But they chose Paligo because it offered exactly the right combination of structured authoring power and cloud-based flexibility, but also ease of use. They'd never really worked with a CCMS before. And so with Paligo, they could work from anywhere without worrying about the setup or the maintenance of it. And implementing Paligo was very straightforward. The onboarding was very smooth, and it allowed the team to go live and hit the ground running with minimal downtime. So one of the biggest benefits that Tonkean has seen is separating content from the layout, meaning that they can structure the content independently of its presentation and they've significantly improved the efficiency, so allowing their small team to make content updates without really reformatting or rebuilding whatever they have. And this makes it way easier to manage and update their documentations, and keep their knowledge base very consistent as well. And with the collaboration workflow that we have, that's also been a real game changer for them. The team can work and include reviewers and subject matter experts in the content process, which makes it very simple to gather input and really ensure accuracy before publishing. You can also read about Tonkean on our website if you want to find out more, if you think that resonates with you. But final words here as well. They, really, have gained the structured content management that they needed to support their knowledge base growth with streamlined processes that really allows them to keep pace with demand without overextending their team or overworking their team. So it's a really good example here as well, of how an easy-to-use platform is being used, and can really empower large but also small teams to achieve efficiency and scalability. - Good. Thank you, Therese. And, of course, we chose these two examples of customers with a bit of thought because manufacturing and software is really those two industries where Paligo is very strong both historically and forward. So I think it's a good representation, even though it's very different industries. The use case is super strong with both of these. And for those of you listening, please do know that you are free to ask questions in the Q&A. You'll find that on your right-hand side. So just pop any question you have in there, and we'll do our best to answer it at the end. And moving on to another, or actually a final question from the survey results. And this one is more about time-saving using specific features of Paligo. So Nermin, talk us through this. - Yeah, so as Daniel mentioned, it's an estimate of how much time has been saved during the creation and updating and maintaining documentation through versioning, branching, and the variable features in Paligo. Now, I would need another webinar to dive into each of these features and explain them, and so on. But let's say that these are features that I would categorize within Paligo's version management. If I'm to say something more about variables, it's a way of swapping out smaller part of content within publications. And to just reiterate on what we mean by publications. It's the definition of a type of container of topics and the structure of how these topics, and how the topics are structured, sorry. So to read out the statistics, 17% of our customers think that they have saved 0% to 10%, 22%, 11% to 25%, 21% of our customers, 26% to 50%, and 51% to 70%, oh, sorry, 17% think 51% to 75%, and then 12%, 65% to 100%. A lot of numbers at once. So I promised a cliffhanger on versioning. So I think this is the right slide. So it's an upcoming item that myself and my team will be working on. And as you know, there are different requirements if you work in software or if you work in hardware in terms of versioning, keeping different versions alive, and for a long time, being able to get back to these versions. Within software, mostly, we only care about the latest version. That's not the whole truth, but that's what we've seen in general. In terms of hardware, it can vary. It might be regulations, internal regulations, and so forth. So the cliffhanger is that we will be improving, although there are ways of tackling this. But we will be improving the version management for keeping versions alive for a longer time and getting back to these in an easier way. - This is awesome. - Yeah. - This is really exciting. - So I'll finish this slide off with the cliffhanger. - Good. - Applause for that. - Thank you, Nermin. So interesting features coming up in future releases. Therese, we're moving on to the last case before wrapping this up. Tell us about PointClickCare. - Sure, and here, as well, you can read about PointClickCare on our website to find the customer story there. But trying to keep it short and simple, I have to look at my notes quickly, just like Nermin, lots of numbers coming up. But PointClickCare, they're a leading health care technology platform, and they work with more than 27,000 long-term and post-acute care providers, and over 3,100 hospitals and thousands of ambulatory clinics with numerous health systems all across the US. So they really needed a robust platform, a robust solution to manage their growth, and their content demands and streamline the documentation workflow, really. And their content was, obviously, content and documentation was, obviously, growing, and managing and organizing the documentation became really challenging for them. So they turned to Paligo to bring structure to their content, and achieve scalability that is required to support healthcare providers at every stage of the patient's journey. So it, indirectly, touches the patient's journey, which is really inspiring, in a way. So with our structured approach, with our platform, PointClickCare are using taxonomies to help them organize content logically, making it really easy to manage, retrieve, and update their content without any duplication. Nermin, you talked about variables, you talked about branching, and you talked about reuse as well. And thanks to all of those functionalities. PointClickCare no longer has to duplicate content across the documents, and they can make changes in one place and apply them everywhere needed, really enhancing that efficiency and consistency. So the team now really saves a lot of time. And they benefit from a clear, streamlined review process, really ensuring that everything is kept up to date while collaborating across different departments. So it really enhances not only the team, but also improve the accessibility for their end users. And with the reuse capabilities like we spoke about before, the reuse functionality or capability is really, really powerful. It easily provides accessible, relevant information and empowers here the healthcare providers with the information that they need when they need it. And so, it's here as well, Daniel, it's a powerful example of how structured content and workflows can really drive efficiency and support scalability, and really enhance user experience in big, high stakes industries, just like health care as well. And we're very proud to support them. - Good. Now, I know I've spoken to PointClickCare a couple of times and what they do is really impressive. It's huge scale of operations. We have about 10 minutes left, so we're moving on and talking a bit about why Paligo is structured authoring for all. I mean, we are, particularly, proud to make structured authoring accessible to everyone, no matter of their level of knowledge about structured authoring, because that it can sometimes be understood as being quite difficult or even daunting to some people. But we really make an effort to ensure that structured authoring is easy and accessible for everybody. Sometimes, it's the most beneficial option for companies that create and manage large or complex documentation, such as manuals or online help centers that we just heard about. But ensuring that we have high-quality consistency in your content, it stays well organized. It's always presented in a clear and consistent way. So let's see what our customers think about how well that goes. Now, overcoming siloed content, and reducing content maintenance time, that's some of the primary wins you get of switching to structured authoring. Like, we discussed here previously. It's really about that efficiency, about content reuse, maintaining less content while publishing more. And you don't really need that prior knowledge of structured authoring or the underpinning XML formats. As Nermin mentioned earlier, you still have access to them. So if you're a power user, you can still drill all the way down into the very technicalities of it, or if that's how you prefer to work. But if you don't, you don't have to worry about it. And with Paligo support and resources, as well as this super easy-to-use interface, you will be up and running with structured authoring faster than you may think. I think that's a super important message that well-confirmed by these quotes from our customers. Therese, anything you want to add here? - I want to really emphasize here, getting up and running smoothly is essential for any project or any product or system. I think if I give you a bike, the best bike in the world, if you don't know how to use it, there's no point of it. You need someone to teach you how to use that bike in the best way possible, so that it becomes the best way for you to travel around or whatever it might be. And that's what we, at Paligo, can offer you. It's that smooth onboarding, personalized onboarding, customized onboarding, together with additional teams like the professional services for the migration of the content, the informational architects, and support team, and also customer success team, of course. - In terms of the quote at the end there or at the bottom, sorry. It highlights the different ways of publishing, and it mentions Zendesk there. So I would just like to mention some of our most popular one which is PDF, HTML5, but also to CRMs like Salesforce and Zendesk, and to Git repos, to content delivery platforms as Zoomin or Fluid Topics, just to mention a few. - Good. And just shifting over and maybe touching our integrations slightly because that's also part of the productivity gains our users and customers get. - Yes, exactly. We're well aware of that choosing a CCMS is not just centered around the technical writing. It needs to exist in a context of where other organizational units work in. So we have chosen our integrations with care and just to mention a few, and the possibility. So as I mentioned, you can publish to Zendesk, you can publish to Salesforce, but also to Freshdesk. In terms of the collaboration workflow, you can integrate with Slack and Teams to get notifications and increase the efficiency within the collaboration workflow. But also to integrate your tech docs into GitHub or Bitbucket is an option. Or why not push directly to Amazon S3. In terms of translations, to mention one, you can translate via Phrase. But we also have integrations with, if I'm not lying to you, but there might be more, at least Algolia and Cavallo are two of our search engines, which we have integrations to. But if you want to create your own automations, you can obviously use our REST API. - Good. Thank you, Nermin. Now, we're getting close to the end of the 55 minutes here, and luckily there's only two slides left. And I just wanted to dig into a bit about the details here on we don't only introduce huge efficiencies post implementation or post using polyglot, but we also get organizations ready to scale as their content needs grow. We see this from many customers, like, they really love how they can scale their operations with Paligo. And as our users or product or customers product portfolios expand their translation and localization requirements grow, having Paligo in place is that foundation to help them reduce content costs as they scale. Making collaboration smooth with reviewer and contributor workflows, looping in all your SMEs and all your engineers and experts out there in the organization into your technical documentation or your content, Paligo really helps that getting done using fewer resources and more efficiently. Everybody stays within the platform as they review and give feedback. So I think we just want to conclude with this final piece from Forrester. As a closing observation, I think we, as Paligo, believe that the value we bring is strongly connected to the challenges of organizations have on scaling and expanding. So what we're looking here is the results from a report from Forrester on the potential of CCMSs or Component Content Management Systems. It's a couple of years old, but it's still valid. In this scenario, Forrester interviewed a couple of 100 decision makers responsible for content and content management in their organizations. And as you can see, Paligo actually helps solving real world problems from a multitude of organizations in all different industries, multichannel publishing, translation capabilities that empowers and enables content strategy. You can actually grow alongside your own go-to-market strategies. And Therese, Nermin, is there anything you want to highlight here before we jump to the questions and answers? - Yeah, I mean, looking at on the right-hand side of the screen, lack of unified content strategy across teams and organizations. That's pretty much what we've been talking about during the customer cases that the three that I've spoken about. It, really, is an organizational issue. And we, at Paligo, help with that. But also when it comes to translations, it's vital in a CCMS tool because it really enables organizations to deliver consistent and accurate content as well. So I think those two there really speak to me personally. And having spoken to most of our customers here at Paligo, I would say those are the two pain points as well that we can see on a consistent basis for sure. - Good. All right, let's use the last minute to answer a question. Jumping over to the Q&A. So I'm actually going to add here a question from Wes. Super interesting question. "Do we have data on ROI linked to improving customer experience by using Paligo? For example, making documentation more easily searchable and deflecting customer or technical service calls, or improving customer satisfaction." And we actually had a question on that specific topic. Ticket deflection, self-support improving as since implementing Paligo. And interestingly, about half of the respondents said, this is not applicable to Paligo. And in my experience, when you look into, particularly ROI on ticket deflection, it's super challenging for organizations to measure this. It's very hard to attribute ticket deflection specifically to content. It might be about your processes, how well searchable the content is as Wes question includes, and I think that's why we had the majority or half of the respondents saying that that's not applicable to their process. On the other hand, we had the other side of the respondents saying, if you exclude the smallest piece, we actually had 40% stating that Paligo added more value to the ticket or deflection self-service process by almost 40% of the respondents. So Wes, I'll see if I can find your email address, and send you a short email on this, so you have that data as part of the handouts from this webinar. And there's a few other questions. We will get back to and answer those over email. Otherwise, thank you so much for joining. And Therese, Nermin, thank you so much for your time and effort into these 55 minutes. - Loads of fun. I'd love to do that again. - Good. And thank you, everybody, for tuning in. Don't forget to download your copy of the report. We'll send that out on a link to everybody after this webinar. So, bye for now, and have a nice day, everybody. - Thank you, everyone. - Bye-bye.