Question 1

How much does it cost?

Accepted Answer

It depends on scope, systems involved, and operational risk. Single Fix starts from €1,500 or €2,500 as a buyout. Full Workflow starts from €4,900 or €7,900 as a buyout. Operational Layer starts from €9,900 setup + ongoing. We estimate the cost of the friction first, then give you a fixed quote.

Question 2

What is a Single Fix?

Accepted Answer

A small, bounded piece of work: for example a scheduled report, a simple handoff, or a notification flow. It is the right starting point when workflow breadth and operational risk stay low.

Question 3

Is there a mandatory monthly fee?

Accepted Answer

No. No mandatory software subscription. You can choose buyout or ongoing coverage.

Question 4

What does Extended Coverage cover and what does it not?

Accepted Answer

It covers active monitoring, incident response, and capped monthly improvements. It does not cover large new development, out-of-scope integrations, or unlimited requests.

Question 5

How long does it take?

Accepted Answer

Single Fix: usually 1–2 weeks. Full Workflow: usually 3–5 weeks. Operational Layer: depends on how many workflows are in scope. Timelines are defined in the written proposal.

Question 6

Do we need to change PMS?

Accepted Answer

No. We work on top of the systems already in use to remove manual steps and automate repetitive work.

Question 7

Which systems do you work with?

Accepted Answer

PMS, channel manager, operational email, WhatsApp Business, internal notes, task tools, Excel or Google Sheets reporting, and the channels already used to coordinate suppliers. In the first call we verify what your real setup supports.

Question 8

Can a workflow still be worth automating if some steps remain manual?

Accepted Answer

Yes. Mixed workflows are completely valid. We automate what should be automated and leave manual tasks, approvals, or fallback where they still make sense. The chain does not need to be 100% automated to remove a large amount of waste.

Question 9

Can you work with suppliers who do not have APIs?

Accepted Answer

Yes, when the context allows it. We can coordinate the workflow through existing operating channels — email, tasks, direct contacts, or other agreed steps — without pretending full automation exists where it does not.

Question 10

Who approves actions or messages sent to the guest or external parties?

Accepted Answer

The hotel decides. At the start, approval can stay human on sensitive steps. Once the workflow is stable and trusted, approval can be reduced only on the agreed low-risk steps.

Question 11

What happens after go-live?

Accepted Answer

Every engagement includes stabilization. Then you choose autonomy or ongoing coverage. In both cases the fallback is defined in advance.

Question 12

What happens if something stops working?

Accepted Answer

Before go-live we define escalation and fallback. If an issue appears, we return to the agreed safe state and intervene.

Question 13

Who owns what you build?

Accepted Answer

The hotel keeps full operational use of everything we deliver. Any reusable technical components remain our property — this is stated in writing before signing.

Question 14

Can you work with smaller or larger hotels?

Accepted Answer

Our offers are designed for independent hotels typically in the 30–150 room range. Smaller or larger properties are assessed case by case.

Question 15

Can you work during high season?

Accepted Answer

Yes, but with tighter controls: small releases, agreed windows, and no structural changes on critical days.

Question 16

Where does guest data go?

Accepted Answer

It stays in the hotel systems or agreed infrastructure. We apply data minimization and log access.

Common Questions