Proposal · Short-term rentals
Sixty units, one changeover Saturday
The back office for a managed villa portfolio - owner statements, changeover logistics, access codes and the compliance paperwork each booking generates.
Proposal. We have not built this one. It is written out to the same level of detail as the work we have shipped, because the useful argument is about the design, and that argument costs less before a price exists than after.
- Next.js
- Postgres
- Flutter
- TTLock
- myDATA
The numbers
- 1
- Ledger behind both the owner statement and the accounts, so the two agree by construction
- 0
- Manual filings, because the stay declaration goes against the right AMA when the booking confirms
The problem
A manager with sixty units under contract has a hard week every week: most changeovers land on the same day, cleaning crews have to be routed, keys or codes handed over, owners paid a share that differs per contract, and each booking generates a short-stay declaration against the property's AMA.
All of it lives in three spreadsheets and a phone.
How we would build it
Changeover is its own object in the schedule rather than a property of a booking, because a cleaning crew's day is a routing problem across units and not a field on a reservation. Once it is an object, it can be assigned, reordered and marked done from a phone.
Owner statements are generated from the same ledger the bookings post into, so the number an owner sees and the number in the accounts are the same number by construction rather than by reconciliation.
Compliance is filed as a consequence of the booking, not a monthly chore: the short-stay declaration goes against the correct AMA when the booking confirms, which is also what the EU-wide registration requirement from May 2026 assumes.
Access codes are generated on confirmation and expire at checkout, which removes the physical key handover behind most of a manager's evening phone calls.
What it would change
The change worth arguing about is structural rather than numerical: the manager stops being the integration between six systems. No hours-saved figure appears because there is nothing yet to measure - the first one worth quoting comes off your own portfolio, after it runs.
A worked example
Changeover is its own scheduled object rather than a field on a booking, because a cleaning crew's day is a routing problem:
- Units
- 60
- Typical changeover day
- Saturday
- Each changeover generates
- clean, key, filing
- Owner splits
- differ per contract
No hours-saved figure appears because there is nothing to measure yet. What would change is structural: the manager stops being the integration between six systems.
Want us to build this?
A 20-minute call with the two people who would build it. You tell us what you need; we tell you whether it is worth building and roughly what it costs.
The full page: Hotels & hospitality