Hi HN, I’m Vincent, CTO of TeamOut (
https://www.teamout.com/). We build an AI agent that plans company events from start to finish entirely through conversation. Similar to how Lovable helps build websites through chat, we apply that approach to event planning. Our system handles venue sourcing, vendor coordination, flight cost estimation, itinerary building, and overall project management.
Here’s a demo: https://www.youtube.com/watch?v=QVyc-x-isjI. The product is live at https://app.teamout.com/ai and does not require signup.
We went through YC in 2022 but did not launch on HN at the time. Back then, the product was more traditional, closer to an Airbnb-style search marketplace. Over the past two years, after helping organize more than 1,200 events, we rebuilt the core system around an agent architecture that directly manages the planning process. With this new version live, it felt like the right moment to share it here since it represents a fundamentally different approach to planning events.
The problem: Planning a company retreat usually means choosing between three imperfect options: (1) Hire an event planner and pay significant fees and venue markups; (2) Do it yourself and spend dozens of hours on research, emails, and negotiation; or (3) Use tools like Airbnb that are not designed for group logistics or meeting space.
The difficulty is not just finding a venue. Even for 30 to 50 people, planning turns into weeks of back-and-forth emails for quotes, comparing inconsistent pricing across PDFs, and tracking budgets in spreadsheets. It becomes an ongoing coordination problem with evolving constraints and slow, asynchronous vendor responses. Most existing software is form-driven, but the real workflow is conversational and stateful.
Offsites are expensive and high stakes. A single event can represent a significant chunk of a team’s annual budget, and mistakes show up directly as cost overruns or poor experiences. Founders and operators often end up spending time on event logistics instead of their actual work.
I ran into this while organizing retreats at a previous company. Before TeamOut, I worked as an AI researcher at IBM on NLP and machine learning systems. Sitting inside long email threads and cost spreadsheets, it did not look like a marketplace gap to me. It looked like a reasoning and state management problem. As large language models improved at multi-step reasoning and tool use, it became realistic to automate the coordination layer itself.
Our Solution: The core agent relies on a combination of models such as Gemini, Claude, and GPT. A central LLM-based agent maintains planning context across turns and decides which specialized tool to call next.
Each tool has a specific responsibility: - Venue search and filtering - Cost estimations (accommodation + flights) - Budget comparisons - Quote and outreach flows - Communication tool with our team
For venue recommendations across more than 10,000 venues, we do not rely purely on the language model. We embed both user requirements and venues into vector representations and retrieve candidates using similarity search. Hard constraints such as capacity and dates are applied first, and results are ranked before being presented.
On the interface side, we use a split layout: conversation on the left and structured results on the right. As you refine the plan in chat, the event updates in real time, allowing an iterative workflow rather than a static search experience.
What is different is that we treat event planning as a stateful coordination problem rather than a one-shot search query. The agent orchestrates tools, manages evolving constraints, and surfaces trade-offs explicitly. It does not invent venues or fabricate pricing, and it is not designed to replace human planners for very large or highly customized events.
We make money from commissions on venue bookings. It is free for teams to explore options and plan.
If you’ve organized an offsite or large meetup before, I’d genuinely value your perspective. Where would you expect this to fail? What edge cases are we underestimating? Where wouldn’t you trust an agent to handle the details?
My engineering team and I will be here all day to answer questions, happy to go deep on architecture, tradeoffs, and lessons learned.
We’d really appreciate your candid feedback.
I completed a (rather large) contract to reverse-engineer, and eventually rebuild, a hotel chain's property management system from scratch from 2015-2018. We did it all: keycard integration, booking channel sync, credit cards, group bookings, yield management, front-desk GUI, supply management, taking rooms into/out of service, reservation migration from old system to new...you name it, we probably touched it. Dozens of small lessons about the lodging (and broader hospitality i.e. restaurants, country clubs, bars) business domain.
One thing is that hotel = brand (flag) + real estate + operations. You can remix those things in a lot of different ways, e.g. a single ownership group might have two properties on opposite sides of a street, one Hyatt the other Hilton, and they might look different but share staff, or procurement.
The industry's term for brand -- "flag" -- says a lot about how they view Hilton/Hyatt. They come and go, even if the staff running the property stays the same. The main reason hotels choose to flag vs. stay independent, is access to the chain's booking flow.
One of the more interesting consequences of this setup, is that small, independent hotels, are kind of a shit show in terms of technology. Chains generally require a lot of standardization of their member properties, including what software they run to manage the property. Many properties that don't affiliate with a chain don't have any property management system at all. It's basically 10-20 rooms run directly off the moral equivalent of an Excel sheet at the front desk. And why wouldn't it be--small boutique hotels often gross $1-2 million/year; there isn't budget for expensive enterprise software, or maybe more critically, the people who know how to deploy and operate it.
A significant value-add of Expedia and booking.com, especially with independent properties, is getting the supply (hotel) side of the market organized. Many of these hotels outsource their entire reservation tracking system to a single channel (e.g. booking.com) because trying to keep track of bookings across phone, direct web, Expedia, booking.com, and others, is just too hard without specialist software that requires more IT muscle to deploy than a single non-chain hotel can muster.
I mention this because I go to church every Sunday and was thinking about how much real estate churches have (event halls) that sit unused, and what a schlep it would be -- although good for everyone -- to expose the collective supply of the world's churches, HOAs, park districts, and other nonprofits, to the kind of events you're trying to do. It would indeed be a tremendous pain in the ass to get all the physical access (keys), contract terms, payment systems, availability, etc ironed out, but it's a massively underused class of real estate and many of these organizations could really use the cash.
reply