What do you do when you are overselling without enough stock to provide your customers? How do you keep track of the import of products to your store? How can you ensure a consistent feed of updated pricing and quantity each month?

That’s where Babybots comes in. They built a total of five bots that handle the pulling, formatting, and aggregation of 130K+ products for their client. Join us on November 3rd to learn how Babybots utilized Robocorp to help their clients automation project succeed.

Our panel of automation experts will help you understand how creating a digital workforce can improve your supply chain processes. They will discuss:

How automation can help supply chain functions

Why use automation and how to determine if it is right for you

The time savings and revenue opportunities that automation brings

Chris Etheredge

VP of Sales & Cutomer Operations, Robocorp

Cory Shreffler

Managing Director - Process Innovation & Automation, Babybots

Zack Schmitz

Senior Director - DevOps, Babybots

Automation for Field Services & Distribution

From startup costs to implementation and maintenance, many small and mid-sized businesses assume that process automation is simply beyond their reach.

Meet DigiAssist, the new RPA as a Service (RPAaaS) platform from Robocorp partner WM Promus. DigiAssist can automate repetitive tasks for businesses of all sizes.

Built on Robocorp’s technology, DigiAssist brings the benefits of SaaS to automation—lower running costs, reduced time to ROI, increased scalability and ease of use.

Join WM Promus architect Mindaugas Mejeras and WM Promus General Manager Eileen O’Mahony in a discussion about digitizing SME operations and putting an end to inefficient manual processes. 

How RPA is available to all organizations regardless of size

Processes that SMBs can and should automate

DigiAssist fulfilling WM Promus’ vision of RPAaaS

Mindaugas Mejeras

Solutions Architect, WM Promus

Eileen O'Mahony

General Manager, WM Promus

Peter Steube

Head of Partnerships, Robocorp

DigiAssist: Automation for all businesses

As our industry evolves, new RPA providers offer distinct benefits over the first generation tools. For example, Robocorp’s pricing model and modern, AutomationOps approach help businesses save money and accelerate innovation.

Could it possibly be worth the time and money to switch RPA platforms? What about the re-writes and risks of breaking bots? And are the Gen2 players all they’re cracked up to be?

There are many factors to consider when evaluating a platform migration. Which means there will be plenty to discuss during Robocorp's October 12th.

Our panel of automation experts will discuss:

How migrating can reduce costs and open new possibilities

Evaluating the risks and rewards of migrating platforms

What a replacement or dual vendor strategy can look like

The migration process: planning and technical conversions

Olivier Gomez (OG)

Co-Founder & CEO, IAC

Antti Karjalainen

Co-Founder & CEO, Robocorp

Shail Khiyara

Thought leader in Intelligent Automation and AI technologies

Peter: My name is Peter Steube, I'm proud to work with rower Robocorp. For those of you who don't know us, we are a company that is bringing forth an exciting new approach to the automation industry. In a single sentence, we are an open source cloud-native and modern platform focused on empowering RPA professionals to produce more sustainable and cost-effective automation. As most of you know, the RPA industry has historically been dominated by just a few vendors. What you may also realize is that these quote-unquote gen one providers of RPA are commonly constrained by, and this is not limited to their proprietary toolsets, licensed-based upfront pricing, high infrastructure costs, and antiquated development and deployment experiences. In light of the innovation that Robocorp is now offering the industry today, we will discuss the risks and rewards of migrating replacing end or a multi-vendor strategy. In order to do so we've enlisted a panel of automation, industry titans. Shail Khiyara will soon be moderating and driving the discussion. 

Shail has spent the last half-decade building the intelligent automation market, which comprises of both RPA and AI technologies. As a unicorn in intelligent automation and digital transformation he has served as a CMO and chief customer officer at three leading automation firms helping to shape this industry. He is also the founder of VOCAL, an independent automation customers-only group, which actually stands for the Voice of the Customer in the Automation Landscape and now has over 50 key decision-makers in the automation industry from across the globe. We are also joined by Olivier Gomez a.k.a. OG. He is a recognized global expert and pioneer in the field of intelligent automation and RPA, he is also the CEO and co-founder of Robocorp partner IAC as a senior executive with 23 plus years of experience. He is a leader of large-scale automation transformations with strong ROI for the fortune 2000. Olivier scaled and ran one of the largest automation footprints in the world for HP DXC, which included over 6,000 unique bots, which helps give him a very good grasp of operational aspects as well. 

And lastly, Antti Karjalainen, CEO and co-founder of Robocorp. Antti is a long-time open source enthusiast with a background in software engineering. He serves on the board of robot framework foundation and is leading the charge when it comes to evolution within the automation industry focusing specifically on eliminating the boundaries that have played the sector to date. Before handing the floor to Shail, please keep in mind that today's webinar is being recorded and a replay will be published soon after. Also at the end, we will leave a few minutes for audience Q and A. You may submit either in the chat or using the Q and A function in the zoom. With that said Shail, the floor is yours. Good luck guys.
 
 Shail: Peter, thank you, really appreciate it. Welcome all to this exciting session of the future of RPA migrating to gen two tools. RPA, as many of you know, has had an interesting history and it's continuing to evolve and with over 65 companies in the space, 12 acquisitions that have occurred in just the last 24 months. This industry continues to evolve and continues to be disruptive and disruption is a natural evolution, it's happening now. We've seen it in the first wave of RPA players, we've seen consolidations and we have also most recently amongst the big three, we're seeing a private equity takeover very recently. Antti is joining us from rainy Helsinki and Olivier is in what seems to be a very calm evening in your window there in the south of France. Welcome Antti and Olivier.

 Antti: Thank you.

 Shail: Well, let's dive right in. This is sort of a no spin zone where we want to talk about what's next beyond RPA and automation as you know, is a very hot topic. There's around $9 billion of investment that has gone in this space in the last 30 months and before we talk about gen two let's put the customer in the center of our conversation and talk about what are the customer needs? What is it that is not being fulfilled with the traditional automation, let's say gen one?

Antti: Yeah, I mean, Olivier, you go first. 

Olivier: Sure. Let me share my view here. So first of all, what's really important to understand is that this is a very normal and natural evolution for any new technology. RPA and the entire ecosystem is a new segment in the software industry, by the way. I think it is the fastest-growing segment in the software industry. If I'm trying to explain what's in the mind of most of the customers nowadays, it's very simple. They are starting to expect and demand outcome. They are slightly over the excitement wave that happens when something new is created. Trying to give a comparison, probably when electricity was invented people were super excited and super amazed by the capability. Very similar capability, maybe not for super geek people, but for most of the world having a bot that can do work for you and take over the tasks that you don't want to do is pretty cool. It's pretty overwhelming. 

I think now we are over this innovation wave and we are starting to enter what I would call an industrialized wave, where people are starting to have a normal expectations. Nowadays, when people talk about electricity, they talk about how much it costs, as simple as that. So they have an evolved expectation around this innovation. Very similar here, clients are expecting outcomes and there are things like what is the return on my investment? There are things like can you drop the total cost of ownership of running a bot? Can you increase my time to value so that I can basically get the result, not in six months, but in a matter of weeks? So those are the things that I would say the market is starting to request and expect and, again, pretty normal as we are starting to exit this excitement and new shiny object type of phase.
 
 Antti: Yes, so as I look at the first phase of RPA, it was driven by a few companies out there. Obviously UI Path has done great for themselves Automation Anywhere kind of the notable first growers in there, there probably has been others. Then at some point, let's say a few years back, I felt that there was an RPA company coming out every week. I used to see a new one entering the space, and it was always, we saw a lot of copycats like me too, we can do that too, it's the same thing and for the longest time, for instance, the licensing pattern has been the same. It's always bought licenses, it's orchestration license, something tied to the execution units and now finally we have with the first wave going past that first hype cycle in a way, starting to see something new emerging from this sort of second-wave companies that are starting to rethink how we do things in RPA, what is driving real customer value, how these RPA projects are being built and run and operated and maintained, and even sunset at the end of the project. Seeing this a few years ago, will buy in and understand a lot more. 

Because the goal here is once we are past this initial hype wave of I play with the tool, and I'm building trust that the tool can do the job. Now, I need to start scaling seriously and if you have a weak return on investment because you are using a technology that has a super high license cost, as an example, then I can tell you that there's no way you are going to scale, even if the technology does the job, because the CFOs and actually your business case will turn red everywhere. So again, what is gen two, it's simply the disruptors that come after the innovators that are listening to the requirements from the client, and they embed that natively in their technology, and those who are able to do that, they will basically do very well because they will enable the clients to achieve an outcome and to basically do what is required to have this digital workforce replace this human glue we've added forever.
 
 Antti: Yes, I'd like to add to that. First of all, human glue sounds pretty suspicious to me, by the way as a concept. But in general, we've seen RPA COEs in major corporations being built on the first generation. They get a lot of value from the first projects that they go through and build out a massive digital workforce. But at some point, they hit a ceiling. They say, no, we cannot actually go beyond what we have reached here so far with the first-gen technology. Whether it's depending on the licensing or the cost structure, or whether it's just the technical limitations or the tool that they've chosen, so they can kind of start looking for this dual vendor strategy where they want to bring in another tool to augment their capabilities. Obviously, if you've been in many of those discussions and a lot of times the first-gen vendors, what they've done now, obviously huge market penetration, like a ton of of sales, new sales happening, and now they need to expand. 

So what they start doing is they start horizontally adding solutions, whether it's process mining, whether it's chatbots, hyper-automation, all of that, and capability to expand on the customer accounts. But these customers that are saying that, okay, we've hit the ceiling. Now we don't need to add yet another high bill automation capability, we want to just add more bots, how can we do that? And that's where technologies like Robocorp come in and can really help them augment them.
 
 
 

