For the Office Manager, Head of Workplace, or HR Operations Manager at a multi-site company — roughly 200 to 5,000 staff — keeping 1–30 apartments or guest houses the company itself owns or master-leases: OwnHouse lets the company's own employees book, stay in, and turn over those units — availability, eligibility and priority, the cleaning buffer, access instructions, and a stay record — with no rates, no channels, no folios, because nothing is being sold.
How it works
- Set up each unit — capacity, buffer hours for the cleaning buffer, the access and checkout instructions as you supply them, eligible departments, the approval rule, and the cleaner assignment
- A booking request is entered — employee, unit, dates, purpose, and cost center; bookings are admin-managed today, because real employee identity is not built and no employee sign-in exists
- Availability is checked exactly — a unit is available only when the stay would not overlap another stay once the checkout buffer is applied; a conflict is refused, with the nearest available dates shown
- Approval blocks the calendar, and creates the cleaner task and the guest instruction sheet inside OwnHouse — records for the stay, not messages: OwnHouse sends no notification to the employee or the cleaner
- The stay happens and turns over — the cleaning buffer is held after checkout, turnover is tracked against the stay, and maintenance raised by a stay is taken in as a maintenance intake for the admin to arrange
- The stay record stays complete — nights and cost center for every stay, utilisation per unit, and cost-center reporting, with a CSV export
By design — nothing is sold
OwnHouse is for housing a company already owns or master-leases, for its own employees. No payment/channel/OTA integration is in scope, by design.
That is the product's deliberate shape, stated plainly: there are no payments, no channels, and no listings, because nothing is being sold. Employees stay in the company's own units; nobody buys a stay, and no stay is offered to the public. OwnHouse is not a rental product, and it never becomes one — its whole work is availability, eligibility, turnover, and the stay record for housing the company already holds.
Your units — the company's own housing
Each unit the company owns or master-leases is set up once, with what a stay needs to run cleanly: its capacity, the buffer hours held after checkout for cleaning, the access and checkout instructions exactly as the admin supplies them, the departments eligible to stay, the approval rule for requests, and the cleaner assignment for turnover.
The units are the company's own apartments and guest houses — housing kept for visiting and relocating employees, held by the company, not offered to anyone else.
- Capacity
- Buffer hours — the cleaning buffer held after checkout
- Access and checkout instructions, as the admin supplies them
- Eligible departments
- Approval rule
- Cleaner assignment
Eligibility, priority, and availability
Eligibility and priority come from the unit's own setup: the eligible departments and the approval rule decide whose request can be approved for a unit, and in what order requests are considered. A booking request carries the employee, the unit, the dates, the purpose, and the cost center.
Availability is exact, not remembered: a unit is available for a set of dates only when the stay would not overlap another stay once the checkout buffer is applied. If the dates conflict, the request is refused and the nearest available dates are shown — the calendar never double-holds a unit.
Booking, approval, and turnover
When a request is approved, the approval blocks the calendar for those dates, and OwnHouse creates two records for the stay: the cleaner task for turnover, and the guest instruction sheet carrying the access and checkout instructions for the employee's stay. Both are records inside OwnHouse — the honest state below states plainly what OwnHouse does not send.
Turnover is part of the stay, not an afterthought: the cleaning buffer is held after checkout, the cleaner task is tracked against the stay, and anything the stay raises for maintenance is taken in as a maintenance intake from the stay, for the admin to arrange.
The stay record
Every stay leaves a complete record: the employee, the unit, the nights, and the cost center. From those records OwnHouse reports utilisation per unit and reporting by cost center, so the company can see how its own housing is actually used, unit by unit and cost center by cost center.
The stay record exports as a CSV — every stay, its unit, its nights, and its cost center — for the company's own records.
Where it stands — the honest state
OwnHouse is forming its first company pilot group now. The door below is a company pilot application — applying starts a pilot conversation; it does not create an account, and it is not a sign-up for a running service.
Real employee identity is not built. There is no single sign-on and no email-verified sign-in link today — bookings are admin-managed today, and no employee signs in or books a stay through a verified identity. Building that identity layer stands as a gate before any employee self-serve use.
OwnHouse sends no notifications. Live guest and cleaner notifications are not sent by the product — the cleaner task and the guest instruction sheet are records inside OwnHouse, and the admin notifies the employee and the cleaner their own way, as they do today.
Per-stay access-code handling is not a live system. Access is handled by the admin today: the product holds the access instructions the admin supplies for a unit, and nothing beyond that exists — the admin handles access for each stay, in their own way.
Maintenance vendor dispatch is not built. A stay can raise a maintenance intake, and maintenance itself is arranged by the admin today — OwnHouse does not send work to any vendor.
No price has been set. A price range exists in our market research as a hypothesis; it has not been validated and it has not been decided, so no price is shown here and there is nothing to buy on this page. That is separate from the design law above: a company's own subscription, if one is ever decided, is the only billing this product would ever have — a stay itself is never sold, in the pilot or after it.
Company pilot application
This is a company pilot application — an application to join OwnHouse's first company pilot group, not an account sign-up and not a purchase. Tell us who to reach, your company, and how many housing units you keep for employees. If you like, tell us how many stays you handle each month, and how you manage employee stays today. We will be in touch about the pilot group.