To outsource email production well, hand over the repeatable work (build, platform setup and QA) and keep the decisions only you can make (strategy, brand and sign-off). Choose a partner by how they handle the messy part between approval and send, not by their portfolio. Agree in writing who owns testing, who owns deliverability, and who owns the files at the end. Then run a small paid project before you commit. A note on perspective: Email Squad is a supplier of email production, so we have an interest here. This guide is written to help you judge any partner, including us.
When does it make sense to outsource email production?
Teams usually outsource for one of three reasons: capacity, specialist skills, or avoiding a permanent hire. Each points to a different kind of partner.
| Reason | What it looks like | What to look for |
|---|---|---|
| Capacity | Campaign peaks, product launches, a backlog of amends | Fast turnaround and a clear process for urgent work |
| Specialist skills | Responsive HTML, Outlook fixes, platform builds in Klaviyo, Salesforce, HubSpot and others | Proven email-specific work on your platform |
| No permanent team | An agency or in-house team without a dedicated email developer | A reusable template system your own marketers can run |
Outsourcing is a weaker fit when the problem is unclear strategy or poor approvals. A supplier can’t fix a brief that keeps changing, and extra production capacity just makes a slow approval process more expensive.
Which parts of email production can you outsource?
Litmus describes a typical agency workflow as five stages: strategy and brief, copy and design, build and modular coding, testing and client approval, and launch, reporting and optimisation. You can outsource any slice of that, and the choice changes the risk.
- Design only: you get artwork, but someone else still has to build it, and that handover is where problems appear.
- Build only: you supply designs and the partner delivers coded, tested HTML. This is the most common model, and the most dependent on a clear brief.
- Build and platform setup: the partner also loads the email into your email service provider (ESP), sets up personalisation and checks the live version.
- End to end: design, build, platform, QA and often reporting. It’s the simplest to manage and the hardest to switch away from.
- Template-system projects: a one-off build of reusable templates your own team then runs. See our guide to custom email templates.
Keep control of strategy, brand decisions and final approval. A partner can advise on all three, but they’re yours to decide.
How do you judge an email production partner?
| Area | What good looks like | Warning sign |
|---|---|---|
| Email-specific work | Shows built, sent campaigns and responsive states | The portfolio is mostly websites or static mock-ups |
| Development | Understands HTML email constraints and your platform | Treats email like ordinary front-end development |
| QA | A defined process covering clients, devices and content | Relies on a single browser preview |
| Handover | Source files, template rules and ownership are clear | Only the original developer knows how it works |
| Workflow | Briefs, feedback and approvals have clear owners | Decisions keep reopening late in the process |
| Platform access | Works with limited, named access to your ESP | Asks for admin-level access to everything |
A portfolio shows taste. It rarely shows how the work behaved in Outlook, how many rounds of revisions it took, or whether the client’s team could reuse it six months later. Ask what happened after the screenshot: was the email coded, tested, sent and reused?
What should QA cover, and who owns it?
“QA included” can mean anything from a single preview to a full client test, so ask for the scope in writing. These are the points a competent email partner should already know.
- Outlook for Windows. Email on Acid explains that classic Outlook for Windows has used Microsoft Word as its rendering engine, which is behind many of the layout problems developers work around. Microsoft is moving users to a new, web-based Outlook. Current sources, including a Microsoft Q&A reply and a recent third-party guide, say classic Outlook isn’t being retired in 2026 and is expected to be supported until at least 2029, with no cutover date announced. In practice, your partner should test both versions for as long as your audience uses both. See our guide on why emails look different in Outlook.
- Gmail clipping. Drip’s help centre says Gmail clips messages larger than 102KB, hiding the rest behind a “view entire message” link. Heavy code and pasted text can push an email over it, so ask whether size is checked.
- Dark mode, images off and mobile. Ask how these are tested and on which clients, and match the list to your own audience data.
- Links, personalisation and fallbacks. The live email, in your ESP, with real and missing data, is the one that matters. A design preview doesn’t prove it.
- Accessibility. Alt text, contrast and tappable buttons. See our email accessibility guide.
Whichever way you split it, name one person who signs off the final sent version. Without that, design assumes development checked it, development assumes the platform team did, and nobody did.
Who is responsible for deliverability?
This is the point most contracts skip. Production quality and deliverability are different jobs, but both can sink a campaign. Google’s sender guidelines set requirements for bulk senders, defined as those sending close to 5,000 or more messages to personal Gmail accounts in 24 hours:
- Authenticate with SPF and DKIM, and publish a DMARC record.
- Include one-click unsubscribe for marketing and promotional messages, using List-Unsubscribe headers, and honour requests within 48 hours.
- Keep the spam rate below 0.1%, and never let it reach 0.3%.
Most of this sits with your ESP and domain set-up, not with the person coding the email. Decide in advance who checks it. A production partner can reasonably be responsible for making sure the unsubscribe link is present and works, while authentication and list quality usually belong to you or your email platform team. Write the split down.
How should briefs and approvals work?
Litmus, which sells review tools and should be read with that in mind, describes approvals as the biggest bottleneck for agencies, and reports that 35% of email marketers say collecting feedback is the biggest blocker to getting an email produced and sent. The practical lesson doesn’t depend on the tool you use:
- Brief once, properly. Audience, goal, content, links, platform, deadline and sign-off owner.
- Collect feedback in one place, not across chat threads, email replies and screenshots.
- Set a firm cut-off for the final round of comments.
- Agree what counts as an amend and what counts as new work, and how many rounds are included.
- Separate creative approval from production approval. A design can be approved while the live build still has broken links or data problems.
What should a white-label arrangement include?
In a white-label set-up, a partner does the production behind your agency’s name. It works when everyone knows the rules, and it breaks down when they’re vague. Agree these up front.
- Confidentiality. A signed agreement covering client names, content and data.
- Communication. Whether the partner ever speaks to your clients, and how they’re introduced.
- Access. Named, limited access to client ESPs, ideally a role that can build but not send.
- Ownership. Who owns the finished code, the templates and the source files.
- Turnaround and cover. Standard and urgent turnaround, and who covers when volume spikes or someone is away.
- Branding. Whether the partner can show the work in their own portfolio.
Which questions should you ask before appointing a partner?
| Question | Why it matters |
|---|---|
| Who builds and implements the email? | Makes the line between design and production clear |
| What is included in QA, and which clients are tested? | Avoids assuming inbox testing is in the fee |
| Who owns responsive behaviour? | Stops mobile decisions being left until development |
| What files and templates do we own at the end? | Prevents handover surprises |
| How are revisions managed and counted? | Stops feedback becoming open-ended |
| Who covers urgent or overlapping work? | Matters when volume increases |
| What access do you need to our platform? | Shows how carefully they handle security |
| Can we speak to a client who’s used you for a year or more? | Tests whether the relationship lasts |
How do you run a small paid test?
A small paid project is the clearest test of a supplier. Give them a real brief, real content and a genuine deadline, then watch what happens.
- Choose a real email, ideally one with a few awkward elements such as a long headline, a product grid or personalisation.
- Agree the scope and price before they start, including QA and the number of amend rounds.
- Judge the process as well as the result: the quality of their questions, how they handle an amend, how clearly they report problems, and whether the email works in your platform.
- Test the handover. Ask someone on your team to edit it without help from the supplier.
It costs a little, but it’s cheaper than finding out three months in.
What should you own at the end?
- The final HTML and any reusable templates, in your platform
- Source design files and assets
- A short guide: which modules exist, what’s editable, content limits and known compromises
- The QA checklist and the clients tested
- At least one real campaign built from the system, so a new producer can see how it works
If only the original developer can maintain the setup, you haven’t outsourced production. You’ve created a dependency. If you want reusable templates your own team can run, our HTML email development and email campaign design services are built around that.
What are the most common mistakes when outsourcing email production?
- Judging a supplier by portfolio screenshots
- Outsourcing before the brief and approval process are sorted out
- Assuming “QA included” means testing in the clients your audience uses
- Leaving deliverability with nobody
- Giving admin-level platform access when a narrower role would do
- Not agreeing who owns files and templates
- Collecting feedback in several places, with no cut-off
- Letting design, build and platform setup go to different suppliers without one person coordinating
- Skipping the paid test because there’s a deadline
Outsourcing checklist
| Check | Question to ask |
|---|---|
| Scope | Do we know exactly which stages are outsourced and which aren’t? |
| Evidence | Have we seen built, sent email and not only mock-ups? |
| QA | Is the test scope, including Outlook and Gmail clipping, agreed in writing? |
| Deliverability | Is it clear who owns authentication, unsubscribe and complaint rates? |
| Approvals | Is there one feedback route, one sign-off owner and a cut-off? |
| Access | Does the partner have the minimum platform access needed? |
| Ownership | Do we own the files and templates at the end? |
| Test | Have we run a small paid project first? |
How Email Squad can help
If your email production keeps turning into a last-minute scramble, Email Squad can take on the design, build, platform setup and QA. Take a look at our email campaign design, custom email templates and HTML email development services, or get in touch with a real brief and we’ll tell you honestly whether we’re the right fit.
If you’d rather hand it over, our white label email production team can take it from here.
Sources
- Litmus: Email marketing for agencies (vendor guide; its statistics cite the Litmus State of Email Workflows report)
- Email on Acid: New Outlook for Windows (April 2023)
- Microsoft Q&A: How long will Microsoft support Classic Outlook?
- Unanswered: Classic Outlook status in 2026 (third-party guide)
- Drip: Avoid email clipping in Gmail
- Google: Email sender guidelines FAQ
Email questions, answered
What matters most about campaign peaks?
The job of campaign peaks is to remove friction next time. The next producer should be able to understand campaign peaks from the template itself, not from tribal knowledge.
How should specialist HTML gaps work in practice?
Use a real campaign to decide how specialist HTML gaps should work. Make the specialist HTML gaps rule obvious enough that another producer can use it without a guided tour.
What should you watch for with white-label client delivery?
A few clear rules around white-label client delivery will usually beat a flexible system nobody is completely confident using. The aim with white-label client delivery is fewer workarounds next time, not a longer document explaining why the system is complicated.
How should template-system projects be handled?
Keep template-system projects practical. Try the least convenient version of template-system projects first; that is usually where the useful rule appears.
What usually goes wrong with need for predictable QA?
Start with what need for predictable QA needs to achieve in a real campaign, then build the smallest rule that gets you there. The next producer should be able to understand need for predictable QA from the template itself, not from tribal knowledge.
What should be checked before handing over outsourced email production?
Use a real campaign, not a demo. Check how the email production support handles content limits, mobile behaviour, routine editing, links, fallbacks and the final sent version.
What matters beyond the portfolio when choosing outsourced email production?
For outsourced email production, look at how the supplier handles real production: responsive behaviour, HTML, platform limits, QA, revisions, communication and handover. Dependable delivery matters more than a polished portfolio alone.
Is a paid test project useful when choosing outsourced email production?
Yes. A small real job involving outsourced email production can tell you more about communication, judgement and production quality than another credentials deck.
Want to make your email production support easier to produce?
If your email production support keeps getting squeezed between bigger campaigns, we can take the production load off and give your team a setup that is easier to use.