The team has aligned on a focused approach to email automation: only pursue automations where there is a clear, demonstrable marketing impact. Complex IT-adjacent issues — such as transactional email configuration, spam filtering, and deliverability — should be deferred to the client's own IT consultants rather than absorbed by the agency.
This decision emerged from a review of existing email automation work where it became apparent that many automations were being built on request without a strong case for their value — half were not turned on, and open rates on others were negligible.
"I think if we have a really good, clear case where we know that email automation is going to make a difference, then we want to do it. But otherwise..." — Mark Hope
Going forward:
- Do: Build email automations when there is a clear, high-impact use case with measurable marketing outcomes.
- Defer: Transactional email issues, spam/deliverability problems, and other IT-level concerns belong with the client's IT consultant — not the agency.
- Avoid: Building automations simply because a client requests them, without validating that they will actually be used or drive results.
An email automation is worth building when:
- There is a defined trigger tied to a meaningful customer action (e.g., form submission, purchase, appointment booking).
- The automation addresses a clear gap in the client's follow-up or nurture process.
- There is a reasonable expectation of measurable outcome (open rate, conversion, retention).
- The client has confirmed they will actively use and monitor it.
These should be explicitly called out as out-of-scope in client agreements and redirected to the appropriate technical resource.
The team is also evaluating whether to develop internal email automation expertise or hire/contract specialists as needed. HubSpot specialists are noted as widely available. The decision on whether email automation remains a core agency service offering is still open.
See also: [1] (if created)