Oprivia FAQ: platform, pilot, and pricing

Oprivia is a coined name derived from “operational” and “via”, the Latin word for way or route. It refers to a structured operating path after the booking.

Oprivia is a web-based B2B SaaS platform for structured and governed accommodation operations after a booking is confirmed. It connects guest registration, required data, service cases, housekeeping, partner services, records, approvals, and escalations in one operating workspace.

After the reservation, guest details, clarifications, cleaning, handovers and partner services often spread across separate channels. Oprivia brings that work into a traceable operating context.

Oprivia is designed for professional hosts, business apartments, serviced apartments, property managers, portfolio operators and operational partners with recurring coordination needs.

Oprivia is not designed for occasional private rentals without ongoing operational complexity. It is also not a booking portal and does not take over all operator responsibilities.

Oprivia is currently being developed and validated through controlled pilot use. The public website explains the offer; operational access is provided step by step to authorized users.

Oprivia is being built in Switzerland and follows a quality standard based on precision, reliability and controlled development. The Swiss origin describes an operating standard, not a legal or performance guarantee.

The central areas are registration, required information, requests, cleaning, partner coordination, roles, records and evaluation. Which areas are introduced first depends on the specific operating model.

No. Oprivia can be introduced step by step. During the pilot, the areas with the highest practical value for the specific operation are prioritized.

Cross-functional elements include roles, access rights, processing status, time windows, checklists, records, escalations and overviews.

Potential extensions include inventory functions, additional reporting, integrations and further review or risk functions. Features that are not yet available are marked as planned, optional or under review.

A reliable flat-rate time saving cannot be stated. It depends on the number of stays, partners, service cases and process quality. During the pilot, we compare coordination time, processing times, rework, escalations and evidence gaps before and with Oprivia.

Depending on the operating model, Oprivia can structure and support large parts of the digital operating workflow after a booking, from guest data and tasks to deadlines, records, and escalations. Physical services, sensitive approvals, exceptions, and material decisions remain with the responsible people.

No, not by default. Oprivia can operate as a separate platform with its own login. A connection to existing systems is only required if data should be imported, exchanged or synchronized automatically. Such interfaces are subject to technical review and explicit agreement.

Oprivia uses four core roles: Guest, Host, Operator, and Admin/Governance. Tasks, information, and permissions depend on the assigned role, organization, property, stay, and case.

A role only sees the information required for its intended task area. Access can also be limited by organization, property, stay or work case.

A case can be assigned to a responsible role, a processing status and, where required, a time window. Handovers and changes remain traceable.

Escalations can be triggered for overdue items, missing records, blocked cases or defined exceptions. The case is then routed to the designated control or decision role.

No. Oprivia can structure information, apply rules and highlight review needs. Critical approvals, exceptions and decisions remain with the responsible people.

Critical actions are added as new events in a continuous history. Earlier entries are not silently overwritten; corrections remain possible but are documented as additional entries.

Oprivia is not a public review portal. The focus is on internal records, feedback, deviations and work results, not stars or rankings.

Quality is assessed through defined review points such as checklists, photo records, feedback, rework, approvals and documented outcomes.

Depending on the area and agreed setup, checklists, images, documents, notes, confirmations, timestamps or decisions can be assigned to the relevant case.

Critical audit events should not be silently overwritten. Corrections and new findings are added as additional entries. The exact scope depends on platform version and agreement.

The pilot assesses whether Oprivia can be applied meaningfully to a specific operating case. The focus is on onboarding, operational assessment, roles, checklists, partner tasks, photo records and evaluation.

Suitable pilot clients are professional operators or partners with a concrete challenge, recurring workflows, named contact persons and willingness to participate in a structured evaluation.

The pilot can cover registration, required information, requests, cleaning, partner coordination, records, escalations and evaluation. The actual scope is defined separately.

At the beginning, the property, operating model, involved roles, partners, relevant workflows, observation points and excluded services are defined. This creates a clearly limited pilot scope.

The pilot client provides contact persons, property information, existing process documents, partner contacts and feedback. Access, data migration or integrations are agreed separately where required.

A pilot can be continued, adjusted, paused or closed. It creates a decision basis, but no automatic rollout, acceptance or contractual obligation.

Oprivia publishes clearly defined indicative ranges for three operating models. The applicable model and the amount within its range depend on the number of properties, support needs, roles, integrations and ongoing service effort. The calculation logic of the selected model does not change: the applicable base fee plus the corresponding revenue-based component.

