Relevo Lab / Custom Automation
Primary engagement · Hotels & central teams

Custom automation, built around your hotel.

Relevo Lab builds bespoke automation systems for hotels, hotel groups, and the central teams that serve them. No off-the-shelf software. No hourly billing. No code handover. We build the system — then we run it on your behalf.

A different shape of engagement, end-to-end.

Custom Automation is our primary engagement mode. The shape is the same on every project — what changes is the operation we shape it around.

01 · Understand first

We understand the process before we build.

Every project starts inside the operation as it actually runs — talking to the people doing the work, watching the queues, reading the inbox. We document what hurts before we propose anything.

02 · System fits the hotel

The solution adapts. The hotel does not.

We shape automation around existing processes, not against them. The system learns the hotel — handoff routines, escalation paths, language, tone. Change friction is treated as a real cost, not an externality.

03 · We operate it

Setup fee to build. Monthly fee to operate.

Every engagement is a setup fee to design and build, then a flat monthly fee to run the system. We monitor, tune, and update it as the operation evolves. Hotels do not inherit a maintenance burden.

04 · What we never do

No hourly billing. No handover. No new tool.

We do not bill by the hour. We do not hand over a codebase and a login. We build inside the tools your team already uses — inbox, PMS, internal channels — so nobody learns a new system to do the same job.

Four phases. One sequence.

Each engagement follows the same shape. We commit to it because building before understanding is how good intentions become bad software.

01 — DISCOVERY 1–2 weeks

Discovery & rule workshop.

We spend time inside the operation. We map the workflow as it actually runs, document pain points and edge cases, and define a tight scope for the pilot. Output is a written specification both sides sign off on — what the system will do, what it will not, and how success is measured.

02 — PILOT BUILD 4–6 weeks

We build it inside your existing tools.

We build the system in the tools your team already uses — inbox, PMS, internal channels. As few new logins as possible. Dashboards only where they genuinely add value. Weekly check-ins. By the end of phase, the system is functional on real data.

03 — GO-LIVE 2–4 weeks pilot operation

Go-live and pilot operation.

The system runs in production with us watching every output. We tune classification, refine drafts, and close the gaps that only show up on real volume. Nothing automated ships to guests until a human sends it.

04 — OPERATE Ongoing

Ongoing operations. We run it.

A flat monthly fee covers everything: monitoring, tuning, updates as your operation changes, and on-call response when something breaks. The hotel never inherits operational responsibility for software it did not write.

What we have built. Three examples.

Every engagement is custom, so no two systems look alike. These are recent shapes.

01 Group sales inbox

Group sales inbox for a German hotel group.

Multi-intent classification on every inbound message — sales inquiry, follow-up, contract question, internal. Structured extraction per inquiry: dates, segments, room blocks, expected ADR, special requests. Drafts prepared in the salesperson's voice. Folder routing and conversation tracking across the long sales cycle, with status visible in the inbox itself.

Inbox
Shared, multi-user
Languages
DE, EN
Mode
Draft & route
02 Central reservations

Central reservations workflow. One click instead of copy-paste.

The team's old workflow was manual copy-paste from Excel templates: read the inquiry, look up availability, find the right rate, paste the canned response, edit by hand. We replaced it with a system that classifies inbound requests, extracts guest and booking data, checks live availability against the PMS, and prepares a complete reply draft. Reservation agents now click once and review.

Lookup
Live PMS availability
Output
Full draft reply
Human in the loop
Always
03 Workflow bridges

Bridges between the systems already in place.

Most pain in a hotel back-office is friction between systems that should talk to each other and do not. We connect inbox to property management to internal handoff — directly through APIs where they exist, and through pragmatic workarounds where they do not. The result is a workflow that feels native to the tools your team already trusts.

Surface
Inbox · PMS · channels
New logins for staff
None
Approach
API-first, fallback pragmatic

Operators who already know standard does not fit.

Custom Automation is for hotels and groups that have already tried something off-the-shelf and found it does not match how the work actually runs. The setup is built for teams that own their operation and want a system shaped around it — not the other way around.

  • Operations Directors of multi-property groups
  • General Managers of independent hotels
  • Sales leads of central or group sales teams
  • Reservations and revenue managers running shared inboxes
  • Group operations teams serving a portfolio of properties

Curious if a custom engagement could fit your operation?

Write a few sentences about your setup — the team, the inbox, the tools, the part of the work that hurts — and we will take it from there.

Responses within one business day