How to Write a Campaign Brief With ChatGPT or Claude (2026): Interview Prompts and 12 Fields

Key Takeaways

• Storyflow is the best place to write a client campaign brief with ChatGPT or Claude in 2026, because its MCP connector lets the assistant write the brief onto a board, read it back and revise it, beside the moodboard, deliverables table and timeline the brief becomes.
• Use the assistant as an interviewer first and a writer second. Ask it to question you one field at a time; a brief drafted from a single paragraph of context is mostly guesswork.
• A client campaign brief needs 12 fields: business problem, objective, KPI, audience, insight, single-minded proposition, reasons to believe, tone, mandatories, deliverables, budget and timeline with one named approver.
• Make the assistant mark every fact it was not given as "[Confirm with client]". In the worked example below, 3 of 12 fields stayed open after the interview, and they became the agenda for the brief-back call.
• One objective, one number, one date. "400 paid subscriptions at a cost per acquisition of $45 or less by May 17" is a brief; "drive awareness of the subscription" is a wish.
• Connecting is a one-time step: Claude allows one custom connector on its Free plan, and ChatGPT needs Plus or above with developer mode on.
• Storyflow plans start at $7.99 a month billed annually. There is no free plan during early access, but anyone a paid member invites to a board joins free.
• Google Docs is the stronger home when the client needs tracked redlines; Storyflow has no approve button or versioned approvals.

Why a Brief Written in a Chat Window Fails the Client

You paste the client's email into ChatGPT, type "write a campaign brief", and get a clean, confident document in 20 seconds. It has an objective, a target audience, a key message and a list of channels. It reads well. Then you look closer: the budget is a guess, the audience is "health-conscious millennials", and the key message is three messages joined by commas. The assistant did exactly what you asked. You asked for the wrong thing.

A campaign brief is not a writing task. It is an agreement between you and the client about what the campaign must achieve and what it must not do. The writing is the last 20% of the job. Here is where the chat-window version breaks.

The assistant fills gaps with plausible fiction

Language models are trained to produce complete-looking answers. Give one a brief with no budget and it will write one. Give it no KPI and it will choose "20% increase in engagement". Those numbers look like yours, and the client will read them as yours. A brief with an invented number is worse than a brief with a blank, because nobody questions the number.

The brief scrolls away

Every revision ("make the tone warmer", "add the in-store posters") produces a new version further down the conversation. By the third round there are three briefs in the chat and none of them is marked as the one the client approved.

The client cannot open your chat

Your client does not have your ChatGPT history, and a shared conversation link shows every rejected draft. So the brief gets pasted into an email or a doc, and from that moment the assistant can no longer see the version people are actually arguing about.

The brief is separated from what it produces

A brief exists to drive a moodboard, a deliverables list, a budget split and a timeline. When the brief lives in a chat and those live in four other files, the first scope change ("can we add a radio spot?") updates one of them. The fix is to put the brief where the assistant can read it back and where the plan sits beside it.

The 12 Fields Every Client Campaign Brief Needs

Briefing frameworks disagree on the count, but the client campaign briefs that survive a whole campaign carry the same 12 answers. Twelve is the point where every field earns its place: drop one and a predictable argument appears in week three. The table below is the checklist your assistant should interview you against.

Fields 2 and 3: the objective and the KPI decide everything else

Write these first. The objective decides the audience, the channels and the deliverables; everything else is downstream. Ask the assistant to reject any objective that does not contain a number, a unit and a date. "Sell 400 sourdough subscriptions by May 17" passes. "Build buzz around the launch" does not, and the assistant should say so.

Field 6: the single-minded proposition is one sentence with no "and"

The single-minded proposition (SMP) is the one thing the audience should take away. If it has an "and" in it, it is two propositions, and the creative team will pick one without telling you. Ask the assistant for five candidate SMPs, then ask it to argue against each one. The survivor is usually the plainest.

Field 9: mandatories are where clients hide the real brief