Olivier: And just to add to that, because I want to give a practical example here. Typically when you start, you identify activity that you want to automate in ICOs location. When you start scaling and you are a global organization, and you want to scale across the world, including Asia, the cost structure is going to be totally different, and it's going to be more and more difficult to basically build a case to do automation in area where it is not Europe, it is not US. So those are examples of things that are, that ceiling that Antti is describing can materialize in different ways, but you want to start scaling, I don't want more features. I want the core structure of what I am deploying to be right and that's really important,
 
 Shail: I think Olivier, you make a very important point about the core structure and this ties back to what I was mentioning earlier about the bot based architecture with which gen one started, there was also mention of scale. So are you both saying that gen two actually allows you to scale faster because the core fundamental technology is a differentiator. What are your thoughts around what makes; first of all, does gen two allow you to scale faster, which there are challenges in gen one? And if so, what enables you to do that?
 
 Antti: If you think about we need to actually separate whether we're talking about mid-market versus the enterprise. Obviously the enterprise will stick around with gen one for a longer time. Mid-Market hasn't really started with RPA, so we've seen a ton of uptake with RPA in the mid-market where we can see a partner ecosystem, for instance, taking Robocorp and really running that as a service to offer the business outcome of bots and kind of scaled down market where we haven't been seeing RPA that much, but just talking about the enterprise itself, any thoughts on that, Olivier, on your side?
 
 Olivier: So for me, the scalability of a technology is not always related to the technology itself, but it's included. So again, back to my point, it's all about going through the different approvals inside an organization and validation inside an organization that actually what you are doing is positively impacting the P and L of the organization, top or bottom of the P and L, but you have to have visible effect of what you are doing. So back to the technology, if I am deploying something that is allowing me to positively impact the P and L, everyone in the organization, the CIO, the CFO, and the CEO will ask for more. If I am working with a technology provider that understands that I'm working is a service provider that understands that, then all the rest is virtually details. Of course, you will hit limitations with certain vendors, which will force you to move to someone who doesn't have those constraints. But conceptually the scalability of the is simply related to does it make a difference to the business? If yes, I want more, if I want more, I'm looking for the right technology. If I don't have the right partner right now, I switch, obvious.
 
 Antti: Yes, I see that the enterprise is still very focused on the COE-led model where we've seen RPA scale-up, it's always been driven by the COE. Teally the citizen developer model hasn't really come through in that way or I haven't been able to observe it in the market when talking with customers that they had adapted. I see this in developer lead path and just scaled tremendously with positive results. Where we have seen scaling up, definitely driven always by COE and there be typically see more technically capable COEs being able to take technologies like Robocorp, and then run with that and continue for over scaling past the first initiatives.
 
 Olivier: Another point that is important here, that is I would say related to running the automation. So automation ops or whatever you want to call it, you basically are going to scale if you can handle what you have today. And back to the point, we have seen many, many COE that are slowly evolving from a team of people building bots to a team of people doing support of the bots and then you are back to the typical IT issue, right? If I have 80, 90% of my resources maintaining what I have instead of innovating, and again, reaching a ceiling, it's a very typical situation. So the capability of the technology, the vendor, and the service provider to be able to run the footprint efficiently so that you can keep scaling and you don't collapse, this is absolutely critical and gen two, if I have a cloud-based, native cloud-based solution that is giving me instant let's say, instantiation of my bot that is giving me 99.9% uptime so I don't have to worry about that and plenty of other things that will help my run and maintain phase, then I am a lot more comfortable to grow my digital workforce because I can handle it.
 
 Antti: Great point by the way, we have a good article that we authored around automation ops, fully agree with that point of view. Just happens that we've actually incorporated that kind of modern DevOps type of operational model into the product itself, which again, didn't happen with the first generation because they started out with this model that this is going to be outside of the IT, like not part of the IT organization. Slip it in under the covers, and nobody needs to know, well, you'll build a hundred bots, somebody who needs to know about that and maintain them for sure.
 
 Shail: I think that's a very good point that you bring up and customers generally tend to migrate to alleviate the pain points that they have, and that are not being met with their current solutions. So clearly in the market, we are seeing a multi-vendor RPA strategy but in addition to that, additional technologies are being added to the stack. You've talked about chatbox analytics, AI process mining capabilities. Why is this migration required? Why do you think a customer should migrate? When should they migrate from a gen one to a gen two?
 
 Antti: From our perspective, sometimes it's just required because a vendor might be updating, you typically see in the enterprise specifically, you'll see that your customers are gonna be lagging multiple versions with on-premise deployment. Now, gen two, being typically cloud-native, you don't see that kind of lag behind in versions. So you actually might hit a natural point of, hey, we don't even support that version anymore, you need to rebuild your bots to the natural break point in that evolution where you might consider migrating away. Then there might be events like a private equity takeover that starts, let's say the customers start thinking about, hey, is this going to be the company that's going to be innovating in net for the next coming five years? Should I sign up for a multi-year license commitment to this company? That's another natural breakpoint, but all in all, this is something that happens with every technology out there, every possible technology that we see go through these evolution cycles is bound to have a first wave and another wave with migrations involved. 

We've seen it with video conferencing, for instance, everyone migrating over to zoom when we've seen a clear winner. Then Microsoft is in there with Teams, we've seen it with the I-PASS vendors. We used to have TIDCO started out in the late nineties, then we have other players MuleSoft and so forth. It's just a constant evolution that happens in the space and part of the natural progression of, well for it's just a cloud that really didn't exist when the first-generation RPA players were being created, that kind of sets it up for a generation change.
 
 Olivier: Yep. So the way I look at it right, is so first of all, obviously this is something that evolves all the time. This ecosystem that we are describing is changing all the time. It's alive and as anything alive, things die, things come in and that evolution is pretty much the same as any other IT space. It has to be managed and this idea of there is a risk to migrate, be careful, this is a very close to me, this is very close to, I'm trying to build stickiness here into this environment. At the end of the day we can talk about that in details, but obviously as any change, there is a risk that risk can be very easily managed. It's not too far away from, I have a bot that breaks and I got to fix it, it's a bit more advanced way of I'm rewriting it and redoing it, I'm converting, I'm migrating. But at the end of the day, I want to downplay that. I mean, it's very natural. It's very normal. You are totally free. You don't want to be stuck. You want to have multiple vendors. You want to go for the one that gives you what you need and the benefits that we see by having this freedom to move to the right place is by far exceeding the risk that you are taking to do so.
 
 Shail: One thought that comes to mind is that there is a lot of challenges with upgrades. Olivier, I'm sure as you went through 6,000 bots in prior engagements you've had, you may have gone through some upgrade cycles as well. In the market today, there are about 25,000 customers in the market and 50% of them are still sitting on legacy automation software, older versions of the software. And why, because upgrades are a pain and bots tend to break, the bot fragility that I was talking about earlier. And while the majority of the gen one vendors are adding to their TAM, their total addressable market, many customers still cannot take advantage of those new functionalities because they haven't upgraded. So if upgrades are a pain, what makes it easy for customers to migrate?
 
 Antti: Yes, that's a good point, upgrades are oftentimes a pain especially, like I said, running on-prem. We've seen that actually migration work, if you think about just pure migration of an existing bot that might have taken months to implement in the first run, then you do migrate it's typically fraction of the time involved. So it actually might be proportional to a migration workload that you might be looking at otherwise in any case. So we've seen instances where it takes, we had a customer who migrated away from one of the first gen platforms, and they had multiple bots that they had built across a six-month time period and they were coming up on their license terms. So they were a bit in a rush, they brought in a robocorp partner to handle the migration, took them under 30 days from zero to running in production, those new bots taking rid of the old gen one licenses. While the partner was doing that migration, their own internal team got ramped up on the technology and started producing other automations already on top of the platform. So think about six months initially implementation, 30-day replacement implementation. So that kind of gives you a perspective on the fact that when you architected the automation, you figured out all the pain points, you kind of have it defined already, it's much easier to go about and just go with the migration.

So I don't need to host this orchestrator here. I don't need to host these super PBMs. I can actually run these in containers or then run in lighter-weight virtual machines, run multiple bots on the same virtual machine, et cetera, that some of these examples actually include customers having their infrastructure bill in addition to having the license bill. So that has been pretty significant and my favorite type of migration may be being we've seen people running things like Python-based bots through platforms like UI path, which are definitely not designed to do that, but that somehow they have ended up with that kind of architecture. So that's like lift and shift to Robocorp, which is Python-native supported platform. So these are kind of that the things that we see out there, it just makes a ton of more sense to run those Python-based bots on a platform that's actually made for them instead of using a UI path orchestrated to do so. So maybe I've covered all the big three that I've seen, but so many other examples out there. I'll let Olivier, you chime in as well.
 
 Olivier: Yes, so we do a lot of assessment for the clients, and the typical trigger for them to consider another technology is please first reduce the complexity, bring simplicity. So we talk about infrastructure. So infrastructure has a cost, it's not just the cost. You have large companies that are relying on all the vendors and there is always let's say a very long process to create a new bought and provisioned infrastructure and do the network slash firewalls slash installation slash, so it is perceived as, it is not simple, it is difficult and please help me go to a place where it's a lot easier to do. What is connected to that is please also help me handle the fear that I have of making a change of basically. So right now, I'll give you a specific example, we have a client that has a certain install base, which is gen one and they now come to realize that they would like to have a dual vendor strategy. So we do introduce a gen two vendor in the mix so that they basically build trust, they see the value, they understand the simplicity of working off the cloud, of having a more flexible way of consuming and we also show them slowly that not only you can introduce a new vendor to build a new bot, but actually moving from this old bot to this new bot crossing technology is not a big deal. 

You assess correctly the situation, you understand the sending point, the receiving point to new technology, you understand the differences, they both have strengths and weaknesses that we have to handle. You basically convert the bot and then you help the client through very heavy testing, help the client understand that the input-output of the new bot is exactly the same as the old one. So at the end of the day the confidence that I can now use this technology that fulfills all my requirements and actually does exactly the same as the previous technology is something that it's very easy to articulate to the client, if you correctly assess, you correctly convert, and you correctly test once it's tested and the outcome is there, the output is same, then it's just the trigger to decommission the old is very simple.
 
