Session Information:

Reduce your RPA TCO: Two Simple Principles to Drive Down Costs and Maximize ROI

The total cost of ownership (TCO) for RPA is cannibalizing its own ROI, essentially turning the business case for automation upside-down. A major contributor to this problem is the inflated costs associated with RPA Development, Deployment, Maintenance, and Support — components that make up a whopping 65% of RPA’s TCO. Without the right design, governance, and change management principles, these costs can quickly spiral out of control and outstrip the returns you see from automation. However, by making some simple shifts to how you design, communicate, and manage your RPA program, you can radically reduce your TCO and maximize the ROI on your investment.

In this webinar Matt Dodgson, Head of Global Solution Engineering at Blueprint, will break down:

• Which RPA cost components are driving up your total cost of ownership.
• How to visualize your RPA TCO to identify where costs may be creeping above budget.
• Simple design and planning principles that will dramatically lower the costs of RPA development and deployment.
• How to improve RPA governance and change management to reduce maintenance and support costs so you can get more from your investment.

Session Transcript:

Thank you, everyone, for joining today. We look forward to taking guys through our discussion today, which is, we're really going to be talking about maximizing your RPA RPO. Really simple principles that we're gonna help you reduce your total cost of ownership around your RPA programs and automation.

Just to restate some of the housekeeping things that just given, getting to know more contexts. Again, throw any questions you have. The question box went to them at the end. We'll share a copy with this webinar, a recording of this, obviously, with all registrants at the end, and just so everyone's aware, you guys are on mute.

Feel free to enjoy a snack or some coffee while you are taking today.

So we're gonna take you guys through a little bit of an overview of what we'll pretend we're going to talk about, really the costs of RPA.

You know, we're gonna give you a little bit more context then we're going to jump right into today's topic and break down what the cost of ownership looks like. And then we're going to show you a little bit about how blueprint enables our pain initiatives to lower these big costs in a live demo.

And for take any questions that you might have at the presentation.

That's Bruna mentioned, my name is Matthew Dodgson, I want to just give you guys a quick introduction. I head up the Global solutions Engineering team here at Blueprint Software systems. You know, I support the delivery of Blueprints Enterprise Automation Suite, which is this modern solution I'm going to show you guys today, are scaling process automations initiatives and really bringing them up to the enterprise. I've been working in the industry for quite some time, but with Blueprint for almost 10 years.

I'm very passionate working with no fellow people that are in the space, with our customers and our prospects, and I look forward to sharing with you guys some of those details today.

So, to give you some more context of who we are, we're Blueprint are a leading provider of digital process, design, and management solutions to Fortune one thousand organizations. Know, we work with global leaders from every industry, and they're using our cloud based platform.

The Enterprise Automation Suite, in Tandem with their RPA platforms to really identify, design and manage high value automations with precision ease by creating what we call digital blueprints.

Now, creating digital blueprints replaces the need to create time consuming, error prone documents, like PDFs, for example. And it drives both quality and efficiency at numerous points along the automation workflow.

This enables our customers to spend less time designing, managing, or fixing automations it really more time on things that directly grow their business. So, what do we mean when we say, they use this alongside their RPA tool to identify design and manage these automations.

At the heart of our, of the of our platform is what we call a digital blueprint and a digital blueprint. Digital blueprint themselves are much more than just the idea of a process model.

They contain everything you need to efficiently and effectively deliver high quality automations, including the detailed process flows.

All of those dependencies related to the systems or compliance regulations, functional and non functional requirements, things like user stories, acceptance tests, functional tests, and even specific implementation details that are directly integrated.

All into your RPA platform using the Blueprint platform. And our digital blueprints has many benefits, including having all assets and stakeholders in one central platform, which really streamlines workflows improves alignment. So you can move your projects forward with speed and precision.

We have intelligent modeling and assistance built into Blueprint and integrations that make it faster and easier to design and build automated processes while also improving the quality of those processes.

