Sabee for serviced apartments.

The economics of long stays are structurally different

A serviced apartment operator is not running a small hotel with a kitchenette. The unit economics, the guest relationship, and the billing structure all differ from a one- or two-night hotel stay in ways that a generic PMS handles badly. Sabee was built around the reality that a serviced-apartment guest often stays four weeks, sometimes four months, and occasionally signs a corporate contract for a full year with rotating occupants — and every part of the platform reflects that difference, from the rate engine to the housekeeping calendar.

Weekly and monthly rate structures

Nightly rate calendars are the wrong pricing primitive for long stays. Sabee's serviced-apartment configuration supports weekly and monthly rate tiers as first-class pricing objects — a unit can carry a nightly rate for short stays, a discounted weekly rate that kicks in automatically past 7 nights, and a further-discounted monthly rate past 28 nights, with the system handling the transition between tiers as a stay crosses each threshold rather than requiring a manual rate change.

Rate strategy for long-stay inventory also has to account for a different competitive set: apartment guests compare against long-let residential listings and extended-stay hotel brands, not classic OTA hotel rates. Sabee's revenue analytics reports long-stay occupancy and length-of-stay distribution separately from short-stay metrics, so a portfolio manager can see whether the monthly-rate tier is actually filling units or just discounting stays that would have booked anyway.

Utility billing pass-through

Long-stay guests use more electricity, water and heating than a two-night hotel guest, and many serviced-apartment contracts — especially corporate ones — bill utilities separately from the base rate, either as a metered pass-through or a flat monthly allowance with overage charged back. Sabee supports both models: a unit can be configured with an all-inclusive rate, or with a base rate plus a utility line that reads from a metered or estimated allowance and appends the overage to the guest's folio automatically at each billing cycle.

This removes one of the most common manual-billing failure points in apartment operations — a guest who stays three months and never gets billed for the utility overage because nobody remembered to check the meter in month two. Sabee's recurring billing cycle for long stays runs the utility calculation automatically on the same schedule as the base rate invoice, so nothing depends on a staff member remembering a side calculation weeks after check-in.

Keyless entry integrations

Serviced apartments frequently operate with minimal or no front-desk presence, particularly for units spread across multiple buildings or a portfolio with a low staff-to-unit ratio. Sabee integrates with the major smart-lock and keyless-entry platforms (Salto, Assa Abloy, Nuki and others depending on region) so that a confirmed reservation automatically provisions a time-boxed access code or mobile-key credential tied to the guest's exact stay dates, and revokes it automatically at checkout without a staff member needing to manually reprogram a lock.

For a corporate contract with rotating occupants — the same unit used by different employees of the same company across a year — this matters even more: each new occupant gets their own access window without the operator needing to physically re-key anything, and the access log gives an audit trail of exactly who entered which unit and when, which some corporate clients require as part of their own security policy.

Corporate housing contracts

A meaningful share of serviced-apartment revenue in most portfolios comes from corporate housing agreements — a company contracts a block of units for relocating or travelling staff, often at a negotiated rate with specific terms around notice periods, damage liability, and invoicing (many corporate clients require a single consolidated monthly invoice covering all occupants rather than individual guest folios). Sabee's corporate-contract module supports negotiated rate loading against a specific company account, allotment blocks that can be filled by different named occupants over the contract period, and consolidated invoicing that rolls every stay under that contract into one document addressed to the company's accounts-payable team rather than the individual traveller.

This is also where occupancy tracking gets more complex than a standard PMS assumes: a corporate contract for "2 units, 12 months" does not mean those units sit empty between named-occupant changeovers — Sabee tracks the contract-level commitment separately from the unit-level occupancy calendar, so a portfolio manager can see both the guaranteed corporate revenue and the actual bed-night utilization at once.

Cleaning cycles built for long stays

Daily housekeeping makes no operational or guest-experience sense for a guest staying six weeks — nobody wants a stranger in their apartment every single day, and no operator can profitably staff for it. Sabee's housekeeping module supports long-stay service cadences configured per unit or per contract: a light service every seven or fourteen days (fresh linen and towels, light tidy, restock consumables) with a deeper clean scheduled less frequently, and an on-demand service request the guest can trigger themselves through the guest portal if they want something outside the standard cadence.

Turnover cleaning between different occupants still needs to be thorough and fast, particularly on a corporate contract with back-to-back changeovers, so Sabee's housekeeping task cards distinguish clearly between a "mid-stay service" task (lighter, guest is present) and a "turnover" task (full deep clean, unit must be ready before the next arrival), each with its own checklist and expected duration, so the same housekeeping team is not applying the wrong standard to the wrong task.

The guest portal for long-stay residents

A guest who lives in a unit for two months wants a different self-service experience than a two-night hotel guest checking a room-service menu. Sabee's guest portal for long-stay guests supports service requests, maintenance ticket submission, invoice history, and lease-style document access (house rules, building information, local area guides) in one place — reducing the volume of routine phone and email enquiries the operator otherwise fields for a guest population that, unlike hotel guests, is actually around long enough to need ongoing support.

Reporting that separates short-stay noise from long-stay signal

Serviced-apartment portfolios that also take some short-stay bookings (to fill gaps between long-stay contracts) need reporting that does not blend the two segments into misleading averages. Sabee's analytics let a portfolio manager filter occupancy, ADR and length-of-stay reporting by stay-length band, so long-stay performance and short-stay fill-in performance are visible separately — which is usually the difference between an accurate view of the core business and a number nobody trusts.