Shail: So how long does this usually take in your mind as you've gone through this Olivier, this migration itself? Does it vary depending on the complexity?
 
Olivier: Yes, yes, yes. When you assess an environment, not all bots are equal, you can have a very small bot that does very simple copy and paste reporting type of task and then you have a monster of a bot that is not just RPA, that has a brain, it has vision, it has language. So it basically has a lot of capability and it depends on the size. That's why assessing the environment, phasing the conversion, the simple bots, it's a matter of weeks, it's a matter of weeks. The more complex bots, you also want to make sure that the technology you are selecting as the receiving end has all the capability because there's, of course, gaps and mismatch, not all the technology has the same, let's say objects available, the same libraries available. So there's a number of things that need to be done, but the assessment is really critical to understand what it is I can move as a first phase, quite easily to build confidence and then I can address the more complex one later on. So again, I would say from a few weeks to obviously a few months, if it's a monster of a bot
 
Shail: Fair enough. So Antti and Olivier, I've been asking some of the questions that have already been popping up in our Q and A box. So just continuing on that theme, because I think we're at the end of our narrative here today. But one other question that has come up beside some of the ones that I've asked is, does Robocorp have a control room that has an option to trigger multiple bots, dynamic group whenever a new transaction is received?
 
Antti: Yes, absolutely we have and we have been architecting the cloud-based control room solution from the ground up in a way that's going to be able to handle transactional data for the bus pretty scaleably, I'd say. We are running thousands and thousands of bots over there right now and we're just going to be launching some of our work item management features soon enough in a few weeks time I think, I don't want to speak for my marketing team's behalf here so there's already building capabilities to be able to route work to bots and launch multiple bots to process work, do the stuff like fan-out work to multiple bots in concurrent, and then found them in as resource get picked. So kind of that takes advantage of the licensing or that the fact that there is no licensing scheme that would limit your concurrency. So you can have an elastic workforce in the cloud to operate that kind of workload.
 
Shail: Excellent. Thank you. Thank you, Antti. I think we have time for one more question. We're a little bit over time for what we had scheduled, but there is one other question that has popped up that I want to make sure we address. With respect to the migration plan, the question is, do we rewrite the workflows in gen two? Or are there hoarding utilities in gen two?
 
Olivier: So there are multiple ways to approach this. So there are quite a few, first of all, there are quite a few vendors out there who are basically trying to address this market, this conversion market by if I move away from blue prism and I go into Robocorp. So there is a way to extract, let's say XML then to convert that to something that will be an obstructed view, a technology abstracted view of the bot, and then move that back into Robocorp. So there are a lot of people working on the converter. Having said that I don't believe that anyone is at a point where you can click a button and you can convert from A to B. So there is a need to rewrite a part of the bot, whether it's 10% or 90%, there was a need to rewrite a part of the bot. Now, having said that people are making a big fuss about this, but this is not a big deal. You know exactly what the bot is doing. The starting point is not, I need to reinvent the wheel. I need to define what the bot is doing. I need to do the discovery. I need to write a solution document. All of that is done. All you got to do is to take what the bot does, and you have visibility of that and to convert it, if you have a tool that does 50% of the work, that's great and you do the rest manually. This is not a big deal. I want to again downplay this idea that, it's not like moving a house, it's a lot easier to do the conversion.
  

The future of RPA: Migrating to Gen2 tools

Constantly extracting and entering policy information into your systems, moving data between software platforms that don't communicate, and other heavy administrative work - there are certain tasks that are very important, but are expensive and no one likes to do.

These tasks are repetitive and you can better spend your human resources - talking to customers for instance. How can we fix this? Automation is the answer.

By using a digital workforce, companies can save money, get back precious time and refocus employees on customers, not administrative work. Become more competitive in a very competitive market.

Our panel of insurance leaders and automation experts will demystify automation and help you understand how to implement a digital worker in your business and add directly to your bottom line.

Jamieson Fregeau

Co-Founder, Quandri

Jackson Fregeau

Brock Longworth

COO, Cornerstone Insurance Services

Automation for insurance carriers and brokers - Robocorp x Q

Thank you for joining us. My name is Peter Steube speaking on behalf of Robocorp. You are listening to our shared webinar with Quandri as well as Brock Longworth of Cornerstone Insurance Services. And we're going to be kind of going over all the ins and outs of RPA and its applications for the insurance industry today. So again, my name is Peter Steube. I work with Robocorp. We are a company that is enabling the next generation of automation. I'm proud to be responsible for our global partnerships and I'm honored to share the stage with one of our top partners. They are early adopters also innovative entrepreneurs and not to mention they're also related as well. So, co-founders of Quandri, Jamieson and Jackson Fregeau. They have graciously enlisted the presence of their customer. He deserves substantial amount of credit for his own vision to embrace automation as a valuable tool in battling industry wide challenges and competition that is Brock Longworth, CEO of Cornerstone Insurance Services. 

So, over the course of today's webinar, we will be touching upon a broad range of topics which are designed to have something for everybody whether you're an automation veteran, a new entrant or insurance practitioner and everybody in between. So, we're going to start out with a brief introduction to Robocorp, our technology and how it's helping Quandri deliver the future of automation. Then also, we're going to hand things off to the brothers themselves for a business overview, an introduction to what exactly is RPA, the concept of digital workers and how that's augmenting workforces as well as some of the results they've been able to achieve for Brock and other insurance brokerages and providers. Our arguably most exciting portion is a panel Q&A with Brock taking center stage to discuss his experiences pursuing automation with Quandri and some guidance for those who wish to do the same. Then we will wrap with audience submitted questions so please feel free to place them in the chat or the Q&A section of the webinar here and we will hopefully answer all your questions at the end. And definitely, we hope that the people here with us now stay on the entire time. But keep in mind, we will have a replay published soon afterwards. So, for those of you who choose wisely to work with Quandri, you may never interact with Robocorp directly and for us, that's okay. We're thrilled to be the technology platform that enables minds like Jackson and Jamieson to bring high ROI automated processes to life. For those of you who are curious just who we are, we're a startup who's just beginning to transform the robotic process automation industry but we're also very much the real deal. 

In over the past two years, we've taken on in excess of 30 million in US dollars funding from some of venture capitals best and brightest. We've also on boarded 1000s of developers around the globe and touched organizations of all shapes and sizes. I'm excited to share today that these metrics are compounding in multiples not just percentage points. So, we have a great headway ahead of us and plenty of opportunities to continue to support the efforts of Quandri.

So, one might ask, why are you so special? Why have you raised so much money and achieve such great things in such a short amount of time. For those of you who have worked with automation before, it is very likely that this slide will resonate with you. For those of you who are maybe learning what RPA is and just also recognizing that it has been the fastest growing sector within technology for quite some time now and you want to be involved, you might not realize that behind those great headlines which are still very much true and what it's able to achieve exists some lesser known, we'll call them dirty truths about automation in practice. To date, RPA has been a market dominated by what are called proprietary brittle or expensive tools to bring automations to life and they typically have a vision that every user can build, maintain and run bots. It's more or less been a luxury afforded only by large organizations and even for them, there's been deployment struggles, sustainability issues and ultimately false promises of fast and carefree ROI. For us, Robocorp’s approach is different. 

We don't disagree that everyone should have access to automation or better yet be impacted by it. It's more or less that we just think especially as automated processes become more complex and unwieldy, the development should be left to professionals like Quandri. So well, we don't necessarily disagree entirely with the vision of “citizen developers or users creating their own automations.” We just think that at a certain point of mission criticality or complexity, it's best to leave the building and maintenance in the hands of experts. And well, line of business users can focus on ways to use their newly discovered free time as they wave goodbye to administrative, repetitive and mundane tasks. Altogether, for us, the antidote to the challenge is highlighted on the previous slide we believe lies in what's programmable, open source flexible and more or less a modern approach that is more sustainable, easily scaled and fairly priced technology. So, when it comes to Quandri’s projects, it's both important and valuable to know that they aren't alone. We have invested significantly to build an “enterprise grade platform” that is accessible by all. Our infrastructure is fast to set up, elegant and it's intuitive for developers and includes modern architecture features like CICD pipelines, GitHub integrations and it's built on serverless technology for those of you who are aware of what that might be and the best part is we have our entire team, venture backing and expertise to keep it up and running smoothly. There is also built in security that is proven for some of the world's most discerning organizations. There are also dashboards and one place to monitor all the bot operations effectively including secure access control and user management and our community is incredible. Open source is a mentality that extends beyond just our business model. We have a legion of active members providing help when needed and problem solving and innovating together. 

And lastly, when it comes to support for business models and processes and all that you may want to automate, we have an extreme number of libraries and also in alignment with the coding language python which is very ubiquitous and makes it very easy for expert developers like Jamieson and his team to bring anything to market. 

So, with that said, next, we're going to hand things off to an introduction of Jamieson and Jackson. Jackson Jamison, thanks for joining us today and we appreciate everybody sitting through the Robocorp portion of the intro but we'd love to kick things off with your story. Where did Quandri originate and more importantly, did you start with another RPA tool or are you fresh on Robocorp? Why don't we get right into it there as well?

Sure, thanks a lot, Peter. So, as Peter related to, we are brothers. So, I'm Jackson and the other co-founder here is Jamieson. And when Quandri started, Jamieson and I have wanted to go into business together for a long time so we've been looking at different business ideas for a while, kind of waiting for that right opportunity. And where Quandri originated, I was at another company and it came out of a real-world problem where we had really high volume, repetitive operations. So, we were a sales and marketing company and we had 1000s of emails that came in every day and we had people that needed to categorize and respond to those emails and they had to bucket them and we had a pretty large operations team dealing with that. And we knew that there had to be a better way to do it but we couldn't really figure out how to do it properly. So, after a lot of research and looking around, we landed on this bot building technology but actually with the different tools. Some of you may know them, UiPath which is an older version of RPA software and which Robocorp is now displacing tools like that. But what UiPath allows you to do is to build these bots with drag and drop software but it's a little bit clunky and it has really high upfront costs. But we built a few bots with UiPath and even there, we're still blown away with the results. And then Jamieson and I started talking about it and we came to the conclusion that there was a fairly large underserved need in the SMB market for this kind of technology that typically been reserved for large enterprise organizations. 

