Anana
Sign inBook a demo
Anana — where AI meets hospitality
HCP — Hospitality Context Protocol→
Coming soon
Anana free tools
Free Tools→
Purpose-built tools for hospitality.
Research
Research→
Original findings on hotel demand and AI discovery.
Blog
Blog→
Ideas and analysis for modern hotel commercial teams.
Hospitality Commercial Intelligence

See demand earlier
Know what moves it

Built for
CCOs, DOSMs, CROs, CMOs
Park Hospitality Group
Week of Apr 14 · live
— This week, across the portfolio
Demand shifted to Thu–Sat. Spa staffing clustered into a pattern. Group pipeline climbed 18%.
Demand
Pickup shifted from Tue–Thu to Thu–Sat.
4 properties · booking window +2.1 days
Operations
Spa staffing complaints clustered around weekend peaks.
2 properties · 18 of 24 after 4pm
Groups
PREV
THIS WK
↑18%
Group pipeline climbed 18% week over week.
3 properties · $1.2M in play
Synthesized from 3,412 guest messages · 189 rate checks · 417 calls ⌘K
the problem

You already paid for the demand.
Most of what it tells you disappears

Traveler intent appears before the booking — across AI discovery, calls, chats, and emails. Most hotel systems keep the transaction, not the signals that explain it.

Commercial context
Signal Family travel
Requirement Connecting rooms
Context Destination discovery
Measured from tracked traveler questions, not individual search history
Commercial context
Occasion 70th birthday
Party Multigenerational
Opportunity Arrival experience
ChatGPT tracked question
“Best Punta Cana resorts with connecting rooms”
voice
“We’re traveling for my father’s 70th birthday.”
chat
“Is the spa open late on Saturday?”
Perplexity tracked question
“Best Caribbean resorts for a multigenerational family trip”
chat
“Do you match the rate I saw on Booking.com?”
email
“Can you hold 18 rooms for October?”
voice
“One of us has limited mobility. Are the rooms close to the elevator?”
email
“We’re choosing between your property and two others for our wedding.”
Commercial context
Concern Rate parity
Risk Direct-booking friction
Context OTA comparison
Commercial context
Demand Group
Requirement 18 rooms
Timing October
The Solution

One workspace, the entire commercial function. 

01
One thread, every source

Ask across bookings, calls, market intelligence, and your own SOPs in the same thread. The workspace remembers what you looked at yesterday, what the team decided last week, and where the numbers came from.

Multi-turn threads with live data
Knowledge bases per team
Shared history across the group
02
Investigations, not alerts

When pickup softens, an RFP arrives, or the same complaint shows up three times, Anana investigates and writes it up — structured finding, recommendation, and the full chain of tools and sources it used to get there.

Triggered by calls, CRM, or schedule
Filter by status, category, property
Auditable end-to-end
03
Portfolio in one view

Flip between the group view and a single property. Give the revenue team portfolio-wide context, give each GM their own property, and keep the commercial function working in the same workspace.

Per-property visibility controls
Granular role permissions
Designed for cluster leads
The workspace

Ask a question. Sense the portfolio. Act in the tools you already use

Park Hospitality Group · one session
live
The question
for Revenue + Ops
Reading
reading weekend pace at Park Lane NY
checking group block for Fri–Sun
cross-referencing the event calendar
pulling spa + F&B staffing plan
comparing to the same weekend last year
Anana
Pace
On track at 82% occupancy. Fri is tight; Sat has a soft pocket.
Groups
A 40-room block for a private dinner on Sat — no F&B overlap with the ballroom.
Watch
Spa is two therapists short on Sat. Last similar weekend generated 31 walk-ins.
1 of 4
Get in touch

See your workspace on your real data

— Ships on your portfolio, not a sandbox of ours.
— Lives alongside your PMS, CRM, and telephony.
— Founding-team implementation, no account managers.
We read everything. Reply within a day.