LobbyOS · User Journeys
LobbyOS is the operating system for buildings that are more than buildings — homes, clubs, cafés, and the people who run them. These are five days at Vasari Wellness Club & Residences in Iowa City: 44 homes, a wellness club, a café, and a staff you can count on one hand.
Persona 01 · The Club Member
Vasari's club — hot pilates, yoga, sauna, red light, IV lounge, café — is open to the neighborhood. There's no membership office. There's a phone number on the glass.
Beat 1 · The text on the window
Kate walks past Vasari on her way to work. The glass says Text us. No app to download, no form, no "someone will reach out." She texts. LobbyOS answers in seconds — and books her into Thursday's intro class in three messages.
Beat 2 · Day of
No "what do I bring, where do I park" anxiety. The answer arrives before the question — and when she does have one, she gets a real answer, instantly, from the same thread.
Beat 3 · Joining, in the thread
No sales office, no clipboard, no "let me grab my manager." The membership, the card on file, the signature — all in the thread that already knows her.
Beat 4 · The smoothie
This is what hospitality looks like when the system knows the schedule, the café, and the person. One word back, and there's a smoothie with her name on it waiting at 7:05. From then on, it's just: "the usual?"
Beat 5 · Bringing Em
One text books them both. The guest pass lands on Kate's account; the waiver goes straight to Em's phone. By the time Em walks in, the front desk already knows her name.
Beat 6 · The statement
No portal, no PDF attachment, no "your statement is ready." The month in one text, the detail one reply away, autopay on the 3rd. Membership revenue, café revenue, guest revenue — one account.
Persona 02 · The Resident
For residents, the same thread that leased the apartment runs the whole life inside it — packages, maintenance, the club downstairs, one monthly statement.
Beat 1 · Leasing by text
No leasing-office phone tag, no "office hours are 9–5 Central." Real units, real prices, a video tour, and a lease signature — the whole funnel in one conversation.
Beat 2 · Move-in day, orchestrated
Elevator window reserved, parking spot assigned, access live at 9:00, wifi in the thread — and the boxes that beat him there are already in the unit. Move-in day, the worst day of renting, becomes the best demo of the building.
Beat 3 · The package
The everyday texture of living at Vasari: the building notices, offers, and follows through — in one message each way.
Beat 4 · The leak
This is the beat that sells operators: triage in seconds, a real fix scheduled with access handled and logged, and the loop closed with photographic proof. (You'll see this same leak twice more — from the ops desk, and from the plumber's truck.)
Beat 5 · The blend
Residents pay for the club like everyone else — but it's one reply to add and one account to carry it. Rent, yoga, sauna, smoothie: the same thread, the same statement. This is the integrated-building story no standalone gym or PMS can tell.
Beat 6 · One statement
Rent, club, café — one text, one autopay. For the operator, that's three revenue lines reconciled into one account, automatically.
Persona 03 · The Director of Operations
Every text in chapters 1, 2, and 5 was LobbyOS doing the work. This is the human it reports to — the only full-time operations hire for 44 homes, a club, a café, and a med spa.
Panel 1 · 7:42a — the overnight
Dana opens LobbyOS with her coffee. Everything that happened while she slept — handled, logged, summarized. She reads two of the AI's conversation transcripts the way a chef tastes the soup: not because she has to, but because the standard is hers.
Panel 2 · The escalation queue
LobbyOS doesn't dump raw problems on Dana — it brings decisions, pre-staged. A refund above her auto-approve threshold, a guarantor's lease question, one conversation flagged for tone with a softened reply ready. Nine minutes, all three cleared.
Panel 3 · The dispatch
Sunday 10:07pm: resident texts a photo. By the time Dana sees it Tuesday morning, LobbyOS has triaged it, matched the right vendor, attached the photos, and drafted the dispatch with three windows. Her entire involvement in the leak — chapter 2, beat 4; chapter 5, all of it — is one tap.
Panel 4 · The midday glance
Utilization isn't a monthly report — it's live, and it comes with suggestions. The Thursday 6p waitlist has been three weeks deep; LobbyOS proposes a 7:15p section. One tap: scheduled, instructor asked, waitlisted members notified first.
Panel 5 · 5:30p
44 units, a club, a café, a med spa — one director, no office staff, no answering service, no seat licenses. LobbyOS takes the night shift, and tomorrow's overnight card will look like today's: handled.
Persona 04 · The Front Desk
The building's phone number is LobbyOS. The calls, the texts, the bookings, the questions — absorbed. What's left for Marcus is the part software can't do: being there, by name, in person.
Beat 1 · 8:40a — the arrivals board
The 9:00a hot pilates roster, with the two things a great host needs: who's new, and what to say. Em — Kate's guest from chapter 1 — is pre-cleared, waiver signed, with a greet note. No clipboard at the door, ever.
| Reformer | Name | |
|---|---|---|
| 1 | J. Park | Member |
| 2 | S. Okafor | Member |
| 4 | Kate Morrow The usual smoothie fires at checkout | Member |
| 5 | T. Nguyen First class since March — welcome back | Returning |
| 6 | Em Castillo Kate's guest · waiver signed · greet her | Guest |
Beat 2 · The greet
That sentence is the product. LobbyOS did the lookup, the waiver, the room assignment — so the first human moment at Vasari is a host who already knows you, not a tablet asking you to check in.
The division of labor
Every routine question Marcus doesn't answer by phone is a member he greets by name instead.
Beat 3 · The smoothie queue
Kate's class checks out at 6:55p; her Recovery fires to the café queue automatically, name on the cup. The order-taking disappeared — the hospitality didn't.
Beat 4 · The one ping
A locker won't open. LobbyOS can't fix hardware — so it pings the person who can, with everything he needs to walk over and fix it in 40 seconds. That's the only interruption of his morning.
Beat 5 · 3:00p — the handoff
The day's narrative — who came in, what happened, what's pending — wrote itself as it happened. The next shift's console already knows everything Marcus's did. Turnover stops being a leak in the operation.
Persona 05 · The Third-Party Pro
The same leak from chapters 2 and 3 — now from the plumber's truck. LobbyOS meets vendors where they already are: plain SMS. No portal, no app, no phone tag with an office that doesn't exist.
Beat 1 · The job offer
Scope, photos, access situation, three windows. He replies with one character, from a job site, between fittings. This is what Dana's single tap in chapter 3 looked like when it landed.
Beat 2 · Day of
Visitor parking, garage code, a door that unlocks for his phone number inside his window — with every entry logged. Building security and vendor convenience stop being a trade-off.
Beat 3 · The fix
His "done" photo closes the ticket, notifies Daniel upstairs, and updates Dana's dashboard — chapters 2, 3, and 5 resolving in the same second. Nobody wrote a status update. Nobody will ask "any word on the plumber?"
Beat 4 · The kicker
No portal logins, no net-60, no voicemail tag. Next month another text comes; he replies in nine seconds. The best vendor experience in the industry is the one that's indistinguishable from a good customer texting you — and the building gets faster service and better rates because of it.
The point
Kate, Daniel, Dana, Marcus, and Rick never saw the same screen — most of them never saw a screen at all. LobbyOS is the front desk, leasing office, booking system, billing department, dispatcher, and night shift — for buildings that are more than buildings.