So, Jamieson and I fairly quickly decided to go into business together and fairly quickly after that, we found Robocorp which really fit the business that we want to build as there weren't high upfront licensing costs. It was usage pricing and you can build all of the bots in Python. So, Jamieson's a developer, we want to work with developers and allows developers to do what they do best which is code. So that was about two years ago at this point. Since then, we've really focused on the insurance broker market. So, we've been with brokers all across North America at this point and all of this is based on Robocorp’s technology. So, we've been growing quickly focusing and helping insurance brokers and that's why we're here today because we want to be able to get this technology into the hands of brokers and allow them to continue to benefit from this kind of technology.

Excellent! Thanks, so much for that Jackson. As we kind of dive deeper here into what is robotic process automation, how would you guys define that and what problems do you think it's solving and more or less, why would somebody pursue automation?

Yeah, so while we're in the business of building these bots, really, at the end of the day, it comes down to the people. So, as Jackson said, we were starting and looking at this industry and providing automation in many different industries. And what we found when we were looking across industries is that people were spending an enormous amount of time on these high volume, repetitive processes. And Quandri is really born out of is the idea of taking the best of people and the best of computers and putting that together and you're able to achieve something you wouldn't be able to achieve without either of those. And that really is, in our minds, what automation and what robotic process automation is in the most tangible form of taking those repetitive processes that people really shouldn't be working on and putting computers to work on that so that people can work on the things that they should be like talking to customers, collaborating with other people, problem solving, all these really incredible skills that people are great at but in so many industries and so many jobs, people are spending their time bogged down on these high volume processes. 

So, for us, robotic process automation allows people to essentially get that work done but enable them to focus on the skills that they're great at.

And one thing we like to say in that same line is really taking the robot out of the person and giving that work back to the robot. You don't want that person doing the robot work, let the robot do that work. And ultimately, like what these digital workers are, they're automations that are mimicking what a person is doing. So, they're logging in with the username and password, they're clicking over here, they're typing over there. They're running that same process but they're doing it hundreds of times faster for 50% or less of the cost and they don't make mistakes or take vacation. It allows people to really focus on what they do best which in a lot of brokers cases is talking to customers.

Excellent! Thanks, guys for that additional color. And of course, let's have actual data do the talking here. So maybe you guys can walk us through some of what you've been able to accomplish for the insurance industry and some of the benefits that brokers are seeing. I'm sure Brock will also chime in as part of the panel here very momentarily but maybe you can walk us through especially the case study that we're showing here on the screen which is available on Robocorp’s website as well. Kind of talk about some of the results that you've been able to drive.

Yeah, and really initially, I think there's important reasons why we ended up in the insurance industry. So, as Jackson alluded to, we started doing this across many different industries and we're doing that to see where these digital workers have produced the most value. So, as we were doing that, that led us pretty quickly into the insurance industry because there are a large number of high volume and repetitive processes. They're super important to do but shouldn't necessarily be done by people. 

And so, as we're looking at the insurance industry, we think this is because that there are just a lot of different technology platforms that brokers and insurance companies use but there isn't necessarily a way to connect these platforms. Now, a lot of these companies are saying they're coming out with an API or a way to connect the platforms together. But what we're trying to do is provide a solution to that now where essentially as opposed to waiting for five or 10 years for these companies to come out with something to connect their platforms, we can build a digital worker to essentially move data in between these platforms and alleviate these high volume and repetitive processes. And really a great example of that is this case study we're looking at now. So, this is a case study with Cornerstone that we'll dive into a little bit here and essentially, where they had an employee spending up to six hours a day downloading and renaming policies. Essentially, we were able to build a digital world to come in and completely automate this process so that that employee can move on to higher volume processes and work. 

So, on the staff side, we've now been able to cut the cost on this process by 55% while saving them 120 hours every single month. This process is completed overnight so that when they come up to work in the morning, it's completely finished and it is finished 88% faster overnight. What this enables the employee to do is to go and focus on those more important processes like speaking with customers and generating new revenue for the business.

Excellent, thanks so much. And our final slide here before the panel Q&A was to discuss the relationship between Robocop and Quandri. I was kind of giving my bias pitch of Robocorp here for the first five minutes of the call but we'd love to hear from you guys at Quandri, why Robocorp? Why is this where you're building your business or why are you moving forward in using our technology for the folks on the line that might be interested in that relationship? 

I really do think you hit the nail on the head with what you're saying. As Jackson said, we started out with another RPA platform. We started out with UiPath and as we were diving into that, the entire time we were working with them, we were thinking about why we couldn't just do this on our own in programming languages in Python. 

So, as we were looking at that, and looking for ways to do it on our own, where we aren't restricted by the actual platform they make you build in and they are extremely expensive upfront cost, we came across Robocorp. And essentially, there's really a few things that make Robocorp stand out and one is just that it's incredibly flexible. We can bring in any technology we need to get the job done to build a digital worker and it's imported by Robocorp because Robocorp supports the most popular programming language, Python. And the costs are extremely reasonable because we only pay for what we use and when we upload our digital workers to Robocorp, we don't have to pay any strict licensing fees and it's all baked into the digital worker.

And just to add one thing onto what you're saying together, ultimately, what that allows us to do is that allows us to pass cost savings on to our customers. So instead of us making our customer pay a high upfront cost, we can have a small upfront development fee and then we can run that on a monthly subscription sometimes based on strictly what they use. So, it allows us to provide a much more flexible pricing model to our customer and ultimately, that's why we really like Robocorp.

Great! Thanks, so much for that, guys. Now, let's move on to our main attraction here. Brock, thank you very much for joining and I know that you know Jackson and Jamieson well. We've had a chance to get to know each other just a little bit but very excited to hear your insights. And I'm going to hand things off mostly to the guys at Quandri and yourself to kind of take the conversation from here but wanted to say thanks for joining the line.

And thanks a lot for the introduction Peter and going through all of that. It's really helpful for us to see that it's everyone's smiling, I'm sure for everybody on the line too. And now to Brock maybe to kick things off Brock, why don't you just give us a brief description of Cornerstone your business, how you fit into the insurance market?

Sure, yeah. So, we are an insurance broker. So essentially, our function is to attract and interact with customers and then we will present those customers to the insurance marketplace, securing insurance products that meet their specific needs and then we will ultimately attempt to make that sale to the customer and with that insurance product. So, we source the products from the entire marketplace and then ultimately make a sale. So, we are a sales organization at the end of the day and we're very much driven on relationships with the customers that we have and relationships with the customers that we're trying to attract as well. And there's one little differentiator with us like we are a traditional bricks and mortar broker like we do have five off office locations where people walk in the front door. But we also have another brand called Swift Digital Insurance which is our online broker brand operating in the four western provinces of Canada. 

So, because of Swift we've always been or since Swift launched in 2018, we've been pretty focused on kind of technology and what's next and how can we use technology to enable the insurance process as best as possible. I think that is ultimately how we ended up with the guys at Qunadri and how our relationship tickets serve with them.

Thanks, Brock. And I guess ultimately like what was that? You mentioned having that digital brokerage swift kind of pushed in that direction. But with the digital workers or the bots specifically, what really pushed you to look for that kind of solution or what was the pain point that you were feeling in your brokerage to push you in that direction?

Yeah, I think like a lot of insurance brokers like we are suffering from an inability to attract staff. So, we're having a really hard time finding people to come in and work actually in those high processing manual jobs. Like there are 1000s of repetitive clicks and types and touches in some cases of our business. So, it's hard to find someone that wants to sit in the basement and just type all day. So ultimately, it was just an inability to staff those positions that was the driver for us after engaging with you guys in the process. So, we did realize there was going to be cost savings, accuracy, reliability. There's a whole myriad of reasons why it made sense for us once we actually dove into it further. But the initial driver for us actually wasn't inability to staff those positions. 

Hmm. Interesting. And then I think what we're going to do here is insert a little bit of a poll and see from the audience who might be experiencing some of those pain points themselves or who is having that inability to staff or a difficult time running those processes internally. Great music Peter.

I think we can leave the poll open. We have respondents yeah. 12 out of 12 have said yes, they agree Longworth (21:54) so let me just cut it off there and recognize that a lot of people are experiencing the same thing.

So that was 12 out of 12 were experiencing the same thing and that's what we've noticed with a lot of our conversations as well with brokers is that a lot of these businesses, they are similar and you see a lot of these problems across the industry. And that's ultimately why we're building Qunadri is to solve those pain points. But maybe Brock, it'd be good for you to kind of describe to the audience what bots that you have built to solve some of these problems.

Yeah, for sure. So, the first thing that we looked at was, basically, as an insurance broker, we interact with a dozen insurance companies. Those dozen insurance companies work with hundreds of brokers. Those hundreds of brokers use half a dozen different broker management systems. So, there's multiple companies using a ton of different kinds of software and we're all trying to accomplish a similar task. But as Jay said earlier, there's not a lot of integration between those different companies and software’s. I've been in the industry 20 years and it's kind of been the holy grail of insurance companies and insurance brokers that we're going to find this seamless integration where this one software system we all play nice in and it hasn't happened and I'm not holding my breath it's going to happen before I retire. So, I do think that there needed to be something that could kind of bridge that gap for us. And another issue we have too is that just because I want to present myself to my customer this way doesn't mean broker B, C, and D want to present themselves in that way too. So, if ever the industry does reach that situation where we have that harmonious system that we're all using, there's a risk that we don't have the ability to differentiate ourselves as well. 