For self-managed operations, the monthly fee is CHF 99–149 per included property plus 2–3% of the contractually defined monthly net revenue from accommodation services. For supported operations, it is CHF 299–499 per property plus 5–8% of the same calculation basis. Under the portfolio model, one base fee of CHF 1,000–1,500 applies to the entire agreed portfolio plus 8–10% of the contractually defined monthly net revenue from accommodation services generated by all included properties.

No. Self-managed operations primarily provide the platform, workflows and evidence, while operational coordination remains with the operator. Supported operations add agreed operational assistance. The portfolio model extends control, role logic, governance and evaluation across multiple properties, locations or teams.

No. Each operating model has its own base fee and revenue-based component. For example, the portfolio base fee of CHF 1,000–1,500 cannot be combined with the 2–3% revenue component of the self-managed model.

The calculation basis is the net revenue actually realized from accommodation services for the included properties in the relevant billing month. VAT, tourist taxes, deposits and separately recharged third-party costs are excluded. Cancellation fees are included only if expressly agreed; refunded amounts are excluded. Booking-platform fees are deducted unless already deducted from the reported revenue. The exact definition is agreed before contract conclusion.

The decisive factors include the number of properties, locations, operating model, roles, required support, integrations, implementation effort and ongoing service effort. These factors determine the specific base fee and percentage within the published range.

Value is not assessed through working-time savings alone. It also includes avoided errors and rework, faster escalations, stronger evidence, replaced point solutions and additional operational control. No specific ROI is guaranteed.

The base fee covers platform access and the agreed service framework. The revenue-based component links part of the fee to the contractually defined net revenue from accommodation services. The calculation basis, percentage, exclusions and billing period are agreed before contract conclusion.

Pilot conditions are set out in a separate proposal. The decisive factors are the pilot scope, modules, support effort, technical requirements and the required participation of the pilot client.

No. Guest access is free of charge. Commercial terms are agreed exclusively with the operator or contractual partner.

Additional costs may arise for identity services, integrations, special configuration, additional support, external partners, cleaning, laundry, consumables, repairs, or payment processing. These items are shown separately. Whether these costs are included in the agreed price or charged separately is expressly stated in the quote before the contract is signed.

Yes. A successful referral may qualify for a 10% discount on the monthly base fee. Multiple successful referrals may be combined up to a full reduction of the monthly base fee. The specific requirements are set out in the referral terms or individual proposal.

Depending on the areas used, Oprivia may process stay, contact, identity, task, role, record, communication and evaluation data. Details are defined in the applicable privacy notices and agreements.

Visibility depends on role, organization, property, responsibility and specific case. Sensitive information should only be available to expressly authorized roles.

Personal data is processed for defined operational and contractual purposes. Purposes, categories, recipients and access rights depend on the setup, agreement and privacy notices.

Retention and deletion depend on data type, purpose, agreement and legal requirements. Different data categories may be subject to different retention periods.

External providers may be used for hosting, identity verification, communication, analytics or integrations. Their use and any relevant data transfers are disclosed in the applicable documents.

No. Booking channels generate demand and transmit reservations. Oprivia is not a public booking marketplace. Where external channels remain in use, their fees continue to apply separately.

No. Oprivia is not an Airbnb manager, booking portal or channel manager. The platform supports workflows around preparation, stay, cleaning, partner coordination and closure.

A property management system typically manages reservations, availability, rates, units, and related administrative processes. Oprivia governs the operational work a confirmed booking creates, including guest data, service cases, housekeeping, partner assignments, records, approvals, and escalations. It can complement a PMS or operate as a separate post-booking workspace, but it does not provide channel management, rate management, or a booking engine.

No. Oprivia is not a payment service provider and does not receive customer funds in its own name. Where payment functions are activated, the technical processing is handled through integrated third-party providers and under their applicable terms.

No. Oprivia strengthens governance, access control, documentation and auditability. It does not replace legal, tax, data-protection or regulatory case-specific advice and does not guarantee the legal compliance of a particular case.

No. Oprivia can structure workflows, make information visible and support documentation. A specific commercial result or automatic legal compliance is not guaranteed.

First, the operating model, property, current challenge and desired level of support are assessed. This makes it possible to determine whether an initial discussion, a pilot review or another clarification step is appropriate.

No. An initial discussion is used first for orientation. A pilot, pricing agreement or later platform use requires a separate decision and corresponding agreement.