AI Transformation for Concert Merch, Led by Someone Who Lived the Chaos
Fourteen years inside live commerce, artist merchandise, ecommerce, fulfillment, touring inventory, and reporting, turned into practical systems for the work merch teams fight through every day.
I learned this business from the inside: venue floors, vendor timelines, artist teams, Shopify launches, warehouse mismatches, settlement reports, inventory drift, and the spreadsheets everyone quietly depends on. Now I help merch companies turn that chaos into systems teams can actually trust.
I learned the business organically in the chaos, then started designing the systems it was missing.
Most merch companies don't have a people problem. They have disconnected tools, duplicated data entry, fragile handoffs, and reports that arrive too late to change the decision. I map the operating mess, design the workflows, and help turn them into internal tools teams can actually trust.
The operating layer behind modern merch.
Inventory integrity, settlement automation, PO workflows, reporting, forecasting, and barcode sync, mapped as operating systems instead of isolated tasks.

Fourteen years inside the machinery of live commerce and artist merchandise.
I've worked across the surfaces where merch companies actually win or bleed: venue floors, touring inventory, vendor timelines, artist and management expectations, ecommerce launches, warehouse handoffs, customer-facing store issues, reporting, and reconciliation.
That context is what lets me see the full operating system, not just one department's task list. I know where the spreadsheet is hiding, where the duplicate entry starts, where systems drift apart, and where the team stops trusting the data.
My work turns those patterns into practical systems: sync monitors, launch workflows, reporting engines, PO automation, forecasting models, and dashboards that give operators a cleaner way to run the business.
For merch teams running more complexity than their systems can handle.
Best fit: independent or mid-market merch teams running touring, ecommerce, and fulfillment across tools like atVenu, ShipHero, 3PL logistics, Shopify, NetSuite, Monday, and spreadsheets. If inventory, revenue, POs, or reports have to be reconciled by hand, that is the operating layer I help design.
The profile
- Independent full-service touring + ecommerce + fulfillment shops (the core ICP)
- Tour-vending / on-site-sales firms with heavy nightly settlement and inventory reconciliation
- Legacy/family-owned production + merch houses still running manual/spreadsheet ops
- Tech-forward marketplace/POD players (warmest near-term AI buyers; adjacent, position carefully)
- Label-/PE-owned global merch arms (later-stage lighthouse expansion, long sales cycles)
Who I talk to
- VP / Director of Operations (primary economic buyer, owns the day-to-day pain)
- Head of Ecommerce / Director of Fulfillment & Logistics
- Founder / Owner / COO (single decision-maker in owner-operated shops, fastest cycle)
- CFO / Controller (sign-off, since pain is framed as revenue leakage and settlement accuracy)
- Operator, account lead, or settlement analyst responsible for keeping the workflow moving
The pains I solve
- Inventory reconciliation across venues, 3PLs, and the ERP, counts drift and SKU/catalog mapping breaks (blank-row settlement bugs)
- Nightly settlement reconciliation done on calculators and fragile spreadsheets, causing artist over/under-payments
- Manual cross-system PO lifecycle: create in ERP, track in Monday, receive in WMS, reconcile back, error-prone relay
- Per-head ($/head) demand forecasting still done off gut and last-tour numbers, stockouts or dead stock
- Fragmented tooling with no single source of truth; spreadsheets glue atVenu, ShipHero, Shopify, NetSuite, and Monday together
- Lean teams running large volumes, the 'do more without adding headcount' squeeze
Does your merch operation still run on
Tell me where your merch ops still runs on spreadsheets, inventory drift, nightly settlement, PO re-keying, or gut-feel forecasting, and I'll tell you, honestly, what's automatable and what isn't. No pitch deck, just an operator's read on your stack.