And our enterprise analytics and dashboarding, which helps you prioritize and measure what's working, manage, change practically and really sharpen and scale your strategy across your organization.

Now let's jump into exactly what we wanted to cover today.

Now we all know why RPA is at the top of the hype cycle.

And why so many organizations are aggressively adopting it and trying to scale.

So we won't get into the weeds of those details.

You guys are all very familiar and well aware of that.

But just, as we all know how RPA can be so impactful And beneficial. We also know that everything isn't as perfect as it seems.

The reality, is that RPA projects are struggling to capture the value they expected.

In a report, by E Y, 50% of RPA projects are failing to meet their objectives.

In another study, by Deloitte, only, 3% of organizations have been able to scale their RPA initiatives.

Now something that's contributing to those challenges, and the inability to capture the maximum value that RPA offers, is RPS total cost of ownership.

Here's the business case for RPA at its most basic, the returns of automation, in the form of the productivity, quality, and cost savings. Should by enlarge dramatically and drastically outweigh arkady total cost of ownership.

But, the business case is actually being turned upside down because of RFK is total cost of ownership, spiraling, out of control for a lot of programs.

And there's a few reasons why costs are being are being inflated, and we're gonna get into that for you guys.

But first, let's take it, look at the different cost components that contribute to the overhead.

Quantifying an exact price for the total cost of ownership of RPA is a challenging exercise.

There are lots of variables to consider, like the different prices of licensing.

Of our for our pay tools, the use of external providers, like business process outsourcing. And for the purpose of this webinar, we're going to keep things simple and look at the cost of one bot according to Universal according to universe components that every our pay program seats.

So according to Deloitte, a single bot tends to consume somewhere between $20,000.

That number is actually closer to 15,000.

When you count, when you account for all the elements that contribute to the total cost of ownership of one bought, which include a licensing for all your users, the training, all your stakeholders, The training, all your stakeholders on how to use the RPA tools, the infrastructure need to deliver and scale the automation, like cloud delivery models and virtual desktops for your bots.

The add on tools for your automation tool chain, like process discovery tools, or even blueprint that improve the life cycle of your bots, and quality quality, quality of your RPA initiatives.

The use of consultants, consultancy, and professional services to help you with implementation.

The cost of employing professionals to develop and deploy the actual automated processes of bots and arguably the most underrated cost of any RPA program is the effort needed to maintain and support your automated processes, especially when they break, which they do.

So, obviously, those cost components don't carry the same weight.

This graphic is a rough breakdown of how, how much each cost each component contributes to the total cost of ownership for RPA.

Now, I should also note that this breakdown is for unintended bots, which deliver the most value for automations. The cost for attend bots would be very different with licensing, probably being the largest cost contributor, because developing and deploying and maintaining attendant bots is the simpler, less, complex, less complex practice.

You'll probably notice this, you'll probably notice it's in the previous graphic, but pooling the smaller components together, makes it obvious at the most expensive components, by far, our development and deployment, and maintenance and support.

Coincidentally, it's these two components therapy program they're struggling with the most, causing the cost of ownership to inflate to the point where it lowers RFPs, return on investment.

Well, now, what's causing these two areas to spiral out of control in terms of cost me boil down the following.

For development and deployment, RPA has regressed in terms of technology delivered.

The most common way for automation designed to be communicated to RPA developers, is by packaging it in a slow, error prone, manual, paper based document, like P.v.d. or Process Design Doc.

Complex technology isn't designed on paper.

Purpose built systems with the granularity needed granularity needed to build sophisticated solutions are required, in RPA is no exception.

Documents like ..., called slower development and increase the likelihood of error, which only drives up the total cost of ownership.

The ironic part, too is that we are building automations in the most manual way possible, and ultimately, they also lead to missed requirements which produce fragile bots that break more often, eating away at the business value arc is supposed to deliver.

Now, for maintenance and support, in the rush to automate, whether it was to respond to the economic challenges the pandemic caused, or simply leveraged the benefits, Barb K, The benefits RFK offered.

