Ask anyone who runs a hotel what their day looks like and you will not get a list of features. You will get a description of rhythms. Something needs handling right now, at the desk, with a guest waiting. Something else should start on its own when a booking changes. And a third thing — the numbers everyone quietly relies on — needs to arrive every Monday whether anyone remembers to ask for it or not.
Most software picks one of those rhythms and optimises for it. The work does not cooperate.
Right now: chat
The immediate case is the easiest to recognise and the hardest to serve well. Someone needs an answer about live data, and the answer is only useful if the next step can follow from it.
That is why chat in Discontinue is not a search box over a knowledge base. It reads from the systems a workspace has actually connected, and where those systems allow an action, it can take it — in the same conversation, without a handoff into another tool. What it can reach and what it may do are decided by the permissions on the connection, not by how the question was phrased.
The useful property here is not speed. It is that investigating and acting stop being two different activities.
When something changes: agents
Plenty of work has no business waiting for a person to notice it. A rate moves, a booking cancels, a file lands on an FTP server at 04:00.
An agent is a description of that work in plain language, plus a trigger — a schedule, or an event from a connected system. It runs, it uses the access it was granted, and it reports what it did. Where the hotel wants a human in the loop, a step waits for approval instead of proceeding.
Two things matter more than the automation itself. Every run leaves a record of what it touched and what it produced, so a result can be checked rather than trusted. And costs are shown in euros against a spending limit, so an agent that starts behaving expensively is visible before the invoice is.
On a schedule: reports
The third rhythm is the least glamorous and the most load-bearing. Recurring reporting is where operational understanding actually lives, and it is usually the first thing to rot — a spreadsheet someone maintained until they left.
A report is described once, then produced on its schedule from current data, with the hotel's branding, delivered by email, Slack or Teams. When a figure cannot be established — a source did not answer, a range came back empty — the report says so instead of printing a confident zero.
Why connected systems are the whole point
None of the three rhythms works on a system that only knows about itself. A hotel's work spans a PMS, a payment provider, guest messaging, analytics, and a handful of things nobody has migrated yet.
Discontinue connects to those systems through a broker that holds the credentials and enforces what each caller may reach. An agent does not get a copy of your API key; it gets a narrow, checked path to a specific capability. That is what makes it reasonable to let something run unattended at four in the morning.
Where this is going
We are building for the boring middle of hotel operations: the recurring, cross-system, slightly-tedious work that never justified a project of its own. This blog is where we will write about what that turns out to require — the parts that worked, and the parts we had to rebuild.
Discontinue runs on infrastructure hosted in the EU, and customer data is not used to train the underlying models.