Skip to content

Custom applications & automation / Case 04

Client project · WAMA Underwear

Building a Custom Email Countdown Timer Platform for Marketing Campaigns

For WAMA Underwear, a dedicated internal application replaced a repetitive timer-building workflow with editable campaigns, configurable animated GIFs, and email-ready embed code. The work balanced a straightforward editing experience with accurate deadlines and the realities of email image rendering.

PythonFlaskPillowAnimated GIFKlaviyoEmail automation

What this solved for the business or user

The marketing team needed a practical way to prepare countdown timers for promotional emails without asking a developer to edit image code for every campaign. The resulting private editor gives authorized team members a place to enter a deadline, adjust the visual design, preview the output, and copy an embed into an email draft.

At a glance

Key facts about this project.
ClientWAMA Underwear
ApplicationPrivate email countdown campaign builder
Core stackPython, Flask, Pillow, HTML, CSS, JavaScript
DeliveryHosted animated GIF and reusable HTML embed

What was happening

An email campaign may need a countdown that matches its artwork, shows the correct remaining time, and can be used inside existing email templates. Building a new timer by hand for every promotion creates repetitive setup work and more opportunities for formatting or timezone mistakes.

Why the obvious solution was not enough

Email clients do not behave like browsers. Animated GIF playback, image loading, caching, and link treatment can vary between inboxes. The builder also needed to account for daylight-saving changes, readable timer graphics, persistent campaign settings, and a distinction between the private editing interface and images rendered by email recipients. It could not promise a perfectly synchronized live countdown in every inbox.

How the solution works

  1. Build a small authenticated campaign editor rather than introducing a public account or subscription system for an internal workflow.
  2. Let the team configure campaign names, deadlines, timezones, expiration messaging, typography, colors, and supported background treatments through familiar form controls.
  3. Generate the countdown as an animated GIF using a Python image-rendering service, with a preview that reflects the actual output rather than an unrelated mock animation.
  4. Store campaign settings so the team can revisit and adjust a saved timer instead of rebuilding it from scratch.
  5. Provide copyable email-ready HTML for use in Klaviyo, with a configurable destination link and an option that does not send recipients to a landing page.
  6. Keep the timer's deadline and display assumptions explicit. Use a named timezone so scheduling can account for daylight-saving transitions when applicable.
  7. Design the output for common email layouts and verify contrast, legibility, dimensions, and behavior in received test messages.
  8. Document the limitations of hosted images: an email client may cache a frame or a GIF, so the displayed timer cannot be guaranteed to refresh continuously after delivery.

Engineering choices and tradeoffs

What the internal tool needed to balance.
ConcernDesign responseImportant limitation
Email renderingUse a widely supported animated image format and email-ready markupSome clients show a still frame or modify image behavior
Deadline accuracyUse explicit dates and named timezonesA received image may be cached by the email client
Campaign reuseSave configurations and regenerate previewsPreviously sent email markup does not update automatically
Operational accessKeep campaign editing behind authenticationImages in delivered emails still need to be accessible to recipients

The project is an internal production utility rather than a public countdown service. The public case study intentionally avoids real campaign dates, private URLs, credentials, and operational configuration.

The hosted image displays remaining time; it does not schedule marketing emails, activate discounts, or control checkout behavior.

What should be verified before shipping

  • Verify that an authorized editor can create a timer, save it, reopen it, and reproduce the intended appearance.
  • Check daylight-saving boundaries, invalid deadlines, expiry behavior, and the displayed hours, minutes, and seconds.
  • Compare preview clarity against the delivered GIF at intended email display sizes and backgrounds.
  • Send test messages to representative email clients, including mobile and dark-mode views, and document limitations rather than promising identical playback.
  • Confirm that the optional destination link behaves as configured in received email and that a link-free marketing intent does not imply absolute non-clickability in every client.
  • Test invalid input and authentication handling without using real recipient or campaign data in public materials.

What changed

A self-hosted internal campaign editor was built and deployed for WAMA's marketing workflow. It lets authorized team members prepare and manage countdown graphics and copy reusable email markup. Testing covered the builder and image output. The case does not claim measured time savings, increased conversions, or identical live playback in all email clients.

Reusable lesson

A focused internal application can simplify recurring work when the editor, output format, and distribution environment are designed together. For email graphics, transparent communication about caching and client behavior is as important as the rendering code.

How I would evaluate this today

WAMA Underwear is named for case-study context, but no client website or internal application link is provided. No private campaign content, customer information, login details, image endpoints, or infrastructure settings are published. The described features exclude unverified evergreen or recipient-specific behavior.