I rate the product's initial setup phase a seven on a one to ten scale, where ten means an easy setup phase.

The solution is deployed on an on-premises model.

The product's initial setup phase was straightforward.

My company has standard DevOps processes in place that we use to move updates from the development to the testing phase and from the testing process to production.

The initial setup is easy. Let's suppose you already know what you have to keep where, after that it's such a simple process that any average Joe who knows how to initiate his own service management can easily update the information and get working on it. It's not a big deal, and the installation gives you everything you need to get started with a guided setup such that anyone can quickly jump in and initiate ServiceNow. The way it is developed means that it's quite effortless for users to onboard themselves quickly and easily, simply by adding the required information.

As for the actual deployment, it's a matter of how you plan it. There are many implementations that start out according to the greenfield process. By greenfield, I mean arranging your environment from scratch and then introducing your company details, group details, UTI, and so on. Once that is achieved, you can easily add any other applications you want. And, of course, the internal modules such as discovery can be brought into your organizational scheme with even further ease.

The product's initial setup phase was a very straightforward process. My company didn't have to take care of any technical parts since it's a cloud platform. ServiceNow takes care of the product's infrastructure and everything else if users subscribe to such facilities. If you want to purchase some offerings in ServiceNow, you need to take care of the subscription part to be able to use them. Users can do their custom developments in the product. If I work for one of my company's customers who wants to do some customized development in ServiceNow Now Platform, then it can be easily done as it's a low-code platform.

I would rate the initial setup a seven out of ten, where one is easy, and ten is easy. Many clients are moving towards the cloud. However, some still use on-premises applications. With cloud deployment, most people use ServiceNow for discovery and other features while using an approval distribution server somewhere to communicate with the client.

The product's initial setup phase was a little complicated but can be managed.

I rate the initial setup phase around seven on a scale of one to ten, where one is a difficult setup process, and ten is an easy setup process.

In our company, the solution could be deployed in two months, considering that an out-of-the-box configuration feature is provided to users.

We deploy the product on ServiceNow cloud. The initial setup is not easy and includes a lot of integrations. It takes up to one year to complete. It requires six to seven engineers to execute the process.

The solution's deployment takes twenty weeks for completion. But you can start using it within twelve weeks. You would need an engagement manager, a business analyst, two developers, and a tester for the deployment process. So, it requires around a team of five executives for deployment, depending upon the deployment size.

I rate the solution’s setup procedure as a seven.

I would rate my experience with the initial setup a seven out of ten, with ten being easy for this product. 

Large enterprises prefer it within a private controlled instance. Various smaller enterprises are okay with a cloud instance. As controls improve and more people move towards the cloud, that's becoming the more typical deployment method.

The deployment time depends on the complexity of the use cases, processes, departments, and the size of the enterprise. It can range from a few weeks to a few months.

The product's initial setup phase did not have any issues as it is considered to be a strategic tool in our organization. From a finance-related perspective, for which my company chose the tool, we ensured that we carved out our own scope areas in the product as we have our own security measures and controls in place.

The solution is deployed on the cloud services offered by ServiceNow.

For the completion of the deployment phase of the product, a user needs to get the contract rolling, which may make the process tough since I feel that it takes more time internally in an organization as there are a lot of organizational compliances to take into consideration, owing to which many approvals might be required I can organizational level. After users get signed up, the deployment process doesn't take much time since they only have to set up the base structures to get things going in the solution.

The initial setup for the ServiceNow Now Platform was straightforward. It took one to two months to fully deploy the platform.

The initial setup is relatively simple, integration is fine but the UI holds the solution back somewhat. 

With five being the best, I wouldn't rate this solution any more than a three out of five for setup.

The initial setup is easy with most things being out of the box. Deployment took us two weeks.

The solution is deployed on the cloud.

The implementation of the process is very straightforward and simple. 

