Skip to content
Vyrobel Example scenario · 42 villas, 31 owners · four islands
Illustrative scenario, composed from onboarding conversations · vyrobel.com/case-studies
Villas · four islands· 9 min read

Forty-two villas, thirty-one owners, one screen

⚠️ An illustrative scenario, not a customer. Vyrobel is new and has no published customer stories yet. This describes how the product is used by an operation of this shape, composed from onboarding conversations. Nothing here is a claim about a real business, and no figure is a measured result.

This operation manages holiday houses across four islands for owners who mostly live somewhere else. The hardest part of the job was never the cleaning.

Portfolio
42 villas
across four islands
Owners
31
most of them abroad
Team
11
peak season, mostly cleaning
Live in
5 weeks
cut over in shoulder season

Before: three systems and a month-end ritual

Distribution ran through a channel manager, which did its job. Money ran through a spreadsheet per owner, rebuilt by hand every month from booking exports, bank statements and whatever receipts had made it back from the islands. Cleaning ran through a WhatsApp group, which worked until roughly the twentieth villa and then quietly stopped.

The month-end was the part that hurt. Four days of assembling thirty-one statements, followed by two weeks of owners phoning to ask what a line meant. Not because the numbers were wrong — they were usually right — but because a figure in a spreadsheet cell is a claim with no evidence attached.

The switch

They moved in early May, deliberately: bookings on the books for July and August, but a quiet fortnight to work in. Reservations and two years of owner statements imported in the first week, with a reconciliation sheet that found nine bookings where the spreadsheet and the channel manager disagreed. All nine were spreadsheet transcription errors, none material, all quietly corrected.

Week three was parallel running. The cleaning team worked the board and the WhatsApp group at once, which everybody found irritating and which caught two properties whose changeover times had been wrong in the import. Channels cut over on a Tuesday in the fourth week; the fifth was owner onboarding, which took longer than expected because owners had questions once they could actually see things.

No bookings were lost. One rate plan for a single villa was mapped to the wrong season and was caught by the sample-pricing check before it sold anything.

After: the phone stopped ringing

The month-end assembly went from four days to an afternoon of review, because the statements build themselves from bookings and expenses that were already recorded. The larger change was what happened afterwards: owners with a portal stopped calling, because every question they used to ask is answered on a page they can open at midnight from another country.

Housekeeping moved onto the board and the group chat became social again. The unexpected benefit was the maintenance side: a ticket that takes a villa off sale until it is fixed removed a class of problem nobody had been counting, where a house with a broken air conditioner kept selling because the person who knew was not the person who managed the calendar.

Direct share up
Returning guests now book on their own storefront rather than through a marketplace.

What was harder than expected

Owner onboarding. Giving thirty-one people a portal means thirty-one people discovering questions they had never bothered to ask, and the first month generated more owner contact than usual rather than less. It settled by the second statement, but it was not the quiet week anyone had planned for.

Two owners also wanted their historic PDFs to look exactly as before. They don't; the new statement has more detail and a different shape. Both preferred the new one within a month, but neither said so at the time.

Illustrative scenario

Composed from onboarding conversations with villa managers of this size. Named customers and verified figures replace it at launch — we would rather say that than invent a logo.

Vyrobel · Property management for hotels, apartments and villas · contact@vyrobel.com · vyrobel.com
Figures in this story are illustrative. Named customers and verified numbers replace them at launch.

An ordinary visit sets 2 cookies — vyrobel-session and XSRF-TOKEN. 2 more appear only if you ask for them. All 4 are strictly necessary, and there are no analytics, no marketing and no third-party cookies at all — nothing here tracks you across other sites. So there is nothing on this notice to switch off today. We record your answer anyway, because it binds us if that ever changes.

What each one is for
Every cookie this site sets
Cookie What it does How long When it is set
vyrobel-session Keeps your session — the sign-in that follows you between pages, and the basket of a booking in progress. 2 hours On your first page view.
XSRF-TOKEN Protects every form on the site from cross-site request forgery. Without it a form you submit here could be forged from another site. 2 hours On your first page view.
vy_td Remembers a device you chose to trust, so two-factor authentication does not ask again on it. 30 days Only if you tick “trust this device” at a two-factor prompt. Never otherwise.
vy_cookie_choice Remembers the answer you gave on this notice, so it is not shown again and so the answer can be honoured. 365 days Only when you answer this notice.
Privacy notice