Organizations are now picking up the pieces from constant RPA, break fix cycles, bot errors, and the RPA downtime that follows, leading to a pretty damaging synergy, low ROI, the inability to scale, and a high total cost of ownership.

Like we mentioned at the beginning of this webinar, there is a simple design planning, a governance, there is, there are simple design, planning, and governance principles that are key stakeholders can implement right away to reduce these two heavy cost components that radically lower our case total cost of ownership while maximizing their returns. And that's exactly what we're going to show you right now.

The burden of high RPM maintenance support has been a major contributor that is both increase RPS total cost of ownership and cause our paid programs to under deliver.

To give you a loose frame of reference, if you're running 20 bots, the average number of break fix cycles, an effort needed to maintain and support those bots, and cost upwards of $400,000 in business value lost.

Lowering this burden that's driving lowering this burden that's driving up the RPA costs and not allowing orgs to scale and deliver the ROI that was expected, is very much possible by improving these three areas of your RPA practice.

Improved dependency mapping, proactive change management and increased alignment.

Zeroing in on dependency mapping.

RPA is essentially a technology that's built on top of other technologies.

In fact, the most common reasons bots break are due to system changes, like an update to Salesforce, that changes fields in the UI, for example, expiring credentials, which looks which locks the process out of a system it interacts with.

So, that takes it down, and business changes. Like the finance team, updating a template they use, or change the currency They support causing a bot to break.

When the dependencies an automated process has, are not precisely mapped and explicit, it's difficult to control the cost of this RPA component.

Because when a bot experiences an error, it's not only sitting idle and not delivering business value. But a full-time employee has to also spend time looking for the root cause of that error. By examining the code, repairing it, testing it, and then redeploying the automated process.

Each automated process and even granular process steps must be connected to these legacy systems, the business rules and the regulations which they have a dependency to better manage change.

Which brings us to our next point: Change is constant in any organization industry.

Many RFK programs are still managing change in a reactive manner.

Now, what I mean by this, is that there's no preventive action, Corrective actions, corrective action is only triggered when botts throw errors.

This type of reactive approach only increases the RPA downtime, and it really drives up that total cost of ownership.

Proactive change management is only enabled when better dependency mapping patterns, when bots are meticulously linked to all their legacy systems, rules and regulations that they're connected with they're connected to.

With, with better dependency mapping, you also get the ability to identify and visualize the impact of change. So a corrective action can be taken before the bot fails and needs hours and hours of diagnostic work.

Unsustainable, RFK, maintenance and support is also by far.

It's also a byproduct of siloed automation design and planning.

For RP programs to control the cost of maintenance and support, all stakeholders need to be able to collaborate easily in a centralized RPA design and planning environment.

Siloed! disconnected tools, like e-mail for discussions, some type of process editor for design and definition, and then the ... tool itself, Where visibility is lost, just won't cut it.

You need a holistic tool that centralizes your RPA design and planning and execution and it really prioritizes the visibility to all stakeholders. And this is, this is a must.

So that brings us to RPA development.

That brings us to RPA, development, and deployment, which is by far the most expensive component of our pais total cost of ownership, which is normal because it accounts for all the resources needed to build, deploy, and monitor bots.

Now the reason it's ballooning, the total cost of ownership is because as we mentioned earlier, RP has seemingly taking a step backwards in technology delivery.

The high cost of RPA development and deployment can be significantly decreased with a better digital way of packaging and communicating automation work.

A way that prioritizes development by delivering the precise guidance and context developers need to build high quality botts the first time.

Fortunately, that's something Blueprint can do for you today.

So, now, let's jump into Blueprints Enterprise Automation Suite and see how our solution precisely helps you lower Europe key maintenance, support development and deployment while producing higher quality automations, it really maximize the roi of your RPA investments.

Now first off, I'm going to show you precisely how Blueprint helps lower the cost of our paid development and deployment with the with digital blueprints, and better guidance for RFK developers ultimately.

So here we are in Blueprint. Blueprint is a web based cloud hosted environment that makes it easy for people to get access to information, but ultimately, it gets people off of their desktop and off of a file based approach.

