See the portfolio. Know what needs attention
See what is moving across the portfolio, where attention is needed, and the evidence behind it — without assembling the picture by hand.
Start with what changed
See which properties and commercial signals stand apart, so your time goes to the questions worth asking first.
Go from the signal to the conversation
Narrow from the portfolio to the property, then open the interactions behind the finding — without asking teams to reconcile it for you.
Less time assembling the picture. More time deciding what to do
The portfolio stays comparable, the local context stays intact, and the evidence is there when someone asks why.
See what needs your attention.
See what becomes visible when you can move across the portfolio and follow the signal all the way to the evidence.
No. Most groups start with one or two and add the rest. A property measures consistently from the point it connects, so comparisons become available as the portfolio comes online rather than requiring a coordinated launch.
That is normal at a group that has grown by acquisition, and it is one of the reasons this works. The measurement layer sits above your systems rather than depending on all of them being the same.
Also normal, also handled. Reconciling context across systems is one of the harder problems this solves.
Only if you decide they should. Access is set per property and per role. A property team sees its own operation; cluster and group roles see across the portfolio.
They connect and start measuring the same way. No training program to run, nothing to keep in sync.
It depends. Anana can be the primary commercial intelligence layer for some hotel groups, or complement an existing BI stack for others. The right setup depends on what your team needs to measure, investigate, and report across the portfolio.
