Campaign Messaging Matrix Prompt
Build an evidence-aware campaign messaging matrix that connects audience segments, funnel stages, channels, objections, proof, and calls to action.
Use in AI
Choose an AI tool to copy the current Prompt with a short usage note. Nothing is sent to that tool.
Create a campaign messaging matrix from the following inputs. Campaign inputs - Campaign goal and success metric: [Campaign goal and success metric] - Product, offer, and conversion action: [Product offer and conversion action] - Audience research and segments: [Audience research and segments] - Funnel stages and channels: [Funnel stages and channels] - Brand evidence and compliance constraints: [Brand evidence and compliance constraints] - Operational constraints and measurement plan: [Operational constraints and measurement plan] Input requirements The minimum reliable inputs are a defined campaign objective, a specific offer or conversion action, at least one supported audience segment, intended channels, and the evidence available to substantiate claims. Budget, timing, brand voice, prior performance, competitor context, production capacity, attribution method, and approval requirements are useful additional context. If a missing or conflicting input would materially change the audience, offer, claim, channel, or conversion strategy, ask no more than five blocking questions before building the matrix. If progress is still safe, continue with explicitly labeled assumptions and leave unsupported fields unresolved. Do not invent customer research, product capabilities, prices, testimonials, performance results, legal clearance, or channel access. Evidence and tool boundaries Use only information visible in the Claude conversation and any materials Claude can actually read. Treat inaccessible links, unprovided documents, and unavailable analytics as unavailable rather than inspected. Separate: - Supplied fact: directly supported by the provided materials. - Inference: a reasonable interpretation of supplied evidence. - Assumption: a provisional choice requiring confirmation. - Unknown: information not available. - Conflict: sources that disagree and require reconciliation. Claude may analyze the inputs, organize evidence, draft message directions, identify risks, and propose tests. Claude must not claim to have contacted customers, inspected unavailable systems, measured live performance, approved claims, launched ads, changed campaigns, or published copy. All outputs are recommendations or drafts until an authorized person reviews and executes them. Messaging workflow 1. Normalize the campaign objective into one primary business outcome, one audience action, and one measurable campaign signal. Flag competing objectives rather than blending them silently. 2. Evaluate each proposed audience segment against the supplied research. Record the segment's situation, need or job, awareness level, purchase barrier, decision criteria, and supporting evidence. Do not infer sensitive traits or use protected characteristics for targeting unless lawful, necessary, explicitly supplied, and approved. 3. Define the offer architecture: customer value, differentiator, mechanism, proof, conversion action, and reasons to believe. Separate verified product facts from positioning hypotheses. 4. Map the customer journey across the supplied funnel stages. For each stage, identify the communication objective, information needed, principal objection, desired next action, and appropriate proof burden. 5. Evaluate channel fit using format, intent, attention level, targeting context, message length, production limits, and landing-page continuity. Do not force identical copy across channels; preserve the same strategic promise while adapting execution. 6. Build prioritized matrix rows at the intersection of audience segment, funnel stage, and channel. Avoid an unmanageable Cartesian expansion: include only combinations with a defensible strategic purpose, and explain material exclusions. 7. For every row, draft a message direction containing the audience insight, message objective, value proposition, objection response, proof element, hook, core message, call to action, tone, format guidance, and landing-page continuity requirement. 8. Generate up to three meaningfully different variants for each high-priority row when the evidence supports alternatives. Vary a testable strategic element such as benefit framing, proof type, objection treatment, or call to action—not superficial wording alone. 9. Screen all directions for unsupported superiority, guarantees, fabricated urgency or scarcity, misleading omissions, unverified testimonials, unauthorized competitor comparisons, exploitative fear, discriminatory targeting, and claims that may require legal or regulatory review. Use aggregated or de-identified audience evidence where possible; do not expose personal or confidential data in the deliverable. 10. Prioritize rows using strategic fit, evidence strength, expected impact, channel suitability, production effort, and compliance risk. Explain close trade-offs instead of presenting unsupported numerical precision. 11. Design a validation plan for material assumptions and variants. Specify the hypothesis, test unit, primary metric, guardrail metric, comparison, decision rule, required instrumentation, and minimum evidence needed before declaring a winner. If sample-size or baseline data is unavailable, mark the threshold as pending rather than inventing it. 12. Identify human approval gates. Brand, product, legal or compliance, channel, analytics, and campaign-owner approval must be assigned where relevant before production or publication. Stop and request specialist review when regulated claims, sensitive targeting, material legal uncertainty, or unsupported high-impact claims cannot be made safe. Required deliverable 1. Campaign decision frame Provide the primary objective, conversion action, audience scope, offer, funnel coverage, channels, success metric, constraints, and unresolved decisions. Label each material statement as supplied fact, inference, assumption, unknown, or conflict. 2. Audience and evidence map Use a table with these columns: segment; situation or job; awareness stage; need; decision criterion; principal objection; supporting evidence; evidence source; evidence strength; uncertainty or conflict; messaging implication. 3. Offer and claim ledger Use a table with these columns: proposed claim; claim type; exact supporting proof; source; permitted qualification; unsupported extension to avoid; review owner; status. Status must be one of supported, conditional, unsupported, conflicting, or approval required. 4. Prioritized campaign messaging matrix Use one row per justified audience-stage-channel combination and include: priority; segment; funnel stage; channel and format; communication objective; audience insight; value proposition; objection addressed; proof or reason to believe; hook; core message direction; call to action; tone and voice notes; landing-page continuity; evidence status; compliance note; approval owner. 5. Message variants For each high-priority matrix row, provide concise draft variants suitable for the named channel. Identify the strategic variable changed in each variant and the hypothesis it tests. Keep drafts consistent with substantiated claims and channel limitations. 6. Coverage and exclusion analysis List intentionally excluded segment-stage-channel combinations, duplicated messages, journey gaps, unsupported claims, conflicting inputs, and reasons for each decision. 7. Validation and measurement plan Use a table with these columns: matrix row; hypothesis; variant or comparison; audience and placement; primary metric; guardrail metric; baseline; decision rule; instrumentation required; test owner; evidence currently available; unresolved requirement. Distinguish proposed tests from tests actually run. 8. Quality and acceptance review Report each check with expected condition, actual desk-review observation, evidence, status, and corrective action. Check that: - Every priority row supports the campaign objective and a defined audience action. - Every factual or comparative claim maps to proof in the claim ledger. - Funnel-stage messages match audience awareness and information needs. - Objections receive specific responses rather than generic reassurance. - Calls to action are clear, proportionate to the stage, and continuous with the destination experience. - Channel adaptations preserve strategy without ignoring format or policy constraints. - Variants test meaningful hypotheses and can be measured with the proposed instrumentation. - Brand, privacy, accessibility, legal, and platform-policy concerns are identified for review. - No output implies that drafting, approval, testing, launch, publication, or measurement occurred without execution evidence. Assign each check one status: pass, conditional, fail, blocked, or not assessed. Do not use pass when the necessary evidence is unavailable. 9. Approval and handoff register List each deliverable or risk, required reviewer, approval reason, current state, evidence needed, and permitted next action. Keep drafted, reviewed, approved, scheduled, launched, measured, and verified states distinct. Conclude with the smallest safe next action, normally resolving the highest-impact unknown or routing the matrix to the first required human reviewer. Do not authorize publication or describe the campaign as production-ready while blocking evidence, claim substantiation, instrumentation, or approvals remain unresolved.
Variables to Replace
Replace each listed value in the Prompt with information relevant to your task.
- Campaign goal and success metric
- Product offer and conversion action
- Audience research and segments
- Funnel stages and channels
- Brand evidence and compliance constraints
- Operational constraints and measurement plan
How to Use This Prompt
In Claude, replace every variable with the corresponding campaign information. Provide the campaign brief, audience research, offer details, substantiation documents, brand guidelines, channel specifications, prior performance data, compliance restrictions, landing-page context, and measurement requirements that are available. Remove or de-identify unnecessary personal data, then run the prompt. Answer any blocking questions Claude raises and route the resulting drafts through the listed human approval gates before production or publication.
Example Use Case
A SaaS company can provide Claude with its product launch brief, interview findings, approved feature evidence, funnel stages, paid social and email channels, brand rules, and trial-conversion metric. Claude will produce an evidence-linked messaging matrix, channel variants, claim ledger, test plan, and approval register without claiming the campaign has been launched or validated.
Was this useful?