Now, we are working in this invoice processing example.

What we're going to do here, is we're going to import a capture process from Fortress IQ.

We're going to pill, pulling this, extract invoice example.

Here, we have a digital blueprint for an extract invoice process that we captured and are automated.

Now, without Blueprint, we would have to capture all the specifications and the design in a big document before essentially throwing it over the wall to IT for development while they slowly unpack all the information needed to start development.

This replaces the T P DD, or large document that folks use today completely digitizing the approach, Which will have a direct impact on lowering the costs of development and deployment. And you'll see why.

But, Blueprint also, gives you the opportunity to easily model your processes for automation, and create these digital blueprints in an intuitive designer, which I'll show you right now.

So, for example, here.

I'm going to create a new artifact.

Create a process here, and then I'm gonna give it a name.

Once I've done that, I'm going to create, create, extract, invoice process.

So, here's our blank canvas, where we will quickly and easily define our to be process.

That has to be automated.

Adding more steps to the process is as easy as clicking on these additional, that actions.

We can add a new task.

So, for example, add a new task here.

We can even toggle the Assistant Steps, which get more granular, granular detail, that allows us to bring in UI, different system, and really define how the process interacts with process interacts with other systems, and how it's going to drive precise development. And ultimately, it's going to yield a much higher quality automation.

But in consideration of time, we'll go back to the capture process, we import it.

Of course, you'd like to see how you can easily build digital blueprints from scratch in detail, but by all means, reach out for a demo. I personally love to show you how this is done, and how the full power of Blueprint can be used over a call.

So, now back in our original Digital Blueprint, Here is where we can optimize the process with all the capabilities that Digital Blueprints deliver.

Based on previous automations rate based on previous automation designs and the production bots that we've cataloged, the system is recommending certain policies, regulations, rules, and other dependencies that might be missed, and apply for this automation.

This is an example of our intelligent recommendations and our dependency mapping that you don't get in other automation design solutions on the market.

This intelligent assist since reinforces a strong tracing strategy to ensure no dependencies are missed or overlooked, which significantly reduces the bot outages when they, when did the need for maintenance and downtime, and the need for maintenance, and doubt that, sorry.

All of these dependencies are linked directly to the digital blueprint, and are used to quickly report and identify the impact of change and that happens when this is live in production.

While we can True, what, which, ultimately helps us to contribute to proactive change management.

And it really an approach that enables Blueprint to start to prevent these fires are popping up, as opposed to the Bridge Day, which is very reactive, like fighting fires.

Most importantly, we can automate these digital Blueprints by generating a bot package and sending it directly into any of the major RPA platforms.

This allows us to accelerate the transition to development and remove the manual PDD document process.

Again, reducing the effort of RPA development and deployment while producing high quality, resilient automations, because of the precise context digital Blueprints deliver.

So in this particular case, we've actually sent this automation over into Blue Prism.

Now here is the generated bike package in Blue Prism.

The process, this process flow serves as the baseline bot or a bot skeleton, if you will, that the developers will use to get started.

In other words, without Blueprint and RFP developer would first have to interpret what exactly needs to be built by digesting a large PDD, and recreating everything from scratch.

This is how luker provides a head start on development, and not only reduces the time it takes to develop bots by upwards of 50%, but also leads to higher quality development, because there's nothing lost in translation.

In addition to the process flows, the digital Blueprint also sends over links to all the dependencies for easy access and transparency, Ensuring that, ensuring they have precise guidance for the bot, that the business wants to be built.

Without Blueprint, these would be buried somewhere in a PD, and they're easy to lose track of, and miss altogether.

Now, in addition to automating the digital blueprints into a bot package, digital blueprints can also be used to automatically generate suites of test cases and test scripts, which can then be used for development and u.a.t. testing.

Further reducing the effort on development and deployment. And really keeping that total cost of ownership for RPA at a minimum, because it drives that information so efficiently from the design stage into the testing phase.

