Marketing Technology:
Built for Content Support
Technology is only as good as the workflows it supports. Whether I’m navigating large-scale content migrations or integrating new AI-driven creative tools, my priority is the same: removing the friction that holds a team back.
“Ben is a kind, thoughtful and highly effective leader. He would be an extremely valuable addition to any technology leadership team.”
— Steven Stamps, Agentic AI Workforce Designer | Architect of Agentic Autonomous Workflows
Multi-channel support
2
Enterprise Migrations
Successfully managed corporate-wide CMS content transitions for MGM Resorts International
20+
Properties Consolidated
Brought content under uniform, corporate technical governance
100%
Headless Evolution
Supported transitioning legacy content to API-driven systems
Architecture & Platform Briefings
The Adobe Experience Manager (AEM) Consolidation
The Challenge Our web presence had grown into a fragmented collection of custom-coded sites. Every resort had its own unique, isolated setup, which created a massive headache: we were dealing with significant security gaps, we couldn't easily update our designs, and we had no reliable way to understand how our guests were interacting with our sites across the board. It was a classic case of tech sprawl.
The Approach I led the operational effort to pull our entire multi-brand footprint out of those isolated codebases and onto a single, centralized AEM platform. It was a massive migration, but the key was balance: I wanted to standardize our global components so we could move faster, while still giving our individual property teams the flexibility they needed to keep their marketing layouts unique to their specific brand.
The Business Impact By bringing everything under one roof, we finally had a predictable framework to work with. It drastically reduced our security risk, and by moving away from bespoke, custom-coded sites, we significantly cut the development costs and time required to launch new brands. Most importantly, we moved from managing dozens of disconnected technical problems to having one unified digital ecosystem.
The Evolution to Headless CMS (Contentstack)
The Challenge Even after we consolidated our properties onto AEM, the digital landscape kept changing. We weren't just managing websites anymore; we had to support mobile apps, kiosk displays, and a growing list of other digital touchpoints. Our existing platform was custom-designed and locked the content down, making it difficult and slow to push content out to all these new, varied channels. We needed a way to decouple our content so it could live anywhere.
The Approach As a team, we had to move away from that heavy, all-in-one structure towards a modern, "headless" approach using Contentstack. By using an API-first system, we stopped tethering our content to a specific web design and instead created a flexible engine where information could be pulled in by any channel. I guided the team in rethinking our content processes, ensuring they were built to support this new, multi-channel reality from the start.
The Business Impact The shift gave us the flexibility we needed. We moved away from being locked into a single presentation layer and achieved true universal content support. Now, whether it's an app or a website, the information stays consistent and updates automatically, allowing us to deliver a unified brand experience across every touchpoint without the technical overhead.
Technical Ecosystem Strengths
Enterprise CMS Support
Operational familiarity managing multi-million dollar platforms including Adobe Experience Manager and Contentstack.
API-First Omnichannel Strategies
Structuring modern, reusable data fields to seamlessly distribute brand content across applications and web endpoints.
Human-Centric Tech Governance
Ensuring new software acquisitions always streamline human workflows and increase throughput rather than creating tech bloat.
Utilized Technologies
Led teams using or worked directly with a wide range of technologies, including:
- Various AI LLMs
-
ComfyUI and Gradio for direct local processor AI image and video workflows
- Fooocus, Stable Diffusion, Wan 2.2
- LoRA creation and utilization via Kohya
- Adobe Experience Manager (AEM) CMS
- Contentstack CMS
- WebDam Asset Management System
- Adobe Campaign Standard
- Moz SEO Content Aggregator
- Yext SEO Content Aggregator
- Google Business Profile management (400+ outlets)
- HTML, CSS
- Python
- Jira
- Confluence
- GitHub
- Figma
Did You Know?
Using the AI creation engines ComfyUI and Gradio hosted locally allows me to create, refine, and build AI image and video workflows without using paid tokens. This encourages an extensive amount of testing and experimentation using many different AI models.