Anaplan is used for FP&A, and we are currently working on CAPEX and P&L Signify. Whenever the year comes, there are usually healthcare benefits planned, which I work on for a client, CVS Health.
There are projected, budgeted, and forecasted items, and based on that, the dashboards are projected with different schemes of healthcare. The team plans accordingly to arrive at the best possible ways to provide for the customer and how revenue is generated. The dashboards consist of a P&L, balance sheet, and other financial dashboards that we prepare.
About my main use case and how my team interacts with Anaplan, we first go through the development phase based on user stories and client requirements. Some other teams handle the development part while the integration team switches on. Once the development is done, we deploy it, including tests and different functionalities we use to test. If we find any functionality defects, we raise another ticket in Rally for resolution. Once the defects are fixed, we retest the functionality, which includes UAT and production testing before moving it through synchronization to live production.
Anaplan offers various optimization aspects, enhanced dashboards with new features in the front end, and flexible optimization capabilities that provide enriched functionalities with time releases.
The recent enhanced functionalities that made the biggest difference for my team are the Hypercare functionality, which allows for quick resolution of any issues arising from enhancements and implementation tasks. It provides optimization in a better way before upcoming features. Hypercare is an enriched functionality in Anaplan that landed last December and January 2026.
Anaplan has positively impacted my organization by reducing the coding work involved by developers. It increases work flexibility and enables a better division of tasks among testing, development, and implementation teams. With page administrators looking into technologies, the integration takes data from legacy systems and integrates various systems, offering a broader scope than prior systems.
Specific outcomes that show how Anaplan has helped include saving time through integrating large data from AWS directly via CloudWorks. It also reduces the time for scheduling and running reports. Once scheduled, it runs on specific days or times, allowing for month-end closings without manual intervention unless there are bugs or formatting issues. Overall, it works smoothly, enhancing time efficiency and quality levels with an automated data hub.
Anaplan can be improved, particularly regarding latency issues when running deployments that may cause the system to hang. Reducing latency during huge data imports is necessary, as server hang-ups can create significant problems. Cleanup at the Anaplan level for any unwanted data and addressing latency issues could ensure uninterrupted services.
Regarding needed improvements, the user experience has some bugs, particularly with fields involving production and structural data. Data loss happens when redeploying a specific choice, and preventing this would require additional features.
I have been using Anaplan for the past four years and beyond.
Most of the features are repetitive, and the existing functionalities are enriched, so there is not much to add.
My advice for others looking into using Anaplan is that it is portable, and I recommend exploring its flexibility and integration capabilities with existing and upcoming software applications. It is beneficial to analyze the cost advantages as Anaplan connects all databases and applications, both internal and external.
Anaplan is good as of now, but I think there should be exploration into different business areas where it has not been implemented, especially in smaller regions such as the Middle East and Asia-Pacific, based on my observation. I would rate this review as a positive assessment of Anaplan's current capabilities and potential.