So that's kind of I guess the background on why we wanted to automate our e-doc process which is the first process that we automated. So basically, our insurance companies will download our client’s policies to us. They're downloaded into formats whether it's a PDF document that isn't attractive, it's named something really strange. And they all come from different insurance companies, different transactions look different. And so, because we email the documents to clients, we have a client portal where clients can see the documents. We don't want them just looking like a string of random letters and numbers. We want them looking presentable of course. So, we've had somebody manually renaming the documents daily for many years. It's hundreds of touches a day, 1000s of touches a month. It's very expensive for us in terms of hours. It's very repetitive, very boring, you have a hard time finding someone that wants to spend their life doing that. So, it was a really difficult pain point for us and it was a really good case I think for automation. 

So, when we first met the guys at Quandri, that was the first thing we pitch to them and that's the first process we automated. And as Jay said it's been automated 100% and we've been able to redeploy that staff member elsewhere to make an impact on our customers which is what we ultimately wanted. So that was kind of our first process to be automated. Before we even got through the first launch of that bot, we were all thinking like, what's next? And so, we've now launched bot number two. And the swift digital brand that I mentioned, it's an online broker of course. So, we are spending a lot of our energy trying to get customers to complete online forms and to filter information to us that way about the risks they're looking to insure. So that information is coming into our system by email or by download depending on the application the customer is accessing, that information comes to us and then we were manually transferring that into our broker management system to typing their name, their address, entering their risk information. And so the new bot that we just launched in the last week or so here is actually collecting all that information that our customers are giving us online, it's passing it over into our various software systems and putting in a format that our brokers can then take it and run with it and do the process with the customer. 

Prior, I think I haven't done many of them myself but prior, I think our brokers were telling me it's about 15 minutes they were spending taking six or seven emails and typing everything into our system. And then they would contact the customer and then they would carry on their process from there. Now it's really beautiful, actually. They're just getting an activity in their list that says hey, this lead is ready to go. They're opening it up, the files completely built for them, the code systems already built for them and they're just contacting the customer and carrying on. 

Another benefit we're seeing huge just in this first week with that is that with online leads and sales in the insurance industry, you have to be extremely fast because after the customer leaves your website, they're probably heading to the next person's website to the same thing. So, we were finding that was taking us 15-20 minutes to notice it was in our inbox and then it's taking us 15-20 minutes to type everything into our system so we were ready to call the customer and it was often like 30 minutes, 45 minutes. If we are A game on like 45 minutes maybe to give this person a phone call. With the bot doing it though, the leads are coming into our system. It's going into our program that we're using all the time so we're seeing the lead instantly. We're not doing any of the background typing for it so we're getting these calls out probably in like 10-15 minutes. And I mean, it's week one but all indications are that our success and closing rate on those sales will be higher because we're being faster with it. So that's another unexpected way and with the automation we had. So those are two bots

Great. Yeah and so when you're looking and you're thinking about those thoughts Brock and you're thinking about kind of the benefits that you get from those, would you say the top benefits of those are kind of more financial or is it more on the side of enabling your employees go and work on other things or talk to customers and things like that?

Yeah, when I first met you guys actually earlier this year, I was driven financially. I was thinking this is going to be an expense saver and it is. I mean the ROI is definitely there and we look at what we're paying people for the hours they're working versus what we're paying for our subscription to the bot, we are saving money there for sure which is great. But I wasn't actually also considering that our HR director is not spending time recruiting for data entry staff anymore and now she's spending more time recruiting for salespeople. So, there's an added benefit for us. There's a lot of benefits like that that have come up that I wasn't expecting initially. 

So now having been months into having a bot working for us though, I would actually say that the ability to take our people and to have them doing things that are more in human natural talents is actually the big win for us. Like we actually have happier people in our data and operations team because they're not just hammering data constantly. They're actually getting to like work on more complex tasks that aren't boring them to tears and that kind of stuff. So, I've actually even noticed like a morale lift for that particular group because I mean, we knew they were in the basement and we knew they were typing data and we knew it was boring but we I don't think they even knew actually how bored they were with it until it was taken away from them. 

So, it's been like morale benefits as well. There's been recruiting benefits, there's been definitely the financial benefits that we hope for initially. But I think the biggest win for us to your question Jay actually is that we're seeing that we're providing a better customer experience because we're faster and we're actually able to deploy expert people to customers faster because I don't have a licensed broker renaming an email or a licensed broker typing a phone number anymore. They're actually contacting their customer and they're giving insurance advice which is what we should be doing. So, I think it's just allowed us to redeploy our resources in a more meaningful way for our customers and I'd put that as a number one win for sure.

Yeah, that's interesting. And it's interesting to see how that evolves over time of the of the bots running.

So, it surprised me actually. I definitely came at it from let's save some money and there was a trickledown effect of all kinds of benefit we weren't expecting.

Automation for insurance carriers and brokers

You already know the power of automation. You know that the uses of automation are countless and the possibilities endless.

You also know that while businesses are interested in automation, many simply don’t know where to turn. That’s where you come in.

And that’s where Robocorp comes in. With an open-source tech stack and consumption-based pricing, it is Robocorp’s goal to give our partners the tools, technology, and service to succeed.

Join Robocorp’s team on August 24 to hear why it makes sense to become a Robocorp partner. Our team will discuss:

Why Robocorp’s product is ideal for partners

The training, support, and other program benefits

Glad have you all here and share some exciting new announcements on our partner program and what we're doing to work with you to help you scale your business and be as collaborative as we can in the market. So, let me introduce everyone that's going to be speaking on the session today. My name is Chris Etheredge. I lead our go to market operations, I'm based out of the Dallas Texas area. On with me is Peter who leads our partner ecosystem and Saana who is responsible for customer success internationally for us, thank you probably all maybe interacted with them at different times and I'm sure they all get to look forward to meeting those of you that are new to Robocorp. 

So, we thought we'd take some time today just to walk you through a little bit about Robocorp. I apologize, we've got a mix of people on the line here from partners that have been with us from the very beginning of our journey all the way to new people that are considering going to market with Robo Corp and welcome to you all. So, I'll walk us through just a quick overview of who Robocop is how we're approaching the market and then Peter and Saana will take us into more details on the partner program itself to a lot of really interesting stories and talk about some of the programs we're putting in place. 

So, if you're not familiar with us, we've been on this journey officially since 2019 but our founders go back even further than that in the RPA space. But they brought the company to market, we've been very fortunate to have the backing of some of the very best in Silicon Valley. Benchmarking Canvas Ventures have gotten behind us at this point and are helping us really scale the organization and make the solution available to the entire globe. And one of the key parts of our entire go to market strategy is our partners and we believe that we have the ability together to make the value and the power of automation available to companies of all sizes and break down those barriers of functionality cost that often keep companies from either starting an automation journey or taking it to scale. And that's what we're really all about as an organization is giving you the partners the tooling and the capabilities in a cost-effective pricing model that allows you to help us take that to market and make that vision a reality. So when we brought the company to market, there were kind of a few sets of challenges that our founders saw that were common across the first generation of solutions that we're out there, the UI pass, the blue prisms, the automation anywhere and the other usual suspects that you see out there largely GUI based automations with a citizen developer type model and with that comes a lot of challenges and I hear this every day from companies of all sizes that I interact with. They're dealing with fragile bots because of the gooey based nature of those recording and playback type automations. They have a great deal of challenges developing within those proprietary systems. I haven't met a developer yet that has told me that they like coding in UiPath. 

When it comes to actually getting to deploy these automations into the customers, they're burdened by high startup costs which lead to a very delayed ROI. And ultimately, that plus the impact of the fragility that is often associated with these bots keeps companies from being able to get to scale. So, our founders saw the need for a solution in the market, that would take a different approach and bring about an opportunity for companies of all sizes to take advantage of automation. And you know, it's a popular and crowded space. So often get asked the question what's different about Robocorp compared to the people that we see out there in the market every day. And this slide is coming up is just kind of a simple list of how we compare and how we approach it. We're not actively out there going after the citizen developer market, we're bringing a set of developer tools that allow you to have a more programmable approach to building sustainable automations. We're very fortunate to be able to leverage a very powerful open source ecosystem of tooling that is ripe with innovation that allows you to have the capabilities of automating against any system that's out there. When we built the platform itself, it was done ground up, cloud native and introduces a lot of flexibility in how these bots are ultimately operated and orchestrated. It aligns well with modern software development practices. We talk a lot about agile automation ops and how that aligns with the way companies are using a DevOps based approach to build software. We believe bots should be built in the same exact way. And then finally, we've introduced a pricing model that's purely based on consumption so that we directly align the clients or the partners expenditure with the value that the bots are generating. We don't have a bot licensing model, we don't have a per seat model, we don't add extra charges for maintenance, etc. It's all encapsulated in one simple price that counts minutes of execution at the bot level and that gives you a lot of flexibility. We'll talk about that more as we go through the presentation. 

So just at a high level, how our solution works, there's really two primary parts to it. On the left, you see set of open source development tooling. It is based on Python which gives us a very vibrant and powerful ecosystem to take advantage of. Our CEO likes to say that every molecule in the universe has a Python library associated with these days. What that simply means is we're able to give you the power to automate against almost any target system that's out there and be able to bring the automations that your clients need to bear on their problems. We abstract that with another open source project called Robot Framework. We'll talk more about that in a second but it allows people that are not necessarily Python experts to ramp up on our technology very quickly and efficiently build out their automations. Once the bots are built, you can deploy them in a variety of ways including integration to popular source code repositories and then orchestrate those in our control room in both an unattended and attended fashion. And the other point that I'll make on here is because of the foundational components of the solution, we're able to support you operating in a variety of operating systems. A lot of our competitors are heavily windows focused. We support both Windows as well as Mac and Linux right out of the box which really impacts your overhead from an infrastructure standpoint.

