Agent 39 of 71 · Demand Generation & Social
Distribution Planner
Get the right approved line in front of the ICP in the right order. Turn a blueprint and its assets into a dated calendar where every placement carries the same tags, channels reinforce rather than repeat, and the Minimum Viable Loop is always shipped first.
Agent contract
Use to sequence approved assets across owned, earned and paid channels: who publishes what, where, when and in which variant, so one message reaches the ICP consistently and every placement is tagged.
When it runs
- A campaign blueprint is approved and assets exist or are in production.
- A launch needs its channel calendar for owned, partner and community placements.
- A new approved subhead or kernel should be run as a Minimum Viable Loop.
What it needs
| Input | Required | From |
|---|---|---|
| Approved campaign blueprint | Yes | Campaign Strategy Agent |
| Approved variant grid and kernels | Yes | Message Memory |
| Channel owners, cadences and blackout dates | Yes | You |
| Channel activation plan from a launch | Optional | Channel Activation Planner |
| Persona channel habits | Optional | Buyer Personas |
How it works
- Inventory approved assets and variants with their tags; anything untagged or unapproved is listed as blocked, not scheduled.
- Ship the Minimum Viable Loop first: one approved subhead placed on site, email and LinkedIn in the same week with identical Narrative tags.
- Assign each channel a role in the sequence (announce, explain, prove, convert) and match variants to the stage that role serves.
- Sequence placements to avoid audience collisions: no ICP segment receives the same variant on two channels within 72 hours.
- Name a human owner and publish date for every placement; agents draft and schedule-plan, owners publish.
- Attach the UTM and tag convention per placement so performance can be joined back to Narrative, Persona, Stage and ProofID.
- Render templates/distribution-plan.md as a dated calendar with a blocked-items list and a Day 7 read checkpoint.
What it delivers
Distribution plan: Minimum Viable Loop row, channel roles, dated placement calendar (asset, variant, tags, UTM, owner), collision checks, blocked items, read checkpoints.
Output contract: distribution-plan
Quality bar
- Every placement has an owner, a date, a variant ID and a full tag set.
- The Minimum Viable Loop is scheduled before any multi-channel expansion.
- No placement uses an asset that is not approved in message-memory.
Hands off
- LinkedIn Strategy AgentLinkedIn placements need post-level drafting and targeting specs.
- Email Strategy AgentEmail placements need list, consent and cadence checks.
- Marketing QA AgentThe calendar is ready for a pre-publish tag and link QA.
When a person steps in
- If two campaigns target the same segment in the same window, escalate to the Chief of Staff for prioritisation.
- If a channel owner cannot confirm capacity, mark the placement at risk rather than assuming it ships.
Channel and distribution plan in Demand Generation Engine: approved by Demand generation lead with budget holder.
Example
Request
“Schedule the controller campaign assets for the next six weeks.”
Result
Plan with MVL in week 1 (subhead MSG-0044 on homepage hero, newsletter lead and CFO post), 27 placements across 5 channels, 2 collisions resolved, 3 items blocked pending proof, Day 7 checkpoint booked with owners.
Illustrative example from the package documentation, not a client result.