Costs
Part of Which email marketing software deserves the subscription
Choosing email marketing software without vendor names: an eight step method
An eight step method to choose email marketing software without vendor names: weighted requirements, dated evidence, pilot tests, total cost, contracts, migration.
What to take away
- Convert real use cases and failure consequences into weighted requirements before naming vendors; selection begins with requirements and failure tests, not a popularity list.
- Use current official evidence to shortlist, then make finalists perform the same hard cases with minimized data.
- Do not sign until total cost, responsibilities, security, support, migration, export, deletion, and termination terms are understood.
How to choose email marketing software in 2027 has eight steps. Name the decision owner and preserve current costs, incidents, workflows, data, and outcomes. Product pages are first-party claims whose prices and limits can change.
1. Define use cases
Document message classes, audiences, markets, volumes, triggers, data, integrations, users, decisions, outcomes, service levels, risks, budget, and deadline. Separate essentials from future possibilities.
2. Build weighted requirements
The GOV.UK Service Manual's commercial software guidance tells public-service teams to compare user needs, integration, customization, ongoing cost, supplier dependency, accessibility, security, and exit when considering commercial products. It does not select an email vendor. Use the evaluation categories, then adapt weights and obligations to the business and its markets.
Weighted evaluation categories
- User needs and accessibility
- Integration and customization
- Ongoing cost and supplier dependency
- Security and privacy
- Exit and portability
- Contact models and permissions
- Sending, automation, analytics
Cover contact models, permissions, suppression, sending, segmentation, automation, content, accessibility, localization, analytics, experiments, APIs, security, privacy, support, reliability, cost, migration, and exit. Weight consequence as well as convenience.
Worked example. Weight user-need fit at 25 points, evidence quality 15, security and privacy 15, total cost 15, integration effort 10, support 10, exit and portability 10. Score each vendor 0 to 5 per category, multiply by the weight, and add the totals.
A three-vendor shortlist might score 380, 345, and 310 out of 500. Those are sample scores, not vendor results. A failed mandatory use case scores zero and removes the vendor instead of dragging the average down.
3. Research current evidence
Read official pricing, feature, limit, contract, privacy, security, status, and support pages. Date every finding. Ask vendors to explain conflicts between sales material, documentation, and contract language.
4. Shortlist transparently
Disclose affiliate, referral, reseller, consulting, and partnership interests. Apply the same eligibility criteria and scorecard. Do not reward a vendor for sponsoring research or providing a more polished demonstration.
5. Demonstrate hard cases
Require missing consent, recent objection, duplicate identity, late purchase, time-zone boundary, scanner click, failed integration, over-limit send, wrong personalization, automation pause, account suspension, full export, and deletion cases.
6. Run a controlled pilot
NIST SP 800-161 Rev. 1 addresses cybersecurity supply-chain risk across acquisition and the system life cycle for U.S. federal organizations. Its scope is broader than email marketing and it is not legal advice. It supports treating supplier evidence, dependencies, responsibilities, monitoring, incident handling, and exit as continuing controls rather than a one-time questionnaire.
Use synthetic or minimized data where possible. Build a real form, segment, campaign, automation, report, integration, approval, incident, and export. Score task completion, effort, accessibility, support, risk, and evidence quality.
Plan for a typical pilot of two to four weeks per vendor. Expect one owner at roughly half time and two or three colleagues contributing a few hours a week.
7. Calculate total cost
Model contacts, sends, users, add-ons, channels, overages, implementation, migration, engineering, training, monitoring, consulting, support, currency, tax, annual commitments, growth, and exit under normal and peak scenarios.
List price is usually tiered by contact count, so the tier boundary is the main cost driver. Typical published list prices for mid-market platforms run from roughly $20 to $60 a month at 2,500 contacts and roughly $300 to $1,200 a month at 100,000 contacts. Those are typical ranges, not quotes.
Per-send charges appear on transactional, SMS, and high-volume plans, and implementation, migration, and dedicated IP add-ons are usually billed separately.
8. Contract and migrate
Negotiate service, security, privacy, change, price, data, sub-processor, incident, audit, assistance, portability, deletion, and termination terms with qualified reviewers. Migrate in phases with suppression reconciliation, validation, rollback, and customer support.
Preserve scorecard, evidence, pilot records, known gaps, contract assumptions, then preserve decision and rejected alternatives.
Recheck selected plan immediately before signing; vendor pages may have changed since research began.
Owner assignments: implementation, data migration, permission reconciliation, domain authentication, and template governance; integration monitoring, support escalation, analytics, and incident response; renewal and exit. Schedule an evidence-based review after normal production volume exposes conditions the pilot could not reproduce.
The GOV.UK technology selection guidance recommends adaptable choices, data control, security review, and ownership-cost analysis. Use those public-service questions when assessing how to choose email marketing software; they are not product endorsements.
The CISA software acquisition fact sheet covers development practice, supply-chain exposure, deployment, and vulnerability management. Add those government-acquisition questions to a how to choose email marketing software review without treating them as local approval.
Selection evidence gate
| Stage | Evidence | Gate |
|---|---|---|
| Requirements | Weighted cases and exclusions | Owners approve priorities |
| Research | Dated official and contractual facts | Unknowns stay visible |
| Pilot | Common scripts and failure tests | Mandatory cases pass |
| Contract | Cost, duties, data, support, exit | Residual risk accepted |
Common questions
How many email software vendors should be shortlisted?
Use the smallest number that covers meaningfully different viable models and can be tested with the available time, staff, and data.
Should feature count determine the winner?
No. Score required behavior, evidence, operating effort, risk, cost, support, portability, and exit instead of counting unrelated features.
What should disqualify a vendor?
A mandatory use case that fails, an unacceptable security or privacy gap, unworkable cost, unclear responsibility, or an exit that cannot be proved should block selection.
