Modular email systems, ESP implementation, and lifecycle strategy across SFMC, Iterable, Braze, Klaviyo, and the rest of the alphabet. Figma handoff to production send, documented so your team can run it without me.
Modular, documented component libraries built from Figma to production. Brand-safe, dark-mode-tested, and structured so your team can build new sends without breaking anything.
Journeys, triggers, and automations built right the first time. Onboarding, retention, and winback flows. Mapped, built, and instrumented so you can see what's working.
Platform decisions, audits, QA frameworks, and team training. The strategic layer that keeps the program from turning into spaghetti six months from now.
Six builds. Different platforms, different problems. The kind of work I want more of.
JustAI routes personas at send time, kept outside Iterable's segmentation so four-persona logic stays manageable across two journeys. Nine hand-coded base templates produce 30 persona-specific builds. Fallback logic ensures no failure reaches an inbox.
Joined as the only developer on the account and shipped a launch eCRM under a six-week hardware deadline. That work kept earning more work, turning solo builds into team leadership as the account kept expanding.
A feeding guide email pulling from pet and food data. The data couldn't be validated in time. Wrote the interpretation into the AMPscript itself: decimals into rendered fractions with matching images, grammar handling for names and quantities, dynamic layout based on populated fields.
The marketing team needed a self-serve template system. Built one that uses every capability the builder supports: hide-when-empty sections, mobile image swaps, repeatable content blocks, and tokens for every color, copy field, link, and image.
The live data feed that was supposed to power a hyper-personalized welcome journey never materialized. The personalization still had to ship.
Customer.io's Design Studio supports nested containers and persistent HTML overrides, real technical range for a builder-based ESP. Built the modular system around those capabilities, dropping into raw code only where the visual editor hit its limits.
Where I've built. Tap a tile for what I do in each.
Inverted logos, vanishing text, blown-out backgrounds, white boxes around buttons. I build modules that hold their shape whether the inbox flips them or not. Flip the switch. Same email, both ways, nothing breaks.
I've spent eight years building email, most of it figuring out how to make something polished survive a medium held together by tables, inline styles, and inbox clients that all disagree with each other.
By day I run email development at an agency. The rest of the time I build modular systems and lifecycle programs for teams that want it done right the first time.
If you've ever opened a "finished" email build and watched it implode in Outlook, you already know why this work matters. That's the part I'm good at.
Henry Wiygul · Dallas TX