Companies often start robotic process automation (RPA) projects with a couple of use cases in mind and generally want to solve a present, short-term issue rather than looking at things holistically. In this article, the founder of Predikly, a data innovation company, discusses why a long-term strategy is crucial to establish at the beginning of the RPA implementation cycle.
Five years ago, when my company started working on robotic process automation (RPA), we had to explain to CIOs or CTOs what RPA is. Today, the table has turned, and the conversations are generally about how or where to start with RPA.
There are a set of customers, though, who have implemented a few bots or processes but don't know how to scale. After serving more than 70 customers, I have come to the conclusion that a start-and-scale strategy is crucial to establish at the beginning of the implementation cycle.