If you think about the dev tooling in detail, we spent a lot of time on this. As I mentioned, it is Python based, there's over 7 million developers out there in the Python ecosystem doing all kinds of things. Robot framework, as I mentioned, is an abstraction layer. It's a keyword driven syntax that makes it very easy for anyone with basic scripting skills to build out automations. We coupled that with a very broad set of automation libraries that have come out of these open source projects and things that we have built, our partners and our customers have built and contributed to the open source projects so that you have at your disposal hundreds of different libraries and keyword actions out there for integrations to popular systems as well as common bot actions. And then there's a variety of things from a dev tool chain standpoint that make it very easy to manage your Python environments, etc. and allow you to be as efficient as possible. And really where that all becomes super powerful for you as a partner is the ability to build a multi-channel or a best path automation that makes that robot as sustainable and powerful. as you can. We obviously support automation at the UI level. But we make it very easy for you to go deeper into the application stack to build bots against locators and UI elements directly against API's or all the way down to the data layer itself. And we see this in single use cases all the time where an automation will start at the UI level in SAP for example then go against the API of Salesforce and then manipulate data at the Excel data layer versus going through Excel the app. So, it gives you a lot of flexibility and how you ultimately architect these solutions and bring them to bear for your clients and we think there's a lot of inherent advantage there. And it gives you the ability to build bots that are much less fragile than the first-generation players often. 

And then once the bots are built, you have the opportunity to leverage our cloud control room for securely orchestrating and running and monitoring the bots. So often talk to customers that have been using a competitor's technology and they talk about the constraints they operate under all the time around I've got a set number of robot licenses and execution environments and I'm trying to deal with scheduling those bots so I can meet the SLA’s of my business stakeholders and it becomes an issue with just being able to run that as efficiently as possible. 

With us, all of that goes away. It's truly cloud scale in that if you had 100 automation sitting on our platform today, you could theoretically run them all at the same time. You have the ability to make multiple copies of bots and run them in parallel. You have the ability to take a single automation and break apart steps of it so some of it operates sequentially, some of it operates in parallel to improve your throughput and efficiency on that bot itself. So, there's a lot of inherent benefits of the architecture and the features that we enable coupled with our pricing model allows you to rethink how you can bring this to bear on your customers.

And then we often ask the question about well, what are my choices for how to architect this and ultimately deploy it to the customer. We provide some optionality there are multiple ways, you know, the control room if you've experimented with our technology, you can go out to our website today, sign up for a free account and start orchestrating and operating bots in minutes. We also provide the opportunity to deploy it as a private cloud version. So, in cases where clients would like that kind of deployment option, we can fully support that. But then on the other end, the bots themselves can be designed in such a way that you have complete control over what data gets processed locally versus what has to go to the cloud for processing. So, there are partners on this call right now. They're building bots for healthcare organizations for example. Obviously, lots of concerns over data privacy and so they have architected those bots in such a way that no sensitive data leaves the customer's premises. The control room is only used for just controlling the bot start, stop, pass, fail, basic information from a logging standpoint. 

On the other end of the spectrum, you have the ability to deploy these fully in the cloud, utilize containers to deploy them out to the target systems and take full advantage of all of the scale up scale down features that are associated with cloud operations as well as some of the advanced things that we're doing around being able to manage work items in a variety of ways within the bots themselves. So we have a lot of inbuilt security within the platform. I will tell you that in conversations with large financial organizations here in the US, infosec discussions can often be a little bit of a tightrope to walk. We get glowing feedback from the infosec teams on what we've built in the platform and the native security that is there. So we're becoming more and more confident about the things that we can do to meet the regulatory and data privacy needs of your clients. And just as an aside, the platform we have sock two type one certification already, type two will be coming within the next couple of weeks. 

And then finally, when it comes to the pricing side of things, this is often an important slide to share with customers and talk to them about the difference. And the fact that we are completely consumption based, it's really a game changer for them and how they look at the potential ROI of their projects right. And so, no bot licensing, no per seat licensing, no developer licenses, you as a partner can get started immediately and started developing these models for nothing other than your cost of time to do so. And you only start, we only monetize at the point of the bot being deployed to the control room and being orchestrated through and so there's a great deal of potential savings there just on the licensing side. But if you're engaging with customers that may be have a blue prism or an automation anywhere already installed, it's important to talk to them about the infrastructure costs that they're incurring through those platforms. I've talked to multiple fortune 500 customers within the last month that have told me that they spend more on their infrastructure to run Blue Prism or AA or UiPath than they do on those licenses associated with it. We have a real opportunity around affecting that spin and make it much more accessible for those large clients as well as those in the SMB market. 

So, with that, I'll wrap up my comments and hand it over to Peter to talk to you more about the partner program itself. Thank you.

Thanks so much, Chris. Tough pill to follow there with an excellent overview of just Robocop in general and the technology that we're bringing to market. So, what I hope to do here is to maybe add a little bit more color about why partner with Robocorp and why work with us specifically and the opportunity that it presents to services providers. 

In addition to the obviously the technology and the next generation capabilities that we're bringing there, Sanna will also be helping out as we move along here. So, as we get started, I wish I was a little bit better with sound effects. I was in charge of the DJ at the beginning but drumroll please. We have great news for everybody. The total addressable market for automation services just got a heck of a lot bigger. Altogether, well, we're built for professional developers. We have the belief that access to automation should be democratized just like our competitors do. But specifically, in that everyone should be impacted by automation not necessarily building automations whereas up until now, as more or less been reserved for large enterprises and even then, it's difficult to scale because of not only licensing issues but just fundamentally how the genuine providers have been built. 

So, partnering with Robocorp offers the unique and powerful opportunity for our partners to win at both ends of the marketplace. So, what that means is that there are now Greenfield, small and medium sized both businesses and projects that now have ROI or an increasing amount of ROI underneath Robocorp’s platform or built on top of Robocorp’s platform. We see partners all the time revisiting “failed pitches” with customers, things that they couldn't just make work in the traditional tools and traditional providers. Not only that but we are seeing bigger projects actually get done when it comes to flexibility and the scalability and complexity of bots not necessarily the actual volume we see. And Chris was talking about the fortune 500 type conversations that we have. Anecdotally, we hear from these large enterprises that have been massively successful with RPA already is that they're really only touching 30% of the use cases that they've laid out and that's really all that's getting effectively deployed. So that's what we've tried to visualize here and we think that there's a lot being left on the table with automation. And this is where our partners can step in to provide those services and deliver those automations to customers and do it in a sustainable way. 

So, throughout today's discussion, we'll touch upon some of the business models that are transforming and emerging due to our platform’s existence. Maybe the most obvious Chris has already alluded to it is we are actively supporting migration projects that make existing automations more cost effective and more sustainable and altogether make a little bit more sense for your customer. 

Second, for all types, the reality is that within our framework, there is potential for an elusive combination of both higher margins for you and happier end customers with you as well. We see faster deployment times. Again, I'll continue to reiterate more sustainable deployments altogether, that makes for a more positive experience for you and your services and delivery team and then also your end customers as well. 

Lastly, we want to be clear that this is not a call for you to cannibalize or completely disregard your existing partner relationships. Of course, we're very proud to have Roboorp partners doing 100% of their work with us. And, of course, we like those folks especially as much but much of our partner roster today, especially noting the new opportunities that I've just reviewed here, they're successfully taking a multi-vendor approach to delivering automation especially at the onset of our working relationship. And we think that well, the citizen developer thesis certainly has its merits in some cases, our favorite analogy around the offices here is that while you certainly might hire a citizen car driver or a citizen landscaper to mow your lawn, you probably wouldn't hire a citizen surgeon to replace your knee or a citizen dentist to do your root canal. So, for us, that's kind of summit to what people are moving forward with in terms of things that work underneath that model and things that don't work. 

So, in summary for this slide, it's up to the partner where they want to focus and what business model they want to apply. But for us, we have a one size fits all package. Our automation libraries are comprehensive enough to address all specific industry needs, target applications and use cases that you might be accustomed to and our platform is optimal for projects of all shapes and sizes, new and old. 

So, as I mentioned, you know, migration opportunities are something that's definitely bubbling up within our network and within our community. So, we're very happy to kind of sneak preview one here that was done by a partner of ours called Quandri based in Western Canada. This was done for a biotechnology company. It was an account creation use case for one of their back-office systems. We will soon release further details of this but what we have here is a little bit of a meme or as the kids might call it a glow up. So, we have you know how it started on the left-hand side and you see that the vision for RPA didn't really become a reality. There were challenges in the time that it took to develop this process as well as in reality, it never even got developed in its entirety. There was complexity and over engineering and all together to us, this doesn't sound like the right vision for automation. So, entire Robocorp and our partner, we were tasked with bringing or fixing this automation and making it work within a 30 day time period which we're happy to deliver on. It ended up being an end to end single process substantially less lines of code and substantially less confusion for the engineers. And altogether, the result was the equivalent of a human running the process would take 5 to 10 minutes, Robocorp took less than a minute. The most important point to make here is that it was never truly implemented with our competitors. The end result was ultimately not much faster than a human for what they were able to automate and they were never able to get 100% end to end automation in the flexible model that we've provided here for our partner to work within.

So we've already talked about the business opportunity and addressable market. There's a team that will continue to reiterate throughout the course of this webinar and will stand by with all sincerity. It's not just you when you're out there, we want to win with you. So, from a technology perspective, it's both important and valuable for you to know that when you sell through to your customers, our best in class technology and our best in class team is backing you. We have invested significantly in building an enterprise grade platform here. Chris highlighted the venture capital funding and what we have behind us and are putting to work. What is unique and again speaks to the opportunities in working with us is that you can start small for free, create an account right now and start to build your practice and start to develop and test your automations with the confidence to build big. So, if you do have aspirations of selling into the fortune 100, the fortune 500, you can have the confidence to start small with us today and then build towards those bigger opportunities. 

So, when it comes to infrastructure, one, a lot of it is on our shoulders and we're here to help support. And as Chris mentioned, that's one thing that is very much overlooked in the industry today is the amount of time and effort along with the money that it takes in order to maintain the infrastructure associated with the genuine providers of RPA. We have an elegant, modern, intuitive developer experience. We support CICD pipelines, GitHub integrations, we are built on serverless technologies. I could throw out more buzzwords but I'll probably cut myself off there. 

Security, it's built in, it's robust. We're selling in ourselves to fortune 500 Enterprises, financial organizations, healthcare organizations as well as the US federal government. Chris mentioned also the acronyms that we're adding to our roster in terms of sock certifications that will certainly not end and will continue to expand and place security as a top priority for us. 

