Building an Agent Swarm to Run a Hotel in 4 Hours

By Peter Sitati

1. Quick intro

I’m Peter Sitati, and I’m building a multi-agent concierge for hotels — one that works both guest-facing and internally. I’m drawn to the intersection of customer acquisition, retention, and operational efficiency, and hotels have all three challenges showing up at the same time. It tackles coordination on both fronts: keeping guests served across booking, dining, and activities, while keeping the back-office (housekeeping, finance, ops) in sync underneath.

2. The hackathon experience

I’d been working on agentic development since around Christmas 2025 — mostly personal projects on LangGraph. By the time the HeyLua hackathon came up, I was looking for an excuse to get out among other devs, see what people were actually shipping, and put a different framework through its paces. The docs looked easy to get going with, so I signed up.

The build went smoothly. The platform was well documented, and Spaces — released fairly recently — was something I figured out and shipped inside the hackathon window. Coming from LangGraph, the supervisor abstraction felt familiar without the boilerplate I was used to. The biggest surprises were the onboarding (email plus an OTP and you’re in) and the breadth of ideas other devs brought to the table — the verticals people were building into were genuinely varied.

3. The platform in action

Savannah Ridge concierge runs the moving parts of a hotel — booking, housekeeping, food and beverage, finance, entertainment, customer success, plus a task manager handling cross-department ops and daily briefings. It’s built for hotels juggling guest experience and back-of-house ops without enterprise budgets. Under the hood that’s seven specialist agents and 41 tools coordinated by a supervisor (HeyLua’s Space), routing each guest message — over WhatsApp or a web widget — to whoever should handle it.

Architecture: a Space supervisor routes guest messages to seven specialist agents; service agents emit cross-agent webhooks (charge + activity) that land in Finance and Customer Success

The interesting part is what happens between the agents. When a booking lands, the charge flows to Finance, the activity flows to Customer Success, and the guest profile gets broadcast to every agent — so the dining coordinator already knows who you are when you ask about dinner. Hotels have a lot of pieces that have to stay in sync, and that cross-agent traffic is how things stop slipping through the cracks. It plugs into existing hotel software via outbound calls, so it’s not a rip-and-replace — it sits on top of what’s already there.

4. What’s next

Post-hackathon, the plan is to get the agent in front of a few real hotels — see whether it actually solves the problems on the ground, or just the ones I imagined during the build. I’d like to work side-by-side with the early adopters; they’ll surface things I couldn’t have captured solo. From there it’s iterating until the platform can scale to serve as many hotels as want it.