This is a scalable product. Because it is on the cloud, lots of people can connect to it and there is no problem with growing the number of connections. If you want, you can even add a mobile app now. Previously they didn't have a mobile app option.

Remedyforce's scalability has some limitations and because of that, it is not going to fit in most large enterprises. However, very large companies are using the product with success. For example, Carrefour is a very large grocery chain something like Walmart and they are using Remedyforce.

There are reasons to use Remedyforce and it is okay for big clients. One of our big clients is the Al Tayer Group. They are a dealership for expensive luxury cars like Range Rover, Ford, and Ferrari (the real Ferrari). The number of actual users is small, but the amount of business they do is huge.

I have a meeting, a new project coming up with Al Ghurair Group. Retail groups love this product because it is very fast but not expensive. Forpen is another big enterprise and they are using Remedyforce heavily. They are treating it as a large enterprise solution. The product works for them for now because they did many things on top of it to make it work. Really they are paying more than what it deserves to put into it. Sometimes you might own a Toyota Corolla and you keep enhancing it to try to make it work like a Ferrari. Actually you are wasting your time and resources on it because the solution you need already exists. Go buy the other one you want because it is better for you. It may feel harder to switch than it actually is.

Can you scale it? Yes. But doing it may not be a good business decision. There comes a point where there is no point in enhancing the product more. For some of the clients in the UAE, change is hard for them. They think that they already have a solution that they know how to use and they are happy with it. They think it's a headache to change and switch and get used to something else. It is also not always easy to go to procurement to finance a change. You need to justify why you need to change a product and defend the expense.

We have not expanded the solution beyond an originally estimated number of users and the use cases that we had originally estimated. We've basically stuck to the original business case and therefore, we haven't had any significant scaling challenges with them.

There are about 8,000 users that are on the solution in our company.

The solution is quite easy to scale, however, it does depend on the license. If you want to scale, you need to move to a new license tier.

The solution isn't scalable.

In terms of scalability because of our own existing infrastructure and our own unique support model, it's bit difficult. It's a challenge we're facing currently. Right now, we're wondering if we should continue with this solution or move over to ServiceNow, which may make scalability easier for us. ServiceNow is on the cloud. We're looking at options and whether we need to move onto the Helix platform before moving everything into BMC ITS and then migrate back and move all of the integrations to Diago.

Currently, we have in the ballpark of 5,000 users.

If a company needs to expand the solution, they are able to do so. It is quite scalable.

As we added more custom configuration, we started running into SOQL errors, which could not be resolved yet.

No issues.

I've found the solution to be scalable. I don't think an organization would have trouble scaling.

There are two or three other people using the solution in my organization, so there are three companies that currently use Remedyforce.

Remedyforce is pretty much scalable. We have about 4,000 employees who use it in our organization.