Saana will very soon discuss the dashboard and how you're able to run your entire business effectively through a single pane of glass. In addition to that you have built in secure access control for all of your customers as well as role management. And then also, when it comes to open source, that's the mentality that extends even beyond our business model. We have an active community providing help when needed, we have a Slack channel with an excess of 4000-5000 developers around the globe. It's not just us that are here to help you. 

And then lastly, business models if you're accustomed to implementation or time and materials-based services, great! We have a better option for you because we can help you meet your deadlines and we can help your deployments be more sustainable. If you are augmenting your practice with migration services, obviously, that's an opportunity as well. 

And then lastly, I'm going to hand things off to Saana who's going to review something entirely new or something that's emerging within the industry. And she's going to talk about why it's best to do it with Robocorp and that's the robotics as a service business model. So, Saana handoff to you for now.

Thank you! So, as Peter mentioned, Robocorp’s tooling works very well for all different business models in the RPA landscape. However, the tools work especially well for the robotics as service providers and this is an area where we are planning to add even more features and resources to ensure that the RaaS model gets as smooth as possible for our partners. 

So, there are many reasons why our tools work better for RaaS providers compared with the other RPA tools. So, with our platform it's very easy to get started with new customers as the upfront investment is slow or nonexistent and you can get started right away whenever you want. The development of the robot for a new customer can start immediately whenever you want and if you are in a hurry, you don't even need to conduct our sales to get to a higher tier. You can sustain it with your credit card and get the features to your use. 

So, another aspect that makes Robocorp’s platform appealing for us providers are our consumption-based pricing which Chris already mentioned. So, our pricing scales with you and enables use cases to be implemented that even those ones that haven't had an ROI earlier. But with high volume use cases and the 24 seven use cases, remember are building packs and bundles and contact us before you do the math for the consumption. And we are also very happy to optimize your robot for our platform help you to optimize your robot. 

Our cloud native control room we did Star Sports(26:09) is a modern way to organize your robotics as a service business. But if wanted, we are also happy to be the engine behind your user interface. So, which is why we are building API's for most of our features. 

Next, I will present you something new that we are planning to add to our control room offering designed especially for RaaS providers. So, at the moment, we are planning on a new layer for Robocop control room and this is called Partner Account Level Management. This account is designed specifically for the RaaS providers. For those of you who are not familiar with Robocorp’s control room, currently, we have two layers, organizations and workspaces. So, each of your RaaS client should have one organization where you can control, access and monitor the robots for each client separately. And under the organization, you have workspaces and these are typically used for different business departments. Workspaces can have ulimited amount of processes and assistance under them and the usage is tracked on an individual process level. So, what we are adding to the current setup is Robotics as a service account and it will add it on top of the organization's and this RaaS account will enable even smoother experience for our RaaS partners. In this model, you will have one account to manage all of your customers and you can manage billing and invoicing from one central place. So, we will let you know more about this later this fall. 

That's all what we want to cover about RaaS and let's continue with the benefits of our partner program. So what you as a partner get when you join the Robocorp partner program. At Robocorp, we want to ensure that you are able to grow your business with us with as little friction as possible. And this is why we support you when you get started with our tools and after the first steps have been taken, we help you expand. So, I'll talk more about the support side and Peter will then continue with the joint marketing opportunities. 

So, the support you get from us from the community; to enable your developers to build as many robots as possible. We have training courses available for the developers to get familiar with our tools. Currently, we have levels one and two available and the level three is coming this fall. When you're starting to implement your first customer use case, we can arrange the workshop with your developers where we will walk through your use case, give your developer's recommendations for libraries and keywords(29:13) and the best practices for setting up your customers setting up your cstomes robocorp organization. And once the robot has been built, a code review with our engineers will ensure that your nearly production ready robot is high quality and optimized for our platform. 

We also as a company, we want the communication with the Robocop team to be as effective as possible so you can reach us easily. We are slack teams and we can also write zoom calls on a short notice. If you have a poker(29:49) with your robot or something else, we are happy to help. Before we move on to that marketing opportunities, I just want to highlight that support from us doesn't cost you anything. So, we are happy to help you build more automations with our platform. Thank you! Peter will continue with the marketing opportunities.

Alright, classic. I was the one that left my cell phone mute Anyway, thank you very much Saana for the handoff. So, when we think about go to market initiatives at Robocorp and helping to expand either your existing practice or build something entirely new, we would like to take a comprehensive approach. We're obviously very eager to document and promote your work. Some of the examples that you'll see on the screen here is how we do that. So we have webinars, we have listings on our website, we have other case studies, social media promotions, all the above all that noise making and cheerleading, we are happy to do and actually can be very enthusiastic about and get rave reviews. For us, when it comes to actually working through these marketing opportunities, we're working to implement processes that make it a light lift for you the partner. We recognize that you yourselves may not have the time or energy to contribute a lot to marketing and you're out there focused on your development efforts and focused on the success of your end customers. 

So, for us, we want to do as much as we possibly can to get you the attribution and materials that you both need and deserve to help build your practice. We have a proud commitment as I mentioned to amplify any and all of your accomplishments. And then also, in addition to what you see here, we have other outlets as well. So, we have done bot videos and sizzle reels on behalf of partners. We contribute paid advertising to the webinars that we do with our partners as well as testimonials, copy, review, help, placing details about Robocorp on your website or any additional collateral. These are all things that we were happy to pitch in and you'll get feedback in a rapid and an effective way. 

So for us, I spoke at the beginning of the slide about a comprehensive approach. So how do we turn it up a notch? Well, we aren't afraid to put on consultative hats ourselves. So, sharing a business models, providing sales templates, again being there with you every step of the way whether it's your first sales pitch, or your first developer hire. We in our community of other partners are here to assist and enter Partner Central. 

So Partner Central is a new advancement I guess for Robocorp and I'm going to give you guys kind of a live tour here very quickly. So, it's a private partner only portal of information designed to support the building of your Robocorp practice in its entirety. We've done our homework on similar efforts within the technology industry. We couldn't help but notice that more or less, when you look at private partner portals, they are simply an outline of what revenue target you need to achieve in order to unlock your next platinum, gold, silver rating, etc then leaving it all to you and your own devices in order to accomplish it. So, we think we can do better. We're holding ourselves to a higher standard and Partner Central is one of the ways that we hope to deliver that. So partner central is currently a work in progress but we'd like to show you some of the most complete sections. Specifically, for our existing sign partners on the line now, we've now established a simple baseline of what it is to be certified, listed on our website and eligible for additional promotional networking and outlets so you'll see those details here. 

Also, as I breeze through see ways to ramp up your development whether that be building your team through hiring, outsourcing, subcontracting, etc. Additional developer resources and links to our developer documentation, help with your first PoC, help with setting up your customers and their environments, inspiration for use cases and FAQs about security are all things that we intend to scale up here as we add to the platform. Of course, there's very basic things like what do you get as a partner? So that's all included here. Our team, our roadmap, some of the things that we're doing in terms of expanding our offering for partners is show and tell opportunities where myself and mostly Hannah Cathunion(34:49 and our enablement team is meeting with small groups of partners every two to three weeks to discuss specific topics and we'll be posting that partner only feedback with in here as well. 

And then the last thing that I'll show for everybody on the line now is our list of promotional options. So, as I had mentioned in the slide, there's a lot more that we can do aside from just giving you a thumbs up on LinkedIn or retweet on Twitter. There's plenty of other options here that are available to partners of all stages not only those that are “certified” and have begun delivering projects to their customers. 

So, as I return to the prepared presentation now, I'm going to hand things off to Saana again to discuss about what's next in terms of our partner program and its roadmap.

So as already mentioned, we have raised new funding and with help of funding, we are planning to focus a lot of resources on the partner program both on the product side and also on the partner program side. So, the products will get new features and improvements specifically targeted to RaaS providers and partners. For example, the Partner Account Level Management (as reviewed earlier). 

Some other improvements on the roadmap include improved onboarding process for partners in the tooling, a new automation studio that will help teams with varied skills levels to learn proper automation incrementally and improved dashboards and analytics for partners end customers. And our partner program is also renewing a bit. So, as Peter already showed you, we launched our Partner Central and we are also increasing the support for our partners with the help of workshops, code reviews and also the joint marketing opportunities. And of course, let us know if you have any other ideas to improve our program. We want to improve it with you.

Right and I'm going to take things back from Saana very quickly just to outline where we are today in terms of our partner ecosystem. And mentioning earlier that open source is not only the business model that Robocorp has but also the genuine approach that we have towards building our community and our platform. So, the most obvious statement that we're making here with this map is that the model is proven. We're actively working with approximately 75 partner organizations around the globe. But what we'd like to report more specifically is that we're proud to facilitate ways for this community to work together, sharing experiences, delivering on projects together. 

For us, we like the word coopetition rather than competition because we've noticed that all of our partners have at least one thing in common but they think there's a better future for automation. Lastly, what we are seeing is competitive moats being built around expertise and successful deployments. So, it's definitely worth stating that the early mover advantage is winning out for a lot of our most successful partners some of which are listed here. So, it's not too late to be an early adopter of Robocorp and we're going to as we wrap things up here give you more details about how to actually move forward with us in our partner program. 

So, in summary, there are a number of great reasons and specific ideas as to why one might partner with Robocorp and why you should do it today. 

·        For us, it's the technology foundation. It's open source, flexible, its cloud native, it’s disruptive and a consumption-based pricing model of which Chris spoke to eloquently at the beginning of this call. 

·        Next is the opportunities; whether it's the Greenfield small and medium sized businesses or a fresh approach to the existing automation projects that you've already worked with, we're serving it all. 

·        Next is this support and attention that you get. I think one of our favorite compliments that we received from an anonymous partner a few months ago is that it took him two weeks to hear back from a Gen one provider versus two weeks to work with us to deliver on a project and get it out the door to his customer. So, attentiveness and support are something that we take a lot of pride in and we'll continue to prioritize as we build out our partner program. 

