Our roadmap and how customers shape it

Today

The platform connects to one outside service: Airbnb, in the sense that short-stay units are first-class in the building — their turnovers in the rota, their consumables in inventory, their income in the P&L next to rent. It does not take bookings or set prices; it keeps the record of what the building did.

Decided, in order

1. Other short-stay platforms. Booking.com, Agoda and direct bookings tracked the way Airbnb is, so a unit on three platforms has one turnover schedule and one income line per platform.
2. Calendar sync. Reading the iCal feeds those platforms publish, so check-outs schedule turnover cleanings without anyone typing a date.
3. Payment links. A pay button on the invoice and the portal that records the payment when it clears, so "mark as paid" becomes something the platform does to itself.

Waiting for demand

A thin app-store app wrapping the website. Bank-statement import for reconciliation. A direct login for your accountant. Each of these is a few weeks' work and only worth doing if customers want it more than the next item above. Tell us and it moves.

Not planned

Chat between tenants and staff (WhatsApp already exists and works). A bank or wallet of our own. A listing marketplace. Any "AI that runs your building" — the platform records and reminds; it does not decide. The test for every feature is whether it helps a month get done or gives someone a reason to stay on the screen. We only build the first kind.

How to shape it

Every workspace has a Suggest link in the footer. Suggestions are read by the people who build the platform, not a support queue, and every one gets an answer. Things that several customers ask for in the same month get built in the next one; the CHANGELOG names the workspace that asked, if they agree.