Oprivia was built inside the operation, not on a whiteboard
Adriano Walter Brander combines four years of hands-on hosting in Basel with trade compliance and governance experience across business processes in more than 100 countries. Oprivia grew from these two perspectives: a platform that structures post-booking operations through clear responsibilities, evidence, and decision paths.
The bottleneck begins where the booking ends
Every reservation sets information, people, deadlines and evidence in motion. In practice, the same three structural gaps appear repeatedly:
Information without context:
Data arrives, but it is incomplete or not clearly connected to the relevant stay.
Tasks without visible ownership:
Work must be completed, but responsibility, deadline or escalation path remains unclear.
Services without documented completion:
A step has been performed, but the evidence, exception, approval or result remains distributed across different places.
Oprivia turns these disconnected handoffs into a controlled workflow with clear ownership and documented completion.
Turning regulated requirements into governed workflows
Oprivia applies principles drawn from highly regulated international business environments: requirements are assessed, accountability is assigned, controls are defined, and material decisions are documented. Applied to accommodation operations, this creates a shared control model for guest data, tasks, service partners, approvals, and escalations. It structures complexity without automating professional accountability or replacing booking and property management systems.
Three principles
Approvals and material decisions remain with authorized people. Escalations may be routed to the accountable role according to defined rules. The reason, process and outcome are assigned to the relevant case. Operational accountability must belong to a named role rather than depend on personal follow-up or fragmented communication channels. Every material step requires evidence and a verifiable conclusion.
Anchor accountability
Every critical step requires an accountable role, a clear assignment, and traceable boundaries.
Make operations visible
Open items, feedback and deviations should not disappear in isolated communication channels.
Safeguard decisions
Approvals, escalations and corrections remain documented where they originated.
A shared structure instead of isolated channels
Oprivia is developed from observed workflows rather than a fixed feature catalog. Four principles guide this approach:
Observe instead of assume
The starting point is real workflows, recurring friction points and the roles involved.
Limit the scope
A pilot starts with clearly defined workflows, documents, partners and control points.
Test in live operations
Selected steps are accompanied, documented and assessed under real operating conditions.
Develop from evidence
Experience, deviations and open questions are fed back into further product development in a targeted way.
From hosting experience to an operational platform
Development follows clearly defined work steps with verifiable outcomes.
Spring 2022
Analyze the operational gap
Analysis of post-booking work steps and recurring information loss between stakeholders, channels and systems.
End of 2025
Design the operating logic
Design of stay-related logic, role model, workflow logic, records, and escalation paths.
Early 2026
Develop based on evidence
Translation of the functional logic into feature specifications, acceptance criteria, documents and prepared pilot processes.
Current status
Setup and onboarding
Oprivia is ready for operational use. New customers can start regular operations or agree on a separate pilot. The module overview describes its main uses, and the FAQ explains the available scope, direct deployment, and extensions that require separate assessment.
Experience across regulated operations and hands-on hosting
Adriano Walter Brander brings experience from highly regulated international business environments. At a global organization, he held senior responsibility for trade compliance processes supporting international business and cross-border supply chains. His professional background spans customs, foreign trade law, sanctions, export controls, freight forwarding and logistics, international tax matters, and internal control and governance requirements.
Alongside this work, he managed Airbnb stays in Basel for several years without using a property management system. Guest registration, visitor taxes, housekeeping, damage cases, guest requests, and external partner coordination were part of daily operations. Oprivia emerged from these two perspectives. The platform is ready for operational use, and new customers can start setup and onboarding once the required modules, roles, and services are agreed. A pilot is optional; additional interfaces are assessed separately.
Swiss origin. International perspective
Oprivia combines a Swiss commitment to precision, traceability, and reliability with a product architecture designed for consistent use across operators, locations, and markets.
A clear purpose and clear boundaries
Oprivia complements booking and property management systems by structuring the operational work that follows a confirmed reservation.
What Oprivia is designed to support
- Registration and mandatory guest data processes
- Requests, cleaning and partner coordination
- Roles, workflow status, records, and reporting
- Approvals, handoffs, and escalation paths
What remains outside the scope
- no booking marketplace
- no full property management system
- no payment processing as a financial service provider
- no legal, tax or regulatory advice
- no substitute for human review or professional responsibility
The operational layer after booking
Booking platforms such as Booking.com, Airbnb, and Vrbo primarily support property discovery and reservations. Property management systems and channel managers typically manage functions related to availability, rates, units, and distribution.
Operational execution begins once a booking is confirmed. It includes guest registration and local visitor taxes, service cases, housekeeping, damage documentation, service partner coordination, approvals, and escalations. Depending on the operator, these activities may span several roles, systems, and communication channels.
Oprivia is designed for this post-booking operational layer. The platform brings roles, cases, workflow status, evidence, and decisions into a shared, traceable structure. It complements existing booking and property management systems; reservations, pricing, and distribution remain in the systems designed for those functions.
The reported figure illustrates the scale at which accommodation is visible and bookable online. The operational execution of each individual stay remains a separate responsibility.
9M+
The number of active listings illustrates the international reach of short-term accommodation. Each confirmed booking is followed by operational tasks, responsibilities, and information flows.
2.4M
alternative-accommodation listings on Vrbo
Entire homes and apartments require property-specific operating processes, including access, housekeeping, technical issues, damage handling, and handovers.
1.2B
The reported booking volume illustrates the scale of the processes that may follow confirmed reservations. Oprivia supports the structured handling of those operations after booking.
Sources: Company disclosures from Booking Holdings, Airbnb, and Expedia Group/Vrbo. The figures refer to listings, alternative accommodations, and booked room nights as reported by the respective companies. Reporting periods and definitions differ, so the figures are not directly comparable. The named companies are included solely as market examples. No partnership, integration, or endorsement is implied. Sources accessed on August 16, 2026.
Is Oprivia a fit for your operation?
In a nonbinding initial conversation, we clarify your use case, the roles involved, and the appropriate scope. We then plan setup and onboarding for regular operations or an optional pilot.