But Digital Blueprints can also automate the backlog of user stories needed to develop the bot. So here, we've generated a backlog of user stories for this automation and synchronized directly in Jira, which is what this development team uses to help guide and manage their work.

Now that we've kind of covered how Blueprint can help lower the cost of RPA during development and deployment, we're going to show you how Blueprint specifically reduce the cost of our team maintenance and support by enabling that improved dependency mapping, proactive change management, and increased alignment.

So, if we fast-forward in this particular example to after the completion testing and deployment of the automation, Louvre continues to deliver value throughout the life of this new automation.

It's helping to streamline changes, and sure, continue compliance. And this is where blueprint enables proactive change management.

Here, for example, we have notifications of things that have changed that might affect the automations. These notifications are summarized at the top and it can be categorized in these different diagrams, category in severity.

For example, let's say you're only interested in the regulation, so we'll start to filter this down to specific regulations. And of those, we only care about, in this case, the high severity ones.

This filters down to a single change that's happening with a click in Blueprint.

It can tell you exactly which out of the entire portfolio of automations are going to be potentially affected.

Clicking this particular notification takes us to what's called the impact analysis view.

Now, without blueprint performing an impact analysis like this, would be P, would be a piecemeal practice, where you, essentially, need to manually isolate each bot that might be impacted by the change and then dig into the code to understand what the implications are.

You can see that a change to this part of the regulation will potentially impact these exact five automations, including the one we've recently been focused, focusing on around invoice.

At this point, we'd like to alert the owners of this of these automations that they need to take action before the bot fails, and it's subject to ours investigation while it sits idly, losing business value that's supposed to be delivered.

So in this case, here, what we're gonna do is click on our little Alert icon.

And we can enter in a note into this particular, to notify the owners and teams letting them know of this change and that they need to analyze their particular automation.

And we won't send this out.

And now that the owners have been alerted, they can actually action on this, they can do something with it. Without blooper, the most typical way that all this is co-ordinated is via e-mail, which is definitely not efficient and not easy to manage. Now, let's kind of switch chairs here for a moment and become those owners were just notified.

As an owner, Nancy, I'm going to log into blueprints because I received a notification.

And here, as the owner of that process, I see alert in my personal dashboard identifies the regulation that's changed. Which automation I need to look at, and any associated comments that have been provided.

With everything linked, I can now go explore the regulatory change, and see exactly what it is, and I can even navigate into Blue Prism to the affected part of the automation, or I can send that note to my team to have them investigate.

As we've shown you today, blueprint creates value across numerous categories.

All of that rolls up in the primary value of the Autumn enterprise automation suite. Which is significant improvement in automation quality.

Higher quality automations have less downtime and fewer break fixed.

And thereby require less maintenance and because of higher quality automations, RP is total cost of ownership is dramatically reduced while the availability of your bots is increased. It's really maximize your return from that RPA and it really enabled you to scale out to the organization.

Now, here's another visualization of blueprints impact in our case total cost of ownership and maximizing roi.

Let's use a conservative estimate that assumes each automated process is supposed to deliver $250,000 in business value.

Without Blueprint bot outages and the effort needed to fix them can cause RFK maintenance and support costs skyrocket.

For one baht.

Do you mean that it breaks six times per year on average, and that's being generous?

Each break takes about 20 hours to fix, and that's about 120 hours of work per year or 120 hours of downtime.

Leaving the baht only able to run this plan, about 92% of the time.

At 92% uptime, that means about $20,000 in business value is launched as lost in the downtime.

Now, if you've got one bot, these numbers are hardly anything to phone home about.

But if we start to scale that up to 10, 20, 50 or even 100 bots, that value becomes quite significant.

Now by using Blueprint, we've seen customers build significantly higher quality bots that break half as much as they used to also a conservative number, which means that their bots are now able to run 96% of the time.

That means they can now deliver $10000 in business value, that they, otherwise, they would have lost in downtime while they're also saving about 60 hours of work time that would have been needed to fix the bots. That's $3000 in team costs.

