Are Event Teams Marketing or Demand Gen?

TL;DR

Event teams buried under marketing are being measured on the wrong thing — and one answer in a game of Beta or Bust makes the case in ten seconds. In this episode of Event About It, Megan Martin sits down with Huong Nguyen, 2x CEO founder of Shiloh Events and Aletheia, to unpack why the reporting structure question matters more than most teams realize, and why the conversation goes well beyond org charts.

  • Event teams under demand gen move pipeline faster than event teams under marketing, because demand gen measures outcomes, not attendance.
  • A hotel’s refusal to budge on 150 empty rooms after a client’s surprise layoffs is a contract negotiation lesson every planner needs to hear before it happens to them.
  • When the pipes burst mid-keynote at a San Francisco shipping port, Huong’s team built a new conference in a parking lot overnight. The AV equipment bill that followed is the reason she talks about event insurance now.
  • Ten years of building a multi-million dollar agency without a LinkedIn presence is not a cautionary tale. It is a retention strategy.
  • The NVIDIA employee who vibe coded his own event platform on Claude learned exactly where that approach breaks — and Huong watched it happen.

Key Takeaway: The event team reporting structure is not an administrative decision. It is a pipeline decision. Where the team sits determines what they measure, and what they measure determines what they produce.

Summary

Huong Nguyen started her career producing events for NASA — yes, the actual one — co-founded Zoomtopia, and spent 13 years building Shiloh Events into a multi-million dollar agency serving Zoom, Microsoft, Samsung, LG, Uber, and Google without most of the events industry knowing her name. She named her company Shiloh, Hebrew for peace. She is now building Aletheia, an AI-powered intelligence platform for event operations, because she got tired of waiting for someone else to solve the problem she had been living with for over a decade.

This episode covers:

  • Why demand gen is the right home for event teams — not marketing — and what that reporting line change actually does to accountability and measurement
  • The hotel contract clause most planners overlook until a client downsizes without warning and 150 rooms sit empty
  • What actually happens when the pipes burst during a keynote at a San Francisco shipping port, and how to move an entire conference to a parking lot overnight
  • Why ten years of building a seven-figure agency without a personal brand was a deliberate strategy, not an oversight
  • What a $500K contract at age 24 taught her about working for free, timing, and what clients are actually buying when they hire a small agency
  • Why vibe coding gets you a prototype and leaves you with a maintenance problem — and the NVIDIA client story that proves it

If you run event programs and you are still trying to justify the investment in a marketing meeting, this is the conversation to share up the chain and across the table.

Key Themes & Takeaways

1. The Ten-Second Answer to the Demand Gen Question

“Marketing’s great, but I think demand gen denotes a more higher return on investment because you’re generating demand that yields more business. For me when I hear demand gen, I hear more of an aggressive action. Whereas marketing is like an awareness.”

The Question: Move your event team under demand gen instead of marketing — beta or bust?

The Answer: Beta. Without hesitation.

Why It Matters: This was one of ten takes in a game of Beta or Bust, and it was one of the few that landed without debate. Huong’s reasoning is not complicated. Demand gen has a number it is accountable to. Marketing has awareness metrics that are easier to hide behind. When an event team sits under demand gen, the attribution question becomes harder to avoid and easier to answer, because the entire function is measured against pipeline, not impressions.

Megan’s follow-on point: event teams are cross-functional by nature. They touch sales, marketing, product, and brand simultaneously. That footprint does not belong in a function that measures reach. It belongs in a function that measures revenue.

Key Takeaway: Where your event team reports determines what question they get asked on Monday morning. Demand gen asks what did this produce. Marketing asks how did it go. The first question makes better events.

2. Logistics Is the Easy Part. Emotion Is Where Pipeline Lives.

“Logistics that’s easy. Anyone can do that in their sleep, to be honest with you. But the emotional part of it, it takes a lot of human intelligence, empathy, emotional intelligence, understanding your audience. All of that drives attention, retention.”

The Game Take: Design your event for emotion first, logistics second — beta or bust?

The Answer: Beta. Immediately.

What She Means: Huong is not talking about making people cry, though the cold open of this episode does make the business case for the ugly cry. She is talking about sequencing. Most event teams build logistics first: the venue, the agenda, the room block, the catering minimums. Emotion gets layered in as an afterthought, usually in the form of a “wow moment” that has no strategic anchor.