·        Then extending that, we're in this together. Robocorp does not have its own services dvision. It intends to focus on our core technology product leaving you all to capture those services opportunities. 

·        Last, we're seeing that early adopters are being rewarded and expected that will only continue to grow exponentially. We have a proven network of partners but there's plenty of time and available resources to welcome new ones as well as work more closely with the ones that we've already have established relationships with. 

With that I'm going to hand things off to Saana to share her final thoughts and share how to get in touch with us but I want thank everybody for joining us today. We will have a short Q&A section or time for Q&A afterwards but wanted to say thank you first and foremost.

Thanks also from my part. So, if you are interested in joining the Robocorp partner program, you can get started by contacting us. And I just want to highlight one more time that the program itself doesn't cost you anything and all the support that you get from us is included. So, we will coach you through our certified partner path and help you for example, getting your developer certified and implementing your first robot with our tools. I will share the Contact Us link in the chat if one of you already wants to contact us. Just choose to everyone if you haven't already. So, we can get started with the partner program. Okay, I think now we have time for questions.

Great. Thank you, Saana. Thank you, Peter. There's a couple of questions that have come in via the Q&A and in the chat. Andais(41:21) has asked about the API access and so that's something that we have pre robust capabilities on today. I'm going to send you a link right now on the API and web hook documentation so you can see for yourself, what's in the platform today and what's available and we always are looking at extending that and making that more accessible for everyone. So, if there's particular needs that you have or ideas, please let us know. We're glad to take that feedback and look at what we can do to make it even more powerful. 

Second question came in asked about the scalable environments that Saana had on her slide. Sana, do you want to expand on that?

Hi, yeah, sorry, I didn't mention that part. So yeah, so we want the environments. So, at the moment, the problem with the license model with our RPA tools is that you can only run one robot at a time. So, what we want in the future to hammer with the Robocorp platform is that you can have multiple robots running at the same time in one run environment so that you can also lower your infrastructure costs. That is something that we are testing at the moment.

Great, thanks, Saana. Next question came in and says, I'm planning on starting my own robot as a service business but I'm still working on my own. Can I still join the program? The answer is absolutely, yes and like Peter can tell lots of stories about partners that started out with us in that exact fashion, a person or two that had an idea. And we're looking for a platform to start building that business out. And, that's an exciting part of us right? We've seen a lot of success with that model.

I think that they are ideally some of the most perfect partners to enter into our ecosystem. Chris, if I can just add that very frequently, we see individuals like yourself whoever asked this anonymously recognize the weaknesses or lack of opportunity available in the traditional models of service and traditional models of RPA practice entirely and they come to us with the understanding that this is where they want to go but realize that sensibly as adults and humans with other responsibilities, it might take three or six months for them to get there. So, we're happy to quietly support those initiatives and privately as well and are very keen to any of those sensitivities will leave you to handle the drama with your employer not yourself. 

But joking aside to Chris's point, we're happy to establish a working relationship with you in advance of a public launch.

Thanks, Peter. Next question asked if we could share the slide deck. Absolutely. We'll make that available to everyone. And further to that part of Partner Central is making more and more presentations and demos and collateral available to all of you as a partner to retrofit to your purposes. So yes, will absolutely make this somehow more prevalent. 

Next question says how will we be informed about future technical roadmap? That's something we want to get better and better at. We recognize the need for you to be able to plan your business on the future and understand kind of what's coming. You got a little bit of a sneak preview of a couple of things today. But we do want to start communicating in a more rapid fashion around things that are planned for future development items and get your feedback on things that would be helpful. So, look for that in the in the coming weeks and months. We have the benefit of Hannah being on our team now. She was a former head of product management and has now come over to the partner enablement and support role and she's going to be a great asset for liaising with the engineering to talk to you about some of those innovations that we're bringing to bear on the market. 

Next question, I intend to use bots to scale the operations of my startup. Would that be a good fit for the partner program? Yeah, absolutely. I mean, we have startups that are doing business with us directly today that work with partners to help them build out those automations. Some do it on their own and those are great stories for us. Companies have just a handful of people that are scaling via automation versus having to throw people at their scaling challenges, right. And so, there's an opportunity to build your business in such a way by leveraging this technology from the outset that can provide you orders of magnitude of benefit down the road.

Okay, I think we've gone through most of the questions that were in the Q&A. We've got a few minutes left here. Glad to answer any others that anyone has. Here's one, can you support migrating from an existing RPA platform to Robocorp? Yeah, the answer is absolutely yes. We've got experience doing that even here recently. With the automation anywhere conversion that we discussed, there are multiple others that we have underway in various stages and we're glad to share those lessons learned and help however we can. We are working on things around how to give our partners access to technology that would make the bot conversion process faster and easier from let's say a Gen one player like a BP or AA or UiPath. We're not quite there yet but we are working on it. 

Are there any future plans on having capture cracking functionality? Saana, do you want to take that one?

Yeah, we do get asked about capture quite regularly. So, at the moment, I don't think we have anything on the roadmap. But I will come back with this one as we are getting questions about this quite often. But of course, as everyone knows, the captures are there for a reason. But of course, sometimes it might be good for the robot to be able to get past them.

A question coming in from one of our existing partners. In the event a client wants to bring management of bots internally but their bots are hosted within a workspace you created for them? Is it possible to transfer them over and remove yourself so I'm sure this will happen down the line so I'm curious? 

Yeah, the answer is yes to that. It's a fairly simple process and just standing up and account that the customer would own. 

We do see scenarios where clients prefer to have a direct relationship with Robocorp and then use our partners for the managed services around building the bots and maintaining them but they want a direct relationship with a vendor. We're open to working with you in any and all of those scenarios. 

Here's a question and I like this one. Our customers tend to refer to Gartner Magic Quadrant for all their decisions. Any plans to get on the Gartner radar? Yeah, we're well aware of this from past lives and know that a lot of customers turn to that and look, we have just started briefing Gartner within the last month, we got really good feedback. What we were told is they're getting asked about us all the time. We are in the process of formalizing our relationship with Gartner and having more access to their analysts and their entire community. So yes, we know that we as a company and you as partners need that kind of visibility that'll help you grow and we're on it

Let's automate together: Robocorp partners

Register now for your chance to win $25,000 in giveaways for attendees - get your first bot implementation for free!

Administrative tasks are manual, repetitive, and prone to errors. They slow down your billing, and more importantly, your payments. That’s where automation can help.

While automation may sound great, you likely have questions: Is automation only for large healthcare systems? Do you need a high-tech back office to make it work? Is it HIPPA compliant?

Our panel of healthcare leaders and automation experts will demystify automation and help you understand understand how it can help your bottom line. They will discuss:

Why use automation and what tasks are the best candidates

How automation can help practices of all sizes

How automation has made teams less stressed and more efficient

Head of Content Marketing and Partnerships at Robocorp

Alex Zekoff

Co-Founder, CEO at Thoughful Automation

Kathrynne Johns

Director of Financial Services at Trumpet Behavioral Health

Kevin Silver

Vice President and Chief Financial Officer at Butterfly Effects

Transcript: Automation for healthcare providers

Hello, everybody. Thank you for joining us. My name is Peter Steube and I work with Robocorp. Robocorp is a company that is bringing forth an exciting new approach to the automation industry. We are an open source cloud native and modern technology platform that is disrupting an industry historically dominated by just a few vendors. In our view, these traditional providers have blurred the real vision for a “digital workforce.” Until now, the automation of software processes has frequently been inaccessible in price, difficult to scale and or unsustainable in practice. As we augment this industry for the better, we're thrilled to see technology service providers and their end customers of all shapes and sizes embrace what is an anxiously awaited new approach. 

Personally, I'm responsible for Robocorp’s partner relationships and part of that is with great pride, I'm able to frequently highlight the exciting success stories that come from our ecosystem. So, it's with pleasure that we bring to you today's discussion featuring one of our top partners thoughtful automation, and their CEO Alex Zekoff. Alex has selected two top innovators and customers of his own from the healthcare space to join us, Miss Kathrynne Johns (Director of Financial Services at Trumpet Behavioral Health) and Kevin Silver (CFO of Butterfly Effects). Before handing things off to Alex and our guests, I wanted to start by saying that today's webinar is purposefully designed to be informative for those of you who are either one, entirely new to automation or to those of you who have the experience to realize the challenges that lie within what is still one of the fastest growing segments in technology today. 

It's with the complete audience in mind that our discussion will highlight what is now possible through the combination of Robocorp’s technology and Thoughtful Automations best in class services. Together, we're delivering automations that are financially sensible, secure, reliable, scalable and above all designed to drive measurable results to your organization in the form of accuracy, time and cost savings. Our format will consist of Alex quickly walking us through what automation is, what it can achieve and what it looks like today through thoughtful automations expert lens including a demonstration and case studies specific to the healthcare industry. 

After that, we want to focus most of today's discussion on the opportunity we have to learn from industry leaders Kathrynne and Kevin, who both had the forethought to implement digital workers within their organizations and are here to share with us their journeys, offer guidance, help address any concerns and to talk about the results that they are seeing. 

Lastly, we will open up the floor for a brief Q&A. So please don't be shy in the chat if you have anything to submit to us. And finally, if that isn't enough to entice you to stay with us for the entirety of today's session, we will conclude today's webinar by outlining the details of the giveaway worth over $25,000 of implementation services so that those of you who registered can follow in our guests footsteps by becoming innovative champions also. 

Coding, billing, collections, reporting, and other healthcare processes are perfect for automation.

RPA Resources

Learn about the many uses of automation and the technology behind it with original content from Robocorp.

Upcoming webinars

Automation for Field Services & Distribution

Past webinars

DigiAssist: Automation for all businesses

The future of RPA: Migrating to Gen2 tools

Automation for insurance carriers and brokers

Let's automate together: Robocorp partners

Automation for healthcare providers

Reimagining the automation playbook

Robot Assistants: A bot for every task