Mandatories are the rules the work must follow: logo clear space, a legal line, a product shot that must appear, a competitor that must never be named, a price that must not be shown. Clients rarely volunteer them because to them they are obvious. Ask directly, and ask twice: "What would make you reject a concept on sight?"

Field 12: one approver, named

A brief with three approvers is three briefs. Name one person with final say and list everyone else as consulted. This single line prevents more rework than any other field in the brief.

How We Weighted Where the Brief Should Live

Writing the brief and keeping the brief are two different jobs. Both ChatGPT and Claude write a competent brief once you interview them properly. The question this guide ranks is where the brief should live once it is written, given that an assistant drafts it, the client reads it and the team builds from it.

The six criteria and their weights

• Assistant writes and reads it back (25%). Can ChatGPT or Claude put the brief into the tool, read the current version and revise it in place, or do you copy and paste?
• Brief beside the plan and visual direction (25%). Can the brief sit in the same place as the moodboard, deliverables table, budget and timeline it drives?
• Client access (15%). Can the client open it by link, and what do they need to sign in for?
• Cost for a freelancer or small agency (15%). What one person and a team of four pay each month.
• Redlines and approval record (10%). Suggesting mode, comments, version history, a clear approval trail.
• Polish of the brief-back (10%). How finished does it look when you present it?

Each tool scored 1 to 5 per criterion; the weighted total is out of 100. Redlines carry only 10% because most small-agency briefs are approved on a call and an email, not line by line. If your clients redline every word, raise that weight to 25% and Google Docs moves to first. That is the honest trade-off.

What we did not weigh

Media buying, ad reporting, invoicing and contracts are out of scope: none of these tools does them and a brief does not need them. Storyflow also does not publish or schedule posts, so if the brief must flow straight into a scheduler, plan for that handoff.

Comparison Table: Where to Keep a Campaign Brief You Write With ChatGPT or Claude

Prices are as of October 2026, checked on each vendor's own page. Notion prices are its USD list prices. Canva's pricing page refused our request on October 9, so check its current price there.

Sources: Notion pricing, Notion MCP help, Claude's Google Workspace connectors, ChatGPT's Google Drive app, Canva pricing, Canva AI connectors, Milanote plans.

How to Write a Campaign Brief With ChatGPT or Claude, Step by Step