Designing for emotion first means understanding what your attendee is walking in with before you design what they walk away with. The logistics should serve that arc, not compete with it. Retention is the signal — if people come back year over year, something emotional is working. If they are not coming back, no amount of logistical polish fixes it.

Key Takeaway: The cold open of this episode says the most powerful thing at your next event is not an open bar. It is an open heart. That is not a brand statement. It is an outcomes framework.

3. The Vent: 150 Empty Rooms and a Hotel That Would Not Budge

“Events industry is very fluid and very like agile and it’s a lot of moving target. So we need vendors and we need partners who have that characteristic to flow with us. And that was very shocking for this one particular hotel.”

What Happened: A client had surprise executive departures followed by layoffs. Headcount dropped. Room block and F&B commitments were now wildly out of proportion to what the program actually needed. Huong went to the hotel to renegotiate. The hotel said no.

The Result: 150 empty rooms. An F&B minimum they had to meet by ordering food nobody was going to eat. Waste on both sides of the conversation.

The Business Reality the Hotel Missed: Those rooms were not going to sit empty. The hotel was going to resell them. The liability reduction Huong was asking for was not coming out of their revenue — it was coming out of paper commitments they were going to replace anyway. The rigidity was protecting nothing.

The Reputational Math: Huong’s point is short and precise. The events industry talks. A hotel that will not flex when a client has a corporate emergency gets quietly removed from the preferred list of every planner in that planner’s network.

What Planners Should Do Before Signing: Ask for the force majeure clause. Ask for the attrition clause and understand what triggers it. Ask what happens if headcount changes by more than 20 percent before the contracted date. Ask for the hotel’s insurance, not just the venue asking for yours. These are not aggressive asks. They are the difference between a contract and a partnership.

Key Takeaway: Rigidity protects revenue on paper and destroys relationships in practice. The question to ask before signing is not just what happens if something goes wrong — it is whether this property will work with you when it does.

4. The Pipes Burst Mid-Keynote. Here Is What Happened Next.

“We were all freaking out. And it even spilled into the keynote area. So during session, people got poured on.”

The Story: A tech conference at a San Francisco shipping port. Sponsor expo up. Keynote running. And then the pipes burst.

Water, everywhere. Falling on people, on furniture, on equipment. The fire sprinklers triggered. Thirty minutes for the firefighters to arrive and shut the valves. The keynote area flooded. Attendees sitting in session got wet.

The Overnight Pivot: Huong’s team made the call that most planners would spend hours debating. They closed the keynote space, moved everything out to the shipping port’s massive parking lot, and built a new conference footprint overnight. Keynote stage. Meal service. Expo. Lounge furniture. All of it, outside, by morning. It was August in San Francisco. The weather held.

What the AV Equipment Bill Looked Like: The LED screen was destroyed. Equipment that took a direct hit from the flooding was gone. Then the conversation nobody prepares for started: whose insurance covers this?

“It’s rare that we actually have to really call upon it, but you really need to think through your event insurance and look at the venue’s insurance. Typically they ask for our insurance, right? But we don’t ever ask for theirs.”

Key Takeaway: Rank your event’s technical and physical dependencies by what actually stops the show. Equipment getting wet is a budget problem. A keynote space flooding mid-session is an existential problem. The contingency planning and insurance coverage should reflect the difference.

The Aftershow

The main episode was the overview. The Aftershow is where Huong and Megan spent 45 minutes on the parts the events industry does not usually say out loud: how she built a seven-figure agency underground, what working for free actually bought her, why a vibe-coded event tool is not the same as a scalable event platform, and the mission underneath both of her companies.

5. The Myth of Needing to Be Visible First

“The myth that you need to get out there and be a credible leader before you can actually earn business is an absolute false myth.”

The Numbers: Shiloh’s client roster for its first ten years included Samsung, Philips, Hitachi, Fujitsu, LG, Zoom, Uber, and Google. None of it came from a LinkedIn presence. None of it came from speaking gigs or industry panels. It came from retention.

How the Machine Actually Worked: Huong worked for free for six months at the start. She made friends at NASA who were moving into the tech world. One referral led to Microsoft. She focused entirely on making Microsoft happy. Zoom came through Microsoft. Uber came through Zoom. Google came through Uber. At the time of this recording, Shiloh has been with Zoom for seven years.

“Just do well with what you have already. I have Zoom. I’m gonna do really well on Zoom. And they retained me up until now. We’ve been with them for seven years because I was so focused on making sure that they’re happy.”

