Host Inputs & Ask-List (Nava House)
What this page is for
This page collects the concrete questions and inputs we’d ideally get from you (Skye) to turn the Nava House snapshot into a co-designed node plan. It’s the “what we’d need from you” list, written out in one place.
How to use this page
You don’t need to answer everything in one go. You can:
- Respond in whatever format is easiest (text, voice note, call).
- Skip anything that doesn’t feel relevant yet.
- Flag anything that feels off or misframed.
How we will use this page
As you answer pieces of this ask-list, we’ll:
- Correct our outside-in assumptions about Nava House.
- Refine the node plan, including boundaries and economics.
- Update this bundle so future versions reflect your actual preferences and constraints.
The current ask-list for Nava House
NAVA Node Offering — Skye Ask-List (Draft v1)
Intent
------
Help you quickly decide whether it makes sense to keep exploring NAVA by:
- showing what we’d need from you,
- keeping the lift as light as possible, and
- giving you enough clarity to say “yes, keep going” or “no, not now.”
1) Property & Portfolio Snapshot
--------------------------------
1. What property (or properties) do you want to explore first as a NAVA node?
- Location(s)
- Property type (single-family, small multi, estate, etc.)
- Current use (full-time STR, hybrid personal use, etc.)
2. For the lead candidate property, can you share:
- Typical nightly rate range (low / mid / high season)
- Occupancy range (even rough bands are fine)
- Any standout amenities or constraints (e.g., HOA rules, noise, parking limits)
3. Are there any other properties “on deck” that you might want to consider later,
or should we treat this first node as a focused pilot?
2) Operations & Team
--------------------
4. How is the property currently managed?
- Self-managed, cohost, or full-service manager?
- Any existing local staff/vendors (cleaning, maintenance, concierge, chef, etc.)?
5. Who would be the day-to-day point of contact for NAVA-related changes
(e.g., adding amenities, updating listings, coordinating local experiences)?
6. Are there any operational constraints we should assume from the start?
- Maximum acceptable change to your current workflows
- Scheduling limits (e.g., only between guest stays, only certain months)
3) Ideal Guest & Positioning
----------------------------
7. When you picture the “ideal guest” for this property over the next 1–3 years,
who are they?
- Demographics (roughly) and interests
- What they care about most in a stay (privacy, wellness, convenience, status, etc.)
8. How do you *want* the property to be positioned versus the market?
- Quiet retreat, wellness/performer hub, extended-stay remote work base, etc.
- Any brands, experiences, or hotels you’d like to be “in the same conversation” with?
9. Are there guest segments or use cases you explicitly do *not* want to serve?
4) Economics & Expectations
---------------------------
(We don’t need perfect numbers; directional is fine.)
10. What’s your rough baseline today for the lead property?
- Average nightly rate (or range)
- Average occupancy (or range)
- Any sense of seasonality we should know about?
11. When you think about NAVA improvements (amenities, programming, positioning),
what outcomes feel meaningful enough to be “worth it” to you?
- Better occupancy, higher ADR, better guests, more repeat stays, etc.
12. Are there any hard financial constraints or guardrails we should respect?
- Maximum upfront investment you’d even consider
- Appetite (or lack thereof) for performance-based or rev-share structures
5) Tech, Privacy & Data
-----------------------
13. What tools are you currently using today?
- PMS / channel manager, smart locks, cameras (if any), guest messaging, etc.
14. How do you feel about guest privacy and data today?
- Any red lines (e.g., what data you don’t want collected or stored)
- Any compliance or regulatory constraints we should assume
15. Are you open to running a more “privacy-forward” stack
(e.g., fewer invasive sensors, clearer guest data handling)
if we can keep operations manageable and economics healthy?
6) Local Ecosystem & Community
------------------------------
16. What local relationships exist already (if any)?
- Wellness providers, chefs, guides, artists, healers, etc.
17. Are you interested in connecting the property more intentionally
into the local community (events, residencies, memberships)?
- If yes, are there any specific directions that feel exciting or off-limits?
7) Risk, Time, and Communication
--------------------------------
18. What are your biggest concerns or risks you’d want us to keep front-of-mind?
- Guest risk, brand risk, regulatory, neighbor/community, energy/complexity, etc.
19. Realistically, how much time/attention can you (or your delegate) give this
over the next 3–6 months?
- A quick monthly check-in? A deeper design sprint at the start?
20. How would you *prefer* to interact with us if we proceed?
- Async updates + occasional calls, or a short, intense setup phase, etc.
8) Decision & Next Step
-----------------------
21. When you look at this list, what’s the minimum set of questions we should answer
together before you can confidently say “yes, let’s keep going” or “no, not now”?
22. Is there anything key we didn’t ask that you wish we had?
(This helps us avoid missing the one thing that really matters to you.)
How we’ll use your answers
--------------------------
- We’ll keep your inputs private and scoped to building a NAVA node plan for you.
- We’ll use them to sketch a first-pass node plan (amenities, positioning, economics, and roadmap).
- You’ll get something you can react to quickly: does this feel aligned and worth continued exploration?