How an 8-room hotel on the Moselle saves 4 hours a week

Most automation stories are about large hotel chains with their own IT department. This one isn't. It's about an owner-operated 8-room hotel on the Moselle that has exactly the problem thousands of small properties across the German-speaking region share: a solid PMS for the day-to-day booking work – and a pile of manual tasks around it that nobody takes off your plate.

The starting point

The hotel runs 3RPMS as its hotel software. 3RPMS reliably manages reservations, availability and master data. But for everything that comes after the booking, the hotel was on its own. In practice, daily life looked like this:

• Invoices were written by hand. Every § 14 invoice with correct tax disclosure and a tourist-tax line item assembled manually – a recurring time sink where typos and forgotten items creep in.
• Guest communication ran on a patched-together setup of Make and Chatwoot. Booking confirmations and enquiries were cobbled together across several tools that nobody but the builder could really maintain.
• Payroll data was transferred by hand. The working hours of cleaning and service staff were moved manually toward the payroll office – with the usual risk of transcription errors.
• There were effectively no analytics. Occupancy, average rate, RevPAR – anyone who wanted to know had to compute it from exports themselves. In practice that meant: nobody knew.

The problem

None of these points is dramatic on its own. Writing an invoice takes a few minutes. Sending a confirmation does too. But in total, the manual work reliably ate several hours a week – and worse than the time was the error-proneness: a forgotten booking confirmation, an invoice with the wrong tourist tax, a payroll line that shifted while being retyped. In a small property where the owner pitches in personally, every one of those hours is an hour that doesn't reach the guest or the business.

The implementation

zimrly sits as an add-on directly on top of the existing 3RPMS – the PMS stays where it is and supplies the data. It was introduced step by step, not all at once:

1. Invoice automation first. The biggest lever was the § 14 invoice. zimrly now generates it automatically from the reservation data – with correct tax disclosure and the tourist tax shown, archived and handed off to accounting. "Every invoice by hand" became "generated, checked, done".

2. Guest communication on WhatsApp. The Make-and-Chatwoot patchwork was replaced by zimrly's WhatsApp inbox. Booking confirmations and check-in reminders go out automatically. An AI assistant answers simple guest questions on its own and only surfaces what genuinely needs a human reply.

3. Payroll export. Working hours run through time tracking and are handed over as a ready-made export toward DATEV/LODAS – no more manual transfer, no transcription errors.

4. Insights and pricing on top. Occupancy, average daily rate (ADR) and RevPAR are now visible daily, without an Excel export. The repricer connection lets you set a price cap so dynamic pricing doesn't get out of hand. Self check-in is available as an option whenever a guest prefers to check in themselves.

Before / After

The result

The bottom line: the hotel saves around 4 hours of manual work per week. Just as important as the time is what disappears: invoices are instant and legally compliant instead of typed by hand in the evening. No more forgotten booking confirmations, because they go out automatically. Payroll data without transcription errors, because it's no longer retyped. And, for the first time, a reliable view of occupancy and rate instead of gut feeling.

We deliberately don't quote invented revenue or occupancy percentages – anyone who promises those is usually guessing. What's verifiable: less manual work, faster and legally compliant invoices, no forgotten confirmations, error-free payroll data. That was exactly the goal.

The pattern behind it

The decisive thing about this story isn't a single feature, it's the principle: the PMS did not have to be replaced. 3RPMS stays the system for the day-to-day booking work. zimrly wraps around it as an add-on and closes exactly the gaps a PMS typically leaves open for small German properties – invoices, tourist tax, guest communication, payroll data, analytics. Modules are booked individually, in the order they hurt. That makes the entry small and the result large.

If your property runs a PMS and yet still does too much by hand around it, that's not a software-replacement problem. It's a gap problem. And gaps can be closed without rebuilding everything.