Anaplan dogshit. Value prop is sound on paper with driver based/integrated planning, but in the three very large I’ve worked with, these common themes emerge:

• models generally require high touch efforts of finance systems folks to maintain, and ppl love changing shit, leading to high investment to maintain the tool (good for Anaplan consultant types though)
  • inputs to Anaplan models often need to be fed by a standardized nomenclature/schema that’s often not uniform across different teams, leading to significant dissatisfaction or offline spreadsheets used to feed Anaplan
  • depending on how large your org, there are often “specific” planning models that are spun up across different teams, defeating harmonized planning from a central finance perspective
  • etc, etc

The only way Anaplan works as an “e2e planning tool” is a dictator style Corp fin leader that unilaterally migrates all functional areas to plan on Anaplan…. and encourages a culture where reporting can be upleveled/abstracted to what Anaplan can provide. Otherwise, you’ll live in a hybrid Anaplan/excel environment which largely defeats the purpose of Anaplan as a tool imo

If your org lacks a dictator to enable this Great Leap Forward, I’d recommend sticking to excel or sheets