Kiteville concept rendering of a landscaped courtyard with outdoor seating at golden hour

Kiteville · The operating model

Flexible living, operated as one connected system.

Centralized support and AI-assisted workflows are intended to reduce repetitive work, while local teams remain responsible for each property and resident experience.

Illustrative property image · Intended operating approach

The operating shift

Change the operation, not just the façade.

Kiteville’s intended model moves suitable properties away from a nightly hotel-service routine and toward flexible multi-unit living. Repeatable support can be shared; essential care stays close to the property.

01

Resident experience

Traditional hospitality

Nightly turnover and hotel-service routines

Kiteville’s intended model

Flexible stays and support organized around everyday living

02

Property support

Traditional hospitality

Administrative functions repeated at every location

Kiteville’s intended model

Shared support combined with accountable local teams

03

Portfolio information

Traditional hospitality

Disconnected property-by-property workflows

Kiteville’s intended model

Common reporting and operating visibility across participating properties

One connected operating model

Centralize the repeatable. Keep care local.

The ambition is a coordinated support layer across markets—not a claim of an existing worldwide network. Technology assists the workflow; people remain responsible for decisions and delivery.

01

Central support

Coordinate resident inquiries, administration, procurement standards and portfolio reporting through shared systems.

02

AI-assisted coordination

Support routine communication, organize service requests and surface operating patterns for human review.

03

Local property teams

Deliver inspections, repairs, cleanliness, safety and resident care with property-specific staffing and accountability.

Human oversight stays in the loop.Exceptions, sensitive resident matters, physical inspections and repairs require accountable people.

These are intended technology use cases, not a claim that every workflow is deployed. Adoption depends on integrations, data quality, privacy safeguards and property-specific needs.

The efficiency thesis

Reduce duplication, not essential service.

Potential efficiencies come from reorganizing work—not simply cutting staff. Software, central support and local delivery all belong in the property-level cost comparison.

01

Shared administration

Reduce duplicated support functions across participating properties.

02

Flexible-stay operations

Organize service around longer stays rather than nightly turnover alone.

03

Coordinated purchasing

Use common standards and nearby vendor routes where local economics support them.

04

Earlier issue visibility

Bring service and operating information together so teams can investigate sooner.

No verified savings percentage or margin improvement is presented. Efficiencies and investment returns are not assured.

Operating-model support

Cost discipline. Channel mix. Cash coverage.

Sponsor workbook assumptions inform diligence—not verified savings or a replacement for Tegra’s rent, occupancy and NOI scenarios.

Source: Kiteville_Financial_Projection_Model_structured.xlsx · received November 13, 2026 · Assumptions, Expense Breakdown, DSCR and Interest Reserve. Historical tabs have different revenue scopes and require reconciliation; workbook equity IRR is not a preferred-investor return.

Kiteville & Tegra

Operating experience. Independent capital oversight.

Kiteville’s multi-market property experience helps inform Tegra’s underwriting and operating questions.

Kiteville is Tegra’s initial, non-exclusive operating partner. Tegra independently evaluates acquisitions, financing and investment risk; other qualified operators can participate under property-specific approvals and agreements.