These ten steps take a messy client input (an email, a call transcript, last year's deck) to a signed-off brief on a board. Budget 90 minutes for the first one, about 45 once you have the prompts saved.

Step 1: Decide where the brief will live (Storyflow first)

Choose the home before you start chatting, because it decides whether the assistant can read its own work back. For a brief that becomes a campaign plan, create a Storyflow project for the client and a board called "Campaign brief". Then connect your assistant once: in Claude, open Customize, then Connectors, then Add, then Add custom connector, name it Storyflow and paste https://mcp.storyflow.so/mcp, then sign in. In ChatGPT on the web, turn on developer mode under Settings, Security and login, then add Storyflow as a connector with the same address. The full walk-through is on the Storyflow MCP page and in the help article on connecting AI assistants. At sign-in you choose which projects the assistant may see and whether it may make changes.

Step 2: Give the assistant the client's real material

Paste or attach everything the client sent: the email thread, the call notes, last year's campaign results, the brand guidelines PDF, the product page link. Tell the assistant what each item is. "This is the client's email from March 1. This is their brand book. This is last spring's results deck." The assistant cannot tell an aspiration in an email from a fact in a results deck unless you label them.

Step 3: Ask it to interview you, one field at a time

This is the step most people skip, and it is the one that makes the brief yours. Ask the assistant to read the material, list which of the 12 fields it can already answer from the material, and then ask you about the rest one question at a time, waiting for each answer. Prompts are in the copy section below. An interview of 10 to 15 questions takes about 20 minutes and produces a brief built on your answers instead of its guesses.

Step 4: Mark every unknown, never fill it

Tell the assistant, in the same prompt, that any fact neither you nor the material supplied must be written as "[Confirm with client]". Budgets, dates, legal lines, approver names and KPI baselines are the usual gaps. Storyflow's own in-app campaign brief workflow follows the same rule: it writes the slot and marks it rather than inventing a market figure or a budget. Your open items list is now the agenda for the brief-back call.

Step 5: Write the objective and KPI first, the background last

Have the assistant draft field 2 and field 3 before anything else, and push back until the objective has a number, a unit and a date. Then the audience, insight and proposition as one chain. The background goes last and gets five sentences at most; it is where briefs bloat.

Step 6: Generate five propositions and argue against each

Ask for five single-minded propositions, each under 12 words, each without "and". Then ask the assistant to attack each one from the audience's point of view: would they believe it, do they care, could a competitor say it? Keep the one that survives. This is the step where an assistant is most useful, because it does not get attached to its first idea.

Step 7: Put the logistics in tables, not prose

Deliverables, budget and timeline are tables. Each deliverable row needs format, ratio, length, versions, languages and revision rounds. Each budget line needs what it covers. Each date needs an owner. Ask the assistant to build these as tables on the board, not as paragraphs in a document. On Storyflow the connector can build a table directly, and the rows stay in date order because you wrote them that way.

Step 8: Build the brief on the board

Ask the assistant to write the brief onto the Storyflow board (the brief to project board page shows the finished shape): a document for the narrative fields (problem, objective, audience, insight, proposition, tone) and tables for deliverables, budget and timeline, grouped into sections. If your assistant client supports MCP apps, ask it to show the board so you watch it build. If you would rather use Storyflow's own AI agent, run the campaign brief workflow inside Storyflow instead: it lays out ten sections from client and audience to timeline and marks what it was not told.

Step 9: Put the visual direction beside the brief

This is where a board beats a document. Ask the assistant to add a moodboard section next to the brief from the references the client approved, or use Storyflow's moodboard workflow (moodboard from a brief shows the result). A photo you attach in the chat does not reach Storyflow by itself; the connector gives you an upload link for the board instead. Now the creative team reads the proposition and sees the look in one place. Our guide to turning a brief into a moodboard with AI covers this step in depth.

Step 10: Brief it back and get one written yes

Share the board link with the client. They open it with no account, and they sign in to comment. Walk the open items on a call, update the board while you talk (or paste the client's comments into the chat and ask the assistant to apply them; the connector does not read comment threads itself), then ask the named approver for a written yes by email. Storyflow has no approve button, so the email is your approval record. Paste the date of that email into the brief's timeline table.

Where to Keep the Brief: Five Options Ranked for ChatGPT and Claude

Every tool here can hold a campaign brief. The ranking is for the specific job of a brief that an assistant drafts, a client reads, and a team turns into a campaign.

1. Storyflow

Verdict: the only option here where the assistant writes the brief and the plan it drives onto one board, then reads that board back to revise it.

Best for: freelancers, small agencies and in-house brand teams whose briefs turn into moodboards, deliverables tables and timelines.

Pricing: Plus $7.99 a month billed annually ($9.99 monthly), Pro $14 annual ($19 monthly) with AI image generation, Max $39 annual ($49 monthly) with a team workspace, roles and permissions. Paid-only during early access; a Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now. See Storyflow pricing.

Storyflow is a visual project planning workspace for creative work: an infinite canvas that holds notes, documents, tables, images, moodboards, mind maps, kanban, charts and slide decks. Its MCP server, launched in October 2026, lets ChatGPT, Claude, Gemini, Grok and any assistant that adds a remote MCP server read boards and documents and build on them: documents, notes, tables, charts, slide decks and colour palettes, placed where they belong on the board. The connector runs on your assistant's own model, so it does not spend Storyflow AI credits, and Plus, Pro and Max have no MCP action limit. Inside the app, Storyflow's own AI agent has a campaign brief workflow that reads the board plus up to 5 attached documents and 3 other boards, and builds the brief in sections with unknowns marked.

• Strengths: brief, moodboard, deliverables, budget and timeline on one board; the assistant reads the current version back before revising; view link opens with no account; invited collaborators edit in real time.
• Limitations: no suggesting mode or versioned approvals; browser only, no offline mode; no free plan during early access.

2. Google Docs

Verdict: the best home for a brief that will be redlined line by line, and now reachable from both assistants.

Best for: clients with legal, brand or procurement teams who review in suggesting mode.

Pricing: anyone with a Google account can create in Docs. Gemini in Docs is not in Business Starter; it starts at Business Standard on Google Workspace pricing.

Claude's Google Docs connector creates new Docs and reads comments and suggestions, and ChatGPT's Google Drive app can create and update files when your Google permissions and workspace allow it. That closes most of the copy-paste gap. What Docs cannot do is hold the moodboard and the plan beside the brief in a way the team works from; those live in other files.

• Strengths: suggesting mode, comment threads, version history, universal client familiarity.
• Limitations: the brief is linear text; visuals and plans sit elsewhere; the assistant edits a document, not a project.

3. Notion

Verdict: the strongest connector of the document tools, and the right answer when the client already runs on Notion.

Best for: in-house teams and agencies embedded in a client's Notion workspace.

Pricing: Free; Plus $10 per member a month billed yearly ($12 monthly); Business $20 per member yearly ($24 monthly), which adds Notion Agent. See Notion pricing.

Notion MCP lets an assistant read, create and update pages and databases, and Notion's help lists Claude and ChatGPT among the clients. Claude's Notion connector includes creating pages, updating pages and adding comments. For a brief, that means the assistant can write it as a page and track deliverables in a database. Per-member pricing adds up for a team of four, and a Notion page is still a document first.

• Strengths: mature MCP, databases for deliverables, client teams often already there.
• Limitations: per-member pricing; visual direction sits awkwardly in a page; MCP tools act with your full Notion permissions.

4. Canva

Verdict: the best finish for a brief-back presentation, weaker as the working brief.

Best for: agencies who present the brief back as a designed deck.

Pricing: Canva has a Free plan, Pro for one person and Business priced per person. Its pricing page did not load for us on October 9, 2026, so confirm today's price for your country there.

Canva's AI Connector works with ChatGPT, Claude, Gemini, Grok and others, and lets the assistant search, create and edit designs. Claude's Canva connector adds autofill, export and comment threads. That makes Canva strong for turning a finished brief into a polished brief-back. It is a design tool, so the brief's tables and open items are harder to keep current there than in a doc or a board.

• Strengths: best-looking output, brand templates, wide assistant support.
• Limitations: brief fields become design elements; revising a deliverables table is fiddly; per-person Business pricing.

5. Milanote

Verdict: a good visual board for creative direction, but your assistant cannot reach it.

Best for: designers who build visual direction by hand and paste the brief in.

Pricing: Free with up to 100 notes, images or links and 10 file uploads; $9.99 a month billed annually per person; Team $49 a month billed annually. See Milanote plans.

Milanote's plans page lists no AI features and we found no ChatGPT or Claude connector. You can still write the brief in the chat and paste it onto a Milanote board next to images. Every revision is another paste.

• Strengths: clean visual boards, a real free tier.
• Limitations: no AI, no assistant connector, manual sync between chat and board.

Interview Prompts You Can Copy

The prompts below are written for ChatGPT or Claude. Paste them in order. Replace the bracketed parts. They work without any connector; the board prompts need Storyflow connected.

The interview prompts

The drafting prompts

The board prompts (Storyflow connected)

Worked Example: A Six-Shop Bakery's Subscription Launch

This example is a composite built for this guide, not a real client. The numbers are chosen to show the arithmetic a brief should carry.

The input the client sent

The client, a six-shop bakery we will call Hearth and Rye, sent a three-line email: they want to "launch the sourdough subscription properly this spring", they "have about 30k", and their head of marketing wants "lots of short video". Attached: last spring's in-store promotion results and a 14-page brand book.

What the interview recovered

The assistant read the material and could answer 4 of 12 fields from it (business problem, tone, mandatories from the brand book, and part of the audience from last year's results). It then asked 14 questions over 22 minutes. Three answers changed the brief:

• The objective became "400 paid subscriptions by May 17", because the bakery's break-even on the subscription bakehouse shift is 350 subscribers.
• The "about 30k" turned out to be $27,500 in total: $18,000 media and $9,500 production. The agency fee sits outside it.
• The insight came from one question about what customers do instead: regulars already reserve loaves by phone on Fridays, and 1 in 5 calls is a customer whose usual loaf sold out.

The KPI arithmetic

$18,000 of media divided by 400 subscriptions sets the ceiling at $45 per subscription. The brief states it as "cost per paid subscription of $45 or less, measured in the subscription checkout, reported weekly". The assistant flagged that the client had no baseline cost per acquisition, so the brief carries "[Confirm with client: last year's cost per in-store sign-up]".

The proposition, and the four that lost

The five candidates were "Your loaf, held for you every Friday", "Never miss the sourdough again", "Sourdough, delivered weekly", "The bakery's best, reserved" and "Fresh bread and a better week". The assistant struck the last for its "and", the third because a supermarket could say it, and the fourth because "best" is a claim the audience does not believe. "Never miss the sourdough again" lost to "Your loaf, held for you every Friday" because the winning line describes the mechanic and the insight in one sentence.

The deliverables and timeline

What the assistant got wrong, and what caught it

Two mistakes reached the first draft. The assistant wrote "launch April 1" because the client's email said "early April"; the open-items note caught it, and the client confirmed April 6 after Easter. It also listed "Instagram and TikTok" as channels although the client had never mentioned TikTok; the red-flag check flagged the channel as unsourced. Both mistakes were visible because the brief lived on a board the assistant re-read, with every unconfirmed fact in one note.

How it looked on the board

On Storyflow, the board held five sections: the brief document, the open items note, the deliverables and timeline tables, the moodboard with 12 approved references, and the budget table. The client opened the link with no account on the morning of the brief-back, signed in to leave four comments, and approved by email the same afternoon. The production team then built the shot list on the next board over. Our guide to turning a client brief into a production plan picks up from there.

ChatGPT or Claude: Which Assistant Writes the Better Brief

Both are capable of the interview and the draft. The differences that matter for briefs are practical, not about writing quality.

Where Claude has the edge for briefs

Claude allows one custom connector on its Free plan, so you can connect Storyflow without paying for Claude, and its Google Docs connector creates Docs directly. Claude Pro is $17 a month billed annually or $20 monthly. Its Docs connector also reads comments and suggestions, so it can pick up a client's redlines when you revise.

Where ChatGPT has the edge for briefs

ChatGPT's projects keep a client's material and past chats together, which helps when you brief the same client every quarter. Its Google Drive app can update an existing Doc where permissions allow. Adding Storyflow needs ChatGPT Plus or above with developer mode switched on; see ChatGPT's plans.

The practical answer

Use whichever assistant you already pay for. The brief's quality comes from the interview, the "never invent" rule and the red-flag check, not from the model. The bigger decision is where the brief lives afterwards.

What It Costs: A Freelancer vs an Agency of Four

Monthly figures, billed annually where the vendor offers it, as of October 2026. The assistant line assumes Claude Pro; ChatGPT pricing is on OpenAI's page.

What the table hides

The real cost is revision time. A brief that lives in the chat costs you a copy-paste on every change, and a brief separated from its plan costs you a missed update on every scope change. Price the hours, not just the seats.

The free path that exists today

If a paid Storyflow member invites a client or collaborator to a board, that person joins free and can edit, and a free account gets 25 connector actions a week from their own assistant. That is enough for a client to read the brief and ask their assistant about it.

Decision Rules: Where the Brief Should Live

Your brief turns into a moodboard, deliverables and a timeline

Use Storyflow. Keep the brief, the visual direction and the plan on one board, and let the assistant revise all three from one read. Agencies running several clients at once can see the setup on the agency campaign planning page.

The client's legal or brand team redlines every line

Use Google Docs with suggesting mode. Draft it with Claude's Docs connector or ChatGPT's Drive app, and move the approved version onto your planning board afterwards.

The client already runs everything in Notion

Write the brief as a Notion page through Notion MCP so it sits where the client works, and keep your production planning wherever your team already works.

The brief-back is a pitch moment

Write the brief in Storyflow or Docs, then have the assistant build the presentation in Canva, or build slide decks on the Storyflow board and present it fullscreen. Our guide to how agencies present campaign concepts covers the order of slides.

You are a solo designer who builds direction by hand

Milanote's free tier holds a small visual board; write the brief in the chat and paste it in.

Common Mistakes When You Let an Assistant Write the Brief

Mistake 1: One prompt, one brief

"Write a campaign brief for a bakery subscription" produces a generic brief because it has nothing else to go on. Fix: interview first, draft second.

Mistake 2: Letting it fill the budget

An assistant will write "$50,000 budget across paid social and influencers" without blinking. Fix: the never-invent rule in the first prompt, and "[Confirm with client]" for every unsourced number.

Mistake 3: Three objectives

Assistants love balanced lists: awareness, consideration and conversion. Fix: force one primary objective and list the others as "not measured in this campaign".

Mistake 4: A proposition with "and"

"Fresh bread and a better week" is two ideas. Fix: generate five, ban "and", argue against each.

Mistake 5: Deliverables in prose

"A suite of social assets" means nothing to the editor. Fix: one table row per asset with format, ratio, length, versions and revision rounds.

Mistake 6: The brief stays in the chat

The client cannot see it and the assistant forgets which version was agreed. Fix: write it to a board or a doc the assistant can read back, and treat that copy as the only copy.

When Storyflow Is Not the Right Choice

Storyflow ranks first here for one job: a brief an assistant drafts that turns into a visual campaign plan. For other jobs, pick something else.

You need formal redlines and versioned approvals

Storyflow has comments but no suggesting mode, no approve button and no versioned approval record. If the client's legal team must sign off each clause, use Google Docs, or a proofing tool built for approvals.

You need a free tool today

Storyflow is paid-only during early access; its Free plan launches before the end of 2026. Google Docs, Notion Free, Canva Free and Milanote's free tier all work today.

You need the brief offline or on a phone app

Storyflow runs in the browser only, with no offline mode and no native mobile or desktop app.

You need the brief to drive scheduling or invoicing

Storyflow does not publish or schedule social posts, and does not do invoicing or contracts. If the brief must flow into a scheduler or a billing system, keep the brief where that system can read it.

Campaign Brief Template You Can Paste Into Your Assistant

Paste this table into ChatGPT or Claude with the rules prompt above, and ask it to fill it from your material and interview. On Storyflow, ask it to write this as a document and the last three rows as tables. Prefer a ready-made board? Start from the campaign brief template or the creative brief template.

The Bottom Line

ChatGPT and Claude are good at writing campaign briefs once you stop asking them to write and start asking them to interview. The rules that make the brief trustworthy are simple: one objective with a number and a date, one proposition with no "and", every unknown marked rather than filled, one named approver. The decision that saves the most time is where the brief lives after the chat ends. For a brief that turns into a moodboard, a deliverables list and a timeline, write it onto a Storyflow board through the connector, so the assistant can read back exactly what the client is looking at. If your clients redline every clause, draft in Google Docs instead. Start by connecting Storyflow to the assistant you already use on the MCP page, then run the interview prompts on your next client email.