How many people you need for deployment and maintenance depends on if you are looking only for the base implementation. I'd say two or three people are enough to deploy the solution. It does vary based on the requirements of the project and customer, however, two or three people are enough.

The initial setup is straightforward. 

The initial setup requires a lot of customization based on the individual company's processes. I would say the setup process is medium complex and would rate it as three out of five.

I would say that from my point of view that configuring ServiceNow is pretty simple. But there are also a lot of things to consider. If you want to build a complex system, the configuration process can be complex as well. If you understand the software, you get a standard set of functionalities, but you can configure that for your own needs. For example, I had a situation where I knew a particular customer had some different requirements than what was provided out-of-the-box for the standard version. In this case, I was able to configure ServiceNow to match their needs. I can write complex scripts or I can do programming to build new processes within ServiceNow. But the implementation is different for every customer.  

How long the implementation takes becomes a very open-ended question because they have so much existing functionality already in the product that may need to be configured and the need for customization depends on the user's requirements. There are so many factors involved that I can not really define an absolute amount of time required for standard implementation. It depends on the use case. The basic installation of the application itself can be done in ten minutes and the solution can be made to be up and running within three months. However, if you want to have a complex, custom-built chain management process, it can take years.  

The solution isn't very user-friendly and is a very heavy lift for when you are starting and setting up custom setups. 

In terms of maintenance, our IT department is only so big. It does require maintenance in terms of customization, and that can be a lot. 

The initial setup is very straightforward and simple. It's not overly complex. 

I'd rate the initial setup a five out of five. 

The initial setup is straightforward. Because we are using the cloud version, we don't have to install it on the end user's machine; we just provide the URL and access to it.

We have a technology and operations team with 25 to 30 people for the global maintenance of the solution.

When we implemented and set up this solution for the first time, we did some customization. Now that we have adopted the Out-of-the-Box version, it means less customization. We are taking an "As-Is" solution so that we can use more capabilities for customizing it.

I rate ServiceNow nine out of 10 for ease of setup. We didn't have any issues. 

As it is Cloud Hosted solution, the initial setup is as easy as setting up an application on a mobile phone.

The initial setup is more straightforward than complex. If you want it complex, then you can do it. The main risk of such a product is that you can invent things that have not yet been invented. But, if you want to go straight from out of the box, you can do it.

It's some kind of an intellectual approach. If you want it out of the box, use it, and take advantage of all these standard issues. If it is already provided by the software, it's fine. From my perspective, this is the way it has to be implemented. It's quite straightforward.

Customers can install it by themselves and request implementation through an integrator. This is the way this product has been built.

The initial setup and deployment of the solution was very easy.

If you are familiar with this solution then the initial setup is straightforward. However, there are a lot of options so it can be complex. Some of our customers have found it unclear. It takes between three and six months to deploy.

I cannot comment regarding the initial set up because we had the ServiceNow team help us with it.

Although we wanted to use the out-of-the box features as assets, the processes in the organization were not that straightforward so it required some amount of customization and that lead to us having discussions with the team from ServiceNow. I cannot say that it was really smooth and easy. Because of the complex workflows and processes being followed in the organization, there were a lot of discussions involved, and a lot of customizations done. The ServiceNow team was able to give us a lot of insight, including where the improvement can happen, but then we couldn't add up everything, as the workflow is a bit complex and it involved other vendors.

The initial setup is complex but it depends on the industry. It's not just following steps, it's change management. You have to get it standardized. Overall, though, it's okay. 

The initial setup takes around a month, it's not a matter of days. It's a setup that can take time even if you know what needs to get done. In a larger organization, it's a major challenge. It will take more time to roll out.

The initial setup is very straightforward. Obviously, you need to know what you're doing.
There are a lot of courses and training required to deploy a ServiceNow platform effectively. ServiceNow administrators can do a lot, but there might also be niche products, like HR for example, that require specialized understanding.

If you're going with out-of-the-box settings and just configuring your system, then you can actually deploy it as early as three months. So, the deployment time varies.