Three active homestay units are represented as separate HOS operating records.
Operating evidence · First-party operating environment
HOS in operation: Kay House.
Kay House gives SheetSolutions a real operating environment where HOS has to deal with the same things hospitality teams deal with every day: multiple properties, channel bookings, direct reservations, historical records, operating expenses, accounting context, calendar synchronization, and owner oversight.
Relationship disclosure
Kay House is connected to SheetSolutions and is used as a first-party operating environment for HOS development and validation. This is not an independent customer testimonial, and this page does not claim third-party endorsement.
Evidence snapshot · reviewed September 2026
What is verifiably present in the operating environment.
The snapshot is intentionally non-sensitive: it proves product use and operating structure without exposing guest or financial detail.
Channel context is represented explicitly instead of being inferred from free-form notes.
Historical operational records predating the current HOS deployment are present in structured booking and expense records.
Operational finance is represented with source relationships rather than as an isolated summary number.
Airbnb iCal connection metadata exists per property with successful synchronization history.
The live tenant environment includes operational notifications, Kay House branding, and receipt configuration.
Operating transition
From fragmented records toward connected operating context.
This is not a before-and-after performance claim. It documents how the operating model is represented differently inside HOS.
01Property & reservation context
Earlier / fragmented context
Property, booking source, guest stay, and status can be represented differently across booking channels and operational records.
Current HOS operating model
HOS keeps each booking connected to a property, channel, stay dates, guest record, booking status, and payment-status context.
02Historical migration
Earlier / fragmented context
Older operating history can remain trapped in legacy files or earlier record structures even after a new application exists.
Current HOS operating model
Kay House uses structured HOS records that include historical booking and expense activity predating the current deployment.
03Operational finance
Earlier / fragmented context
Expenses and booking money can be recorded without a consistent accounting relationship to the event that created them.
Current HOS operating model
Kay House finance data is represented through structured booking charges, expenses, finance workflows, and double-entry journal records.
04Calendar coordination
Earlier / fragmented context
Channel calendar state can require separate checking and does not automatically explain the rest of the operating context.
Current HOS operating model
HOS stores safe Airbnb iCal connector metadata, synchronization runs, and normalized availability blocks per property.
05Owner-facing operating state
Earlier / fragmented context
The owner may need to reconstruct what happened by checking booking, finance, property, and communication context separately.
Current HOS operating model
HOS is being developed around a connected operating model where property, booking, finance, notification, and evidence state can be reviewed together.
Evidence boundaries
What this case study does not claim.
01
No guest names, contact details, payment credentials, private notes, receipt contents, or raw calendar URLs are published on this page.
02
No revenue-growth, time-saving, occupancy, profitability, or ROI percentage is claimed because those outcomes have not been established through an independent controlled study.
03
A configured capability is not presented as universal product availability. Integration and automation scope still depends on the deployed HOS release.
04
Kay House is first-party evidence of product use and operating fit. It is not presented as an independent reference customer.
Topic context
Browse all topics →See where this page fits in the wider HOS operating model.
01Multi-property operating contextPortfolio Operations
A connected HOS topic cluster for multi-property operations, owner dashboards, occupancy and revenue metrics, booking windows, and portfolio-level evidence.
Open topic →02Stay-aware guest workflowGuest OperationsA HOS topic cluster for pre-arrival, check-in, in-stay requests, property instructions, issue escalation, and guest-related operating context.
Open topic →03Property preparation between staysTurnover & ReadinessA HOS topic cluster covering vacation-rental cleaning, turnovers, housekeeping tasks, readiness evidence, maintenance exceptions, and upcoming arrivals.
Open topic →04Operational finance with traceabilityFinance & EvidenceA HOS topic cluster for payments, payouts, expenses, receipts, reconciliation, property metrics, evidence, and owner financial review.
Open topic →