If you have 50 bots that are breaking six times per year, not only are you spending 6000 person hours fixing those bots instead of building new ones, but that downtime is costing you a million dollars in business value that was supposed to be generally generated through those automations.

Now, if you can build bots that break just half as much, that's half a million dollars in business value that you're now getting that you couldn't before, not dimension 3000 team hours. That can now go towards more strategic activities. And $150,000 and save teams costs saved team costs.

So to sum it up, what we've covered today, the business case for RPA is being turned upside down, where RPS total cost of ownership is really outstripping its returns.

RPA development, deployment, maintenance, and support, are both the biggest or the biggest components that contribute to the overall cost, and also what's causing those costs to spiral out of control.

What was simple design, governance and change management principles, RPA has total costs, can be dramatically lowered, while also maximizing those returns.

Those principles includes replacing SLO, error prone, paper based, manual documents, lead to more breaks and outages with digital blueprints that produce higher quality automations.

You want to improve, you have to improve your dependency mapping with things like blueprints, intelligent recommendations, and assistance, enabling a proactive change management strategy with better dependency mapping and instant impact analysis, and, increasingly, alignment for all your RPA stakeholders with digital blueprints, and a centralized environment to really manage change and robust governance.

So if you're interested, just visit the link on the screen to schedule a free consult, with one of our solution experts like myself, to see firsthand how blueprint can deliver the value we created we create for your organization.

Within that conversation, we can do a cost analysis to see how your RPA cost can be reduced with blueprints.

And at this time, I'd like to open it up for any questions that folks may have. And be happy to take those now.

That was great, Matt. Thank you. So we're opening up the floor now to audience questions. If you'd like to ask a question, please feel free to pop it into the question tab in the control panel on the right side of your screen.

We have a few that have come in throughout the presentation, which I'll get started with.

The first question we have here is, In one of the last slides, I noticed Blueprint provides bought migration. Does that refer to moving about from one platform to another, Can you elaborate?

Of course, I can, absolutely. So thanks, Brenda. So one of Blueprints popular use cases is facilitated migration of entire Bob Portfolios from one RFK platform to another Blueprints Enterprise Automation Suite. It allows you to ingest spots from all the major RPA platforms, and then reverse engineer them into our platform and convert them into this common format, known as a Digital Blueprint, which we looked at today.

From there, these digital blueprints can then be automatically sync with any Target RPA tool. Meaning, bots no longer have to be rebuilt from the ground up.

And that's why we're able to reduce migration costs by up to 80%.

It really accelerate RPA vendor switches by a factor of three times.

Awesome. Here's another one, you mentioned that Blueprint is able to automatically generate user stories. We use jira to manage the development work on our bots.

Does blueprint provide an integration that would need enable us to sync those user stories with jira?

Absolutely, We do. That's a great question, again.

And my apologies if I didn't go into it in detail during the demo portion of the presentation.

But Blueprint does indeed provide a bidirectional real-time integration with jira and many other work management systems and L M. tools. Things like Azure DevOps, micro focus, ILM, you name it.

So in the case of jira, user stories, we automatically generate can absolutely be synchronized with jira or any of those other work management technologies, like Azure DevOps, for example.

And it really helps bring them so that they can be land, they can land directly in the Development Workspace, and they can drive bot development. The same can be said about things like, test cases, which are automatically generated, again, from digital blueprints.

And those can be sent with test suites. You can use the IG via those same integrations that are available.

And we also have a robust set of things, like web hooks, and even a public API that you can use to build custom integrations, or even connect blueprint with any home-grown systems you may be using on either of those fronts.

Great, well, let's see, can you explain how Blueprint is able to reduce the cost of migration by so much?

Absolutely, so I'd be happy to.

So migration has traditionally been so expensive, and ultimately uncommon as a result, because there wasn't any portability in the ... ecosystem.

And what I mean by that is bought from one platform, couldn't really be exported, and work in another platform briefly.

