Anaplan vs. Jirav

With its versions and native time features Anaplan is well suited for all activities around planning in time and scenarios. Tasks involving calculating across multiple dimensions make Anaplan shine - the easiness to build complex calculation and present results on customizable pages. With its access restrictions it's well suited also for working with sensitive data (employee and customers personal data).

I feel that Jirav would be best suited for companies with less than 75 employees that need a more robust software than Fathom (Quickbooks Onlne integrated FP&A tool based in Australia) that is very customizable, with simple revenue modeling, few personnel changes every month, few departments, no multi currency, and need collaboration only with top-level personnel. I think Jirav is a product that is being highly recommended in the accounting industry for outsourced accounting firms, but accounting only looks at historical information and there needs to more finance industry influence, approval, and input so they can improve their product.

• Anaplan removes the time consuming process of integrating the results of individual spreadsheets.
• Anaplan facilitates the standardization of assumptions across all sub-processes
• Anaplan provides full transparency of the calculations and source inputs
• Anaplan allows us to automate certain planning processes that would have been impossible when relying on the computational capabilities of an individual computer.

• Jirav integrates well with Quickbooks Online (QBO), and I like how you can easily customize the reporting presentation by combining GL accounts and showing more or less details as needed for managerial reporting
• I like that Jirav is browser-based and that I can easily share reports with internal and external parties for comments
• I feel more confident using Jirav than I do with Excel because there is more data validation, and some notifications will appear if there are errors in the model
• The sales capacity model and ramping employees schedule that their implementation / professional services team built for us works well overall (with some limitations)
• Ideally, having a direct integration into Jirav would be great for all our data. However, some of our software didn't have a direct integration, so I was glad that Jirav offered the ability to use a connected Google Sheet that lets me input data that can be imported directly into the system

• Some end users don't spend the required amount of time to familiar themselves with Anaplan.
• Auditability, while good in theory, can be lacking and clunky when needed.
• Model building can become convoluted over time, leading to confusion over the specific use of line items.

• At times, I feel that Jirav is too customizable. It would be great if they could tailor the system to be more industry-specific. For example, if the system could provide standard formulas for SaaS industry metrics already within the system, then that would have saved me a ton of time with having to create the metrics myself. The formula creation for metrics is quite tedious as well because you can only do simple calculations, such as A + B or A x C. You cannot do A + B + C or A x B x C.
• I struggle with the way they have their staff planning set up because I have to reimport an Excel every month with all the changes (new hires, terminations, pay changes), and the changes appear to be retroactive on reports, which doesn't make sense if someone receives a raise or pay change during the year. It would be much easier for planning for bookings if they could add a column for quota by salesperson.
• If there are notifications of errors in the model, then the notifications will continue to present themselves after I resolve the issue. It would be nice if I could clear out notifications I know are not relevant anymore. I also still find errors in the system that I would have expected the system to notify me about, such as Assumptions that are set up but they are not included in any formulas, so I should delete that assumption to prevent anyone from thinking changing that assumption will impact the model.
• There is some functionality for sharing reports and information, but there is not enough granularity in security settings to allow me to share certain information easily. For example, if I want to share information with managers to manage their departments' budget, but also not see their boss' compensation, then it takes some work to set that up. Or, if I want to share a report with a recruiter of planned headcount and salary, then I need to export it to Excel first and delete Actual headcount and salary, so they don't see current employees' compensation (including the person's boss' salary).
• Customer and vendor names do not import, only the totals, so if you look at Actuals vs Plan, the actuals will show a total figure and the plan will show detail, creating the need for an external and manual reconciliation
• There is no multi-currency available
• Scenario analysis can be difficult to do quickly. For example, if I want to see the plan with planned hires and without planned hires, then I would need to create two separate plans, individually select and delete the planned hires in one plan and keep then in another plan, which is time-consuming
• Using Google Sign-In causes the system to time-out frequently for me, so I get kicked out of the system and have to log back in. If I have multiple tabs of Jirav open, then re-logging in sometimes doesn't bring me back to where I was originally at.
• You can export reports to Excel, but there are no formulas of the calculations, which makes it more difficult to understand how calculations are being performed unless you look in the browser and dig into the calculations. This also might make it more difficult if you decide to go to another software in the future since you may need to start from scratch in the next software
• Seasonality has been difficult to model. For example, the way our model is set up, I can use an assumption for Q1, Q2, Q3 and Q4. However, if I update Q3 for this year, then it also updates Q3 of all subsequent years, which I don't want. A more complex model and additional maintenance would be needed to accomplish more accurate seasonality planning

Anaplan is a very strong multi-dimensional modeling tool that provides a calculation engine to empower a complex planning process. It is fairly easy to learn for those with experience in similar tools, or excel. It forces structure and auditability that spread sheets do not have, along with extensive security capabilities

