How a Business Process Consultant Uses Softools to Innovate Future-Proof Solutions for Enterprises
One of our newly graduated Softools Expert app builders, Andrew Robson, created a record by finishing our App Builder Training course within just a week. Mr Robson has no technical background in coding, but he has been automating processes, building business apps, and consulting for companies. We interviewed him to know about his Softools experience and what propelled his meteoric rise in the NoCode space with his own startup - The Process Doctor - which builds NoCode-based solutions for companies.
Softools: Why did you choose Softools? What made you take the leap?
Andrew Robson: I was pointed to it by Skore. Skore has their process management platform and they have a relationship with Softools, where you could take a process that you design -- a process map or a process model -- and then Softools can convert it into an application automatically. Which was quite interesting to me. So I have a look at it, and I subscribed to Softools's newsletters. Then one of the editions came along and said there was some NoCode training that they're going to do and it was available. So I decided to have a look at Softools to get a bit more in-depth experience of what it is.
Softools: You finished the Softtools ABC course in a week, tell us a bit about your journey and the secret behind this speed of learning.
Andrew Robson: I knew I couldn't break anything. I got a sandbox environment. It was systematic so it was quite simple to follow and the fact that I sort of had an understanding of what was going on made it quite enjoyable to do. Because sometimes when you've done the training and you click on the "completed" button it sort of archives that part and you can go back into it. I did the first risk file, then left it for a while and then went back to just review what I did. I had made some mistakes. So I think the fact that the training was kept up, the processes were kept open, made it quite easy because I could go back and review each module I learned.
Softools: How long ago did you build your startup -- Process Doctor -- and where do you see it going when you start using Softools for it?
Andrew Robson: Process Doctor is about technology. It looks at how we can use technology, and source the right technology for the right problem. For example, if you want to do a process for ordering stock, you can use Softools. You can create it and build it in, and market that solution by saying we're working with a supplier too. All of those can work together as a full package. So it's about finding or building the right product for the right problem. It's about showing the Art of the Possible.
And I think the other thing is about the democratisation of technology. We used to have these application teams who sit far away from us. They're not the easiest to develop or deal with. After Softools, well, I've got no technical skills whatsoever, but I could build an app quite quickly. That is a transferable skill. So you don't actually have to stretch your IT team for all the things. Within your finance, HR, procurement and other teams, you could have a subject matter expert who's actually building the applications, maintaining the applications, and keeping them going on with NoCode tools like Softools.
Softools: Do you think you can achieve that? Because now that you're already building things and you have plans of building more products. How do you see Softools fitting your process and your daily work?
Andrew Robson: Now we've got Softools. We build simple enterprise tools using it. We go to market saying "look what I've built and you can use these for your own processes." The idea is that I've got a couple of tools I've put on the website – they are categorised under Creative Apps, the Business Process Management, Project Maturity Model and so on. So you can just go in and check that, and see where you are. So I am building up from there based on what my users want, and Softools allows me that fluidity. I think organisations like Softools have quite a close relationship with the users. So the development tends to be focused on what the users want, not what technical people can do.
Softools: What are your tips for future app builders, those who want to get into it? And if you have a checklist or anything that you would want to give them.
Andrew Robson: Just Do it. Just go for it. Learn to fail, fail fast, and move on. The first one probably won't work, but take what you've learned from that and then just develop it and develop it. Don't worry about getting an excellent, perfect solution. You can't break anything. Nobody's going to die. If it goes wrong it goes wrong, do it again, it'd be fine.
Please sign in to leave a comment.