[Music] hi everyone welcome to glidefast on air i'm lauren jankowski the marketing manager here at glidefast and i'll be moderating today's webinar leveraging servicenow's software asset management professional to control i t spend and compliance today's presenters will be shane cooper a solutions consultant from glidefast will young a senior senior architect from glidefast and sarah butler a systems analyst from one oak before we get started i'd like to give you some background information on glidefast glidecast consulting is a consulting firm that is dedicated exclusively to servers now as an elite servicenow partner our expert team of developers and architects have worked on both sides of the table on the customer side and the consulting side our company was founded by servicenow architects and we're proud to have a team of over 100 experienced consultants an average csat score of a 9.6 and many accolades as you can see here we have multiple international association of it asset manager certifications including certified software asset manager and certified asset management professional i'll be monitoring the q a throughout today's session so please send in any questions as they arise and we'll do our best to answer them for you as another perk of attending today's webinar we'll be giving away a 50 visa gift card at the end we'll be announcing it at the end so make sure you stay on for the entire webinar now i'd like to hand things over to shane to dive in thanks lauren uh yeah so today uh we're gonna cover software asset management just to do an introduction into it for those of you who are not familiar with it i'm gonna go into detail on uh sam pro and then we'll get into uh what we did for one oak some of the accomplishments and the final solution and then one of lessons learned and then sam pro's never-ending story and we'll explain that when we get there so just to give you a little introduction on software asset management so most of the time people assume software asset management just involves the application or the technology for scanning software installed in an organization but in reality it's both that and a set of business practices for an organization to that supports the use of the software so these practices are used for things like customer satisfaction cost effectiveness risk reduction strategic planning and decision support software asset management is quickly becoming a requirement for many organizations both big and small and the software asset manager can utilize this to track licensing consumed they can compare it to the rights purchased as well as track and automate allocations for those licenses automation and self-service combined with proper business practices can streamline this whole process and nothing does that better than sam pro so i want to read this um there are studies done by gardner that state that most organizations go through at least three or more software audits a year and if you've been involved in an audit like that you understand the pain points a lot of that comes from data that is not really concise or consolidated and it makes it difficult for gathering this information for the audits servicenow and sampro does a great job of putting everything into a nice neat location and i kind of want to go over some of the main uh functionality behind sampro the sam pro allows you to normalize software assets um after you get your discovery source set up it's capable of normalizing the data together and what that means is it can take all of your individual names brought in from your discovery source and match them with publishers and products and this makes the data more readable easier to account for and it uh it also allows you to group everything together for licensing consumption later on servicenow provides content packs to go along with this to make normalization a lot easier servicenow also offers uh you to leverage publisher packs so it's not uncommon for different publishers to use different licensing models just think of adobe or citrix or microsoft for that matter it can make it really difficult for tracking license usage whenever you have all of these different licensing types in addition to the content packs these publisher packs make it a lot easier to group these different licenses together and it's not more apparent than whenever you view the publisher dashboard you can actually see all of these licensing organized in the way that they should be to make it easier to view and so this also allows you to take action on your license position so the license workbench is a great place to view license compliance you can view your different publishers of all of the software that you have installed you can dig down into the publishers and then you can see your software models and your products and you can see your compliance your unallocated uses allocated uses installations it's a great place to be able to narrow down what is compliant and what isn't as far as your license installation another feature that is very widely used is your is the ability to import your organization's entitlement data so whether you had a previous software asset management application or if you were tracking this via spreadsheets there's a template that servicenow offers that allows you to put all of your data into that template and then import all that data bulk into sampro it will the import will create software entitlements and software models at the same time as the import so having all that data in the same place allows you to really utilize uh the functionalities to detect uh software spend and after importing all of this data in there you can import your financial transaction data and this allows you to track analyze and optimize software spending so this function singles out expenditures that are specifically software purchases and so you can narrow down all the expenses based around a single publisher or product so this is just some of the base functionality in sam pro and having all this information in an easy to get location can make audits like we mentioned earlier a lot more a lot more painless so with a little customization the sky really is the limit for what sam pro can offer and to discuss that further i'm going to let will talk about what we did for one oak thanks shane as mentioned i was the primary implementation specialist for one oak and we were able to deploy a fairly unique solution that covers the whole life cycle of software asset management software asset management professional the plugin and servicenow contains a lot of functionality but there are some additional things that will really make that entire process come together on the left side we talk a little bit here about the sam implementation that we did and a lot of that is the baseline implementation that you get from many partners configuring the software asset management professional plugin making sure that the publisher packs are enabled and configured correctly setting up the integration with the microsoft sccm system to pull in the software installation data and usage data pretty standard steps for most implementations additionally we configured the client the client software delivery i always messed that one up which allows us to work with sccm and push and pull software from people's machines we also configured the contracts module to allow them to track their contracts as they're associated with the software whether that's a maintenance contract or some sort of additional agreement that goes along with that software and all of that's part of a fairly base cmp implementation but we wanted to go a little bit beyond that and give them some automation functionality that would help save some time so we implemented reusable catalog workflows that are easy for the software asset manager to configure and gave that standardized process for people who are requesting software we also set up an integration with their active directory because they use active directory to control and list some of the software accesses that were already in their environment we also integrated with their purchase order system so that licenses can be procured automatically as the user is requesting those items and there may not be licenses available additionally we created a license renewal workflow that automates a lot of the tasks that the software asset management team was working on to do those renewals saving them steps that they would have to do in multiple different records across the system of course we addressed the entitlements and allocations as well by performing the bulk load that shane was talking about in addition we created some custom functionality for bulk loading their allocation something that was missing from the baseline platform and servicenow also there was a subscription table for those of you who are familiar with servicenow two different ways of measuring our software usage the subscriptions or the installations and if we don't have an api for the subscription data it was difficult to track how the subscriptions were actually being used so we created the subscription records from those catalog items so that we could track those subscription softwares that don't have the api and i have an asterisk here for you for those of you who have upgraded to the newest version and are in orlando that's actually no longer a necessary step because they've allowed you to create allocations for subscription products whereas before that wasn't a capability so all of this really kind of comes together to fill in that whole life cycle picture of software asset management starting at the top looking at our request phase of the life cycle we implemented a self-service software catalog which you've probably seen in different demonstrations but one thing that was really unique is that we also needed to include socks compliant approvals if you have worked with socks regulations you understand how difficult it can be to make sure that you're meeting the appropriate levels of separation of duty and all of the different requirements around socks and recording what's necessary for that and so we made sure that their request process included those particular requirements for those regulations on the fulfillment side we put in automation that would allow us to trigger the procurement process when we determined that there were no licenses available to assign out to the user so when a user requests an item it does a check to see not only what do we have purchased and what do we have allocated but also what do we have installed on people's computers we want to make sure that we're never going over what we've purchased so that we're not exposing ourselves to potential risk and so the process that we built for them considers all of those different factors and data points when making a decision about whether to move into the procurement process in addition we set up dynamic generation of the fulfillment tasks and notifications so that all of the teams who work with the software asset management process both inside servicenow and outside servicenow could remain connected about the process and know what steps they needed to take next in the deployment phase of the life cycle we'd have the integration with active directory and that active directory setup also triggers their sccm and that sccm of course delivering software and in some cases we're also granting access to applications based on the integrations that were in place for their active directory one of my favorite features that we implemented for them as well is to educate the requester after their request has been fulfilled we will send them an automated email that includes applicable knowledge next steps or anything that they may need to know that gets pre-defined by the software manager and automatically send out as the user moves through the process of requesting our software in the reconciliation phase we're again trying to save steps trying to save time and really make it a simple process for both the people who are fulfilling and the people who are requesting so our automation creates the needle entitlements allocations and contract records that are going to be necessary from these previous steps after we've triggered procurement we need to make sure that we're recording all the financial data and the number of licenses and the type of licenses we tie that into the original request so we know which requested item it came from who was the requester and we can create the allocation out to that specific requester and then we have the traceability all the way through of where did this originate who approved it where was it fulfilled what was the dollar amount and that whole visibility is really providing a great value moving into the service section of our life cycle we establish reclamation rules to manage that software harvesting and those reclamation rules are fairly baseline functionality within servicenow but we identify that it's really important not to uninstall software from people who are vip level that may need software or may not use it in the same manner as other employees and so we actually added to the servicenow baseline configuration to build in exceptions for certain roles or certain people so that we're not causing any issues with those vips and then of course we use automation to assist with those enterprise software and contract renewals really something that is normally a more of a manual process opening up the records changing the dates creating new records migrating between the different records we wanted to save some time there and so we automated those steps as well um let me move on to the retirement phase and talk a little bit about what we were able to implement there as well one thing that we wanted to do is identify the terminated employees to make sure that we are managing the records for them as well one thing that we see a lot is employees will leave the company or move on to different roles in the company and it can take some time for the desktop teams to be able to clear out the computer to perform the reformat and sometimes those records sit and wait even though they're not being used and the user doesn't have access to that software the system still has the record that says that they have access to it so we identified their existing retirement workflow and we were able to piggyback onto that workflow and use that to update the records for those user computers and the software that was installed to make sure that that inventory and that deployment record is always correct and always trued up to what is actually in the environment we also are managing the software models to identify the software that's passed its lifecycle onenote was very conscientious about the versioning of the software that they're using and making sure that users have the appropriate version and they can use now the life cycle both what's provided by the publisher of the software and their internal life cycles to make sure that they are aligning to what needs to happen with the different versions so all of this together one big picture was it able to really set the 10 software managers free to to really deliver the service instead of worrying about the daily operations so for those of you again familiar with the platform you're aware that the software model is really the heart of software asset management and using some of the automation within the platform and some manual pieces to manage the software they were able to create just over 2 000 software models that are managed within their environment so those could be subscription-based software engineering-based software installed software but over 2 000 models now that they're able to manage with after asset management using those models they then move into that catalog request where they can have people come in and request the titles that they're looking for so they have a 48 item checklist for those catalog items when building them to make sure that they're complete and ready for the automation and ready for the delivery to the end user so things like making sure that they're entitlements making sure that there are allocations making sure that all of the relevant fields are filled out the knowledge articles the deployment groups getting all of those pieces together has now become a regular checklist for them that they can go through and make sure that everything's ready to go into those catalog items they've built 34 active catalog items which allow them to completely automate this life cycle so somebody can go in and request it and and not have to have the software asset manager going in and touching each request and validating each request and manually moving it through each of these phases for each of these 34 catalog items and they did this in a couple different phases we had our initial deployment and spent about six months doing our initial configurations and loading all of those different pieces and making sure everything looked good and reconciliation was working and then took on additional phases with additional business partners and finding those organizations and products that were high volume or high impact or high dollar amount that we're really going to save the company time and effort and because of that they've now had over 1200 requests go through this process but again they're not having to touch manually they're not having to review every single time they go through and that's allowed them to get an average close time now of four hours which if you understand the complete life cycle of the software you're probably a little bit surprised by that short amount of time that's from when the user requests it to when it's been delivered to the user on their desktop often being pushed directly to their computer they're ready to go and that process sometimes could take uh you know days and weeks to complete because of all the approvals and the steps and having to call procurement and you know going through all of those processes that used to be manual they used to have a much much higher time and now they've been able to expedite it and and basically a completely automated process in that four hours uh accepting of course your approvals and things like that they've also used the automation that we built to do 21 software renewals and if you've been through a software renewal those are very cumbersome often having to go through the contracts and identify is this the right license type do we have the right number are we increasing our accounts or decreasing our accounts are we going to change the licensing type to maybe get a better deal or a better value and so the automated catalog process that we built for their software asset manager allows them to go in and specify some of those details and let the system do all of the back end work that's necessary for those renewals so sarah can go in and attach her quote and fill in the details of of what she needs changed i am going to need a total of 1200 licenses and i need these license metrics and i'm going to extend my existing contract and the system will automatically go in and do all those steps for her and again taking the time for her to deliver that service really reducing it so that she can focus on more of her daily operations and less of the system data input type of activities that she was doing before we talked a little bit as well about the reclamation candidates and how the system is able to identify low usage software and using their rules which the most common rule that they use is a 90 day we are generating those records and then using those about 149 reclamation candidates now the installations that aren't being used they have recovered about 120 000 in unused licenses so just setting up the system and configuring it to their particular requirements um really a cost avoidance there and a reclamation of 120 000 which is i think a pretty great return on investment for them but it's not always perfect there's a lot of lessons that need to be learned there are always challenges that need to be faced when doing any sort of a deployment any sort of automation and one oak had some great lessons learned we had some growing experiences and and wanted to share these with you in hopes that these would help you in any of your software projects so if you've been around servicenow for very long you'll know that servicenow's software asset management has really grown over the last couple years so when you implement it it can pose some challenges depending on your current environment one of the things that we discovered was the dependency on discovery a lot of people don't know that for some software products particularly things like sql or citrix some of those more complicated enterprise type products really require discovery they're not like your desktop software where you can just get a list of everything that's installed and you can just count those installations and everything goes well we identified that discovery was necessary and even though one oak had been using discovery we had not identified that they were using the probes which are the old version of discovery and software asset management is very heavily dependent on you using the most current version of discovery which is patterns so as we move through the process we identified that they didn't have those patterns running and we had to engage with servicenow and bring in some of the specialists that glidefast to migrate them from the probes to the patterns to make sure that the count the consumption the dashboards all those pieces that are dependent on discovery for certain products were really in place and ready to go so sarah if you want to go ahead and pick it up from here i covered number one perfect so we will jump into number two so part of the implementation that we had as what a draw for sam pro was for me is the ability of the publisher packs and the api functionality so we were able to pull those subscriptions into our sampro instance and as we were trying to create all of our entitlements and licensing for our adobe products we found out that the api from our creative cloud portal would not pull all of our subscription users back into sam pro and after working with live fast partnering with servicenow and we found out that adobe actually has a process where you have to have an enterprise level account in order to utilize the api we just had a clp level and so the api would never work and so we were able to identify and help servicenow add some additional documentation that the licensing tier and the licensing that you might have with a particular vendor could affect these apis that servicenow has set up so they have the ability but depending on what you're actually entitled to may limit if you could use that api functionality um a third thing that we i wanted to highlight as a lessons learned is there are several licensed metrics types that are not available in sam pro currently and so the days of her device and per user are slowly dwindling and we have with our company being within the midstream gas company we have a lot of engineering applications that have concurrent licensing and so out of the box sam pro does not have a license metric for concurrent we have some applications that are licensed per work permit and so those are not drop down items that i can select when i want to create an entitlement and i want to make that entitlement of what we're actually licensed for and so we had to partner with blindcast again and create some some custom license metrics but i just wanted to point this out as all of your entitlements may not match exactly and so i've reached back out to servicenow i've asked for different licensing metric types to be added in future releases and then we kind of create some custom ones so just a point of caution as you guys are implementing or thinking about implementing um sam pro and sarah i would just add to that there's been a recent release with servicenow where they actually have an engineering license manager that works with openlm so some of those engineering applications that previously weren't supported and partly thanks to feedback from clients like you servicenow was able to add in very similar to like a publisher pack functionality where now they're starting to be able to measure those types of things the concurrent licenses network licenses and things so it's really important that not only servicenow gets your feedback as you're working through these license metric issues but that you keep up to date and that you have a partner who understands the changes that are coming to help make sure that you're aligning to those different license metrics absolutely so number four contracts and renewals so as well alluded to in the beginning uh contracts were an important piece for me so this is what i use to track maintenance renewals and i use that to look at our spend year over year are they increasing per our contract and is maintenance gone down and so really like to just look at those year over year as we're doing our renewals so as part of cmro the contracts module um had to be configured as well and so a big piece that i i wanted glidefast to help us with is that i can process the renewal through appropriate workflows so if i'm changing license types or if it's a subscription versus a perpetual renewal i wanted to create a workflow that i could put those in that would flow to our procurement team that would then update my entitlements as well as create a new contract for me to manage throughout that year of that renewal and so that is not a baseline functionality of sam pro and so that is a contract module does have to be configured and then we did have to build that specific workflow for my renewals and you might have simple renewals where it's just you're renewing the same license again price did not change or you're going to have your more complex we might be a per user license and we need to move to concurrent so they built that workflow to handle those different types of situations so just one to highlight that that's not something out of the box but that it can be created in working with an implementation partner and then lastly i wanted to highlight the um kind of your continued continued growth as you go through sam pro so we implemented sam pro with the london instance and we've since upgraded to new york and so i just wanted to highlight and encourage anybody that's out there thinking about implementing sampro or software management platform that you partner with servicenow you partner with an implementation partner to help with those upgrades so we found out that as sam pro advances and they're constantly making updates because it was a fairly new product it's only a couple years old and feedback that we're giving them they're putting those fixes into the releases and so a lot of the configurations that glidefast even helped us with when we implemented last year those changes have already been taken into account in the new release of new york that we're in and so some of the functionality and some of the configurations we had we've had to go back and kind of revert and adjust and so really looking at those upgrade plans those maps the enhancements what's coming out and partnering with servicenow if any help is needed to do those upgrades and perform them as well as glide fast or an implementation partner of your choice to help kind of note what did we have to do after this upgrade what testing do we need to do for the next one and then really lean on them and leverage them to help get through those updates because they're going to add continued functionality and something that you may have had to configure a certain way because that functionality wasn't available it could be available in the next release and so really just want to highlight that you're partnering with your implementation partner you're documenting and you're understanding what new functionality is there so you guys can have the best experience during an upgrade absolutely sarah and i would just add to that it's important the partner that you pick um not all partners are created equal so getting somebody that's an elite partner that's tied in lockstep with servicenow i can tell you personally i've had me servicenow to review the roadmaps to make sure that our customers are prepared so that we know the functionality is coming and can prepare our customers for it really important to find the partner that's really tuned in to software and what's coming down the road absolutely and 0.5 leads us perfectly into sampro's never ending story i think one of the main points that we wanted to get across with this is that your software asset management process should not end after implementation i mean your organization's uh requirements are always changing uh you'll have different software different vendors and so on so what you've implemented two years ago or even maybe even two weeks ago may not be what you need right this moment so a lot of that can be involved in handling new software or new vendors or you have new departments that pop up within your organization new business requirements and so as these items come up so new software for example um if a new piece of software comes in you have to handle uh you have to create the model itself you have to handle discovery of the pro the installation entitlements allocations of it product updates and then also on the vendor side of things some vendors allow capabilities to tie into the system and add allocations and entitlements from their end and so as you change vendors these things might come up as well and so reevaluation is key throughout this whole process and not just from the technology side of things but also within your organization your department heads or your application owners more than likely will know more about the software and their usage of the software than the software asset manager will and so a good plan is to have ongoing meetings to evaluate this software with these key players and going along with that they can also help you understand the license utilization and how they have split things apart for on-prem and cloud and so pulling in the the right people into these meetings and having these ongoing evaluations play a big role in a clean software asset management process so throughout this whole process of gathering usage information reconciling licensing updating policies and procedures you can work out with your organization to achieve a successful software asset management process so i'm going to end us there awesome and it looks like it's time to um dive into some of the questions that are coming through um so we could start off with this one what are socks applications and how do they differ from regular applications yeah sarah do you want to answer that one for us since you're most familiar with that um socks applications are a set of applications sarbanes-oxley so really they're around financial applications and they are they are held to a more regulated and under a microscope so you have to be in compliance and not only do we have internal audit that looks at that but we have external companies that have to make sure that we understand who has access to that application that the approver is also not the person that granted that access to that application and then we have quarterly attestation so we're going through we're making sure that everybody that has access was approved if somebody has left the company we're pulling back that information we're making sure we're updating those roles and just to maintain that strict compliance with those financial type applications awesome um here's another one that came through when you migrate from one entitlement to a renewed entitlement is there a way to move the allocations too i'm glad that you asked that i get that question quite a lot and it's something that we were able to to build for sarah and the 100 team but unfortunately is not available in the baseline platform if you're familiar with the structure and service now the entitlement being the record of what you've purchased from your vendor that the company has a right to use and then the allocation is the internal distribution of that license which users or which computers are supposed to have that software and when you move from one entitlement to another in the case of a new entitlement those allocations are still tied to your original entitlement there's not an automated way where you can just press a button to say move all of these allocations over to my new renewed entitlement so that's a process that we had to work on and add a customization that we did in the one oak instance that i think has been really beneficial to sarah and looking at the you know how much time it was taking her to do those individual allocations um so no at the answer that question is no there's not a built-in way to do that but with a little bit of development it's something that you could easily accomplish yeah and it's absolutely saving a lot of time on my end for sure awesome we just had another one come in um when harvesting software is it sccm that removes the software or is it servicenow some of these questions make me laugh and i'm sure sarah's chuckling a little bit too because this is one of the misconceptions that we deal with a lot in software asset management the orchestration capability in servicenow often people look at that as the ability to uninstall software i can send a command to a device and have it perform a software uninstalled but that's not really the design behind software asset management it does use the sccm integration and more specifically it's the csd the client software delivery integration that allows you to add users to collections in sccm remove users from collections in sccm and that's the best way to do this so servicenow does not want to be the platform that is performing those software actions there are specific tools sccm is the tool that is purpose-built to manage software on windows devices so servicenow just wants to work with that application and trigger those actions to happen in those external systems not be the system that's doing itself you can imagine the security concerns that would happen if servicenow as a cloud-based platform can execute code on a windows desktop anywhere in your environment so again short answer that question summing it up servicenow triggers sdcm to perform the software installs and uninstalls but is not doing the actual steps uh in the platform awesome thanks will um it looks like we have two more questions what's a typical next step or phase after the initial implementation um sarah do you want to talk to us a little bit about your evolution i talked a little bit about how you know we started back in january 2019 and spent about six months getting the initial setup configuration done you want to talk a little bit about what happened after that yeah thank you so we initially started with the five publisher packs that we'll talked about at the beginning so we really wanted to dig into those list all of those entitlements and that would that was kind of our phase one so we have built out all of our entitlements for those top five publishers some of those did have outward facing catalog items that users could go through and benefit from the sam pro workflow but some of those are just internal they would never be a user-facing application so next steps is starting to look at and building out your software models which is basically your catalog and your your portfolio of what software your company owns and then you really start at different phases and our second phase we looked at those stocks applications and we started to tackle those so the same way that we did the top five publishers you're going to gather the information you're going to build your software models you're going to use your checklist you're going to partner with the application owners to create the catalog item and then you're going to apply that workflow so that was phase two we worked on the socks applications and so now we're moving on and we're looking at what are some of the highly requested desktop type applications do we need to look at the next group of maybe our gas measurement and what set of applications do they use and so i know that you guys have heard time and again you know start slow and start with you know a handful of publishers and so that's what we did we tackled the the top five publisher packs then we moved on to stocks and so now we're looking at those highly utilized applications and some people may look at spend and so you really just have to start the process over again so you're going to build up your model you're going to build out your catalog items you're going to apply your workflow you're going to do your contracts and so you just kind of repeat that process over and over and as you start to build those catalog items and that automated workflow your ticket load that you had previously will start to decrease and so you can you know spend more time in the tool and feeding the tool adding those models in adding that contract information and then continuing to build up that software portfolio great thank you sarah looks like we have one more question that we can get to do you have to use the contracts module to track your maintenance dates i'm glad you asked that question um there has been some changes in servicenow recently even from when we are implementing with sarah and one of those things is that on the actual entitlement itself now they're able to track maintenance as its own dates and its own um own information not as a separate record um and there are some some benefits of doing it different ways but uh i'll just say before i hand over to sarah a little bit um you can do some maintenance tracking on the entitlement itself particularly with the perpetual plus maintenance metric or some of the other microsoft type metrics but it really doesn't give you uh the same kind of full picture as you do when you use the contracts module sarah any thoughts yeah absolutely so on the subscription entitlement you do have the ability to list here's my start date and my end date and then the same thing that will mention for the perpetual with the maintenance so here's my maintenance date from here to here but that is inside of the software model inside the entitlement record so that's a couple layers down i like the benefit of using the contracts module just because i could easily filter for a particular application and it will pull all of those records up for me so it'll show year after year it'll show me my dates it'll show me my spin so i can see if it's increasing or if i decrease because maybe i drop some licenses off so the contract module just gives me an easy quick view and you're still adding those dates and those time frames and the cost on the entitlement but with the contracts it's just a quick easy view and then you link the two together and the automation that we've built for sarah those things automatically on the back end uh i think has been a real time saver and still allows you to have that rich data really just kind of that extra step beyond just tracking your basic dates and your basic information and even though the 10 team has a separate repository for contracts the actual terms and conditions and the executed you know pdfs and signatures and all of that this just allows sarah to have the visibility in servicenow of those longer arching contracts right i mean they cover multiple years multiple renewals multiple entitlements there may be terms or dollar amounts or things that change that are more difficult to do just on the entitlement so i think having those things together and bringing them into one system is really added to what one oak is able to do yeah it's really cut down on one of my documentation time that i had previously so i can issue a renewal through the renewal workflow now and it's going to automatically create my new entitlement it's going to automatically create my contract with the start and end dates the cost the purchase order the request item where i was manually doing all of that before so that workflow has been a great time saver and it helps keep everything documented well it looks like that's all the time we have for questions today so now i'd like to move on and announce the winner of our 50 visa gift card giveaway and it looks like the winner is jane young congratulations we'll be emailing your prize to you um directly after this webinar i'd like to thank everyone for attending today's webinar we hope you found it super insightful and feel free to reach out the reach out to the glidefast team or will or shane um their emails are their first dot last name at glidefast.com and i'd also like to give a huge huge thank you to sarah butler from one oak for being a guest speaker on today's webinar it was awesome hearing um your experience through your sampro implementation thank you everyone and we hope to see you on future webinars [Music] [Applause]