What is our primary use case?
We use Anaplan as a retail budgeting and planning solution. We use our retail private-based planning solution for almost one hundred entities. Anaplan is a cloud-based solution.
We have integrated SAP with Anaplan because our base is SAP. Anaplan doesn't require any coding language. It's very Excel-based with respect to the models, so a user should be very strong in modeling.
How has it helped my organization?
Anaplan is a driver-based solution. For a finance-driven project, the business inputs the revenue or the expense lines, which is directly connected to your financial statements and further integrated to your core systems for your consolidation of other things. For example, with store planning for new stores, it calculates the ROI.
What is most valuable?
It's real-time connected planning, so the calculations are pretty much seamless as far as your model is connected. That's the major advantage, and it's cloud-based and very UX friendly.
What needs improvement?
There are workspace issues, like the limitation on model sizes. The model is very limited to 130GB, a base model. We were one of the use cases to go beyond 130GB for a model size. So it's not enterprise-wide. Performance is quite weak if there are concurrent users. In the next release, I would like to see performance improved. It can't handle concurrent users because of the way it's designed.
Integration is not that strong. We use a connector called Anaplan Connect, which needs a lot of interface to work on.
License cost is quite huge compared to the other solutions we ran in the market. It's too costly for SME businesses.
For how long have I used the solution?
I have been using Anaplan for three years.
What do I think about the stability of the solution?
Anaplan invests a lot. In the past year, there have been a lot of developed features. They have spent a lot of time on R&D and pretty much every day, every quarter, or every 15 days they do an announcement pack, and every month I see new features coming in because they have made a lot of improvements.
But they have also made a lot of improvements that might not add value to us. However, I like to see more and more as we get into new business cases. Within a month, there could be 10 to 15 improvements, and not all will be useful for us, but from a product strategy perspective, it's good. From a business point of view, we use maybe one or two developments because of how we have developed it earlier.
What do I think about the scalability of the solution?
They have restrictions on the space, so scalability is currently limited, but they are working on that because they are trying to make it wider.
We have around 300 people using Anaplan in our organization, and they have a category of users to work on. Model builders manage the model and there are also planners and then reporting users. We have a wide range of users, like IT consultants, who are on the lead level. I lead, but I also do hands-on. There are developers and then FP&A professionals, and I have brand managers and finance managers who are doing the reporting.
Our entire retail division is on Anaplan for FP&A solutions. Every business is using it. Once you get in, you can't come out because you have replaced your traditional way of planning using Anaplan, so pretty much all users are bound to use it. From a scalability point of view, our organization is quite wide with respect to divisions, like retail. We brought treasury in for cash flows. We are working on real estate and probably will go with automotive soon.
We are thinking that our numbers will increase to around a thousand plus. The reporting is quite huge because that's the cheaper one in Anaplan. With planning, you will be reaching around 400 plus because it's not financial alone; it's business cum finance, so it's a wide reach.
How are customer service and support?
They are very customer oriented. You get your responses very quickly, and their turnaround to fix problems is also very quick: around four hours. They don't have any kind of portal, but they are building on it. It is all through mail communication. Once you send something, there is somebody immediately supporting you 24/7.
They have a huge documentation space for troubleshooting. Because it's a very small solution with less customization, it's more about your thought process and they have forums to help you out based on user experience. From a technical side, it is very easy to understand. But to do the customization part you need someone for support, and the forums are helpful.
Which solution did I use previously and why did I switch?
We have business planning and consolidation SAP BPC. It's primarily a financial-driven tool because you just do it at a high level and collect information as a data dump. You don't have any driver-based solutions that extensively in BPC. We went with Anaplan because our focus was on driver-based solutions and cloud strategy.
The solutions are completely different because the other solution is purely an Excel-based solution, a native product, and is much less driver-based. It was very finance-focused, but Anaplan is quite a different strategy for us.
How was the initial setup?
It's very straightforward actually and much more user friendly. A business can run it, and I learned Anaplan during this course.
Normally, the deployment shouldn't take more than three to four months for simple usage. For us, we took around six months because of the user adoption, which is a hundred plus entities. The six months included the customization and testing.
What about the implementation team?
It's a top-down approach. Basically, you go to the end to see what you want and work backward to the calculations and data.
What was our ROI?
Right now, we haven't seen any ROI from using Anaplan. With the current solution, we are trying to make that work because that was our first learning. When we thought it would reach to business, we struggled to establish the finance itself. When it reaches to business, you get the ROI. If it doesn't reach to business, it is just another tool where people just upload data. We got licenses and we pretty much use them for different focus areas. We have had success in a few cases, but we haven't gotten the full ROI, which is what we invested initially.
What's my experience with pricing, setup cost, and licensing?
The license is a yearly subscription. There are three licensing tiers: the model builder, planner, and the reporting. The reporting is the cheapest. Model builder is the costliest one. Depending on the type of license you buy, you get more spaces to work on.
There are some additional costs to the standard licensing fees. For example, we go with the extended workspace ISIS. For that, they charge for model optimization if you are below the premium customer level, so we were having more licenses. We are in the premium level, but if you are below premium, they charge for your model optimization, or they charge you if they want to investigate something on the licenses.
What other advice do I have?
I would rate this solution 8 out of 10. There is still room for improvement because of the integration issues.
If your strategies are more toward driver-based solutions and if you have a very lean implementation approach, Anaplan is the best solution you can get. If you're okay with spending lots of money and aren't SAP-bound, Anaplan is the best in the market right now.
Which deployment model are you using for this solution?
Public Cloud