Tools & workflows
Choose email marketing software from your requirements
Start with the messages, audience and operating constraints you actually have before comparing email marketing platforms.
An email platform can offer sophisticated automation while still being an awkward fit for a small editorial newsletter. Another may make a simple send easy but leave your team struggling with shared review. Describe the work you intend to do before comparing advertised features or headline subscription prices.
Write three representative sending situations. You might have a monthly newsletter, an occasional service announcement and a welcome message for new subscribers. These are examples, not a recommended programme for every business. Identify the owner, intended recipients, source of the audience list and necessary review for each situation.
Turn situations into requirements
For the monthly newsletter, requirements might include reusable layouts, a test-send process and a way for a second person to review the draft. For a segmented announcement, the question is whether you can select the intended audience without maintaining multiple inconsistent lists. Treat each requirement as something to demonstrate, not a phrase to tick off on a pricing page.
Consider the less visible work. How will the team handle address changes, unsubscribes and people who appear in more than one imported list? What record must move with a contact? Who can export the audience or send a campaign? Establish your organisation's requirements for permission and personal data with the appropriate adviser; a software feature does not determine whether a particular mailing is appropriate.
Build and review a sample message
Use a small authorised test list and non-sensitive content. Prepare an actual draft with the headings, images and links your publication needs. Check it on the devices and mail applications your reviewers can access, and make the limits of that test explicit. A preview inside the sending tool is useful, but it is not the same as checking a received message.
Look at the editing experience for another team member. Can they change an image without breaking the layout? Is it clear which draft was approved? Can a correction be made without rebuilding the whole message? Ask how the workflow handles an accidental duplicate send before assuming the team will never make that mistake.
Compare the cost of your own scenario
Check the vendor's current documentation for the relevant plan, limits and charging basis. Calculate the scenario using your expected audience, frequency, users and required functions. Record the date and assumptions. A low entry price is not a useful comparison if one candidate excludes the review access or export capability you need.
Finally, export a small test audience and a sample piece of content. Inspect what the export includes and how you would continue operating elsewhere. Keep the final comparison focused on observed fit, operating effort and unresolved questions. The right choice is the one your team can run responsibly, not necessarily the one with the longest list of possible automations.
