How it works · onboarding to steady state

Set up in two weeks. Quietly running by week three.

No platform to learn, no migration weekend, no six-week implementation. We learn your portfolio, write the runbook in your voice, shadow your team, and then take the operational tail off your desk — on a fixed, predictable cadence.

  • 14 daysFrom call to live coverage
  • 1–3 operatorsNamed to your portfolio
  • 60-day pilotCancel any time
§ 01 · The arc

Four steps. No surprises.

  1. 01

    Discovery call & portfolio walk

    45 minutes. We learn the doors, the team, the software, the quirks — and where the operational pain actually sits.

    Day 0 · 45 min
  2. 02

    Runbook drafted in your voice

    We write the playbook your team would have written if they had a quiet week. Triage trees, vendor preferences, escalation rules, owner-comms tone.

    Days 1–7
  3. 03

    Soft handover — we shadow

    We sit alongside your team, handling overflow first. Calls forwarded, tickets shared. You correct us in real time.

    Days 8–14
  4. 04

    Full coverage. Monthly review.

    Lines, tickets, renewals, notices — running. We send a Friday digest weekly and a portfolio review every month.

    Day 15 onward
§ 02 · Inside each phase

Who does what, and when.

Every phase is a two-sided handshake. Here's exactly what we own, what we need from you, and what lands on your desk by the end of it.

Phase 01

Discovery & portfolio walk

One call to understand the shape of the work — and tell you honestly if we fit.

Day 0 · 45 min
We do
  • Map doors, software, team and after-hours load
  • Locate where the operational pain really sits
  • Give a straight read on fit and first targets
You bring
  • A rough door count and your current tools
  • The 2–3 things that wake you up at night
  • Any vendor or escalation must-knows
You get
  • An honest fit assessment — no deck
  • The shortlist of what we'd take first
  • A timeline and pilot terms in writing
Phase 02

Runbook drafted in your voice

The playbook your team would write with a quiet week — written for you.

Days 1–7
We do
  • Build triage trees and escalation thresholds
  • Record vendor preferences and call order
  • Set the owner-comms tone in your voice
You do
  • Review the draft and correct the voice
  • Approve who gets called, and when
  • Flag the edge cases we couldn't know
You get
  • A living runbook, versioned and shared
  • Clear escalation rules everyone can see
  • A single source of truth for your ops
Phase 03

Soft handover — we shadow

We take overflow first while you watch, so nothing goes live untested.

Days 8–14
We do
  • Handle forwarded calls and shared tickets
  • Run the runbook live, under your eye
  • Log every judgment call for review
You do
  • Correct us in real time as things come in
  • Tune thresholds that feel too loose or tight
  • Decide when you're ready for full coverage
You get
  • Proof the lines are covered before go-live
  • A runbook hardened by real tickets
  • Named operators your team already knows
Phase 04

Full coverage & monthly review

Steady state. The tail is handled — you stay informed, not involved.

Day 15 onward
We do
  • Run lines, tickets, renewals and notices
  • Dispatch vendors and track to resolution
  • Send a Friday digest, every week
You do
  • Read the digest in a few minutes
  • Join one monthly portfolio review
  • Adjust scope as your doors change
You get
  • The operational tail off your desk
  • A monthly view of trends and renewals
  • Headroom to do the strategic work
§ 03 · Once we're live

The operating rhythm.

Coverage runs on a predictable cadence. You always know what we're doing, what came in, and what — if anything — needs you.

Daily

Always-on

The line is answered and the queue is worked — in your name, by your rules.

  • Tenant & guest line answered and triaged
  • Maintenance intake and vendor dispatch
  • Escalations routed per your thresholds

Weekly

Friday digest

One short note that closes the week — no dashboards to check.

  • What came in and how it was handled
  • Open items waiting on a vendor or you
  • Anything that bent the runbook

Monthly

Portfolio review

A working session on the patterns behind the tickets.

  • Trends, recurring issues, vendor performance
  • Renewals and notices coming up
  • What to adjust in the runbook next

Note · Same engine, two tempos. Long-term residential runs on a business-hours-plus-on-call rhythm; Arvallis // Stays runs 24/7 to hospitality velocity. The cadence above adapts to whichever doors you hand us.

§ Start here

Two weeks from now,
it's just running.

A 45-minute discovery call. We listen, ask the dumb questions, and tell you honestly whether Arvallis is the right shape for your portfolio. No deck. No follow-up nurture sequence.

  • Avail Mon–Fri · 9a–6p ET
  • Reply Within one business day
  • Pilot 60 days · cancel any time