So each RP tool speech, its own language, meaning there's a long list of incompatible actions command variables, even the architecture in each of them.

And that meant a bot needed to be basically built again in the Target RP tool for it to work.

So entire digital workforces need to be rebuilt from scratch With Blueprint.

That massive manual effort, an expense is removed.

So, our core goal is really to start migrating and converting that automation logic.

And that, that bot framework and the bot structure, so we're able to reduce costs so much because of what we call as our common object model. It's something that we've developed, it's just behind the scenes.

And it's, you know, it really provides these bilateral integrations we have with the RPA vendors.

In other words, when bots are ingested into Blueprint, we're able to re-engineering convert as many commands into common into this common model. Referred to as the digital blueprint.

We take the whole structure, turn it into a digital blueprint, and then because of the common object model, we've really developed, we can actually convert commands underneath into a generic framework that can then be sent into a new RFP platform. So those digital blueprints can then be further optimized and then fed into whatever RPA tool of choice.

So, ultimately, what it's doing is, it's shifting the development effort, from having to read an existing bot and rewrite it from scratch to, you can use these digital blueprints to move an automation over. And now the developer can work in the new destination platform to get the bot up and running again.

So we have another one here. So every tech solution creates new problems over time, which need another tech solution to manage post-production issues and are close to implementing RPA supervisor.

Any commonalities with the same, I think maybe it's not fully clear MFG you submitted the question.

I'm sorry. He just added basically any comparison sheet of RP supervisor with blueprint with reference to post-production management.

Hmm? Hmm, hmm, hmm, so, I'm not as familiar, unfortunately, the RPA supervisor know our, our goal, when it comes to post-production support.

And management is not to replace things like an Orchestrator or, you know, the the kind of orchestrator queue level manager that's in each RPA technology.

In other words, we're not monitoring the bots in terms of their uptime and they're running.

What we're focused on is managing all of the dependencies, managing the mapping that the bot has, back to the business, to the systems, to the rules and regulations.

So, I may not be answering your question to the level you're asking it, and I apologize, but I definitely encourage you to, you know, shoot us a note.

And what we'd love to do is hop on a call and go through a little bit more detail. That definitely can set up a session to give you a little bit more of a deeper understanding of how we would compare to something like an RPA supervisor, tech piece of technology.

Great, we have another one here regarding Blueprints migration use case. We're currently looking at migrating to Microsoft Power automate. Does your migration solution support switching to Power automate?

Absolutely. So the short answer there is, yes. Blueprint has bilateral integration with Microsoft Power automate. So we can ingest your bots from Europe, a tool. They currently use, convert them into digital blueprints, and then feed them over into Microsoft's power automate platform.

Great, and we have one more question, here. So how long does it take to implement Blueprint in an organization, including the learning curve?

This is a great question. Blueprints, Enterprise platform itself is designed to be intuitive, really accessible to all stakeholders.

So it's easy to use whether you're a business or technical user, it, it's very comparable and similar to what people have done for years in Word, Excel, or Visio.

It's just a web based cloud hosted solution but there's also built-in interactive onboarding and contextual help resources to help guide you through Blueprint and accelerate the learning curve.

With all that being said, Blueprint is delivered in Starter Pack offerings with unlimited users, and it's designed to get new user new customers up and running in under two weeks, and there that means you're in their building digital blueprints and seeing a return on your investment within the first spot you built.

In terms of time to value, you know, as I mentioned, in one of the final slides in my presentation, our customers on average experience about a five X return on their initial investment. And that's usually in the first six months that they're using Blueprint. And really for six months is derived from the increase in bought availability and the RP uptime in January.

Great. And that was our final question, so I want to thank everyone for taking the time out of your day to join us. We'll be in touch with the recording of this session in the coming day or so. In the meantime, please don't hesitate to reach out if you want to learn more about how Blueprint can help you achieve RP at scale In the chat function. There's a link there. If you want to reach out with any questions. And also on your screen, there is a e-mail in URL if you want to reach out to us. Thank you so much for participating today.