The phrase email marketing vendor covers two different purchases that buyers regularly conflate. One is the software: the platform that stores your contacts, sends the mail and reports on it. The other is the people: the agency or freelancer who decides what gets sent, writes it, builds the automation and watches deliverability. You can buy one without the other, and the questions you should ask differ completely. This page separates the two, sets out what to check in each case, and describes the contractual details that decide whether leaving a vendor later is straightforward or painful.
Software vendor or service vendor, and why the distinction matters
A platform is priced on contacts and sends, and switching one is a migration project involving templates, automations, integrations and reputation history. A service provider is priced on output, and switching one is a handover of documents and access. Confusing them produces two classic mistakes. The first is buying an expensive platform for capabilities nobody on the team has time to use, which is common when a business upgrades to a marketing automation suite and then sends the same three campaigns a month it always did. The second is hiring an agency that insists on its own preferred platform, so that a service decision quietly becomes a software decision with years of switching cost attached. Decide the platform on your own requirements: list size, integrations with your store or CRM, the automation you actually intend to run, and who will operate it day to day. Then hire the people, from a field that includes specialist email marketing agencies as well as generalists, and require them to work in your platform rather than the reverse.
Deliverability and consent, the parts nobody demonstrates in a pitch
The most valuable work an email vendor does is invisible in a portfolio. Authentication records configured correctly, a warmed sending domain, list hygiene that removes addresses that never open, suppression handling that survives a platform migration, and a documented record of how each contact consented. Ask a candidate to describe their process for each, in order, and listen for whether they have done it recently or read about it. The legal floor in the United States is set out in the FTC's CAN-SPAM compliance guide, which requires accurate header and sender information, subject lines that are not deceptive, identification of the message as an advertisement, a valid postal address, a clear opt out mechanism and that opt outs are honoured promptly. A vendor that treats those as an afterthought is a vendor whose mail will eventually stop reaching inboxes, at which point everything else in the programme stops working too.
What the contract should say
Four clauses matter more than the fee. Ownership of the list and of everything created for you, stated explicitly, so there is no argument about templates, flow logic or segment definitions on exit. Data handling, including where contact data is stored and who at the vendor can see it. Notice period and offboarding, ideally with a defined handover: an export of contacts and suppression lists, documentation of every automation, and administrative transfer of the sending domain configuration. And billing transparency, particularly if the vendor resells the platform licence, since a resold licence with an undisclosed margin makes both cost comparison and departure harder. None of these are unusual requests, and a vendor that resists all four is telling you something useful before you have spent anything.
Checking a vendor before you commit
Ask to be added to a client's list, or to see two or three real sends from the last month with the client's permission. Read them as a recipient rather than as a buyer: is the subject line honest, is the unsubscribe easy to find, does the mobile rendering hold up, is the sender identifiable. Ask for one metric with its definition, usually revenue per recipient or qualified enquiries per send, and ask how they calculate it, since open rates have been unreliable since mail clients began pre loading images and any vendor still leading with them is behind. Finally, agree a first ninety day plan in writing with countable deliverables: audit findings, authentication fixed, a defined number of flows live, a template system in place. It converts a vague retainer into something you can hold to account at the first quarterly review.
Questions people ask about email marketing vendor
Should I let an agency buy the platform on my behalf?
Generally no. Keep the licence and the account in your own name so the contacts, the sending reputation and the automation history stay with you. If a vendor does resell the licence, ask for the margin in writing and for a clause transferring the account to you on exit.
How do I compare vendor quotes fairly?
Write one brief covering list size, platform, campaigns per month, flows to be built in the first quarter and who supplies copy and images. Send it unchanged to every candidate. Differences in the returned numbers then reflect different views of the same job rather than different jobs.
What compliance obligations are mine rather than the vendor's?
Legally the advertiser carries them. The FTC's CAN-SPAM guide sets out requirements including honest headers and subject lines, a valid postal address and prompt handling of opt outs, and hiring someone to send on your behalf does not transfer that responsibility away from your business.
What is a reasonable notice period?
Thirty to sixty days is common and workable for a service arrangement. What matters more is what the notice period contains: insist that offboarding includes contact and suppression exports, documentation of every automation and transfer of domain authentication, listed as deliverables rather than promised informally.