PlaybookPrompts

Turn a messy client transcript into a clean design brief

Creative & Design project-managementdesignclient-work

Client kickoff calls produce scattered ideas, contradictions, and half-formed references. This prompt structures that raw input into a brief a designer can actually use.

Prompt 
You are a creative project manager. Turn the following client call transcript or notes into a structured design brief.

Raw transcript or notes:
{{CLIENT_TRANSCRIPT}}

Project type: {{PROJECT_TYPE}} (e.g., logo, website, packaging, campaign)

1. Identify the stated objective. If the client said it more than one way, reconcile the versions into one clear sentence.
2. Extract all visual references mentioned (brands, images, words like 'clean' or 'bold'). Group them under: References to Emulate, References to Avoid.
3. List the constraints: budget signals, timeline hints, technical requirements, or stakeholder approval steps mentioned.
4. Identify any contradictions in what the client said (e.g., 'minimal but also lots of information'). Flag each one with a recommended clarifying question.
5. Write a single 'North Star' sentence that a designer could tape above their monitor to stay aligned.
6. List what's still unknown and must be answered before design begins.

Do not invent information not present in the transcript. If a section has no usable input, write 'Not specified—needs follow-up.'
Variables to fill in
  • {{CLIENT_TRANSCRIPT}}
  • {{PROJECT_TYPE}}

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: {{CLIENT_TRANSCRIPT}}{{PROJECT_TYPE}}.
  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

Notion AI

$8/user/mo add-on

AI baked into the docs/wiki/projects tool you already use.

Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.

productivitywriting

Perplexity

$0/mo (Pro at $20)

AI search engine with citations.

Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.

learningdata

Claude (Anthropic)

$0/mo (Pro at $20)

Frontier model with long context and strong reasoning.

Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.

writingcodinglearning

ChatGPT (OpenAI)

$0/mo (Plus at $20)

The category-defining general-purpose AI assistant.

ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.

writingcodinglearning

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.