What changes at 20 units
The problem stops being "who cleans tomorrow" and becomes "who saw what, when". Lemon's answers:
- Roles. Host (everything), co-host (everything but billing), property manager (only assigned properties, with granular permissions and a mobile-first dashboard). Cleaners never log in.
- Property groups by building, area or owner, to keep 40 properties navigable.
- Cascade and broadcast. Priority per property for the normal case; broadcast to the pool for urgent jobs, first to accept wins.
- Capacity and availability per cleaner so nobody is offered two 11:00 jobs across town; minimum cancellation notice enforced.
- Supply stock per property with usage reported by cleaners and low-stock warnings before the next clean.
- Payout tracking: fee per property or per cleaner, batch mark-paid, export by date range.
- Audit. Every sync decision logged with a reason; every message logged with delivery status; activity log per organisation.
Calendars at scale
Forty properties on Booking.com and Airbnb means forty feeds and, in the September 2026 data, roughly 4 silent re-keys per feed per month. Lemon's engine handles them without cancelling jobs; a direct Hospitable, Guesty or Hostaway connection removes the ambiguity where you have one, and Lemon deactivates the property's iCal feeds automatically when you connect it.
Cost
€10 per property per month from 21 properties, two months free on annual billing. Above 50 properties, talk to us.