Redesign when the foundation is healthy
Keep the existing code when the template renders reliably, modules are reusable, content editors can work safely, and changes do not routinely introduce regressions.
In that case, the value is in the experience layer: stronger hierarchy, clearer typography, improved spacing, more intentional CTA patterns, better mobile behaviour, and a modular visual system that reflects the current brand.
Rebuild when production itself is the bottleneck
A rebuild is justified when every change requires code surgery, modules cannot move safely, Outlook fixes are scattered across campaigns, mobile behaviour is unpredictable, or marketers duplicate old sends because the master template is too risky to touch.
Those are not cosmetic issues. They affect speed, QA cost, consistency, and the team’s willingness to improve the channel.
Audit the modules people avoid
Ask the people who actually build campaigns which modules they do not trust. You will usually hear things like “never use that card in Outlook,” “copy this old email because the current template is broken,” or “only one person knows how to update that section.”
Those comments are evidence. A good template reduces tribal knowledge.
Design for content variation
A master template should not only support the launch campaign you designed it around. It should tolerate short headlines, long French copy, missing images, different numbers of cards, legal text, dynamic personalization, and mobile stacking.
We test edge cases early because real campaigns are less tidy than the original mockup.
Separate brand rules from code rules
Not every visual decision belongs in the HTML. Define which rules are brand-level — typography, spacing rhythm, image treatment, CTA hierarchy — and which are implementation-level — tables, VML, responsive stacking, dark-mode handling, and client-specific fallbacks.
That separation makes future redesigns faster because the brand can evolve without forcing a full technical rebuild every time.
The decision test
If the team can make a new campaign quickly and confidently using the existing system, redesign. If the team spends more time protecting itself from the template than creating the message, rebuild.
The best email system is visually distinctive for the customer and operationally boring for the team.
Redesign the surface when the system is healthy. Rebuild when the template itself is slowing the team down.
