I work across data, messaging, and internal platforms to make sure customer-facing systems are observable, governable, and resilient. The work usually lives between product, marketing, engineering, and operations.
Most of my projects start when something is fragile, opaque, or manual and end when teams can ship changes without fear.
Deliverability, suppression logic, list hygiene, preference centers, and campaign guardrails. Built to survive real traffic and real mistakes.
SFMC Email Reliability |
Safer Excel Segmentation
Segment, Tealium, mParticle-style architectures. Event contracts, identity stitching, downstream activation into marketing and service tools.
Segment vs Hull |
Tealium vs mParticle
Dashboards, admin tooling, and operational workflows so non-engineers can move fast without breaking things.
Big lessons from (small) dashboards
Routing logic, enrichment, lifecycle signals, and automation between product, CRM, and support platforms.
HubSpot Workflows |
SQL Patterns
I start by mapping data flows end to end, then add controls where users are likely to make mistakes. I care a lot about defaults, failure modes, and making the right thing the easy thing.
“We need to scale this, but we’re scared to touch it.”
“Marketing, product, and support all see different numbers.”
“We ship fast, but incidents keep happening.”
Beyond the core platforms, I explore practical guides, experiments, and lessons learned from real-world projects. My goal is to make operations predictable, repeatable, and visible for everyone involved.
Check out the blog for posts, deep dives, and examples
from past projects.
If a system is complicated, opaque, or risky, I aim to simplify it while keeping it reliable. Think of this as a compilation of lessons you can actually apply.