Currently open to: Remote US or hybrid within 30 minutes of Quakertown, PA
Jeremy Ralston
I build technical systems that turn recurring marketing work into scalable, structured, reusable content operations.
Promo Production Time Cut
-90%Full monthly promo kit for 4 stores in about 3 hours. Individual landing pages in about 20 minutes each, including publishing.
One System, Many Outputs
Three portfolio pieces that show how I solve messy business problems with design judgment, technical systems, automation, and practical execution.
One intake, many outputs: pages, emails, banners, compliant disclaimers
Implemented with
Read the case studyInteractive current-projects map for a PennDOT program and I-95
Implemented with
Read the case studyRules-based Excel formulas (no macros) that publish specials pages
Implemented with
Read the case studyOne structured intake produces pages, emails, banners, and compliant disclaimers. Promo production time is down about 90%: a full monthly kit for 4 stores in about 3 hours, with landing pages in about 20 minutes each, including publishing. Promo email build time is down about 92%, from about 4 hours to about 20 minutes per campaign.
Offer details are captured once through a single structured intake. The app models that intake as data in Postgres (via Supabase), then renders every downstream asset from shared templates: HTML/CSS landing pages, responsive emails, and promo banners. Visual creative is produced at scale using template-based images with dynamic text overlays driven by Photoshop scripting. Publishing is handled through the app and its hosting/DNS layer.
A self-contained WordPress plugin that uses JavaScript to integrate the PennDOT API into an interactive current-projects map for a PennDOT program and I-95, with click-to-view project details in a responsive UI.
JavaScript fetches live project data from the PennDOT API and shapes GIS features for the map in the browser. Those features render onto an interactive, responsive map inside a self-contained WordPress plugin. Selecting a project opens its details inline, so users can explore current work along the corridor without leaving the page.
Rules-based Excel formulas (no macros) turn recurring monthly offer data into publish-ready specials pages, compliant disclaimer text, and validation. No manual page building required. This was truly the prototype that led to the Promotions Content Engine.
Recurring monthly offers are entered as structured rows. Rules-based Excel formulas (no macros) transform that data into publish-ready specials page HTML and the matching compliant disclaimer text. Validation formulas flag missing or inconsistent values before anything is copied out, so the output is ready to ship as soon as the data checks out.
I don't just build websites. I build systems that cut monthly promo production time by about 90%.
The tools I use to design, build, and ship content operations.
I build the systems behind marketing, not just the campaigns. My work sits where marketing operations, front-end development, automation, SEO, content systems, and design judgment overlap, turning recurring, manual production into structured, reusable content operations.
The pattern is always the same: find the repetitive work, model it as data, and build a system that produces consistent, compliant output quickly. One structured intake can drive landing pages, emails, banners, and disclaimers, with validation checks so the result is right every time, not just the first time.
I care about craft as much as efficiency. A system that runs fast but produces sloppy output isn't finished. I hold the details (clean markup, accessible interfaces, accurate structured data, on-brand creative) to the same standard as the automation that generates them.
If a task happens every week, it should be part of an automated workflow, not someone's recurring homework.
Tell me about the marketing work your team keeps redoing by hand.
