JS
John Shelton Marketing Ops · RevOps
← Back to Experience

TheDevMasters (TDM)

Marketing Operations / Automation · Dec 2025 – Jan 2026 · Irvine, CA

Throughout most of my time at TDM, I worked hands-on across campaign execution and creative development. As that work progressed, leadership and I aligned on using the operational context from those efforts to also evaluate structural gaps in the marketing stack and propose longer term system improvements.

My scope ultimately spanned both execution and systems thinking: contributing directly to campaigns while also documenting how CRM structure, tooling choices, and data architecture limited the reliability of marketing metrics and reporting.

Role and scope

I contributed directly to campaign execution, including writing and supporting creative for email campaigns and other marketing initiatives. In parallel, I documented where marketing performance reporting became unreliable due to inconsistent definitions, fragmented data paths, and tooling decisions that did not map cleanly to measurement needs.

Approach

Because reliable performance data was limited, the work emphasized correctness before optimization. While we tracked basic campaign indicators such as opens and responses, definitions and infrastructure were not consistent enough to make those numbers decision grade.

Rather than chasing improvements in metrics that were not yet trustworthy, I focused on identifying why those numbers were difficult to interpret and what structural changes would be required to make future measurement meaningful. The goal was to ensure that when optimization did occur, it would be grounded in clear definitions, stable data flows, and shared understanding across teams.

Key principles

What I worked on

Some conceptual system frameworks, including more structured approaches to lead scoring and signal separation, were developed during this period and discussed with leadership, but were not implemented within TDM’s production environment.

Outcome and learning

The most valuable outcome of this role was not a single metric improvement, but a refined understanding of how easily marketing data becomes misleading without strong foundations. This experience reinforced that metrics like open rate, CTR, and attribution are only as useful as the definitions and infrastructure behind them.

Working within real organizational constraints highlighted the gap between what teams want to measure and what systems actually allow them to measure. That insight directly shaped my design philosophy around signal trust, lifecycle clarity, tooling restraint, and data architecture, ideas that later became explicit in independent project work developed after my operational responsibilities at TDM had concluded.

TDM was where abstract thinking about RevOps became applied, imperfect, and grounded in real organizational tradeoffs.