Prepare an outreach campaign from an approved strategy
Translate a targeting and messaging brief into a populated campaign draft across the required sales tools.
How this works
Translate a targeting and messaging brief into a populated campaign draft across the required sales tools.
Prepare a campaign as a complete draft that can be inspected before launch. Audience selection, exclusions, message versions and sender configuration must agree across tools, and missing infrastructure must remain a setup gap.
Before you start
Defined operating scope
An approved commercial strategy must become account-specific outreach drafts and reviewable steps.
Required source material
Obtain Approved target-account strategy; Message sequence; Configured sender accounts and exclusions. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
A required sender is not configured. Record the setup gap and stop before launch preparation requires new infrastructure.
Prepare the inputs
- strategy
- Required
Approved account, role and geography criteria
Resolve ambiguous targeting before enrichment.
- sequence
- Required
Approved message drafts and timing
Preserve claims and personalization rules.
- sender_accounts
- Required
Existing configured senders
Do not purchase or create infrastructure implicitly.
- exclusions
- Required
Opt-outs, existing relationships and forbidden segments
Apply across every imported contact.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check strategy, sequence, sender_accounts, exclusions before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected strategy and any missing required fields.
Parse and confirm audience, roles, and geographic criteria
- Translate the strategy into explicit filters and document assumptions that need owner confirmation.
- Reconcile imported, excluded, held and eligible contact counts across the tools.
Checkpoint: A saved intermediate result for: Parse and confirm audience, roles, and geographic criteria.
Find and review matching business contacts
- Find permitted business contacts, verify fit and apply exclusions before loading the campaign.
- Preview sequence steps for false claims, broken tokens, wrong sender and unintended launch state.
Checkpoint: A saved intermediate result for: Find and review matching business contacts.
Load approved sequence drafts and select existing sender accounts
- Load the approved sequence and select existing sender accounts; preview personalization using real field values without sending.
- Reconcile imported, excluded, held and eligible contact counts across the tools.
Checkpoint: A saved intermediate result for: Load approved sequence drafts and select existing sender accounts.
Inspect the complete campaign and leave launch to the owner
- Inspect counts, missing fields, exclusions and message samples across the complete draft, then leave launch disabled for owner review.
- Preview sequence steps for false claims, broken tokens, wrong sender and unintended launch state.
Checkpoint: A saved intermediate result for: Inspect the complete campaign and leave launch to the owner.
Package the result and unresolved work
- Check lawful contact use, opt-outs, exclusions, and message claims. The demonstrated flow required preconfigured domains; account purchasing was still planned.
- Preparing the draft does not authorize sending or buying domains and mailboxes.
Checkpoint: A configured outreach draft ready for review. Unresolved items remain visible in the review record.
Decisions along the way
A required sender is not configured.
Record the setup gap and stop before launch preparation requires new infrastructure.
Personalization data is missing.
Use an approved neutral fallback or exclude the contact; never expose template tokens.
An excluded contact reappears through another list.
Apply the suppression rule by stable identity and reconcile the campaign before launch.
What you will produce
strategy-to-outreach-campaign-draft-result.json
JSONA configured outreach draft ready for review. Label proposed and completed states separately.
Include: campaign_id · audience_rules · eligible_contacts · exclusions · sequence_version · sender_ids · launch_state · status · evidence_reference · review_note
strategy-to-outreach-campaign-draft-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving exclusions.
Include: source_reference · question · owner · next_action
Check the result
- Reconcile imported, excluded, held and eligible contact counts across the tools.
- Preview sequence steps for false claims, broken tokens, wrong sender and unintended launch state.
- Inspect strategy and sequence in both the original and output; confirm that record identity and interpretation survived the transformation.
- Check lawful contact use, opt-outs, exclusions, and message claims. The demonstrated flow required preconfigured domains; account purchasing was still planned.
When something goes wrong
A required sender is not configured.
Record the setup gap and stop before launch preparation requires new infrastructure. Retain the affected evidence and recovery status.
Personalization data is missing.
Use an approved neutral fallback or exclude the contact; never expose template tokens. Retain the affected evidence and recovery status.
An excluded contact reappears through another list.
Apply the suppression rule by stable identity and reconcile the campaign before launch. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Prepare an outreach campaign from an approved strategy for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Strategy targets operations leads in one region. Imported list has 20 contacts, including 3 opt-outs and 2 with missing company names.
Expected result
Synthetic expected result: Suppress 3 opt-outs. Hold or use approved fallback for the 2 incomplete records. Draft count and exclusions are reconciled; launch remains disabled.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure accepted account-message matches; relevant replies per approved campaign cohort.
Stop or revise
An excluded contact reappears through another list. Pause affected records and apply this recovery: Apply the suppression rule by stable identity and reconcile the campaign before launch.
Keep the scope clear
- Preparing the draft does not authorize sending or buying domains and mailboxes.
- Use only permitted contact data and honor exclusions throughout the campaign.
Check before using
Check lawful contact use, opt-outs, exclusions, and message claims. The demonstrated flow required preconfigured domains; account purchasing was still planned.
Business activities
- Find and approach prospects
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Approved target-account strategy · Message sequence · Configured sender accounts and exclusions
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow