The Deliver phase of a tactical marketing plan: write it so someone else can execute it (part 4 of 5)

Most marketing plans stop at a strategy, a content list, and maybe a calendar. The teams that execute well keep going. The Deliver phase writes the plan down to the level where a team that was never in the room can build it.

This is the third of the three phases in our method for creating a tactical marketing plan, and it is the one that gives the plan its name. A strategy describes what you intend to do. This phase hands the builders everything they need to actually do it.

Specify every automation as a contract

Every automated program in the plan gets the same four-part specification:

• How many messages
• At what cadence
• Who enters the program
• What makes them exit

Real examples, generalized from plans we have shipped:

• A quarterly reengagement nurture: four messages, one per quarter, to contacts inactive for more than 90 days, exiting on any form submission.
• A post-inquiry nurture: five messages, one every two weeks, to contacts who requested pricing, exiting on a recorded win or loss.
• A partner reengagement program: twelve messages, one per month, to channel partners with no activity in 90 days, exiting when the partner becomes active again.
• An aging-lead nudge: a single triggered message to the assigned owner when a lead sits too long without an outcome.

The exit criteria are the part most teams skip, and the part that prevents the embarrassing outcome of nurturing someone who already bought. The design discipline behind these specifications is the subject of the [Practical Guide to Marketing Automation](/resources/practical-guide-to-marketing-automation/).

Define the data feeds field by field

Automations run on data, and the plan says exactly which records flow where. For each feed, five things in writing:

• The source system
• The direction of the feed
• The fields carried
• The unique identifier used for updates
• Whether the feed adds, updates, and removes records

The principle underneath: the client's existing database remains the system of record, and the marketing platform subscribes to it. The alternative is letting the marketing tool quietly become a second CRM. That is how teams end up in years-long data cleanup projects instead of doing marketing.

This section is also where consent gets engineered. Which field records marketing consent? Where is it captured? How is it proven? Writing that into the plan is much cheaper than bolting it on after a complaint.

Name the reports before launch

Every report the plan promises is defined before anything ships. Program performance month over month. Lead sources by channel. Form performance. Outcomes by owner.

Defining reports last is how marketing ends up unable to prove its own results. Defining them in the plan means the tracking is built into every asset from day one. The first monthly review then has data instead of apologies. Measurement as a diagnostic chain is part of our methodology's testing and optimization phase.

Handoff is not abandonment

The plan sets a review cadence, because launch is when the system starts telling the truth. Entry criteria that looked right on paper catch the wrong contacts. A feed drops records nobody predicted. The first quarter of a tactical plan is a working theory under observation. Staying with it past go-live is the core of how we work.

The final article in this series covers exactly that: what execution looks like in the 13 weeks after the plan ships. The full method, including the gated eight-section template, is at How to Create a Tactical Marketing Plan.