WEBVTT NOTE This file was generated by Descript 00:00:42.311 --> 00:00:44.271 Duke: All right, Corey, what are we talking about today? 00:00:45.336 --> 00:00:45.756 CJ: Oh, duke. 00:00:45.756 --> 00:00:50.286 Today we are talking with the good folks from Serenity, EHS, 00:00:50.521 --> 00:00:52.441 Duke: The very good folks at Serenity EHS. 00:00:52.461 --> 00:00:56.141 We have with us , Nathan Duperrac and Peter Onepo. 00:00:57.135 --> 00:00:58.175 Oh, damn it. 00:00:58.175 --> 00:01:04.045 It's like we're over a hundred episodes and I still like, I 00:01:04.055 --> 00:01:05.915 just want one perfect intro one. 00:01:09.418 --> 00:01:09.648 All right. 00:01:09.648 --> 00:01:10.868 Well, welcome to the show guys. 00:01:10.958 --> 00:01:12.028 So good to have you here. 00:01:12.151 --> 00:01:15.491 I would love for you guys to introduce yourself and then introduce Serenity. 00:01:15.491 --> 00:01:16.851 So, Peter, why don't you go first? 00:01:17.486 --> 00:01:17.966 Peter: Yeah, sure. 00:01:18.016 --> 00:01:18.956 , I'm Peter Onepo. 00:01:19.113 --> 00:01:22.986 I've been in the ServiceNow ecosystem since 2009. 00:01:23.256 --> 00:01:27.591 , most recently I am the co founder and CEO of Serendity EHS. 00:01:28.021 --> 00:01:39.621 And we have a fantastic EHS solution for the ServiceNow Pipeline. 00:01:39.766 --> 00:01:43.316 Nathan: similar to Peter, I've worked in the ServiceNow ecosystem since 00:01:43.586 --> 00:01:46.296 2014, , primarily in product management. 00:01:46.356 --> 00:01:49.486 And then I, uh, I joined the Serenity team actually just one 00:01:49.486 --> 00:01:52.036 year ago, so I'm officially just past my one year anniversary. 00:01:52.420 --> 00:01:53.050 CJ: Nice. 00:01:53.188 --> 00:01:57.698 Duke: A lot of people in service now are focused around the ITSM side of the house. 00:01:58.208 --> 00:02:00.498 , the product does continue to grow and grow and grow. 00:02:00.518 --> 00:02:05.971 But for those who don't know, , tell us what EHS means in the Serenity EHS title. 00:02:06.278 --> 00:02:08.738 Peter: EHS stands for environmental health and safety. 00:02:09.128 --> 00:02:12.498 Sometimes you'll see it as HSE, or there's a couple of other 00:02:12.538 --> 00:02:14.338 different, , variations of that. 00:02:14.883 --> 00:02:20.033 And effectively it is focused on making sure that your employees are, 00:02:20.182 --> 00:02:21.870 healthy and safe while they're working. 00:02:21.870 --> 00:02:25.690 And so that can be a little bit different based on the industry, but effectively 00:02:25.690 --> 00:02:29.413 the, point of it is especially if you're interacting with machinery or doing 00:02:29.413 --> 00:02:34.166 a task that you could get hurt, how do you track are people getting hurt? 00:02:34.196 --> 00:02:35.633 How did we help them? 00:02:35.703 --> 00:02:38.543 And then ultimately, how do we prevent that from happening in the future? 00:02:38.913 --> 00:02:40.673 So there's a lot of like investigative work. 00:02:40.716 --> 00:02:43.516 putting together action plans to correct a problem, to prevent 00:02:43.516 --> 00:02:44.626 it from happening in the future. 00:02:44.963 --> 00:02:50.283 our software tackles all of that, and we try to put it right next to all the other 00:02:50.283 --> 00:02:53.433 things that employees might be dealing with, the traditional ServiceNow stuff, 00:02:53.743 --> 00:02:56.303 , I have IT requests, I have HR requests. 00:02:56.693 --> 00:02:59.980 Now you can manage that whole EHS solution, right there on 00:02:59.980 --> 00:03:01.856 the platform with our software. 00:03:02.093 --> 00:03:05.170 , Duke: if people wanted a, like for like, , who would you say you compete with? 00:03:17.010 --> 00:03:24.275 Silence. 00:03:25.601 --> 00:03:27.855 Peter: those are the big names that are out there and that, we find 00:03:27.855 --> 00:03:29.405 ourselves competing with directly. 00:03:29.562 --> 00:03:32.585 then there's a bunch of little point solutions that like solve 00:03:32.585 --> 00:03:34.215 maybe one part of the problem. 00:03:34.408 --> 00:03:38.681 you know, whether it's just, , the EHS incident itself, or maybe if you 00:03:38.681 --> 00:03:40.161 have to do like OSHA reporting, right? 00:03:40.161 --> 00:03:42.165 So if people get hurt, you have to report it to the government. 00:03:42.685 --> 00:03:45.065 , there's solutions for just that piece. 00:03:45.735 --> 00:03:49.595 , but when it comes to a comprehensive EHS solution, those are, those 00:03:49.595 --> 00:03:51.765 are the big competitors that we're going against right now. 00:03:52.229 --> 00:03:54.679 CJ: what made you guys choose to build on service? 00:03:54.679 --> 00:03:55.435 Now, you 00:03:55.435 --> 00:03:57.355 Peter: We chose to build on top of the service now. 00:03:57.665 --> 00:03:59.765 Honestly, a big part of it is because. 00:04:00.235 --> 00:04:04.862 It's what we know, but in the 15 years that I've been working with 00:04:04.862 --> 00:04:07.762 the platform, EHS had come up a lot. 00:04:07.802 --> 00:04:11.342 There were organizations that wanted to put this stuff right 00:04:11.342 --> 00:04:13.952 next to their other applications. 00:04:14.002 --> 00:04:18.782 So in previous lives, I was both doing implementations and I was on 00:04:18.832 --> 00:04:20.282 the sales side at, Service Down. 00:04:20.672 --> 00:04:22.852 People would ask how do we put all this stuff together? 00:04:23.502 --> 00:04:25.462 And the platform creates. 00:04:25.852 --> 00:04:29.262 That ability to do engagement with employees, which is a big 00:04:29.272 --> 00:04:31.232 problem in the HS space too. 00:04:31.302 --> 00:04:36.059 So there's a lot of alignment between what customers are asking for the individual 00:04:36.059 --> 00:04:42.615 problems that they calling out and our capability to deliver solutions, , on 00:04:42.625 --> 00:04:47.005 the platform that met that, but also the time to value was huge, right? 00:04:47.085 --> 00:04:48.659 So, we could be up and running. 00:04:49.222 --> 00:04:53.012 an app with a first customer in a very short period of time. 00:04:53.572 --> 00:04:55.432 And then we can do deployments very quickly. 00:04:55.842 --> 00:04:59.962 And so this meant that our customers are able to solve these problems. 00:05:00.152 --> 00:05:01.952 They're able to do it in a comprehensive way. 00:05:01.952 --> 00:05:05.322 They're able to get that employee engagement, , on the service now 00:05:05.322 --> 00:05:09.122 platform, and for us, we could do it very quickly and efficiently, and 00:05:09.122 --> 00:05:12.475 we didn't have to build out a whole operations team and, all this stuff 00:05:12.475 --> 00:05:13.515 that we didn't want to deal with. 00:05:13.535 --> 00:05:15.615 We want to get right to building the app for the customer. 00:05:15.705 --> 00:05:23.716 Silence. 00:05:27.420 --> 00:05:30.380 Nathan: they're managing, they don't always have the best relationship with I. 00:05:30.390 --> 00:05:30.740 T. 00:05:30.824 --> 00:05:30.974 I. 00:05:30.974 --> 00:05:31.144 T. 00:05:31.144 --> 00:05:34.514 is trying to streamline and minimize costs, , and take out some kind 00:05:34.514 --> 00:05:36.544 of bespoke, , operations tasks. 00:05:36.544 --> 00:05:40.344 And so by being on service now, I know it's, helped in a lot of accounts 00:05:40.424 --> 00:05:44.580 to actually smooth the relationships between the business users and E. 00:05:44.580 --> 00:05:44.750 H. 00:05:44.750 --> 00:05:44.990 S. 00:05:45.010 --> 00:05:46.860 and the support teams in I. 00:05:46.860 --> 00:05:47.230 T. 00:05:47.735 --> 00:05:50.255 , so yeah, to Peter's point, I think it was an initial hypothesis. 00:05:50.255 --> 00:05:54.575 We saw that happening in our time at service now in, in other business 00:05:54.575 --> 00:05:57.645 domains , and it's continuing to hold true , in EHS as well. 00:05:57.999 --> 00:05:58.829 CJ: know, that's interesting. 00:05:58.829 --> 00:06:02.719 I think since I've been, , involved in service now, , 1 of the things 00:06:02.719 --> 00:06:06.229 that's always stood out to me is how easy it is to build an application 00:06:06.229 --> 00:06:09.879 on top of it versus having to build something from scratch. 00:06:09.899 --> 00:06:13.709 If you're outside of platform and it always occurred to me that this is a 00:06:13.719 --> 00:06:18.115 great platform to build apps, such as this 1, and be able to, , Bootstrap 00:06:18.115 --> 00:06:21.665 it a lot easier than say, , having to build out like a platform that 00:06:21.665 --> 00:06:25.632 can do dashboards and emailing and, a database to collect the records like 00:06:25.632 --> 00:06:26.732 ServiceNow gives you all of that. 00:06:26.732 --> 00:06:31.012 And so I can see how it was, a solution, That was appealing for you all, especially 00:06:31.012 --> 00:06:32.252 what's your ServiceNow backgrounds. 00:06:33.052 --> 00:06:34.352 One of the things that you mentioned. 00:06:34.912 --> 00:06:38.119 I just want to, double click on was, you know, you said smooth out the, 00:06:38.159 --> 00:06:42.499 relationship with the business and it, , in terms of talking about the 00:06:42.499 --> 00:06:46.309 legacy applications that they've, had to utilize, , previously with EHS, 00:06:46.832 --> 00:06:48.332 tell me a little bit more about that? 00:06:48.332 --> 00:06:51.132 I'd like to, understand a little bit more from the business standpoint, How 00:06:51.132 --> 00:06:55.722 much they appreciate the ability to actually have that better relationship 00:06:55.722 --> 00:06:57.622 with it, using the nervous now platform. 00:06:57.975 --> 00:06:58.325 Nathan: Yeah. 00:06:58.325 --> 00:07:01.265 So I think, it gets a little bit into kind of understanding 00:07:01.265 --> 00:07:03.195 the, competitive landscape. 00:07:03.265 --> 00:07:04.805 , and so as Peter was mentioning earlier. 00:07:05.405 --> 00:07:08.225 There's a lot of older platforms like intellects, Gordy, , and 00:07:08.235 --> 00:07:10.485 dozens of, point solutions as well. 00:07:11.095 --> 00:07:12.295 And they all have their benefits. 00:07:12.295 --> 00:07:13.305 They all have their drawbacks. 00:07:13.505 --> 00:07:17.205 , some are highly configurable, , but that comes at an expense , of 00:07:17.205 --> 00:07:18.265 say user experience. 00:07:18.475 --> 00:07:24.345 , and so adoption suffers because users struggle to actually use those solutions. 00:07:24.995 --> 00:07:27.505 Then there might be another solution with a great user experience, 00:07:27.525 --> 00:07:29.135 but really limited capabilities. 00:07:29.155 --> 00:07:29.565 And so. 00:07:29.699 --> 00:07:31.622 What ends up happening for those customers. 00:07:31.622 --> 00:07:35.652 And we see this really with, every large enterprise we talked to is they've 00:07:35.652 --> 00:07:40.292 just kept acquiring, , more point solutions, , additional platforms to 00:07:40.292 --> 00:07:42.682 fill the gaps left by the previous one. 00:07:42.732 --> 00:07:45.572 , and so with each one of those, there's the maintenance overhead. 00:07:45.582 --> 00:07:48.962 There's, even the simple stuff like getting active directory, single sign on 00:07:49.172 --> 00:07:51.912 set up and getting HR feeds, , set up. 00:07:51.912 --> 00:07:54.782 And so all of that just adds a lot of non value add. 00:07:55.147 --> 00:07:56.867 Work, , and ongoing maintenance. 00:07:56.867 --> 00:08:01.610 And so what ends up happening is feature requests, , end up falling to 00:08:01.610 --> 00:08:06.057 the wayside because the maintenance is taking so many of it's resources. 00:08:06.057 --> 00:08:09.877 And so we see that then resulting in frustration where the business wants 00:08:09.877 --> 00:08:13.477 something they're being told they can get it maybe in, in two years. 00:08:13.792 --> 00:08:18.702 , and so that's, I think started probably years ago and just continues to snowball. 00:08:18.702 --> 00:08:22.062 And so, some of the accounts we've talked to just they're blown away 00:08:22.062 --> 00:08:26.912 by the speed at which an idea can be turned into a feature and deployed. 00:08:27.362 --> 00:08:32.262 , and with the ServiceNow teams at our customers, they feel confident with 00:08:32.362 --> 00:08:36.932 things like scoped apps that we can move quickly and deliver those features without 00:08:36.932 --> 00:08:39.342 impacting other parts of the platform. 00:08:39.342 --> 00:08:39.812 And so. 00:08:40.322 --> 00:08:43.119 In the end, we end up seeing that, there's not this, this push and 00:08:43.119 --> 00:08:44.429 pull where one team wants something. 00:08:44.429 --> 00:08:48.309 The other doesn't it's actually flipped in and both are supportive. 00:08:48.749 --> 00:08:50.059 , and we're able to prove that really quickly. 00:08:50.059 --> 00:08:53.569 And so that's what I'm most excited about, especially with our enterprise 00:08:53.569 --> 00:08:58.999 accounts is having the, buy in from stakeholders on, both sides and knowing 00:08:58.999 --> 00:09:03.059 that they all prefer this , over what the previous, , ecosystem looked like, 00:09:03.769 --> 00:09:06.249 Duke: I'm just, I'm still stuck on telling people that they can 00:09:06.249 --> 00:09:07.689 have their thing in two years. 00:09:08.299 --> 00:09:08.699 Nathan: right. 00:09:09.069 --> 00:09:10.109 Duke: Like you imagine. 00:09:10.560 --> 00:09:16.218 CJ: Yeah. 00:09:16.289 --> 00:09:19.129 Duke: I get older, the time tends to go faster, but even now, I 00:09:19.129 --> 00:09:22.769 think two years, it might as well be 20 the way the world changes 00:09:22.859 --> 00:09:26.232 Nathan: right, yeah, it's so much changes in two years. 00:09:26.262 --> 00:09:29.142 , even when we get asked for feature requests and I'm wincing, cause I'm 00:09:29.142 --> 00:09:30.562 like, oh, that might take a month. 00:09:31.552 --> 00:09:31.902 Duke: a whole 00:09:32.042 --> 00:09:35.272 Nathan: and, and when I say, um, when I say that the, customers are 00:09:35.272 --> 00:09:36.902 always like, oh yeah, that's fine. 00:09:37.062 --> 00:09:39.999 So it's been, refreshing for our customers to hear that. 00:09:40.029 --> 00:09:42.549 And it's, it's nice for us , to know that , we're helping and 00:09:42.559 --> 00:09:43.979 contributing positively in that way. 00:09:44.549 --> 00:09:48.169 Duke: Is there any part of the service now app that has one of 00:09:48.169 --> 00:09:50.359 those, this is better together? 00:09:52.420 --> 00:09:52.740 Nathan: many. 00:09:52.740 --> 00:09:55.820 I think the easiest one to think of is, is HR. 00:09:55.984 --> 00:10:00.064 and in some of our, our accounts, primarily the smaller ones, sometimes 00:10:00.074 --> 00:10:02.544 EHS does actually roll up into HR. 00:10:02.797 --> 00:10:05.017 it's not the most common in, large enterprise. 00:10:05.957 --> 00:10:09.267 Where it falls more into the operations team, but there is definitely some 00:10:09.267 --> 00:10:14.287 overlap with HR, especially when it comes to OSHA requirements here in the US. 00:10:14.587 --> 00:10:20.087 A lot of what ends up feeding into your regulatory reports is data. 00:10:20.087 --> 00:10:21.727 That's coming from HR systems. 00:10:21.737 --> 00:10:24.407 So you need to know who the employees are. 00:10:24.917 --> 00:10:26.257 , you need to know where they live. 00:10:26.627 --> 00:10:28.657 You need to know when they started, how long they've been 00:10:28.657 --> 00:10:29.987 in the position that they held. 00:10:30.337 --> 00:10:33.867 And so a lot of that data, you know, naturally lives , in the HR platforms. 00:10:33.867 --> 00:10:37.157 And so , if we're working with a customer whose HR team is already 00:10:37.157 --> 00:10:40.717 on service now, that accelerates time to value even further. 00:10:40.994 --> 00:10:43.204 I think facilities plays into it as well. 00:10:43.267 --> 00:10:45.887 and then I think there's, it's something that we don't see, , quite 00:10:45.887 --> 00:10:47.880 as much, but I have to think that. 00:10:48.245 --> 00:10:51.065 But things like field service management, and I know that I know the service 00:10:51.065 --> 00:10:54.369 now teams have been getting more into enterprise asset management. 00:10:54.879 --> 00:10:58.699 Those start to converge with the conversations we have as well, which, 00:10:59.049 --> 00:11:02.855 becomes things like inspecting pieces of machinery and pieces of equipment. 00:11:03.005 --> 00:11:03.515 and so. 00:11:03.725 --> 00:11:07.765 HR is the 1 that we, I would say is, the most obvious fit, but I think there's, 00:11:07.815 --> 00:11:11.995 so much more opportunity, even outside of that, , to tell those better together 00:11:11.995 --> 00:11:13.825 stories , with other service now products. 00:11:14.427 --> 00:11:16.820 CJ: I love that, I'm just going to tie this back to 00:11:16.820 --> 00:11:18.240 something that you said earlier. 00:11:18.300 --> 00:11:20.700 that really resonated with me as well when we were talking about, , the 00:11:20.700 --> 00:11:23.760 ease of use and building on the ServiceNow platform and a lot of 00:11:23.760 --> 00:11:25.030 the features that you inherited. 00:11:25.030 --> 00:11:29.940 I wasn't thinking about the perspective of you also inherit, , if single 00:11:30.000 --> 00:11:36.000 sign on is already HR integration connected to the instance, right? 00:11:36.320 --> 00:11:38.080 You already inherit those things. 00:11:38.080 --> 00:11:38.430 Okay. 00:11:38.430 --> 00:11:38.440 Thanks. 00:11:38.440 --> 00:11:38.450 Thanks. 00:11:38.460 --> 00:11:41.710 With service now with, your app being built on the service now platform. 00:11:41.710 --> 00:11:45.270 And then, there's all of these other things that you just enumerate it, right? 00:11:45.270 --> 00:11:49.670 Like, tying directly into maybe asset management , and utilizing, probably 00:11:49.670 --> 00:11:52.010 the CMDB probably reporting, right? 00:11:52.160 --> 00:11:55.364 Like all of these different things that, the platform goes to offer and, 00:11:55.374 --> 00:11:59.524 and, it goes right to a just basically a competitive advantage, right? 00:11:59.574 --> 00:12:02.034 By built by being built on the service now platform. 00:12:02.454 --> 00:12:02.734 Nathan: Yeah. 00:12:02.784 --> 00:12:06.564 Time to value is the one I constantly focus on. 00:12:06.624 --> 00:12:09.484 , every one of those integrations, they might not be technically difficult, 00:12:09.484 --> 00:12:12.374 but if you're, , an enterprise, there's different stakeholders that you have 00:12:12.374 --> 00:12:14.754 to align and have the conversations. 00:12:14.754 --> 00:12:17.974 And so optimistically, each integration takes a week. 00:12:18.064 --> 00:12:19.324 , that's super optimistic. 00:12:19.324 --> 00:12:22.524 And, add each one of those integrations and all you're doing is 00:12:22.524 --> 00:12:24.224 adding to . Your deployment timeline. 00:12:24.224 --> 00:12:27.224 And so it's great that , for customers, especially those 00:12:27.224 --> 00:12:28.294 highly adopted on service. 00:12:28.294 --> 00:12:30.844 Now we can cut those timelines significantly. 00:12:31.334 --> 00:12:34.364 , and I think time to value , is ultimately what , the EHS teams want. 00:12:34.685 --> 00:12:38.495 Peter: Yeah, and it goes back to that question about how do 00:12:38.655 --> 00:12:41.015 we work with it teams as well. 00:12:41.505 --> 00:12:44.435 And this is a story that resonates, I think, on both sides of that equation. 00:12:44.732 --> 00:12:50.489 , because you have IT team needs to support EHS and if EHS in a lot 00:12:50.489 --> 00:12:51.739 of cases, they'll actually have. 00:12:51.892 --> 00:12:57.122 Two or three of our competitors, because not one of them does everything well. 00:12:57.732 --> 00:13:01.752 And so it is now supporting these three different platforms 00:13:01.752 --> 00:13:02.902 because it supports platforms. 00:13:02.902 --> 00:13:07.242 So , when we come in and we say the plan isn't to add a new agent, EHS 00:13:07.242 --> 00:13:10.292 platform, the plan is to remove these. 00:13:10.797 --> 00:13:15.397 Other two or three, put this one in place on the platform you already own. 00:13:15.867 --> 00:13:21.317 And now we can cut a lot of the talking about the tactics and the details of 00:13:21.367 --> 00:13:24.387 what's being deployed and start talking a little bit more strategically. 00:13:24.387 --> 00:13:28.527 Like what are the outcomes you're not seeing today because you're so busy 00:13:28.547 --> 00:13:32.252 trying to You know, upgrade porty and make sure that that integration doesn't 00:13:32.262 --> 00:13:35.852 break with single sign on like , we're already up and running and past that 00:13:36.032 --> 00:13:39.662 in a quarter of the time that, a lot of our competitors are in place. 00:13:39.892 --> 00:13:44.468 And so that's, why the service now story plus EHS helps a lot and then 00:13:44.518 --> 00:13:48.348 one of the things you were talking about, CJ, is it is very easy to build 00:13:48.398 --> 00:13:52.308 on the platform, but what can happen with that is it's a double edged 00:13:52.308 --> 00:13:55.808 sword because you can build it doesn't necessarily mean you should build it. 00:13:55.838 --> 00:13:59.498 And so that's where that's where having a pre built application 00:13:59.498 --> 00:14:03.128 with guardrails in place helps simplify that conversation down. 00:14:03.128 --> 00:14:05.978 So I'm not going to pretend that our solution solves every 00:14:05.978 --> 00:14:10.028 problem for every enterprise, but if we can come in and take. 00:14:10.078 --> 00:14:12.802 The baseline out and say, that's solved. 00:14:13.162 --> 00:14:17.592 Now you can really focus in on, , maybe you need a custom feature that 00:14:17.702 --> 00:14:21.642 belongs just to you because your manufacturing process is bespoke. 00:14:21.955 --> 00:14:24.425 And you can actually do that now because you've gotten rid of 00:14:24.425 --> 00:14:27.485 all the red tape that comes with trying to manage three platforms. 00:14:27.985 --> 00:14:32.105 And now you've got Serenity on service now, and then you add this additional 00:14:32.125 --> 00:14:35.795 feature and, it just opens up the door, I think for our customers to do a lot more. 00:14:36.320 --> 00:14:39.200 Duke: Do you find that most of your customers , have EHS 00:14:39.200 --> 00:14:40.900 solutions that they are replacing? 00:14:41.120 --> 00:14:43.850 Or is it companies that are now getting to the point where it's like, Hey, 00:14:43.850 --> 00:14:45.520 listen, we need tools behind this. 00:14:47.269 --> 00:14:49.069 Nathan: I'd say it's both. 00:14:49.149 --> 00:14:54.809 , so at the highest level, I group our customers into 2 buckets in 00:14:54.809 --> 00:14:58.846 the enterprise space, especially with manufacturing and oil and gas. 00:14:59.761 --> 00:15:03.291 Construction, the historically, , have always been dangerous jobs. 00:15:03.301 --> 00:15:04.664 They've had, programs in place. 00:15:05.128 --> 00:15:07.098 Rarely do we, we see them have one solution. 00:15:07.098 --> 00:15:09.388 Like I was saying, they, have multiple solutions that they've 00:15:09.388 --> 00:15:11.128 acquired over the last decade or two. 00:15:11.638 --> 00:15:15.038 , and so they're looking , to replace all of those, , or a large percentage 00:15:15.068 --> 00:15:17.128 of those with a single platform. 00:15:17.658 --> 00:15:20.378 , so that's really common for our, our larger customers. 00:15:21.058 --> 00:15:25.038 , but then on the other end of the spectrum, there's a really untapped 00:15:25.038 --> 00:15:30.648 market, , that we've, found with midsize and even smaller shops where they're 00:15:30.648 --> 00:15:34.368 still in, in Google sheets, they're on Excel docs, they're on SharePoint sites. 00:15:35.033 --> 00:15:38.283 , and so what they're looking for is, is a structured workflow. 00:15:38.563 --> 00:15:40.093 They want to streamline their reporting. 00:15:40.713 --> 00:15:45.393 They're interested in, adding intelligence to their very small teams. 00:15:46.063 --> 00:15:50.723 , and so we've been focusing and asking ourselves, are there ways that we can 00:15:50.933 --> 00:15:53.603 bring these capabilities down market? 00:15:54.118 --> 00:15:58.008 , in a meaningful way to really just get them off , of flat files into something 00:15:58.008 --> 00:16:02.858 that, that is modern, intuitive and, really accelerates their, EHS programs. 00:16:03.278 --> 00:16:05.978 Duke: You're basically making these, the stuff that was maybe 00:16:05.978 --> 00:16:07.568 priced out for most people. 00:16:07.888 --> 00:16:10.698 And bringing that power to those, , small, medium sized enterprise. 00:16:11.478 --> 00:16:11.808 Nathan: Yeah. 00:16:11.808 --> 00:16:13.138 And priced out for two reasons. 00:16:13.168 --> 00:16:16.578 So one, the, the legacy platforms, they are expensive, , just from 00:16:16.578 --> 00:16:17.958 a subscription perspective. 00:16:18.513 --> 00:16:21.113 , but they're also, there's big services, , S. 00:16:21.113 --> 00:16:21.183 O. 00:16:21.183 --> 00:16:21.603 W. 00:16:21.613 --> 00:16:21.653 S. 00:16:21.803 --> 00:16:25.073 that, that tag along with are already, they're already high costs. 00:16:25.233 --> 00:16:28.929 And so, as we look to that market and we see that there's this need 00:16:28.929 --> 00:16:30.649 and they, they have limited options. 00:16:30.859 --> 00:16:34.969 , we want to be a more affordable option, not, , just from the licensing 00:16:34.969 --> 00:16:39.099 perspective, but also , the implementation and , the ongoing maintenance and support. 00:16:41.554 --> 00:16:45.374 Duke: So , I'm looking on your website and under your product section, I see 00:16:45.374 --> 00:16:47.294 there's seven or eight different products. 00:16:47.324 --> 00:16:50.794 Are these like separate scoped apps on service now, or are they 00:16:50.804 --> 00:16:53.891 just, components of a single app that you're either on or off? 00:16:54.353 --> 00:16:57.406 Peter: it's a combination of both what you see on the website is 00:16:57.406 --> 00:17:01.449 a reflection of what outcomes a stakeholder might be trying to get. 00:17:01.709 --> 00:17:04.739 And then in terms of how we deliver that technically. 00:17:04.856 --> 00:17:08.566 a significant portion of what we do is, is all effectively in one scoped app, 00:17:08.566 --> 00:17:10.126 but , we've separated out a few things. 00:17:11.321 --> 00:17:11.341 CJ: so 00:17:11.481 --> 00:17:14.181 Peter: And there's, that's more of a, a technical conversation. 00:17:14.181 --> 00:17:17.071 So if you take a look at it, we're trying to balance how do we 00:17:17.071 --> 00:17:21.731 deliver outcomes for stakeholders who aren't necessarily technical? 00:17:21.811 --> 00:17:24.411 And in fact, in the EHS world, that's one of the things that. 00:17:24.946 --> 00:17:29.166 I think has been a little bit different over my past dealing 00:17:29.166 --> 00:17:30.856 with IT and ITSM, right? 00:17:30.856 --> 00:17:34.186 Is you have to talk about things a little bit differently. 00:17:34.686 --> 00:17:39.596 And so it's kind of reflected in that our marketing is delivering 00:17:39.726 --> 00:17:43.086 outcomes for our stakeholders and then how we deliver that technically, 00:17:43.566 --> 00:17:45.566 , everything is within a scoped app. 00:17:45.566 --> 00:17:47.966 The question is whether or not there might be a couple of different 00:17:48.366 --> 00:17:50.126 modules in the same scoped app. 00:17:50.126 --> 00:17:51.921 And we present that differently to the stakeholder. 00:17:51.921 --> 00:17:52.426 Yeah. 00:17:52.426 --> 00:17:53.806 Duke: There's an obligatory conversation. 00:17:53.806 --> 00:17:54.656 We have to have Corey. 00:17:54.656 --> 00:17:57.716 I don't know if you notice, but on on their website, they got that serenity. 00:17:57.756 --> 00:17:57.946 A. 00:17:57.946 --> 00:17:58.366 I 00:17:58.686 --> 00:17:59.711 CJ: Oh man, that was my next. 00:18:00.506 --> 00:18:01.296 Duke: gotta go there. 00:18:01.326 --> 00:18:01.966 Gotta go. 00:18:02.636 --> 00:18:03.006 Peter: Yeah. 00:18:03.006 --> 00:18:07.369 So there, there's a couple of things that are changing and this is tying 00:18:07.369 --> 00:18:12.729 back to, you've got EHS people who aren't necessarily technologists, right? 00:18:12.729 --> 00:18:14.499 They've maybe come up through the ranks. 00:18:14.549 --> 00:18:18.976 , they were, , in manufacturing or they were, on the, working on gas lines or 00:18:18.976 --> 00:18:22.219 whatever, and they've worked their way up and they understand technology and they 00:18:22.219 --> 00:18:26.169 understand the benefits, but they don't necessarily understand all the specifics. 00:18:26.899 --> 00:18:29.169 And so what we're trying to do is. 00:18:29.849 --> 00:18:34.219 Open that up for them to be able to use it without having to dig too deep 00:18:34.219 --> 00:18:38.259 in like, Oh, yeah, we can build out an integration with chat gpt or we 00:18:38.259 --> 00:18:40.929 can Tap into something else for you. 00:18:41.289 --> 00:18:45.779 And so what we've done is we've looked for specific use cases where customers 00:18:45.809 --> 00:18:50.524 might be able to leverage AI, and we've, built those, we've baked those out a lot 00:18:51.074 --> 00:18:53.194 deeper than maybe just an integration. 00:18:53.194 --> 00:18:56.484 So, for example, we have an inspections application. 00:18:56.974 --> 00:19:00.464 And so if you're trying to come up with a template, like I need 00:19:00.464 --> 00:19:03.424 to go inspect something to make sure it's safe before I use it. 00:19:03.584 --> 00:19:03.894 Right. 00:19:04.344 --> 00:19:07.664 And this is a new piece of equipment, or I don't have an inspection. 00:19:07.994 --> 00:19:10.494 I can go out and I can ask. 00:19:11.279 --> 00:19:13.459 AI to help me build this out. 00:19:13.759 --> 00:19:15.959 And it's been working fantastically. 00:19:15.959 --> 00:19:18.949 Our customers are very excited about it that a lot of them have 00:19:19.399 --> 00:19:22.699 some inspection templates that they can already pull in, but even then, 00:19:22.709 --> 00:19:24.109 like maybe they want to update them. 00:19:24.609 --> 00:19:28.229 And so that's just one example of us being able to tap into the power of AI. 00:19:28.229 --> 00:19:31.079 And we're looking for other places to plug that into our platform. 00:19:31.689 --> 00:19:33.759 So , it's not a generic utility. 00:19:33.779 --> 00:19:36.719 It's very specifically for, , different use cases. 00:19:36.719 --> 00:19:38.079 And we bake that out for them. 00:19:40.794 --> 00:19:41.934 CJ: Yeah, I love that. 00:19:42.261 --> 00:19:44.471 , I'm going to tie what you just said to something that I got 00:19:44.471 --> 00:19:45.381 from, conversation around. 00:19:45.451 --> 00:19:46.851 One of the previous topic, right? 00:19:46.851 --> 00:19:52.051 And it's, the serenity AI ties back into, , the market ties and outcomes in terms of 00:19:52.051 --> 00:19:56.721 like how you presented it previously about being able to, , help customers that. 00:19:57.036 --> 00:20:00.146 Couldn't otherwise, , for your competitors, right? 00:20:00.146 --> 00:20:03.746 Because they are more expensive that they, because they require more 00:20:03.746 --> 00:20:07.496 work and more people to maintain and utilize and things like that. 00:20:07.496 --> 00:20:07.666 Right? 00:20:07.666 --> 00:20:10.616 So it seems like the entire serenity, , sweet, right? 00:20:10.616 --> 00:20:14.956 Like is, is really aligned towards creating the best outcomes 00:20:14.956 --> 00:20:15.976 from your, for your customers. 00:20:16.606 --> 00:20:19.806 But , would you guys feel like that's one of your best selling points? 00:20:20.496 --> 00:20:24.689 Nathan: I think the accessibility, not only of the, technology, but the 00:20:24.689 --> 00:20:30.059 accessibility of the EHS expertise, , and making that accessible, not 00:20:30.059 --> 00:20:33.889 only to the EHS folks, but really to anyone in, in the company. 00:20:34.128 --> 00:20:38.598 is one of the big benefits, , , and value points with what Serenity AI is doing. 00:20:39.168 --> 00:20:43.128 , I think just like one example, you know, we look at our customers, maybe 00:20:43.128 --> 00:20:46.718 on, day one, they want to import some of their historical, data, which 00:20:46.718 --> 00:20:51.488 is, is often big lists of corrective preventative actions that are assigned 00:20:51.488 --> 00:20:53.118 to the business to, implement. 00:20:53.723 --> 00:20:56.423 , and what we see in, in a lot of those is , the instructions of 00:20:56.423 --> 00:21:00.503 what they need to do are a sentence or 2 and not very descriptive. 00:21:00.503 --> 00:21:03.903 And so if I'm not an EHS person, I don't know what that means. 00:21:04.193 --> 00:21:08.403 I don't necessarily know what I need to do to resolve, say, a safety hazard. 00:21:08.933 --> 00:21:12.793 , and with, with AI, what we're able to do is with a simple. 00:21:13.128 --> 00:21:18.598 A couple word prompt that the EHS person enters can supplement that with 00:21:18.648 --> 00:21:22.358 detailed implementation instructions, , for the folks out in the field 00:21:22.358 --> 00:21:23.588 who actually have to implement it. 00:21:23.598 --> 00:21:26.158 And so that's been a huge value driver. 00:21:26.158 --> 00:21:29.498 And one of our customers, that's exactly what they said is I see this 00:21:29.528 --> 00:21:34.158 valuable, to our team, to an extent, but we're already smart in this area. 00:21:34.618 --> 00:21:37.698 , but what they were most excited about, and this was a manufacturing 00:21:37.698 --> 00:21:40.058 company is just being able to. 00:21:40.438 --> 00:21:44.648 Educate and use the tool to enable everyone and not just 00:21:44.648 --> 00:21:48.498 those who have studied and trained and worked in EHS for decades. 00:21:49.306 --> 00:21:51.096 CJ: Yeah, I just think that's so cool, right? 00:21:51.096 --> 00:21:56.466 Like I just unlocking the ability for more people to, , access that knowledge, right. 00:21:56.466 --> 00:22:01.436 And to be able to utilize the platform for me, it's just, I think every process, 00:22:01.666 --> 00:22:04.106 , deserves that level of, , accessibility. 00:22:04.594 --> 00:22:04.934 Nathan: 100%. 00:22:04.934 --> 00:22:05.304 Yeah. 00:22:06.324 --> 00:22:09.114 Duke: So, , I imagine there's some people that are very, very 00:22:09.124 --> 00:22:11.234 interested in exploring this further. 00:22:11.628 --> 00:22:14.168 I know you have several different outcomes that you support, but do you 00:22:14.168 --> 00:22:19.308 have kind of a general idea of what the Serenity implementation looks like? 00:22:19.708 --> 00:22:20.838 Nathan: I can touch on that a little bit. 00:22:21.198 --> 00:22:25.308 , So being that we are a ServiceNow store partner, , we do have a 00:22:25.338 --> 00:22:26.938 traditional implementation model. 00:22:26.968 --> 00:22:32.308 So it would be really familiar to what large enterprises that already 00:22:32.548 --> 00:22:34.248 have a ServiceNow deployment. 00:22:34.248 --> 00:22:34.632 So. 00:22:34.813 --> 00:22:37.093 In line with what they have come to expect. 00:22:37.933 --> 00:22:41.613 And so our apps, they are available on the service now store. 00:22:42.243 --> 00:22:46.403 , we have an implementation team in house that works with our customers. 00:22:46.593 --> 00:22:49.693 , does workshops identifies if there's any configuration or 00:22:49.703 --> 00:22:51.293 customization needs to those apps. 00:22:52.163 --> 00:22:55.243 , and so we do have an in house implementation team for that. 00:22:55.573 --> 00:22:58.453 , a lot of really great service now experts on that team. 00:22:58.726 --> 00:23:01.774 but we are releasing quarterly to the service now store. 00:23:01.774 --> 00:23:05.054 And so, we are constantly enhancing, improving the product, 00:23:05.054 --> 00:23:06.774 making those releases available. 00:23:07.204 --> 00:23:10.844 , but like every other service now app, , the customer has full control 00:23:10.844 --> 00:23:14.344 on if they want to take an upgrade when they want to take that upgrade. 00:23:14.814 --> 00:23:16.784 , and so that, that is pretty standard. 00:23:17.218 --> 00:23:21.078 there is another implementation, , mechanism that, that is really 00:23:21.078 --> 00:23:23.958 new to us and it's something I'm personally really excited for. 00:23:24.488 --> 00:23:27.688 , and this one targets more of those midsize customers that we were talking about. 00:23:27.758 --> 00:23:31.328 for example, we have a waste management customer, , I think there are about a 00:23:31.328 --> 00:23:37.258 thousand employees, so smaller company, , they don't have service now, , But 00:23:37.258 --> 00:23:41.658 they are interested , in automating and, digitizing , their EHS program. 00:23:41.658 --> 00:23:45.868 And so what we have for them actually is, is something that we are 00:23:45.868 --> 00:23:47.608 referring to as Serenity Base Camp. 00:23:47.888 --> 00:23:51.938 , and that's a ServiceNow instance that, that we actually , are operating. 00:23:52.478 --> 00:23:54.728 , but we make that available to. 00:23:54.978 --> 00:23:55.758 Really anyone. 00:23:55.778 --> 00:24:00.898 So service now is not a kind of must have before talking to serenity. 00:24:00.898 --> 00:24:05.828 If, you're interested in serenity EHS and our capabilities, we have 00:24:05.828 --> 00:24:07.458 a mechanism to make that available. 00:24:08.098 --> 00:24:10.648 And so that's something I'm really excited about. 00:24:10.708 --> 00:24:10.868 , it's. 00:24:11.823 --> 00:24:12.573 It's live now. 00:24:12.573 --> 00:24:13.653 We have customers. 00:24:13.663 --> 00:24:16.203 It's also giving us the ability to do things like free trials. 00:24:16.413 --> 00:24:19.713 , , give folks access to the system and try it out for a period of time. 00:24:20.453 --> 00:24:23.563 , and within the coming weeks, we're actually going to get to a 00:24:23.563 --> 00:24:27.953 point where we can put a, put a sign up button on our website and 00:24:28.113 --> 00:24:30.433 anyone can come to SerenityEHS. 00:24:30.463 --> 00:24:30.863 com. 00:24:31.468 --> 00:24:35.198 Register and start using the product, , without, , having , to 00:24:35.198 --> 00:24:36.738 be a ServiceNow customer already. 00:24:37.408 --> 00:24:39.738 And so we have an option really for everyone. 00:24:39.748 --> 00:24:43.768 Most mature ServiceNow shops to, to the smaller shops that, don't have ServiceNow. 00:24:44.933 --> 00:24:46.493 , CJ: this one resonates a lot with me. 00:24:46.493 --> 00:24:49.213 I've had this idea of being able to do something like that on service 00:24:49.213 --> 00:24:52.663 now platform , for years now, and to hear you guys executing 00:24:52.663 --> 00:24:54.523 on it is just so mind blowing. 00:24:54.523 --> 00:24:58.403 I might hit you up later to talk to you about , how you accomplish that. 00:24:58.403 --> 00:25:00.023 But I just think it's great because. 00:25:00.438 --> 00:25:04.248 The ServiceNow platform shouldn't just be limited to folks to 00:25:04.248 --> 00:25:06.898 happen, to have , the luxury of having, signed up for it, right? 00:25:06.898 --> 00:25:10.808 Like when you, when you start to build apps that are this valuable, right, and 00:25:10.808 --> 00:25:13.068 this useful, it's great to be able to. 00:25:13.473 --> 00:25:14.983 You know, offer them to anyone, right? 00:25:14.983 --> 00:25:17.653 Folks, because they're folks who are using EHS might not 00:25:17.653 --> 00:25:19.183 necessarily be using service. 00:25:19.183 --> 00:25:23.242 Now, maybe they don't have, you know, a hugely mature, like, you 00:25:23.243 --> 00:25:26.433 know, , process and believe the EHS is their bread and butter. 00:25:26.753 --> 00:25:27.093 Right? 00:25:27.113 --> 00:25:29.163 And, , yeah, this is just amazing. 00:25:29.453 --> 00:25:30.173 It's this great. 00:25:30.478 --> 00:25:31.348 Nathan: we're really excited. 00:25:31.348 --> 00:25:34.528 I know this is where I get a little more kind of technically excited about things. 00:25:35.071 --> 00:25:39.031 , It allows us to, to experiment more, , with those kinds of customers so we can. 00:25:39.596 --> 00:25:43.286 Test out a new feature, , introduce it, get feedback quickly, make 00:25:43.286 --> 00:25:45.996 changes, , we're constantly updating that environment. 00:25:46.006 --> 00:25:47.696 So it's not a quarterly release cycle. 00:25:47.696 --> 00:25:50.726 It's a, as quickly as we need to release cycle. 00:25:51.116 --> 00:25:54.286 , so we learn a lot and can feed that back into the product. 00:25:54.481 --> 00:25:57.471 And it ultimately benefits our enterprise customers. 00:25:57.471 --> 00:26:01.761 And likewise, we can take feedback from our enterprise customers, , build 00:26:01.761 --> 00:26:06.821 those new features, release them to, to our, base camp customers, , and make 00:26:06.821 --> 00:26:09.441 sure that , they're right, , before we release them back to enterprise. 00:26:09.461 --> 00:26:13.011 So operationally, I'm really excited about what this, , base 00:26:13.011 --> 00:26:14.911 camp model really offers us. 00:26:15.181 --> 00:26:18.754 . And it is exciting because I'm, , there might be a service now partner out 00:26:18.754 --> 00:26:20.314 there that has done this already. 00:26:20.344 --> 00:26:21.754 , if so, I'm, I'm not aware of it. 00:26:21.764 --> 00:26:24.944 So I think , we're definitely charting some new waters with that model. 00:26:26.194 --> 00:26:28.404 CJ: that's, that's crazy, man, that's, I love it. 00:26:28.884 --> 00:26:29.254 I love 00:26:29.369 --> 00:26:29.909 Duke: well with it. 00:26:29.909 --> 00:26:33.553 I mean, earlier, you said you, you push it down market a bit, ? So 00:26:33.553 --> 00:26:38.723 that, , smaller organizations can get in on the big functional dreams. 00:26:38.723 --> 00:26:38.953 Right? 00:26:39.023 --> 00:26:43.683 But if you hear the fact that it's not only for smaller orgs, 00:26:43.723 --> 00:26:44.983 but orgs that wouldn't even. 00:26:45.618 --> 00:26:47.898 Naturally be part of the service ecosystem. 00:26:48.028 --> 00:26:50.998 And now it's like, bam, it's a service that you can consume. 00:26:50.998 --> 00:26:53.348 Just, that's really impressive. 00:26:53.838 --> 00:26:55.948 CJ: And it just highlights the functionality and 00:26:55.948 --> 00:26:57.178 the value of service now. 00:26:57.188 --> 00:26:57.528 Right? 00:26:57.528 --> 00:26:57.698 Like 00:26:57.758 --> 00:26:58.128 Duke: Right?, 00:26:59.148 --> 00:27:01.858 CJ: because for me, you build an app on service now and now you 00:27:01.858 --> 00:27:05.198 can, find customers who also happen to have the service now platform. 00:27:05.198 --> 00:27:05.358 Right. 00:27:05.358 --> 00:27:05.558 But. 00:27:05.973 --> 00:27:09.833 , now, if you can actually build on service now, utilize everything 00:27:09.833 --> 00:27:11.213 that the platform has, right? 00:27:11.213 --> 00:27:14.183 That you don't have to throw, you know, a ton of, , dollars into 00:27:14.183 --> 00:27:15.843 building everything from scratch. 00:27:16.153 --> 00:27:19.073 And then you can actually, acquire customers that exist 00:27:19.123 --> 00:27:21.953 outside of the service that he goes, that's a game changer. 00:27:22.503 --> 00:27:24.183 Like kudos to you guys. 00:27:24.193 --> 00:27:24.863 This is amazing. 00:27:24.863 --> 00:27:25.353 I love this. 00:27:27.989 --> 00:27:29.629 Peter: really nice to hear. 00:27:29.649 --> 00:27:32.159 We haven't really talked about it too much outside of the work. 00:27:32.219 --> 00:27:35.789 So to hear that level of excitement, it was just really affirming. 00:27:35.849 --> 00:27:37.409 So I definitely appreciate that. 00:27:37.469 --> 00:27:40.519 We're in the middle of making sure that we have it right. 00:27:40.709 --> 00:27:43.139 And we can deploy it to our customers. 00:27:43.649 --> 00:27:44.419 At scale. 00:27:44.494 --> 00:27:48.589 but so far with the handful of people who are using it, it's 00:27:48.589 --> 00:27:49.669 been working , really well. 00:27:49.749 --> 00:27:51.049 I gotta give props to the team. 00:27:51.049 --> 00:27:53.549 They've done a great job of implementing it. 00:27:53.789 --> 00:27:56.719 , and I'm, I'm very excited to see where this is in a couple of years. 00:27:56.749 --> 00:28:00.759 Once, once we scaled it up , and have a lot more customers on it, I think it. 00:28:01.204 --> 00:28:05.001 It does unlock the ServiceNow story for a lot more organizations. 00:28:05.716 --> 00:28:06.096 CJ: Right. 00:28:06.676 --> 00:28:07.326 Absolutely. 00:28:07.481 --> 00:28:07.541 Silence. 00:28:07.901 --> 00:28:10.471 Duke: if somebody was interested in investigating what you could offer 00:28:10.471 --> 00:28:12.826 them, or just wants to a deeper dive. 00:28:12.869 --> 00:28:13.799 how would they do that? 00:28:14.098 --> 00:28:17.267 Peter: I mean, obviously you can start with our website, which is www. 00:28:17.348 --> 00:28:17.808 SerenityEHS. 00:28:20.528 --> 00:28:20.928 com. 00:28:21.308 --> 00:28:24.368 , but you can reach out to us directly. 00:28:24.418 --> 00:28:27.528 , we also have, the co founder Chris leads up. 00:28:27.648 --> 00:28:28.268 , our sales team. 00:28:28.268 --> 00:28:31.868 So Chris Markham, , you know, you can look us up on LinkedIn 00:28:31.868 --> 00:28:33.368 or, or, email us directly. 00:28:33.368 --> 00:28:36.638 I think our emails are all our first name dot last name at training. 00:28:36.648 --> 00:28:37.028 EHS. 00:28:37.278 --> 00:28:37.558 com. 00:28:37.998 --> 00:28:42.544 Be happy to talk to people more about, if you need an EHS solution, we're happy 00:28:42.544 --> 00:28:46.004 to talk to you about it and take you through that path and talk about how. 00:28:46.504 --> 00:28:49.418 EHS can touch a lot of areas. 00:28:49.418 --> 00:28:52.998 So, , the story could be different depending on the industry, , depending 00:28:52.998 --> 00:28:54.338 on what your specific needs are. 00:28:54.338 --> 00:28:58.268 So happy to get into that and talk about how the platform can link to 00:28:58.268 --> 00:29:00.018 the outcomes you're trying to get to. 00:29:00.593 --> 00:29:03.953 Duke: We'll have links in the description below to all of those resources that 00:29:04.003 --> 00:29:06.353 peter described . So would the team. 00:29:06.449 --> 00:29:11.579 in the corporate political architecture be called the team, or would it be some 00:29:11.579 --> 00:29:14.969 subdiscipline of facilities or secure? 00:29:14.979 --> 00:29:15.339 Like, 00:29:15.799 --> 00:29:16.449 Peter: Yeah, I think 00:29:16.529 --> 00:29:17.529 Duke: did that fall in the org? 00:29:17.709 --> 00:29:20.709 Peter: That's a fairly variable, especially depending on , industry 00:29:20.709 --> 00:29:22.069 and size of organization. 00:29:22.129 --> 00:29:26.086 , it's like Nate mentioned earlier, it can be under HR, it can be under 00:29:26.236 --> 00:29:31.044 facilities, so we could just refer to it as Whichever team manages 00:29:31.094 --> 00:29:32.994 your health and safety, right? 00:29:33.218 --> 00:29:36.041 to be honest, like some of our solutions color outside the lines. 00:29:36.348 --> 00:29:38.838 so you might have an EHS team and a facilities team. 00:29:39.048 --> 00:29:41.608 And so like they have to work together. 00:29:41.608 --> 00:29:44.238 That's something that's actually come up a lot is EHS will assign 00:29:44.248 --> 00:29:46.088 things out to someone else. 00:29:46.088 --> 00:29:46.368 Right. 00:29:46.388 --> 00:29:46.858 So, 00:29:47.338 --> 00:29:51.438 Nathan: And most, most companies that have a health and safety team, the employees 00:29:51.438 --> 00:29:53.198 know there is a health and safety team. 00:29:53.198 --> 00:29:57.478 They, maybe don't know where it falls in , the executive org chart. 00:29:57.641 --> 00:29:59.991 But I think saying, contact your health and safety team. 00:30:00.261 --> 00:30:02.891 The organizations that have it, they know who that is. 00:30:03.279 --> 00:30:03.519 Duke: Right. 00:30:03.519 --> 00:30:04.789 We are at time. 00:30:05.084 --> 00:30:05.794 Peter and Nathan. 00:30:05.794 --> 00:30:09.354 I want to thank you both so much for coming and telling us about the exciting 00:30:09.354 --> 00:30:11.234 possibilities of EHS on service. 00:30:11.234 --> 00:30:16.254 Now, if you are a service now, product owner or architect or admin at a customer, 00:30:16.534 --> 00:30:19.464 and you want to set up a dragon to slay. 00:30:19.849 --> 00:30:23.669 And get all that glory, be sure to get in touch with your EHS teams 00:30:23.669 --> 00:30:27.889 internally, find out who manages your health and safety and, , just let them 00:30:27.889 --> 00:30:29.879 know you can send them to this podcast. 00:30:30.299 --> 00:30:32.279 You can send them to SobrenityEHS. 00:30:32.279 --> 00:30:36.259 com and, , just keep on delivering value with the ServiceNow platform. 00:30:37.427 --> 00:30:38.687 Peter: Hey, thank you so much for having us. 00:30:38.747 --> 00:30:39.697 Yeah, this was fantastic. 00:30:40.162 --> 00:30:40.712 Nathan: This was fun.