The product's initial setup phase was easier compared to Siemens but difficult compared to Salesforce.

The solution is deployed on the cloud as it is a SaaS application.

The initial setup of Studio Creatio depends on the user's knowledge. If you compare it to OpenText it is much easier to install. However, if you compare the installation to other low-code solutions like Bubble, it is much more difficult. 

In some cases, we provide the solutions for records management for deep or hard requirements like archives. When a customer has large amounts of paper, it is a very difficult tool to set up.

In a fairly large company, we use a team of four analytic consultants and two developers to deploy the solution.

Our projects are usually based on three-month timelines, after that, we continue to provide management services. We do not just set up, finish and forget. 

Its initial setup is very easy because Creatio solutions are complete. The companies just need to parametrize some data, such as company name and logos, and integrate the email and calendar. They have tutorials on how to implement Creatio. It is very easy to set up if you follow these tutorials. You can have a ready-to-use solution in a couple of weeks. If you need some specific customization, then it would need more time, but it is not very difficult because the resources that Creatio provides for this purpose are very useful.

We had a team-setup approach. We originally did an onsite box that we had full control over. We had access to the servers and all the source code, etc. We ended up changing route and went cloud-based for a lot of reasons. Since the time that we went to cloud, they've made a lot of feature improvements and functionality improvements. The improvements streamlined the development process to aid maintaining and upgrading the production site efficiently and correct.

In terms of how long the deployment took, we built the foundational pieces first. Part of our infrastructure, how we manage users in general, requires Active Directory. We had built out that piece in bpm as our first steps towards integration, to be an automated system. It took about four or five months to really start using it to a notable degree.

For the first thing we technically rolled out, the time-off request, it took about a year, but I don't know how much of that would be bpm's issue and how much of that would be ours. We had other business processes running in the background that helped keep our infrastructure aligned. 

There was a huge learning curve initially. If you use the out-of-the-box experience and you don't plan on doing any customization, it could be implemented quickly, and a lot less painfully, than we did it. The fact that we tried the onsite solution first, instead of going cloud right out the gate, added time and complexity. I have a couple of complaints about the cloud where we do not have access to the source code, but I would recommend to anybody that they go cloud. It's just better.

As far as our implementation strategy goes, we really needed to hit the foundational level first: Our employee management, the Active Directory, the housekeeping which keeps the company up and running. We identified all of those milestone points of the process, implemented those in bpm, and then kept it up to sync with our other external software solutions.

That foundational piece was running before we went live three or four months later. We wanted that foundational piece laid and set in stone. 

The initial setup was very simple and straightforward. 

The tool itself is very intuitive. 

Once you follow the steps on the screen, you are able to get into it very quickly.

We have one and a half dozen people to maintain this solution.

On a scale of one to ten, where one is low and ten is high, I rate the setup phase a five since we are in Africa and we are the sole providers of the solution in Africa. It is important to note that I am speaking about external deployments.

The solution is deployed on the cloud.

Around five people were required for the deployment.

The deployment took around 20 odd days to be completed.

It is very easy because I have been working with Creatio for many years. For me, it is not difficult to implement. It is very transparent and easy to implement. The deployment took less than three months.

The solution does not need to be installed if you have the cloud instance, you enter a URL and you are ready to use the solution.

The initial setup was straightforward. Easy projects take about a month to deploy. Moderate projects may take about two months. It only takes about two people to deploy and maintain the solution, although it does depend on the size of the project.

The initial setup is straightforward and can be done within a couple of weeks, including the data import. You need three people to deploy - one on production, one on DevOps, and one who knows the software.