Ask an email design agency who actually does the work, what it has built and sent rather than just designed, how it tests, what the fee covers, who owns the files and whether it subcontracts. Specific, checkable answers tell you more than a polished portfolio.
A portfolio shows what an agency can make. Your questions show whether it can deliver reliably inside your platform, your approval process and your deadlines. Below are the questions worth asking, grouped by theme, with the kind of answer to listen for. The “listen for” notes are our view, not research. For choosing between a freelancer and an agency first, see email designer vs email design agency, and for the wider hiring process, how to hire an email designer.
Who will actually work on our emails?
- Are the people in this pitch the people who will design and build our emails?
- Who is our day-to-day contact, and can we speak to the designer or developer directly?
- Who covers holidays, sickness and urgent work?
- Do you use freelancers or other agencies for any of the work?
Listen for names, roles and a real cover arrangement. Vague answers such as “the team” are a warning sign. The subcontracting question matters beyond quality: if a supplier will handle your subscriber data, the ICO says a processor must only engage a sub-processor with the controller’s prior authorisation, so you should know who else touches the work. Whether a supplier counts as a processor is a legal question, and this is general information, not legal advice.
What have you built and sent, not just designed?
- Can you show a live email I can open in my own inbox, not just a screenshot?
- For one example, what did you test, what broke and what did you change?
- Have you built in our sending platform, and can you show a template your client team edits themselves?
- Can I speak to a client who has used you for more than a year?
Listen for a specific story with a problem and a fix. A portfolio that is mostly websites or static mock-ups is a warning sign. Ask what happened after the screenshot: was the email coded, tested and sent, and could the client reuse it six months later?
How do you handle HTML and the awkward inboxes?
- What do you do differently when coding for classic Outlook, and why?
- What does your email look like when media queries or images do not load?
- Who owns responsive behaviour: the designer or the developer?
- How do you handle personalisation with missing data?
The technical answers should be specific. Microsoft’s documentation for Outlook 2007 says it uses Word’s rendering engine, lists table elements as fully supported and lists float, position and background images among the unsupported features. That page is archived and says nothing about later versions, and I found no current official list for classic Outlook, so a good agency should talk about real fixes it has used rather than quote one source. Google says Gmail might ignore unsupported CSS, so listen for a build that still works without it. Our guides to why HTML emails use tables and HTML email development explain the background. For hiring the developer role specifically, see hire an HTML email developer.
What does your QA cover?
- Which inboxes and devices do you test, and how do you choose them?
- Do you test the sent email or only a preview?
- Do we get a QA report, and what is in it?
- Who signs off the final send?
Listen for testing of the sent email in named clients. Klaviyo describes a test send as the best way to check client-specific rendering; that is one platform’s advice, but the principle holds. A warning sign is “we check it in a browser.” See our HTML email testing checklist for what good QA looks like.
What is included in the fee?
- Please list the deliverables: design files, HTML, platform setup, testing, revisions and handover.
- How many revision rounds are included, and what counts as a revision?
- What happens with rush work, and how is it priced?
- What would take the price up?
Listen for plain-English deliverables and a clear revision definition. Correcting supplied copy, changing a signed-off layout and replacing the creative direction are very different amounts of work, so a good agency separates them. Volume helps when the workflow is predictable, and rush work gets expensive when urgency covers for an unclear brief or scattered feedback. Compare quotes line by line; our guides to email design cost in the UK and email design agency deliverables show how.
Who owns what we pay for?
- Who owns the design files, code and templates when the work is finished?
- In what format will we receive them, and are they editable?
- What happens to our data and platform access when the contract ends?
- Could another team pick this up if we left?
Listen for ownership in writing. GOV.UK says the creator of a work is usually the first owner of copyright, that a person under a contract for services will usually keep copyright unless the contract says otherwise, and that a commissioner is not the first owner unless that is agreed in writing. It also says ownership can be transferred. On data, the ICO says a processor contract must cover deleting or returning personal data and submitting to audits. Both are general information, not legal advice, so have your legal lead check the contract. In our view, a handover that only the original creator understands is the biggest warning sign of all.
How can you check all this before you commit?
With a small paid test, which shows more than another hour of slides. Give the agency a real brief with real content and a genuine deadline, then watch how it handles questions, amends, build constraints and QA. Our guide to hiring an HTML email developer sets out how to run one. A short summary of what to listen for:
| Area to check | What good looks like | Warning sign |
|---|---|---|
| Email-specific work | Real sent campaigns, responsive states and built output | Portfolio is mostly websites or static mock-ups |
| People | The pitch team does the work, with named cover | You meet the pitch team and never see them again |
| Development | Specific answers about Outlook, fallbacks and your platform | Treats email like ordinary front-end development |
| QA | Tests the sent email in named inboxes and shares a report | Relies on one browser preview |
| Handover | Source files, template rules and ownership are clear | Only the original creator knows how it works |
| Workflow | Briefs, feedback and approval have clear owners | Late-stage decisions keep reopening |
Want to put these questions to us?
Email Squad is an email design agency, so we have an interest in you choosing us. We would rather you ask us the same questions as everyone else. Send us your brief and your shortlist of questions, then see our email work, email campaign design and HTML email development.
Sources
Need a hand with your email agency selection?
Email should not be an afterthought. Email Squad can help with your email agency selection from design and HTML build through platform setup and QA.