AURI runs every spa in your estate the same way, then rolls the numbers into one view. Compare properties, catch a weak one early, and run the portfolio as one operation.
is the spread in spa capture across property types.
City hotels capture 3–8% of guests, resorts 8–12%, destination spas 20–35% (Intelligent Spas, 2019). A mixed estate lives across that whole spread. No rooms report shows where each property sits.
One missed €120 treatment a night is roughly €3,600 a month at a single property — illustrative arithmetic. Multiply that by every property below the line.
By the time a weak spa shows up in the quarterly figures, the quarter is gone. Early warning takes a portfolio view.
You prove the standard at one property first, then scale a known quantity.
AURI stands up at one flagship property on its own dedicated instance. Our team handles the setup end to end — managed work on our side, not an IT project on yours. You run it live and settle the standard there.
Each property comes online to the same deployment: the same booking flow, screens, and definitions. Staff move between sites without relearning. A mixed estate is fine — each property connects to its own PMS and posts spa charges to its own folio.
The dashboard picks up each property as it lands. The whole portfolio sits in one place — comparable from day one, no logging into each site.
AURI connects to the PMS each property already runs. The connector matrix and per-PMS notes live on the Integrations page.
A read-only dashboard collects fresh numbers from every property every five minutes, rolled up in one place.
Software is the cheapest lever an estate has — no build-out, no added headcount, just the demand each property already hosts.
AURI takes no cut of bookings — a flat fee, not a commission. Every property keeps the full value of every booking it captures, and across a portfolio that compounds. The full commercial model is on the Pricing page.
Each property runs its own single-tenant instance. The roll-up is metrics only, never a shared guest pool. Any site can be extended as custom work in the scope of an implementation. The architecture is on the Technology page.
For a group, the natural way in is a flagship pilot. We're selecting a small number of founding partners, with setup waived for the pilot. You prove the standard on one property before the estate commits. Read the pilot terms
No — the roll-up is metrics only. Guest records stay in each property's own instance; the group dashboard reads KPIs, not guests. The architecture is on the Technology page.
Yes — a mixed estate is fine. Each property connects to the PMS it already runs, and spa charges post to that property's folio. The connector matrix and per-PMS notes live on the Integrations page.
No. Start with one flagship — prove capture and the standard there, then bring properties online one by one. The dashboard picks each up as it lands. How the contract itself works — length, what's included, what costs extra — is on the Straight answers page.
Each property is scoped and priced individually. That's a one-time setup plus a flat monthly fee, with no commission on bookings, ever. The full model is on the Pricing page.
Something we haven't answered? Book my intro call and ask it there.
If you can't answer that in one screen, that's the gap AURI closes. Start with a short intro call, no obligation.