Setting up K2 is very easy. Before you set up K2, there is a guide that you need to follow, which tells you what you need to do for a good setup. For example, for K2 setup, you need to have your email exchange or SMTP ready, and you need to have your URL mapped. 

There are certain things that you need to have ready before you install the K2 application on your on-prem service. We have documentation on our website that guides you on what you need before you can install K2. So, it is also easy when you have everything ready.

I think the initial setup is fine.

The initial setup was pretty straightforward. We had someone buy the license for us and gave us some prerequisites. Then we bought some license keys and it has basically started working. We have a portal where we can request more license keys as needed. It's easy.

We have two administrators handling the solution. 

The initial setup was straightforward but the customization of the system was time consuming. We started with a POC, worked in a test environment to complete customization and integrate with our full system and then pushed this to production. This whole process took two years. 

The initial setup is straightforward. It depends on the situation and the context of workflow. I take one or two days to complete the setup.

The configuration process with Nintex, especially when using the online tool, Fluent Cloud, is straightforward. While there is some initial configuration required, what sets Nintex apart is its excellent online help feature. Unlike some other platforms, Nintex provides not only articles but also a wealth of how-to videos integrated into the help section. This approach caters well to users, particularly millennials, who may prefer visual resources over traditional manuals.The deployment flexibility offered by Nintex is a notable advantage, supporting both cloud and on-premises models. In my experience, I have worked with both deployment options.

Presently, there is a discernible trend among clients, with a majority leaning towards cloud deployment. This inclination aligns with the prevailing industry shift away from extensive on-premises IT infrastructure. Many clients are actively seeking to streamline their operations and reduce the complexities associated with maintaining large on-premises setups. This shift is particularly evident in the financial services sector, where organizations are committed to leveraging cloud solutions to diminish their reliance on in-house hardware infrastructure. However, it's crucial to acknowledge that concerns persist, especially regarding incident management and disaster recovery. These considerations play a pivotal role in decision-making, prompting some clients to carefully evaluate the implications and safeguards in place for such scenarios.

The learning curve is different if you start working within Nintex. It takes some time to understand everything. But connecting other PCs to work with your processes is easier once you get through it.

The deployment doesn't take much time because we deploy it, make changes, and save it. We keep it for the later development cycle instead of redeploying it. We deploy the release once we finish the development, which takes a few minutes.

I rate Nintex's initial setup around seven to eight out of ten.

The setup process was not too hard or difficult to understand. It was acceptable since there were no technical issues.

The initial setup is very straightforward.

I have a development team of four people on safety.

The on-premises setup was fairly complex four years ago because we had to build the servers. You have to build test servers, staging and production environments, and all kinds of stuff. When you go for the cloud solution, you don't have to maintain any of those, which is why we are moving to the cloud solution. Our initial investment was quite a bit, and we're trying to move to the cloud solution.

The initial setup is straightforward.

The initial setup was straightforward.

The initial process was easy for me to execute. However, it is complicated for those who don’t have any experience working on it. We deploy the product on the Windows servers. The deployment includes planning user access management.

The setup is easy.

They have a well-managed three-tier implementation. It's very straightforward.

There's an integrated tool used during the deployment, and the process only takes five to ten minutes. The deployment tool makes it very fast and easy. 

You just need a team of five, maximum, for deployment and maintenance. You might not necessarily need a dedicated person to handle the deployment. 

The initial setup, as far as I understand it, was not complex. It was very straightforward. However, I personally didn't install it. It was installed when I came to the job.

Setup is simple and straightforward. There are a few prerequisites for installation, but the Nintex documentation for on-premise installation is solid and, if followed, the installation will run very quickly. It does involve some downtime so planning is required (several IIS resets during installation). However, it’s one of the easier things to install in SharePoint.

In Office 365, installation is as simple as installing it from the store and adding the app to the site collection, so could not be much easier.

The initial setup is straightforward because it can be deployed on a DB server, application server, and web server.

The initial setup was straightforward. During the trial, I had installed it myself. The installation was not a problem at any time.

The deployment and maintenance team is approximately four people. We have three environments, and four people handle the deployments and batch updates.

The initial setup was straightforward, with appropriate demos, documentation, and user manuals.

In the initial setup, I found there to be too much compromise in the cloud version. The cloud version is deployed in any environment with no problem. We did not install an optimized version for now, but I think it is not going to be complicated because it is on serval different SharePoints.

I believe the initial deployment took about three months. We used an integrator to help with that and it was successful. They provided some training for us so we'd be able to figure out how to do things ourselves. It was great. 

The initial setup is straightforward.

Compared to Nintex, Nintex is easier to set up. Unlike in K2, in Nintex, you can just build on top of SharePoint. If you want SharePoint, the environment is set up and can install directly in Nintex. In K2, you are configuring two environments. 

We are part of a technical team and we have the expertise, so the initial setup was not complex for us.

Setup is easy in standalone. Distributed setup is complex and requires more network knowledge.

The initial setup is very easy, it doesn't take too much effort to install if you know what to do. Setup time depends on what you do. For example, you can get up and running and make the system worthwhile within one week or it could last two or three months. This is a complicated question.

Largely, the initial setup is straightforward. It's not too complex.

The deployment of the product takes two or three days. In terms of the workflow, it can be implemented in about one week. Overall, you can go live within two or three weeks.

The initial setup was absolutely complex. It is so difficult to configure the previous versions. But in the new version, the installation has improved and it was much better.

With the initial setup, most of the cases are straightforward.

The deployment and implementation are done ourselves.