Key Takeaway: Retention is a distribution strategy. When a client stays for seven years and refers you to three more, you never had to spend a dollar on marketing. Most agencies learn this too late because acquisition feels like growth and retention feels like maintenance. They are the same thing from different directions.

6. Working for Free at 24. Half a Million Dollar Contract. One Year In.

“I was able to secure Grace Hopper conference, which is 20,000 people in Houston, and the lady who interviewed me just so happened to see me as her daughter. And I was 24. And she’s like, ‘My God, you’re so young and you have this agency. Let me give you a try.’ And it was a half a million dollar contract. I was like, whoa.”

The Setup: After her MBA, Huong could not get hired. She expected doors to open. They did not. She decided to work for free for six months, planning events for nonprofit contacts, building relationships, proving the work.

What Free Work Actually Bought: A donor at one nonprofit she was working with was a senior VP at a major company. He brought her in. From there it was NASA contacts who had moved to Microsoft. From Microsoft to Zoom. From Zoom to Grace Hopper — 20,000 attendees, $500K, when she was 24 years old.

Key Takeaway: The first clients you get for free are not the work. They are the proof. The proof opens the next door, which opens the next one. Nobody builds a seven-figure agency in year one by winning on pitch decks. They win it by making the first ten clients so satisfied that the clients do the selling for them.

7. Why You Cannot Vibe Code Real Event Technology

“Do it for fun, but don’t take it too seriously because it really takes away from your core discipline of a planner. If you want to be a coder, go be a coder, but don’t be a planner and a coder.”

What She Tried First: Before building Aletheia with a dedicated two-woman engineering team, Huong tried Replit and Lovable. Her assessment: “It still wasn’t perfect. It looked stale, it wasn’t customizable.”

The NVIDIA Story: One of her longtime clients moved to NVIDIA and built his own tool on Claude to integrate the marketing, sales, and event planning functions. It was impressive work. The problem was execution — getting a broader team to adopt it, security compliance, deployment at scale.

“He’s facing this enormous mountain of resistance against it.”

Megan’s addition: the part of the vibe coding conversation that gets skipped is maintenance. You can build something in an afternoon. Keeping it secure, integrating it with other platforms, updating it when APIs change, expanding it across event types — that is a full-time job stacked on top of the full-time job of running event programs.

“I just felt a lot of pain of events from both agency and my client. And it was enough pain where I felt it would be worth it if I took on additional pain to solve that problem.”

Key Takeaway: Vibe coding is not the same as building event technology. One is an afternoon project. The other is what Huong has been doing for a year and a half with a dedicated engineering team — and she will tell you it is harder than the agency work she has been doing for 13 years.

8. Shiloh Means Peace. Aletheia Means Truth. That Is Not a Coincidence.

“I am trying to create a world in which we can be more organized, more centered, a central source of truth so that we can operate more peacefully. The ultimate goal is work life balance. To evolve this industry that was glorified for hustle and turn it into something where I actually like my industry.”

The Mission: Huong named her first company Shiloh, Hebrew for peace, because that was what she wanted to deliver to the clients who hired her. She named her second company Aletheia, Greek for truth, because truth is what event operations are missing — a central, accurate, real-time picture of what is happening across a program.

Key Takeaway: The most powerful event technology companies are going to be built by people who have lived the problems they are solving, not by people who spotted a gap in a market report. Huong has 13 years of operational scars. That is the product brief nobody else has.

Final Word

There is a version of this conversation that is about org chart decisions and insurance clauses. That version is useful.

What this episode actually is, is a 13-year case study in building from the inside out. Huong did not need visibility to build Shiloh. She did not need a big agency reputation to land a $500K contract. She did not need a tech background to build Aletheia. What she needed — and built deliberately over a decade of client work that most of the industry did not see — was the experience to know what the problem was, the patience to wait until she could solve it credibly, and the confidence to show up ten years later and say what she had learned.

The cold open of this episode says the most powerful thing at your next event is not an open bar. It is an open heart.

Thirteen years of invisible hustle, parking lot pivots, and 2 AM engineering conversations is what an open heart actually looks like in an events career.

“Until next time, keep growing, keep laughing, and keep eventing about it.” — Megan Martin

Frequently Asked Questions

Should an event team report to demand gen or marketing?

The case for demand gen is measurability. Demand gen functions are accountable to pipeline numbers, not awareness metrics. When an event team sits under demand gen, attribution becomes a shared responsibility rather than an afterthought, and the team’s success is measured by what it produces for revenue — not by how the event rated on a satisfaction survey. For event teams trying to prove ROI at a leadership level, the reporting structure is often the first thing to fix.

