Define the Service Before Comparing Agencies
Start with the commercial problem rather than the number of emails you want produced. A retailer improving repeat purchases needs different work from a software business reducing trial abandonment. Specify the audience, desired behavior, current constraint, and systems involved. Ask agencies to explain which problems email can realistically address and which depend on product experience, sales follow-up, inventory, or website conversion improvements outside their direct control.
A complete scope separates strategy from execution. Strategy includes audience research, lifecycle mapping, contact policy, and testing priorities. Execution covers copy, design, template development, audience selection, quality assurance, scheduling, and deployment. Deliverability monitoring, platform administration, integration maintenance, and analytics may be separate services. Require an explicit inclusion or exclusion for each area so important operational tasks do not disappear between your internal team and the agency.
Define output and responsibility together. Ten campaigns mean little without agreement on variants, languages, revision rounds, dynamic content, and approval deadlines. Lifecycle programs also require monitoring after launch, not just initial construction. Establish a responsibility matrix naming who supplies offers, approves claims, checks landing pages, resolves technical incidents, and authorizes sends. This makes proposals comparable and prevents a low production fee from concealing substantial internal work.
Make the First Month an Evidence-Gathering Phase
The first month should reduce uncertainty before increasing send volume. Begin with an inventory of platforms, sending domains, forms, integrations, templates, automated journeys, and reporting dashboards. Request a documented audit with prioritized risks rather than a vague discovery presentation. An inherited program may contain overlapping automations, stale exclusions, or broken events that make immediate campaign expansion counterproductive even when the creative work itself looks ready to launch.
Grant access through named user accounts with appropriate roles and multifactor authentication, not shared passwords. The agency may need your email platform, customer relationship management system, analytics, ecommerce administration, and DNS coordination, but not unrestricted access everywhere. Keep a register of permissions and approvers. Where sensitive customer information is involved, review contractual data handling, subprocessors, retention, and incident notification requirements with the people responsible internally before access.
Sequence onboarding around dependencies. An illustrative first month might cover access and audits first, data validation next, then a limited pilot and measurement review. Do not promise a launch date before confirming consent records, authentication, and event reliability. Ask for a baseline report, a risk register, and a ninety-day backlog ranked by business value and implementation effort, with clear assumptions about work your team must complete.
Balance Campaigns With Lifecycle Programs
Campaigns communicate time-sensitive priorities: launches, seasonal offers, events, or editorial updates. Lifecycle messages respond to a customer’s stage or behavior, such as subscribing, requesting a demonstration, purchasing, or becoming inactive. Agencies should explain how these two streams cooperate. A busy promotional calendar can undermine a carefully designed onboarding journey if recipients receive conflicting offers or excessive messages from independently managed programs within the same week.
Prioritize lifecycle work using trigger reliability, audience size, customer usefulness, and commercial relevance. A welcome sequence may be sensible before a complex predictive program if basic signup data is dependable. For each journey, document entry conditions, delays, branching logic, exclusions, exit conditions, and success measures. Check what happens when customers purchase, cancel, change preferences, or enter another journey while the existing sequence is still running today.
Require an operational maintenance plan for every automation. Product links break, discount rules change, integrations fail, and messages become inconsistent with current policy. Agree on review intervals and alerts for abnormal volume or missing events. Test with controlled records before activation, including edge cases such as refunds and duplicate triggers. Treat lifecycle emails as maintained business processes rather than assets that become finished permanently at launch.
Segment Around Useful, Reliable Customer Signals
Good segmentation starts with a decision that changes the message. Purchase category, account stage, stated interests, renewal timing, and recent product activity can justify different content or timing. Creating dozens of segments without corresponding treatments adds operational complexity without clear benefit. Ask the agency to show which observable signal changes an offer, suppresses a send, or routes someone into a different experience with a defined purpose.
Examine the quality and provenance of each field before using it. A job title imported years ago may be less useful than a recent preference selection. Distinguish volunteered information from inferred behavior and avoid assumptions that customers would find intrusive. Specify how missing values, contradictory records, shared addresses, and duplicate profiles are handled. Segment definitions should be understandable to your business team, not hidden inside platform filters.
Set contact rules across segments, not only within them. A high-value customer can simultaneously qualify for several campaigns and journeys. Establish frequency limits, priority rules, and exclusions that protect the overall experience. For inactive audiences, define a cautious re-engagement and suppression policy using more than opens alone. Ask agencies to quantify segment overlap before launch and explain how they will prevent accidental over-contact when multiple teams schedule messages.
Match the Engagement to the Work
| Engagement | Best fit | Buyer safeguard |
|---|---|---|
| Campaign production | Established strategy; recurring creative needs | Define variants, approvals, and QA |
| Lifecycle project | Specific journeys need building | Include trigger testing and documentation |
| Managed program | Ongoing planning, execution, and optimization | Name owners and reporting obligations |
| Technical audit | Authentication, data, or delivery concerns | Require prioritized fixes and verification |
Evaluate Authentication and Gmail Sender Readiness
Authentication is foundational, but it does not guarantee inbox placement. SPF identifies authorized sending infrastructure; DKIM provides a cryptographic signature that receiving systems can verify. DMARC adds a policy and reporting framework tied to alignment with the visible From domain. Ask who maintains these records, reviews reports, and coordinates changes across all legitimate senders. An agency should not alter DNS without an approved change and rollback process.
Google’s sender guidance distinguishes general requirements from additional requirements for senders exceeding 5,000 messages daily to personal Gmail accounts. Google aggregates messages from the same primary domain when assessing that threshold. Bulk senders must set up SPF and DKIM and publish a DMARC record; Google allows the DMARC policy to be set to p=none. Other requirements also apply. Confirm applicability against Google’s current guidance rather than assuming that splitting traffic across subdomains avoids the bulk-sender classification.
For applicable bulk marketing and subscribed messages, Google requires one-click unsubscribe and a clearly visible unsubscribe link in the message body. A footer link alone does not implement the required one-click mechanism. Google also expects unsubscribe requests to be honored within two days. Ask the agency to validate platform implementation, alignment, complaint monitoring, and sending practices; technical authentication alone cannot compensate for unwanted mail or poor acquisition.
Protect Permission and Suppression Records
Permission should be traceable, not assumed because an address exists in your database. Preserve signup source, timestamp, disclosure context, and relevant preference changes where available. Imported lists require particular scrutiny: a previous business relationship does not automatically justify every marketing use under every applicable law. Ask how the agency assesses acquisition methods and prevents questionable records from entering campaigns while your internal legal or privacy reviewers assess requirements.
Maintain a central suppression approach covering unsubscribes, hard bounces, complaints, and other exclusions appropriate to your program. Suppression is different from deleting an inconvenient record: the system must still prevent an excluded address from being reintroduced through a later import. Define synchronization between tools, processing timelines, and permitted transactional exceptions. An order confirmation should not become a workaround for sending promotions to people who opted out.
The FTC’s CAN-SPAM guide describes requirements for covered commercial email, including accurate headers, nondeceptive subject lines, a valid physical postal address, and a working opt-out mechanism. Opt-out requests must be honored within ten business days. The FTC also warns that hiring another company does not remove the advertiser’s responsibility. Have qualified reviewers assess your circumstances and other applicable laws; an agency contract should never promise universal legal compliance.
Measure Outcomes Without Overclaiming Attribution
Agree on a measurement hierarchy before the first campaign. Commercial outcomes might include qualified opportunities, purchases, renewals, or repeat orders. Supporting indicators include clicks, landing-page conversion, unsubscribes, complaints, and delivery failures. Define each metric’s denominator so reports remain comparable. Delivered messages are not proof of inbox placement, and open rates are imperfect because image blocking and privacy-related image retrieval can separate recorded opens from actual reading behavior.
Attribution rules materially affect reported revenue. Ask which interactions receive credit, how long the attribution window lasts, whether opens qualify, and how cancellations or returns are handled. Platform-attributed revenue can overlap with paid search, social, and direct traffic reporting. Reconcile it with your analytics and transaction records, but expect differences. A credible agency explains those differences instead of selecting whichever dashboard produces the largest apparent contribution.
Use experiments where feasible to assess incremental impact, rather than assuming all attributed purchases were caused by email. A randomized holdout can compare eligible recipients who receive a treatment with similar eligible recipients who do not. Small audiences may not support confident conclusions quickly. Require documented hypotheses, primary outcomes, and stopping rules, alongside commentary on sample limitations and business changes that could distort interpretation of test results.
Understand Costs Without Shopping by Email Count
Agency costs depend on complexity as much as volume. A single multilingual campaign with dynamic content, several approval groups, and custom reporting can require more work than multiple straightforward newsletters. Evaluate the number of templates, variants, journeys, integrations, and stakeholders involved. Ask proposals to distinguish initial setup, recurring management, platform charges, specialist technical work, and optional projects so you understand the total operating commitment before signing.
Compare commercial models against your workload. Retainers can suit continuous planning and optimization, while defined projects can suit migrations or bounded lifecycle builds. Production-based arrangements need careful definitions of what counts as one campaign or revision. Ask how urgent requests, extra meetings, unused capacity, and change orders work. A lower headline fee may simply shift quality assurance, analysis, or coordination responsibilities back to your own employees.
Estimate internal effort alongside external fees. Your team may still supply product information, approve promotions, resolve data issues, and maintain integrations. Identify these dependencies and attach realistic turnaround expectations. Negotiate a scope review process when complexity changes rather than accepting indefinite informal extras. Evaluate value through the agency’s ability to address your priority constraints, not through unsupported forecasts or a promise that additional sends automatically generate profitable growth.
Retain Ownership and Plan the Exit Early
Your business should control its platform account, sending domains, customer records, billing relationship where practical, and administrator access. Agency-managed convenience should not create dependency that blocks a future transition. Clarify ownership of copy, designs, templates, automation logic, reports, and documentation. Some tools or creative components may involve third-party licenses, so distinguish transferable deliverables from licensed materials before assuming everything can move freely to a new provider.
Specify how knowledge is recorded during the engagement. Useful documentation includes naming conventions, segment definitions, journey diagrams, tracking rules, integration mappings, test results, and operational runbooks. Store approved versions where your team can access them. Reporting should be reproducible without relying on one agency employee’s private spreadsheet. Request explanations of custom code and dependencies so a replacement provider can maintain the program safely without reverse-engineering its logic.
Include an exit procedure covering notice, handover support, exports, access revocation, and treatment of retained data. Confirm which platform objects can actually be exported; a contact file is not a complete automation backup. Preserve suppression information during migration and test authentication before switching traffic. Agree how confidential information will be returned or deleted, subject to necessary retention obligations, and who verifies completion of the transition checklist.
Select With a Weighted Vendor Scorecard
Build your scorecard before reviewing polished pitches. An illustrative weighting could allocate thirty percent to strategy and lifecycle capability, twenty-five to data and deliverability operations, twenty to measurement, fifteen to delivery governance, and ten to commercial fit. Adjust these weights to your risks. A business migrating platforms may reasonably prioritize technical operations more heavily than a business with stable infrastructure and an urgent need for better creative.
Score evidence rather than confidence. Ask finalists to critique a sanitized journey, explain a sample performance discrepancy, and outline their response to a sudden complaint increase. Request relevant work examples they are authorized to share, while recognizing that another client’s outcome does not predict yours. Meet the actual delivery team and clarify staffing, escalation routes, backup coverage, and the senior oversight included in your proposed agreement.
Finish with a bounded initial plan and explicit review criteria. Define what must be audited, repaired, launched, and documented, plus how both parties will judge progress when commercial outcomes take time. Reject guarantees of inbox placement or revenue that ignore outside dependencies. If you want help clarifying how email fits your broader acquisition and retention priorities, consider a free website and marketing strategy call with ZORO Marketing.