What this is
Custom Node.js automation tied ticketing, email, and show promotion across four locations. The Hyena’s portfolio build on my site states the outcome in plain numbers: millions of emails delivered, four venues on one spine, segmentation and venue-specific delivery in the same pipe.
This piece is not a victory lap. It is a governance map: where one system helped, where it tried to flatten voice, and what I would negotiate differently on a second pass.
What centralized well
Repeatable pipes beat ad-hoc sends when the calendar always moves. Announcements, pushes, re-engagement. If the workflow is stable, the machine can carry load humans should not re-type.
Segmentation discipline matters more than more email. The work is deciding what earns a touch, not blasting the list because Monday arrived.
One integration spine reduces the failure class where two venues run two truths about the same show.
Where it stayed messy
Brand versus room character. Comedy rooms are not interchangeable. Automation that standardizes too much does not sound confident. It sounds empty. The fight is not AI versus human. It is which lines may stay local without breaking compliance, deliverability, or truth in ticketing.
Throughput versus taste. Speed can become a habit. The risk is not only filters. It is audience fatigue dressed up as productivity.
Operational truth versus marketing narrative. Ticketing systems, door realities, and promo copy can disagree. When they do, the customer feels the seam before leadership does.
Multi-venue scale is won or lost on rules: what you standardize, what you localize, and what you refuse to automate because the cost shows up in trust, not metrics.
Tests I still run
If we removed the automation tomorrow, which venues would miss it first, and why?
Which messages must be identical for legal, safety, or partner reasons, and which must be authored because voice is the product?
Where is human approval a quality gate, and where is it covering fear of trusting the pipe?
I do not treat those as rhetorical. Different businesses answer them differently. The mistake is pretending one answer fits every room.
Last to show up on a dashboard
Trust fails last. It is also the slowest thing to recover once you burn it for a clean calendar.
Multi-venue email needs explicit rules for global versus local content. Otherwise scale becomes sameness.
- One spine reduces conflicting venue truth and manual re-entry.
- Centralization risks flattening room voice. Local rules must be designed, not assumed.
- Ticketing, door reality, and copy must stay aligned or customers feel the seam.
Impact. Operators who only optimize sends optimize noise. Operators who govern voice and truth protect repeat attendance.