Hospitality & TravelTech
One availability calendar instead of several dashboards, automatic messenger confirmations, payments and documents from booking data.
Case
For a hostel we built a booking system where the unit of accounting is the bed, not the room: dates, free places, payment, check-in.
A guest books and pays online, the administrator sees occupancy by date and no longer keeps it in their head or in a notebook. Notifications go out by themselves.
Off-the-shelf booking systems could not count beds the way a hostel needs, so we wrote our own.
What eats time in hospitality
Bookings arrive from several channels, each with its own dashboard. The availability calendar is merged by hand, and sooner or later two guests get the same room for the same night.
Second, the routine around check-in. Confirmations, reminders, details, invoices. All done manually, though every step repeats identically.
What we do
Booking and calendar
One availability calendar instead of several. Overlaps are impossible by design, not by the receptionist paying attention.
Automatic messages
Confirmation, day-before reminder, check-in instructions — in the messenger the guest actually uses.
Payments
Online prepayment, payment on arrival, bank transfer for companies.
Documents
Invoice and act generated from booking data without retyping details.
Site access
Where electronic locks or barriers exist, we tie them to the booking — the guest gets access for their period.
Reporting
Occupancy, average spend, where guests come from, which periods sag.
What it runs on
Node.js and PostgreSQL, web interface, integration with payment systems and messengers. Where hardware exists — locks, barriers, meters — we connect to it the same way as to industrial controllers.
Frequently asked
Do you build a channel manager for Booking?
Does the guest need a separate app?
How many rooms make it worthwhile?
Answers on this topic
Plain explanations without marketing — useful even if you never hire us.
Selling on WhatsApp: the 24-hour window and lost messages
How the WhatsApp Business API actually behaves: the 24-hour window, templates, and why an "ok" from the API does not mean the customer saw your message.
Custom system or an off-the-shelf box: an honest comparison
When a boxed product wins, when custom wins, and the third option: a working system adapted to your process. Lock-in, code ownership, support, migration risk.
Automating invoices, contracts and delivery notes
Why salespeople lose hours to paperwork and what to automate first. A worked example: 196 documents generated by the system with no manual typing.