What is Aletheia and what does it do for event planners?

Aletheia is an AI-powered intelligence platform for event operations, built by Huong Nguyen, CEO and founder of Shiloh Events. It pre-engineers AI prompts for specific event workflows — budget, food and beverage, venue sourcing and proposal analysis, speaker management, timelines, revenue, and attendee data — so planners do not have to manually think through how to ask the right questions. The goal is to reduce time spent on operational execution so planners can focus on strategy and experience design.

Is attendee satisfaction a good event success metric?

Not as a primary metric. Huong’s assessment in this episode is that attendee satisfaction alone displaces other factors that are equally or more important: pipeline in the room, account composition, renewal risk of attending clients, and year-over-year attendee retention rate. Satisfaction is a useful signal but is a logistics metric, not a business metric. Executives consistently want to know who was in the room and what it produced — not how people felt about the coffee station.

Can you vibe code your own event technology?

You can prototype something. Building scalable event technology is a different undertaking. Vibe-coded tools work for a specific use case at a specific size and do not automatically adapt across program types, event sizes, sponsor configurations, or revenue models. The hidden cost is maintenance: security compliance, API changes, adoption by a broader team, and updates as the platform evolves. Huong’s advice: do it for fun and treat it as exploration, not as a replacement for purpose-built event technology.

How do you negotiate a hotel room block when your client’s headcount is cut?

The time to negotiate this is before signing the contract. Ask for attrition clauses with realistic thresholds — most planners accept the standard 80 percent hold, but a 60 to 70 percent trigger with a defined remediation process gives you more flexibility. Ask whether the hotel will release rooms from your block if they resell them. Ask for a force majeure clause that explicitly covers significant organizational changes on the client side. After the contract is signed, your leverage drops substantially.

What event insurance clauses do planners most often miss?

Two specifically. First, most venues ask for the planner’s or agency’s insurance but rarely offer their own. Ask for the venue’s insurance documentation and understand what it covers if their property fails during your event. Second, understand whose liability applies to rented equipment damaged by a third party’s infrastructure failure. In the burst pipes scenario in this episode, the AV equipment destroyed by the flood came down to whether the venue’s property failure triggered their coverage or the planner’s. Know the answer before you need it.

How did Huong Nguyen build Shiloh Events without personal branding?

By focusing entirely on retention rather than acquisition. She worked for free for six months to prove the work, built her first paid client relationships through NASA contacts who had moved into tech, landed Microsoft, focused on making that client stay, and let Microsoft refer her to Zoom. Shiloh has been with Zoom for seven years. Zoom referred her to Uber. Uber referred her to Google. None of it required a LinkedIn presence, speaking engagements, or industry visibility.

What is the difference between vibe coding an event tool and building real event technology?

Scale and maintenance. A vibe-coded tool solves one problem for one program type at one size. Real event technology has to work across a 100-person field event, a 20,000-person flagship conference, a ticketed program with revenue goals, an internal SKO with no external sponsors, and every variation in between. It also has to be secure, maintainable, adoptable by a team, and updatable as underlying platforms change. Huong tried Replit and Lovable before building Aletheia with a dedicated engineering team. The vibe-coded attempts produced something that, in her words, “still wasn’t perfect. It looked stale, it wasn’t customizable.”

Listen & Subscribe

Subscribe to Event About It:

Connect with Huong Nguyen:

Related Episodes

About the Author

Megan Martin is the founder of M Squared Dynamics, a consulting, facilitation, and content strategy firm helping event leaders, marketers, and sales teams turn live experiences into measurable business growth. She’s the host and executive producer of Event About It, co-founder of Opportunity Hunters, and a two-time PCMA Visionary Award nominee (2022 winner). With nearly 20 years in the industry, Megan operates at the intersection of event strategy, marketing alignment, and behavioral intent signals, turning events from line items into pipeline drivers.

Connect with Megan and M Squared Dynamics:

Keep the Conversation Going

If this resonates, sign up for the Step and Repeat newsletter at msquareddynamics.com/stepandrepeatsignup for more on demand generation events, event ROI, and what it actually takes to build events that drive pipeline. And if you want to hear it in conversation, “Should Your Event Team Report to Demand Gen Instead of Marketing?” is the companion episode to this post — listen on EventAboutItPodcast.com.

Posted in