PlaysbyMoat8
Back to the library
The workflow guideMarketing

Turn public ad research into original creative concepts

Monitor a competitor’s public ads and prepare new concepts for your own product and design team.

6 implementation stepsAdvanced

How this works

Monitor a competitor’s public ads and prepare new concepts for your own product and design team. A concept studio should turn observed competitor approaches into original experiments for your own offer. Visible ad duration, repetition, and engagement are research clues, not proof that a competitor's concept converts or that copying it will work.

Collect public ads, describe their underlying communication mechanisms, and select a few patterns relevant to the brand. Develop distinct scripts and mockups using approved product facts. Keep the research evidence separate from the creative assets intended for publication.

Before you start

Product message

Choose the offer and audience problem the new concept must explain.

Competitor sample

Use permitted current ad-library material with dates.

Design constraints

Provide brand rules, available assets, and production limits.

Prepare the inputs

ad_examples
Required

Public records and media

Record what was actually viewed.

own_product_facts
Required

Approved claims

Do not import competitor capabilities.

concept_criteria
Required

Audience and communication goals

Define relevance beyond popularity.

brand_assets
Required

Approved references

Keep exact marks and product details.

production_scope
Required

Formats and resources

State what can be prototyped now.

Implementation, step by step

  1. Collect a bounded sample

    • Record current examples and their visible dates.
    • Group related variants without treating every version as an independent concept.

    Checkpoint: A dated research set.

  2. Describe mechanisms

    • Identify hooks, proof, narrative sequence, visual devices, and calls to action.
    • Separate observable structure from assumptions about targeting or performance.

    Checkpoint: A pattern map.

  3. Select transferable ideas

    • Compare patterns with the actual product, audience, and production capacity.
    • Reject concepts whose persuasive force depends on a claim the product cannot support.

    Checkpoint: A justified shortlist.

  4. Create original concepts

    • Write new scenarios, copy, and visual directions using the team's own examples.
    • Preserve the abstract mechanism without copying distinctive script or artwork.

    Checkpoint: Distinct concept briefs.

  5. Build reviewable mockups

    • Use available design tools to create rough assets that make the idea concrete.
    • Label placeholders and avoid presenting mockups as final production files.

    Checkpoint: A creative review set.

  6. Prepare the next test

    • State what each concept would test and which evidence would be useful.
    • Let the designer and media owner choose the production and experiment scope.

    Checkpoint: A bounded test handoff.

Decisions along the way

A pattern relies on a competitor-specific feature

Choose another mechanism or use an honest own-product example.

Only a thumbnail is visible

Limit analysis to observed elements.

Two concepts are cosmetically different

Redesign one around a different message or proof mechanism.

What you will produce

ad-concept-briefs.md

Markdown

Guides original creative development.

Include: concept_id · mechanism · audience · message · proof · visual_direction · test

concept-mockups

Editable or image files

Makes review concrete.

Include: concept_id · version · placeholder_notes · status

Check the result

  • Verify research descriptions against the original ads.
  • Check all product claims against approved facts.
  • Inspect originality of script and visual execution.
  • Keep performance assumptions out of factual concept descriptions.

When something goes wrong

Mockup copies source composition too closely

Rework the expression around the underlying principle.

Generated product imagery is inaccurate

Replace it with approved assets.

The concept lacks a testable purpose

Return to the audience question before further production.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Develop original concepts from public software ads.

Inputs

Synthetic example. Synthetic competitor examples use a checklist reveal and a customer quote. Your product has no approved testimonial.

Expected result

Synthetic expected result. Create an original checklist demonstration and a product walkthrough alternative. Do not invent a customer quote to imitate the second ad.

Run a small pilot

Start small

A small source set and a few distinct mockups.

Record the baseline

Record concept-review effort and rejection reasons.

Agree success criteria

Agree originality, factual accuracy, and testability before production.

Stop or revise

Stop a concept when its central proof cannot be supported.

Keep the scope clear

  • Research access does not grant rights to reuse competitor assets.
  • Concept preparation does not authorize publishing or buying traffic.

Check before using

Long running time is only a proxy; check originality, branding, and claims before testing.

Business activities

  • Run advertising and acquisition tests

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: Competitor ad pages · Brand and product brief · Selection criteria

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 ↗