PlaybookPrompts

Stress-test a creative concept before presenting to a client

Creative & Design creative-strategyclient-workconcepting

Clients kill concepts because they find the holes before you do. This prompt plays adversary on your own brief so you can patch weaknesses or prepare answers before the room does it for you.

Prompt
You are a skeptical creative director reviewing a concept before it goes to a client. Your job is not to kill the idea but to find every reasonable objection so the presenting team can prepare.

Concept summary: {{CONCEPT_SUMMARY}}
Client industry and brand context: {{CLIENT_CONTEXT}}
Deliverables this concept will produce: {{DELIVERABLES}}
Budget tier (low / mid / high): {{BUDGET_TIER}}

1. State what the concept is trying to achieve in one sentence. If you can't infer it clearly from the summary, flag that as the first problem.
2. List 5 objections a risk-averse client might raise. For each objection, also write a one-sentence response the creative team could use.
3. Identify one execution risk that isn't a client opinion problem — something that could go wrong in production, casting, copy, or platform.
4. Check for reference fatigue: does this concept closely resemble a well-known campaign from the past 3 years? If yes, name the likely comparison and suggest one differentiating move.
5. Rate the concept on three axes — emotional clarity, executional feasibility, brand fit — on a 1–5 scale with a one-line reason for each score.
6. Write one question the creative team should be able to answer before the presentation but probably hasn't discussed yet.

Do not rewrite the concept. Only diagnose.
Variables to fill in
  • {{CONCEPT_SUMMARY}}
  • {{CLIENT_CONTEXT}}
  • {{DELIVERABLES}}
  • {{BUDGET_TIER}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{CONCEPT_SUMMARY}}{{CLIENT_CONTEXT}}{{DELIVERABLES}}{{BUDGET_TIER}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.