HubSpot email template development.
Renders in Outlook. Still reads. Email is the one place where twenty-year-old rendering engines still decide what your brand looks like. Coded HubSpot templates with drag-and-drop modules, tested across clients, dark mode included.
Looked perfect. In one client.
The template was designed in a browser and approved in Gmail. Then it reached Outlook on Windows, where the background image vanished and the buttons became blue underlined text, and a quarter of your list saw that version.
Approved in Gmail. Broken in Outlook.
Email — the rendering gapWhat a coded template gets you.
Tested across real clients
Outlook on Windows, Apple Mail, Gmail on web and mobile, and the dark mode variants of each. Tested rather than assumed, because assumption is how a quarter of a list gets a broken email.
Drag-and-drop modules
Email modules the marketing team can rearrange without touching markup, so a new campaign does not need a developer.
Dark mode handled
Logos, backgrounds and borders that survive colour inversion. Most templates are never checked in dark mode and it is now a large share of opens.
Accessible structure
Semantic order, real alt text, sufficient contrast and a sensible reading order for screen readers. Also what stops an email looking broken when images are blocked.
Personalisation that degrades
Tokens with fallbacks, so a missing first name reads as a normal sentence rather than as an empty space or a visible placeholder.
Modular, not monolithic
A small set of blocks that compose, rather than one template per campaign type. Twelve near-identical templates is how brand drift starts.
Engineers, working the way engineers work.
Scope in writing
What is being built, what it will not do, and how we will both know it is finished. Fixed scope where the work is knowable, a sprint rate where it is not.
Build in the open
Version control, a preview environment and a running demo, so you are not waiting until the end to find out what you are getting.
Review against the portal
Tested inside your actual portal with your actual content, at phone, tablet and desktop widths, before anybody calls it done.
Ship and document
Deployed, with the source handed over and a page explaining how to change it. You own what we build.
Designed for the browser.
Email is not the web. Flexbox and grid support is inconsistent, background images are unreliable, and web fonts are optional at best. A design signed off without those constraints in mind becomes a compromise at build time, and the compromise is always visible.
What people ask before they commit.
Can we use the HubSpot drag-and-drop editor instead?
For straightforward sends, absolutely, and we will say so. Coded templates earn their place when brand consistency matters, when the layout is beyond the default blocks, or when you send at a volume where rendering bugs cost real money.
Do you test in Outlook?
Yes, across the Outlook versions that actually have share, plus Apple Mail and Gmail and their dark modes. It is the whole reason to code a template rather than build one.
How long does an email template take?
Three to five days for a single template with modules. A full system of composable blocks is one to two weeks.
Can you match our website design?
As closely as email allows, and we will tell you where it does not — usually web fonts, some spacing precision and anything depending on modern CSS layout.
What about deliverability?
Template code affects it less than domain authentication, list hygiene and sending patterns do. We cover the template side and flag the rest, because that is where the real problems usually are.
Where people go from here.
Renders everywhere.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.