The Handover That Runs Itself
The move in short
Custom Build — A pipeline that fires each morning when the first checkout of the day is logged in the property-management system, aggregates overnight guest review submissions, housekeeper checkout reports, and any open maintenance tickets across all units, runs an LLM synthesis to produce a single ranked handover digest — units flagged for attention, maintenance items by urgency, any guest sentiment pattern from overnight reviews, and a suggested task sequence for the cleaning team — delivered to the head of operations before the first check-in window opens.
The Company
Kalkoven Vastgoed manages 60 serviced apartments across Bruges — a mix of canal-side short stays and longer corporate lets near the ring road. They don't own the properties; they manage them on behalf of private owners, which means the business runs on reputation in two directions at once: guests and landlords. There are 42 people in the company, four of them in operations, and on any given morning there are guests checking out, cleaners moving between units, maintenance jobs waiting, and owner reports that are always slightly overdue.
The Pain
Lena, the head of operations, starts most mornings the same way. She opens her laptop somewhere between seven and half seven and spends the next hour piecing together what's actually going on across all 60 units. She's checking the PMS for checkouts, scrolling back through WhatsApp messages from the housekeeping team, looking at the maintenance ticket list, and trying to remember which reviews came in overnight. None of it is in one place. By the time she has a clear picture, the first check-in window is already close and she hasn't told the cleaning team anything useful yet. On busy Fridays or around Bruges festival weekends, she's still catching up at eleven.
The Move
You'd build a short automated pipeline — no developer needed, something like Make or n8n connecting the tools they already use. Each morning, as soon as the first checkout gets logged in the PMS, it triggers. It pulls the overnight guest reviews, the housekeeper checkout notes from whatever form the team submits them on, and the open maintenance tickets. All of that goes to an LLM, which reads it and produces one digest: which units need attention before the next check-in, maintenance items ordered by how urgent they are, any pattern in the guest feedback from the night before, and a suggested sequence for the cleaning team to work through. That digest lands in Lena's inbox before eight.
She doesn't open five things anymore. She reads one page, and it already tells her what to do first.
The blind spot
The ops team produces all this information already — the reviews come in, the housekeepers send their notes, the tickets are logged. It just never gets pulled together automatically. So everyone assumes the answer is a better dashboard or a bigger team, not just a pipeline that does the reading and sorting they're already doing manually every morning.
The pattern
The same kind of move works in a lot of ordinary situations:
- A property sales agency where the negotiator spends an hour each morning triaging new enquiries, old follow-ups, and flagged viewings before she can actually talk to anyone
- A facilities management company where the site supervisor checks three different systems every morning before he knows which jobs to dispatch first
- A short-stay rental business where the owner-reporting process means someone manually pulls together occupancy data, maintenance costs, and review scores once a month, by hand, for thirty landlords