What is our primary use case?
It can be used for FPNA, forecasting, and planning. It can also be used from a tax point of view and an allocation point of view.
What is most valuable?
It's highly flexible. If you've got a complex environment with complex calculations, you can build that out. So that's a really good positive.
Because of that flexibility and ability to build models in the way you want to build it, it means you can tailor it to the company's requirements. You can really tailor it, which is the big positive with Anaplan, and the fact that you can track what everybody does. There are more constraints within SAP and Oracle than in this kind of product.
It's like Excel but with a mix of VBA, and it's a bit more controlled. So you have, from a client's point of view, an internal/external audit trail. The audit trail logs absolutely everything you do. That's really useful when people build out these models for it because you want to know what people are doing. It's very difficult to do that in Excel. So it's like Excel, but a more controlled version of it. You are using formulas and you build it out with formulas.
Anaplan can be easily deployed and scaled.
What needs improvement?
The negative is that the higher the flexibility, the higher is the complexity. That can act against you as a negative because it does require a model builder or a coder/developer.
It's not something that can be easily learned. It's a full-time job for someone who's a kind of specialist. Once you've learned it, it's great, but it does take a few years to build that knowledge up.
Any integration or interfaces into it and out of it can be hard, depending on the client and the tools available.
As additional features wise, if it could be more intuitive, it might be helpful.
For how long have I used the solution?
We're in the midst of implementing it.
What do I think about the scalability of the solution?
It's very easy to scale. It's not that hard. However, the cost can go up depending on the volume.
Which solution did I use previously and why did I switch?
The client's previous software was less flexible, more clunky, and didn't give them what they wanted. Anaplan has been more flexible, more streamlined, and gives them what they want. If they want X, they get X, and they don't get Y instead.
How was the initial setup?
It can be deployed quite quickly. It would take about three to six months.
You can have both external support or internally trained support, and the maintenance can be either. The software itself, because it's cloud-based, will get automatically upgraded. It's software as a service.
What about the implementation team?
Staff wise, you would need a PM. Depending on the number of models being built, you will need one or two model builders. One model builder per model is probably the expectation. You need to have a subject matter expert and an architect involved. You will probably need four staff members at minimum for deployment.
You can have both external support or internally trained support. So the maintenance can be either, but the software itself, because it's cloud-based, will get automatically upgraded. It's software as a service.
What was our ROI?
It's going to give the clients what they want, so the return on investment will be pretty rapid. They could expect a return on investment within the first year.
Which other solutions did I evaluate?
What other advice do I have?
It's a good product, but you need to consider whether you need a center of excellence in-house. You need to consider process mapping, the standard operating procedures that you would produce with it, and the integrations or ETLs, and your interfaces, inwards and outwards. You need to be very clear about your business requirements and know exactly what you need, in terms of your inputs, the calculations you need to run it through, the outputs, and the end results that you would provide to the client, along with the master data/static data.
If you're not clear, then you can't implement it, and you'll just waste money with the developers, the model builders, and the consultants that you're dealing with. However, if you're clear about it and you can provide clear examples of what you need, then it works like a dream.
It takes a long time for a beginner to understand what's going on. You need to make sure that the developers that you use or the model builder you use puts copious notes on everything, especially at the back-end from a technical point of view.
Then at the front-end, with dashboards, you need to make sure that there are lots of good quality instructions, operating procedures, and process maps.
On a scale from one to ten, I would rate Anaplan at eight.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.