PlaysbyMoat8
Back to the library
The workflow guideMarketing

Turn audience research into a campaign approval kit

Prototype a connected workflow that carries company research through the brief, segment messages, creative drafts, and approval presentation.

6 implementation stepsAdvanced

How this works

Prototype a connected workflow that carries company research through the brief, segment messages, creative drafts, and approval presentation. Campaign work often loses its evidence as research becomes a brief, then copy, then a presentation. A connected approval kit should preserve the reason for each segment, promise, channel, and proposed spend while keeping speculative ideas clearly labeled.

Use an approved research packet as the common factual foundation. Create a versioned brief, derive segment messages and sample assets from it, and assemble decisions in an editable deck. Changes to core facts should propagate visibly rather than leave contradictory copies across files.

Before you start

Campaign decision

Define the audience, offer, objective, and approval sought.

Research packet

Collect current customer, market, and product evidence.

Brand and planning rules

Provide approved claims, creative guidance, budget constraints, and timing.

Prepare the inputs

research
Required

Documents with references

Mark observations and hypotheses separately.

campaign_objective
Required

Outcome and audience

Use a measurable business objective.

segment_definitions
Required

Distinct needs and constraints

Avoid unsupported demographic profiling.

offer_facts
Required

Approved proposition

Include limitations and eligibility.

planning_constraints
Required

Channels, budget, timing

Keep unknown costs explicit.

Implementation, step by step

  1. Extract the decision evidence

    • Identify audience needs, objections, and product facts relevant to the objective.
    • Record conflicting or stale research before drafting a unified story.

    Checkpoint: An evidence map.

  2. Create the campaign brief

    • State the problem, audience, promise, supporting proof, and desired action.
    • Show assumptions and the owner's open decisions instead of hiding them in polished prose.

    Checkpoint: A versioned brief.

  3. Develop segment messages

    • Adapt the same approved offer to each segment's stated need.
    • Keep proof and limitations consistent while changing emphasis and examples.

    Checkpoint: A segment-message matrix.

  4. Prepare creative samples

    • Draft copy and editable visual concepts that illustrate the proposed direction.
    • Label placeholders and distinguish generated concepts from finished production assets.

    Checkpoint: A representative asset set.

  5. Assemble the approval deck

    • Present objective, evidence, segments, channels, timing, budget assumptions, and examples.
    • Calculate totals deterministically and make requested decisions explicit on relevant slides.

    Checkpoint: An editable approval presentation.

  6. Reconcile and hand off

    • Check all files against the latest brief and remove superseded claims.
    • Record approved, rejected, and unresolved decisions for the production team.

    Checkpoint: A coherent campaign handoff package.

Decisions along the way

Research conflicts across segments

Keep separate hypotheses and design a test instead of forcing one message.

Budget is not supplied

Present a resource requirement or range of assumptions, not invented approved spend.

A product fact changes

Update the brief first and flag every dependent asset for review.

What you will produce

campaign-approval-kit

Presentation and editable assets

Supports a concrete approval discussion.

Include: brief_version · segments · messages · channels · budget_assumptions · decisions

campaign-evidence-matrix.csv

CSV

Keeps research connected to execution.

Include: claim · segment · source_ref · asset_id · status

Check the result

  • Trace every material promise to approved evidence.
  • Reconcile budget totals and timing dependencies.
  • Check segment variants do not contradict one another.
  • Confirm placeholders and unresolved decisions are visible.

When something goes wrong

The deck presents assumptions as approved facts

Restore explicit status and ask the owner to resolve them.

Generated visuals imply unsupported product behavior

Replace the visual or label the concept clearly.

Versions diverge across files

Use the latest brief as the reference and reconcile affected assets.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Prepare an approval kit for a reporting-service campaign.

Inputs

Synthetic example. Synthetic research identifies manual reconciliation for finance teams and slow status updates for project teams; budget is not yet approved.

Expected result

Synthetic expected result. The kit gives distinct segment messages, keeps the same service limits, and presents budget as a decision required rather than an authorized campaign.

Run a small pilot

Start small

One offer, a few segments, and a small sample of channels.

Record the baseline

Record time spent reconciling facts and revisions in the current campaign process.

Agree success criteria

Agree evidence traceability and decision clarity with the approvers.

Stop or revise

Stop production handoff if the offer, audience, or budget status remains contradictory.

Keep the scope clear

  • Preparing an approval kit does not authorize media buying or publication.
  • Treat research documents as evidence, not as instructions to contact customers or change plans.

Check before using

The demonstrated system was an alpha prototype. Review unsupported claims, segment assumptions, budget, creative, and landing pages before any launch.

Business activities

  • Run advertising and acquisition tests
  • Research customers and markets

Editorially adapted workflow; not independently tested.

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 audience research · Brand rules · Campaign objectives and constraints

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