The marketing automation brief needs a stop rule before a launch date
A marketing automation implementation should define who enters a journey, what happens next and when communication stops. Scope the data, content, connected systems, human handoffs and acceptance checks before building the workflow. That gives your team a clearer basis for comparing agency proposals and maintaining the journey after launch.
Put the advice into practice
Give the first enquiry a useful follow-up
Plan campaigns, nurture and customer emails with clear triggers and review.
Plan your email programmeStart with a journey your team can describe
“Automate our marketing” can mean a welcome email, a proposal follow-up or a connection between several systems. Choose one defined journey for the initial brief. Record the customer’s situation at the start and the decision the journey should help them make.
Consider a hypothetical consulting firm that offers an assessment guide. A person who requests it may want to understand the service before speaking to an adviser. The useful journey provides the guide, offers relevant supporting material and gives the person a suitable way to ask a question. It also needs to stop or change when that person begins a conversation with the team.
Use this implementation brief
| Decision | What to specify | Example to discuss |
|---|---|---|
| Entry | Trigger, eligible audience and required permission. | A new guide request with the appropriate recorded communication preference. |
| Data | Fields, source of truth and handling of missing values. | Service interest comes from the form; the CRM owns relationship status. |
| Content | Message purpose, sender and approval owner. | The second message answers a common assessment question. |
| Handoff | Who acts when a person replies or requests a call. | A named adviser receives the enquiry context. |
| Exit | Events that stop, pause or change the journey. | A reply, changed preference or active proposal removes the person from this sequence. |
| Acceptance | Scenarios that must work before release. | A duplicate entry does not trigger duplicate communication. |
What must the agency check about the platform?
Ask the agency to confirm the features available in your actual account and plan. A diagram can show a journey the current subscription cannot support. Mailchimp’s automation flow documentation, for example, notes that feature access depends on the plan.
Identify each required connection and distinguish a supported connector from custom development. Agree which data moves in each direction, which account owns the connection and what should happen when it fails. A successful test should include the inconvenient cases, such as a missing field or a change made while someone is already in the journey.
How should communication preferences enter the scope?
Record where the relevant permission and preference data comes from, how a change is passed between systems and which journeys must stop. In Australia, the ACMA’s marketing message guidance covers consent, sender identification and unsubscribe responsibilities. Build the operational handling into the brief.
A customer record and a marketing permission are different pieces of information. Ask the agency to show how the journey distinguishes them in the actual configuration. Someone also needs to own exceptions when two systems contain conflicting preferences.
What belongs in setup, and what belongs in ongoing support?
Setup can cover discovery, mapping, agreed content, configuration, testing and handover. Ongoing support can cover reviewing journey behaviour, maintaining connections, updating content and responding to agreed issues. Ask for each to be itemised so the recurring engagement has a clear purpose.
The handover should explain who can change the journey, where the approved version is documented and how to pause it safely. Our automation handover guide and B2B lead nurturing guide cover those follow-through decisions.
Bring the first journey to an agency discussion
Share the current form, email platform, CRM, sample messages and the people responsible for follow-up. Sensitive records can wait until the appropriate access and data-handling arrangements are agreed. A diagram and a small set of test scenarios are often enough to scope the initial investigation.
Explore Grendesign’s marketing automation implementation and ongoing support for the connected journey, and email marketing services for campaign strategy, copy and design. If the brief includes wider custom systems, review our AI and automation work alongside the marketing journey.
