Back to the exhibition

Quana · project

Inavo

The hotel’s operating system, entered by scanning a QR code.

Inavo connects hotel guests, staff and management through QR-based digital workflows — replacing phone calls, paper logs and scattered WhatsApp messages with one tracked system.

Inavo

The hotel’s operating system, entered by scanning a QR code.

Layers

3

Apps to install

None

Entry

One scan

The problem

Nobody downloads an app for a two-night stay.

So the guest calls the front desk, and the line is busy. Staff take the request on a walkie-talkie, a paper slip or WhatsApp, and it is lost at the shift handover. Management finds out how the day went the following morning, from whoever remembers.

Inavo guest portal on a phone, showing the room context and the list of requestable services
GuestScan, and the room already knows which room it is.

One request, end to end

From a scan to a resolved ticket

  1. ScanNo app, no account, no login. The QR carries the room.
  2. RequestWater, pillows, housekeeping, a broken AC — or free text.
  3. QueueIt lands in the staff queue with a reference number.
  4. ClaimSomeone takes it, and it stops being everyone’s job.
  5. ResolveMarked done with a note, and a faulty asset attached if there was one.
  6. FeedbackThe guest rates it while they are still in the building.

Three products in one

Each layer is a different person’s whole day

  • Guest — mobile web, no install: “I need something.”
  • Staff — a live operations queue: “I need to handle it.”
  • Management — boards, assets and analytics: “I need to improve it.”

Service recovery

Catch it before checkout, not after.

In-stay feedback goes to a manager’s inbox while the guest is still in the room. A complaint that reaches you at 9pm is a problem you can still fix; the same complaint on a review site three days later is not. That turns feedback from a rating into an intervention.

Assets

The AC that keeps breaking has a name.

Rooms carry their equipment as records. A request can be attached to a specific unit, which then moves Working → Faulty → Repaired and keeps its relocation and maintenance history. Over a season that turns a stream of complaints into a maintenance signal.

Structure

One organization, many properties

  1. OrganizationThe tenant
  2. PropertyA hotel
  3. Tower / FloorHow the building is actually laid out
  4. Room / AreaWhere the QR lives
  5. AssetThe thing that broke
Inavo staff operations queue showing several requests in waiting and in-progress states
OperationsThe queue is the shift handover.

Built with

Web
Next.js 15
API
NestJS — modular monolith
Data
PostgreSQL / Supabase via Prisma
Isolation
Row-level security, per organization
Access
34 granular permissions across four roles
The manager Kanban board across a normal day, requests spread over its columns.
ManagerThe third layer: the day, seen whole.
A room’s asset list with one unit marked faulty.
AssetsEvery unit in every room, and which one is broken.
The feedback inbox showing an in-stay rating with a written comment.
FeedbackRated during the stay, while it can still be put right.
View project