Anaplan's usability is dependent on who is implementing the project and how clear business processes are at the beginning of the implementation. Complex business processes with many inputs and reviews will still be complicated in Anaplan; however, the UX is very flexible in how to help people through the process and there are also other items such as Workflow that can help people move through the system.

There are very few outages. Maintenance is scheduled on two or three Saturdays per month, so as not to affect businesses. When there is an outage, users are kept informed of progress to restore the platform and typically this takes no more than an hour. Anaplan customer support is very responsive if we ever have questions about platform issues

Everything is calculated in memory in the cloud. It's nearly instantaneous updates when you make changes. The only time things get a little slow is when you have a massive model with very intricate calculations...but "slow" for Anaplan is not what I would call "slow" for something like Hyperion. We used to have Hyperion calcs that ran for 60 mins before you could use data. The equivalent would be 60 seconds in Anaplan.

Incentivized

Support quality has dropped since Thoma Bravo has taken over. I think some serious re-focus needs to happen here -- part of the beauty of being in the Anaplan community was how involved you felt in it before. Before I didn't dread sending a support ticket, now I am starting to.

In my opinion, in-person training is always the best if you have the option to do so. This allows real-time interactions with the instructions, whereas the online training I took required me to write-down questions, email them, and wait for responses. This slows down the process, as you can imagine. That said, in-person training is an extra cost and it likely isn't needed for everyone. I would suggest selecting a small number of people to take in-person training and then having them act as mentors to the rest of your team. That way, as the rest of the team takes the online training, they have a resource to help them in real time.

Anaplan training materials are clear, simple, easy to understand and to follow. Visuals are excellent. The vendor is good at updating training materials in a timely manner and encouraging users and administrators to keep coming back to Academy site for refresher courses or new feature courses. I really like their interactive diagrams

One key insight from implementing Anaplan is that success comes from focusing on designing the process, not just building the model. Anaplan is extremely flexible—there are very few planning scenarios it cannot support—but that flexibility means the project needs strong governance, clear ownership of requirements, and a well-defined data model. When those foundations are in place, implementations are fast, iterations are easy, and users can quickly see value.
In our projects, both Financial Planning and Integrated Business Planning models were adopted smoothly because we involved business users early, kept the model design intuitive, and leveraged Anaplan’s Excel-like syntax and user-friendly dashboards. The result was more efficient day-to-day work, reduced manual tasks, and increased collaboration across teams. In short: when you combine Anaplan’s flexibility with a structured implementation approach, adoption and value realization happen quickly.

Anaplan is more powerful than Pigment considering that it is an Enterprise class system and is able to manage bigger data sets. Anaplan allows for advanced scenario modeling and formula capabilities along with custom reporting functionalities. Anaplan has proven its capabilities and stability across various use cases and across bigger enterprises when compared to Pigment which is still in earlier phases of its development

Fathom was the cheapest and most basic as an add-on directly to QuickBooks Online Plus, but you lose functionality with Fathom if you use QuickBooks Online Advanced (QBOA). The main loss of functionality for me was the lack of multiple department reporting, which was absolutely necessary for my analysis. Jirav was half the price of Moscaic.tech, but I've heard Mosaic has standard metrics for the SaaS-industry, which is appealing after going through the tedious process of setting up metrics in Jirav. QBOA has additional reporting than QBO Plus, but not enough robust features for planning and modeling. PlaceCPM is Salesforce-based and a I felt having a strong Salesforce admin that can great reports made their unnecessary, and I feel like most of the time you need a Salesforce admin just to run Salesforce. Cube, Vena and OnPlan are spreadsheet-based, but I don't want to use spreadsheets. Prophix, Board and Anaplan seem outdated. Workday was more than what I needed

We have managed to leverage Anaplan for financial planning and forecasting across the business. It is now used by almost every department, with more than 50 users (but I know of companies that have hundreds of users) and still the platform is quick and reliable. It is easy to make changes to divisions and departments or add users and apply different user settings - the core part of the model is not affected and end users can continue their work without any disruption

• Anaplan's implementation led to a significant reduction in planning cycle errors and bugs, streamlining processes and improving overall accuracy in data inputs
• Standardizing the planning process and enabling cross-functional collaboration through Anaplan enhanced our ability to adapt swiftly to changing business needs, resulting in improved agility in decision-making
• The platform's capabilities, especially in Demand Planning and Supply Chain, positively impacted our ROI by optimizing resource allocation and solving complex business problems efficiently across multiple functions

• 1-3 day shortening of post-month end close analysis from integration with our accounting software
• Elimination of several manual Excels related to headcount variance, salary variance, and planning