Every enterprise CMS evaluation I've sat in eventually stops being about features and starts being about four questions. Drupal answers all four out of the box.
Who is allowed to change what. Roles, permissions and editorial workflow are core, not an add-on. A translator translates without touching structure. A junior editor drafts but cannot publish. That's configuration, not custom code, and it survives staff turnover.
Does the content survive the redesign. Content in Drupal is structured — fields, entities, relationships — not a blob of HTML pasted into a WYSIWYG. When the design changes in three years, the content doesn't have to be re-entered. That single property has saved more budgets than any feature on a comparison chart.
How many languages, and how badly. Multilingual is first-class: interface, content, configuration, per-field translation, and a workflow real teams can run. Most platforms bolt this on, and it shows the first time someone audits it.
What happens when you want out. No per-seat licence, no vendor who reprices you at renewal, no proprietary format holding your archive hostage. The code is yours, and so is the exit.
None of this is exciting. It is exactly what a platform you'll still be running in ten years is made of.