Aimee Kurtz is the producer and executive producer of Death Punch TV, the backstage program The Mediatwist Group built around Five Finger Death Punch’s 2026 20th Anniversary World Tour, and runs the operations behind every Mediatwist production. She produced Sammy Hagar & The Circle’s “Funky Feng Shui” video with Mediatwist founder Chris Kurtz. Aimee leads the production side from the Rock Lititz campus in Lititz, Pennsylvania.
Every arena has a production office. It has a tour manager's office, a wardrobe room, a catering room and, somewhere down a corridor that smells of forklift exhaust, a dressing room with the band's name taped to the door. What most arenas do not have, and what most tours never set up, is a room where the night's content gets made while the night is still happening.
We call it the command center. Aimee Kurtz, who produces and executive produces Death Punch TV, designed how it runs. It is not glamorous. On a good night it is a folding table, two laptops, a card reader, a monitor showing the Facebook Event comments, and a person who has not sat down since load-in. On a great night it is the reason the band's feed at midnight looks like it came from a broadcast network and not from a phone.
What a command center is for
A touring band produces a staggering amount of raw material every day and throws almost all of it away. Not deliberately. It simply never gets captured, logged, cut and published before the bus leaves. The command center exists to close that gap on the same day.
Its outputs on a show night, in order:
- Pre-show. Countdown post in the city's official Facebook Event. Story frames from load-in and soundcheck. Keyword-trigger reminder so fans know which comment unlocks which card.
- Doors to downbeat. Fan segments shot at the barricade and in the concourse. These are the human-interest pieces that carry the Death Punch TV program.
- During the show. Nothing is published. The camera operator shoots crowd and side-stage; the command center logs timestamps against the setlist so the editor knows where the moments are.
- Post-show. The first short-form cut goes out while the crowd is still in the parking lot. The episode cut is assembled that night or the next morning and dropped into the archive by city and date.
- Overnight. Comment moderation and keyword flows are checked. Merch clicks are logged. Tomorrow's city gets its countdown post scheduled.
Why it has to be in the building
Remote editing works for the episode. It does not work for the moments. The clip of a fan's sign being read from the stage has a shelf life measured in hours. If the file has to be uploaded to a cloud folder, downloaded in Lititz, cut, approved and scheduled, the moment is gone and the post is a memory of a moment.
The other reason is access. A content person who is in the building, wearing a laminate, standing next to the production manager, gets told things. The drum tech mentions it is his 500th show with the band. The runner mentions the venue has a 40-year-old photo of the band's first visit in the hallway. Those are segments, and they only reach the feed if someone is there to hear them.
The real-time creative operation
Here is the part of the job nobody writes about because it sounds like admin. It is the job.
Footage discipline. Every file, from every device, gets named and filed by city and date before anyone sleeps. The Death Punch TV archive is organized exactly that way, which is why an episode for a July 31 Toronto show can be rebuilt months later from a folder that is unambiguous about what is in it.
The approval chain. A band's management has a say in what gets published. A command center that posts first and asks later will be shut down by week two. The chain we run: shooter to editor to the band's designated approver to publish, with a standing list of what never needs approval (countdowns, crew segments, fan segments that the fan consented to on camera) and what always does (anything with a band member's face in a non-performance context).
The automation layer. Keyword comment triggers, Messenger flows and card delivery run on their own once built, but someone watches them. A flow that breaks on a Friday night in Nashville needs a human in Nashville or a human awake in Pennsylvania. We have both.
The kill switch. Every scheduled post can be pulled in under a minute. Something happens at a show, a member is unwell, a city has an emergency, and a cheerful countdown post is suddenly the wrong thing in the feed. The command center's first job is editorial judgment, and its second job is speed.
The operator's role
The operator is the person in the room who is not holding a camera. On our tours that job sits with the operations side of The Mediatwist Group, run by Aimee Kurtz, and it is the job that decides whether the night's content is published or merely captured. The operator runs the feed, watches the comment and keyword flows, holds the approval list, owns the kill switch, and keeps the running list of segment ideas overheard that day. The shooter and the editor make the content. The operator makes the program.
The economics
A command center costs a person's travel and a laptop. On a 48-city tour that is real money, and it has to earn its place. It does so in three ways.
First, it produces the program content that drives the organic reach we described in the Death Punch TV case study, which the paid budget could not have bought at any price we were willing to spend.
Second, it produces the audience assets, the viewers and engagers and commenters, that make the next tour's paid campaigns start warm.
Third, it protects the band. A fan segment shot with consent, a crew segment that makes a tech feel seen, a kill switch that pulls a post before it becomes a problem: those are reputational outcomes that do not appear on a dashboard and that a manager will value more than any dashboard.
If you are setting one up
- Put it on the venue advance. "Content production office, one table, two chairs, power, hardline internet, near the production office." If it is not on the advance it will be on a flight case in a corridor.
- One shooter, one editor, one operator. The operator runs the feed, the comments, the automations and the approvals. The shooter and editor never touch the feed.
- Agree the approval chain in writing before the first show, including the list of things that do not need approval.
- File by city and date, every night, no exceptions.
- Build the kill switch before the first scheduled post.
- Keep a running list of segment ideas overheard that day. It is your editorial calendar.
If your tour has a production office and no content office, we can show you what a one-table setup produced across a 48-city run. mediatwistgroup.com/#contact
Sources
- Mediatwist internal production documentation: Death Punch TV archive structure, ManyChat trigger architecture, approval workflow (internal; cite as "Mediatwist operating procedures")
- Five Finger Death Punch 2026 tour routing (Live Nation announcement coverage)