How to Build an Email Marketing Team Structure
Who owns what at one, three and eight people, and the handoff that breaks first as the programme grows.
On this page
The short version
- There are five jobs in an email programme regardless of headcount. At one person they are all yours; at eight they are separate roles.
- The first handoff to break is between whoever writes and whoever builds, because it is the one with the tightest deadline and the least documentation.
- Outsource production before you outsource strategy. The reverse is common and rarely works.
Email programmes contain the same five jobs at every size: deciding what to send, writing it, building it, operating the sending platform, and interpreting the results. What changes with headcount is whether those jobs sit in one head or five.
Naming them is useful even at one person, because it makes visible which of the five you are actually skipping. Most solo operators do strategy, writing and building, and quietly skip interpretation — which is why programmes run for years without anyone knowing whether they work.
At one person
Everything is yours, so the design question is what to cut rather than who does what. Cut breadth: fewer flows, simpler segmentation, a cadence you can hold. Do not cut interpretation, even though it is the easiest to skip, because without it you are producing rather than improving.
A useful discipline at this size is separating the days. Writing and building on the same afternoon means you edit while you build and ship things you have not read properly.
At three people
The usual split is one person on strategy and interpretation, one on writing, and one on build and operations. That works, and the handoff between writing and build is where it starts to fail.
The failure is specific: copy arrives in a document, gets rebuilt in the template by someone else, and small changes made during the build are never reflected back. Three months later nobody knows which version was actually sent. The fix is unglamorous — copy lives in one place, the build reads from it, and changes go back to the source.
Who owns what, by team size
| Job | One person | Three people | Eight people |
|---|---|---|---|
| Plan | You | Lead | Programme manager |
| Write | You | Writer | Writer, with a copy lead |
| Build | You | Producer | Developer plus designer |
| Operate | You | Producer | Dedicated operations and deliverability |
| Interpret | Often skipped | Lead | Analyst |
Interpretation is the job most likely to be nobody's at every size below eight, which is why programmes can run for years without anyone able to say whether they work.
At eight and above
At this size specialisation pays, and deliverability becomes a role rather than a task. The new risk is coordination: more people means more sends, and more sends means the frequency problem that omnichannel programmes have arrives inside a single channel.
The structural answer is a single calendar owner with the authority to refuse a send. Without that, every team with a stake gets its own send and the subscriber absorbs the total.
The documentation that makes handoffs survivable
Three documents cover most of it: the promise and cadence, the pre-send checklist, and a record of which flows exist and what each one is for. All three are short. All three are what a new person needs on day one and what an audit needs in year three.
The flow inventory is the one that pays off unexpectedly. Automated sequences are invisible unless someone lists them, and a list nobody maintains is how a programme ends up mailing people from a flow that nobody currently employed remembers building.
Frequently asked questions
When is the first hire justified?
When the calendar is slipping for capacity reasons rather than planning ones, quarter after quarter. Hiring into a programme with no promise or cadence just produces more of an unclear thing.
Should email sit in marketing or in product?
Campaign email belongs with marketing. Transactional and lifecycle messaging usually belongs closer to product, because it is triggered by product events. The important part is that both are visible on one calendar regardless of reporting line.
Who should own deliverability?
Below eight people, whoever operates the platform, with time explicitly allocated rather than assumed. Above that it deserves a named owner — it is the one area where a slow decline goes unnoticed until it is expensive.