How to Map a Marketing Campaign With ChatGPT or Claude (2026): A Simple 7-Layer Map on One Board

Key Takeaways

• Storyflow is the simple AI tool we recommend for mapping a marketing campaign with ChatGPT or Claude: its MCP connector lets the assistant build the map as a mind map plus sections of notes and tables on one board, read it back, and revise it after your team edits it.
• A campaign map has seven layers: objective, audience, message, channels, moments, assets and measurement. The first five are the argument; the last two are what you make and how you know it worked.
• Use two shapes, not one. A mind map holds labels of three to eight words, which is right for the overview and wrong for a budget. Sections with notes and tables hold the detail.
• The most useful prompt comes after the build: ask the assistant to read the board and list every asset that does not trace back to a message, an audience and the objective. Those are the assets to cut.
• Never let the assistant invent dates, budgets or baselines. Have it write visible slots such as "[set date]" and "[baseline needed]" and list them as open items.
• In the illustrative example below, the whole map takes about 15 connector actions. An invited free Storyflow account gets 25 a week; Plus, Pro and Max have no connector limit.
• Miro, Whimsical, Notion and Canva all connect to Claude today. Each is the better pick for one specific situation, named in the reviews and the decision rules.

Why a Campaign Map Made in a Chat Does Not Stay a Map

You have probably done this already. You described a campaign to ChatGPT or Claude, got back a tidy outline with headings for audience, channels and KPIs, felt organized for an afternoon, and then never opened that conversation again. The outline was fine. The container was the problem.

An outline is a list, and a campaign is a set of connections

What makes a campaign coherent is the lines between things: this asset carries that message to that audience in service of that objective. A chat reply flattens those lines into nested bullets. You can read each bullet, but you cannot see that the influencer kit points at no message at all, or that two of your five channels reach the same 400 people.

A map on a canvas keeps the connections visible. The layers sit next to each other, and the gap where a connection should be is something you can point at in a meeting.

The chat scrolls, and the third revision buries the first

By the tenth message there are four versions of the audience definition in the transcript, and the current one is whichever you remember agreeing to. Nobody else can tell. A board has one current state. When the assistant revises the audience section on the board, the old text is replaced, and the board is the version.

Nobody else can open your conversation

Your designer, your paid media freelancer and your client do not have your ChatGPT history. Pasting the outline into a document fixes the access and loses the assistant: the next revision means pasting again. The point of a connector is that the assistant and the team work on the same object. Storyflow's connector, described on the MCP page, gives the assistant tools to build on a board and to read what is there, including what your team changed.

The assistant fills silence with plausible numbers

Ask for a campaign plan with no budget and you will get one with a budget. It will look reasonable and nobody agreed to it. A map that gets shared carries more authority than a chat reply, so the rule tightens: anything the assistant was not given is written as a visible slot, not as a guess. Every prompt in this guide enforces that.

The Seven Layers of a Campaign Map

Our existing guide to what a campaign map is uses five layers. Working inside an assistant, we add two, because they are the two an assistant most reliably skips or invents: moments (when things land) and measurement (how you will know). The test for the whole map is traceability. Every asset traces to a message, every message to an audience, every audience to the objective. Anything that cannot make the trip gets cut.

Layer 1: The objective is one sentence with one number and one date

"Grow awareness of the new line" cannot be mapped, because nothing can be traced to it or cut against it. "Book 180 home trials between April 6 and May 17" can. If the assistant offers three objectives, ask it which one the other two serve and keep that one. The other two usually turn out to be diagnostics that belong in layer 7.

Layer 2: The audience is a belief, not a demographic

"Urban professionals aged 28 to 45" tells a media buyer where to point the spend and tells a writer nothing. Add what the segment believes today and what stops them acting. "Commuters within five miles of a store who think an e-bike is a toy for people who already cycle" gives the message layer something to change.

Keep it to three segments at most. An assistant will happily produce six personas with names and hobbies. Six audiences on a small budget means six thin campaigns.

Layer 3: The message is the belief you want them to leave with

Write one core message as a sentence a customer could repeat, then two or three proof points that make it credible. The message is not the tagline. The tagline comes later and belongs to the creative team. If your message contains the word "and", it is two messages, and the map will show you that when half the assets trace to one half.

Layer 4: Each channel gets a job

A channel on the map without a job is a habit. For each channel, write what it is there to do (reach new people, prove the claim, convert the interested, remind the undecided), which segment it reaches, and what share of the budget it gets. Two channels with the same job and the same segment is a prompt to cut one.

Layer 5: Moments are the layer assistants skip

A campaign has a shape in time: a first beat, a peak, a reminder, a close. Without that layer, the map is a diagram of a campaign that never starts. Moments are dated beats, each with the message emphasis and the channels that carry it. On Storyflow they live in a table with a date cell per row. Storyflow has no calendar, and its tables do not sort, so tell the assistant to write the rows in date order and keep them that way.

Layer 6: Assets are where the map earns its keep

List every asset with five things: format, channel, the message or proof point it carries, owner, and due date. The "message it carries" column is the one that matters. An asset with nothing in that column is either missing its purpose or should not exist. In practice a first asset list from an assistant is long, because assets are cheap to list and expensive to make.

Layer 7: Measurement is decided before launch, with baselines

Pick one primary KPI that restates the objective, then two to four diagnostics that explain it (visits, booking rate, cost per booking). For each, record the baseline, the target and where the number comes from. If you do not know a baseline, the cell says "[baseline needed]" and someone owns finding it. An assistant asked for "KPIs" will list eight. A map with eight KPIs has none.

Mind Map, Orbit or Sections: Which Shape for Which Layer

"Map" makes people reach for a mind map, and a mind map is half the answer. The shapes hold different amounts of text, and choosing the wrong one is the commonest reason an AI-built campaign map looks impressive and is useless.

The mind map is for the overview

Storyflow's mind map tool builds a whole map in one call: a central topic, branches and sub-branches, laid out and coloured by the tool with the connecting lines drawn. Each node takes a label of three to eight words. That constraint is useful. "Commuters who think e-bikes are toys" fits. A paragraph about the segment does not, and should not be on the overview.

One limit to plan around: the connector builds a mind map whole and has no tool for growing an existing one. It can edit elements already on the board, but a new branch is something you add by hand on the board, or the assistant builds a fresh map and you remove the old one. So settle the tree in the chat first, then build once.

Sections are for the work

The detail lives in sections. Through the connector, the assistant builds each section in one call: a wall with a heading and every card inside it, top to bottom, in the order you give. A card can be a note, a table, a document, a checklist or a ticket. Seven layers means seven sections, asked for in layer order so the board reads like the argument.

The orbit is optional, and good for the message

An orbit is one ring of things around a centre. It suits the message layer when you have material: the core message in the middle, with proof points, a customer quote you were given, two reference images and a competitor link around it. If you have no material yet, skip it. An orbit of six notes that repeat the mind map adds nothing.

What the built-in agent does differently

Inside the Storyflow app there is also a built-in AI agent with a marketing plan workflow. It lays out a fuller execution plan in eight sections (campaign background, goals and deliverables, concepts, timeline, budget, next steps, task tracking, and team and responsibilities), and it is written to leave dates and money as visible slots when you gave none. Use the connector route in this guide when your thinking is already happening in ChatGPT or Claude. Use the built-in agent when you are already on the board. Both produce ordinary board elements you can edit by hand.

How We Chose the Tool for This Job

The question is narrow: a simple AI tool for mapping out a marketing campaign, used by someone who already plans in ChatGPT or Claude. That is a different job from running a workshop, managing tasks or designing a deck, so the criteria are specific to it.

The five criteria and their weights

Scores are our judgment out of 10, based on each vendor's own documentation as of October 2026, linked in the reviews. The weights are published so you can re-weight them: if your team will never use ChatGPT, or if a free plan matters more to you than shape, the order can change.

Why "builds the map from the chat" carries the most weight

Every tool here can hold a campaign map you draw yourself. The request was for an AI tool, and in 2026 the AI most marketers already use is ChatGPT or Claude. A tool whose own AI button builds a map is useful, but it starts from zero context. The assistant you have been talking to for an hour already knows the product, the audience and the constraint you mentioned in passing.

What we did not weigh

We did not score execution features: task assignment, approvals, publishing, reporting dashboards. Mapping comes before those, and a tool that is strong at them is often heavy for a map. We also did not score each tool's built-in AI separately. This guide is about the assistant you already use.

Comparison Table: Simple AI Tools for Mapping a Marketing Campaign With ChatGPT or Claude

How the weighted scores break down:

Storyflow does not score 10 anywhere, and the gaps are specific. It gets a 7 on simplicity because it has no free plan yet and because ChatGPT needs Developer mode switched on before you can add it, where Whimsical is a plugin in ChatGPT's own directory. It gets an 8 on reading back because its connector cannot read comment threads, which Miro's can. It gets an 8 on sharing because it runs in the browser only, with no desktop or mobile app.

How to Map a Marketing Campaign With ChatGPT or Claude, Step by Step

The ten steps below take a campaign from a paragraph in a chat to a map on a board that someone else can open. Steps 1 to 4 happen in the chat. Steps 5 to 8 build the board. Steps 9 and 10 are what make the map worth having.

Step 1: Connect Storyflow to your assistant (once)

In Claude, open Customize, then Connectors, then Add, then Add custom connector. Name it Storyflow, paste the address https://mcp.storyflow.so/mcp, continue, and sign in to Storyflow. Claude's Free plan allows one custom connector, per Claude's help article on custom connectors.

In ChatGPT on the web, you need ChatGPT Plus or above with Developer mode. Turn Developer mode on under Settings, then Security and login. Then go to chatgpt.com/plugins, press the plus button, name the connector Storyflow, paste the same address and sign in.

At sign-in you choose which projects the assistant may reach and whether it may make changes. For a first run, pick one project and allow changes. The full walkthrough is in the help article on connecting AI assistants, with assistant-specific guides for ChatGPT and Claude.

Step 2: Give the assistant the real inputs

Before any mapping, paste what actually exists: the product, the price, the budget if there is one, the dates if they are fixed, last campaign's numbers if you have them, and anything the client or founder has said out loud about what they want. Then add one instruction: use only these facts, and mark anything missing as a slot in square brackets.

Five true sentences beat a page of background. The assistant maps what it is given, and what it is not given it either marks or invents. You decide which with that one instruction.

Step 3: Let it interview you, one layer at a time

Ask the assistant to question you layer by layer, objective first, and to move on only when a layer passes its test (one number and one date for the objective, a current belief for each audience). Expect roughly ten to twenty minutes of typing. It is the difference between your campaign and a generic one. If the campaign starts from a client document, do the campaign brief first and map from that.

Step 4: Agree the tree in the chat before anything is built

Ask for the map as an indented outline in the chat: the campaign name at the centre, seven branches, and no more than five sub-branches each, every label three to eight words. Read it. Fix it there. Building is one call, and a rebuilt map arrives as a second map beside the first, so the cheap place to argue about the tree is the chat.

Step 5: Build the overview mind map

Now ask the assistant to build that tree as a mind map on your board, and to show you the board while it works. In clients that support it, the live board appears in the chat and updates as elements land. On an open Storyflow tab, the map appears live as well.

Look at it for thirty seconds before going further. If a branch is wrong, you will see it faster here than in an outline.

Step 6: Build the seven sections

Ask for one section per layer, to the right of the mind map, in layer order. Be explicit about the shape of each: notes for objective, audience and message; tables for channels, moments, assets and measurement, with the columns named. The template later in this guide has the columns. Asking for the columns by name is what stops the assistant choosing its own.

Step 7: Put the dated beats in the moments table

Give the assistant the fixed dates and have it propose the beats in between, written as rows in date order: date, moment, message emphasis, channels, owner. Where a date is not set, the cell reads "[set date]". Check the gaps. Three weeks with no beat is either a deliberate quiet period or a hole.

Step 8: Run the traceability audit

This is the prompt that justifies the whole exercise. Ask the assistant to read the board and report three lists: assets that carry no message, messages or proof points that no asset carries, and channels with no asset or no stated job. Then ask it what it would cut if the budget dropped by a third.

It is reading the real board here, not its memory of what it wrote, so the audit also catches what you changed by hand.

Step 9: Add measurement with baselines, and a chart only when you have numbers

Build the measurement table with five columns: metric, role (primary or diagnostic), baseline, target, source. Fill baselines from numbers you paste. Leave the rest as "[baseline needed]" with an owner. The assistant can also add a chart to the board, and it should only do that from numbers you supplied, such as last campaign's weekly bookings. Storyflow does not pull data from ad platforms or analytics.

Step 10: Share it, then let the assistant read what changed

Share the board with a view-only link. The client or stakeholder opens it with no account, and signs in if they want to comment. Teammates you invite can edit the board directly.

A week later, ask the assistant what changed on the board in the last week and who changed it. The connector reads changes over fixed windows (the last day, the last week or the last month). Then ask it to re-run the traceability audit against the board as it stands. It cannot read comment threads, so paste any comments you want it to act on into the chat.

The Five Tools, Placed for This Job

Each tool below is placed for one job only: mapping a marketing campaign from a conversation in ChatGPT or Claude. All vendor facts were checked on the vendor's own pages in October 2026 and are linked.

1. Storyflow

The verdict: the simple route from a campaign described in a chat to a map your team can work from.

Best for: marketers, founders and small agencies who think in ChatGPT or Claude and need the result to become the plan.

Pricing: Plus is $7.99 a month billed annually ($9.99 monthly), Pro $14 ($19 monthly) and Max $39 ($49 monthly), all flat prices with no per-seat charge, listed on the pricing page. Storyflow is paid-only during early access. Its Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now.

Why it ranks first here: Storyflow is a visual project planning workspace for creative work, and its connector exposes the shapes a campaign map needs as single calls. One call builds a whole mind map. One call builds a section with every card in it. Tables carry date cells for the moments layer. The same board then takes the things a map turns into: a moodboard, a content plan, a slide deck for the pitch. The assistant reads the board back, so the map can be audited and revised in place instead of regenerated.

Strengths:

• Mind map, sections, tables, charts, diagrams, documents and slide decks on one board, all buildable from the chat
• Works with any assistant that can add a remote MCP server, including ChatGPT, Claude, Gemini and Grok
• The connector runs on your assistant's model, so it does not spend Storyflow AI credits
• A view-only link opens with no account
• Flat pricing: adding a collaborator to a board does not add a seat charge

Limitations:

• Paid-only during early access, with no free plan yet
• The connector cannot read comment threads and cannot generate images
• It adds and edits; removing elements from a board is done by you
• No calendar, no table sorting, no desktop or mobile app, no offline mode
• It does not publish posts, pull performance data or run formal approvals

2. Miro

The verdict: the right answer when the map is going to be built or reviewed in a live workshop, and your team is already in Miro.

Best for: marketing teams of five or more who run planning sessions on Miro boards.

Pricing: Free with 3 editable boards; Starter $8 per member a month and Business $20 per member a month, both billed yearly, per Miro's pricing page.

Why it ranks second: Miro's connector is well documented and generous. Miro's MCP documentation says the server "works for all Miro plans, even free teams" and lists Claude and ChatGPT among supported clients. Its tool list covers diagrams, documents, tables that switch between table, kanban and timeline views, and reading, replying to and resolving comments. That last one is a real advantage over Storyflow for review rounds.

It ranks below Storyflow for this job on two counts. Its documented diagram types are flowcharts, ERDs and UML diagrams, and its tool documentation does not name a mind map tool, so the overview is assembled from shapes. And in our view a Miro board is a workshop surface first: strong for the session, less natural as the place the campaign's references, plan and pitch deck later live.

Strengths:

• Connector available on every plan, including Free
• Reads and resolves comment threads
• Tables with timeline and kanban views
• A free plan you can start on today

Limitations:

• Daily tool-call limits by plan: 100 on Free, 500 on Starter, 2,000 on Business
• Per-member pricing, so cost grows with the team
• No mind map tool named in the connector documentation

3. Whimsical

The verdict: the simplest setup of the five, and a good pick when your campaign map is really a mind map plus a customer flow.

Best for: solo marketers and product marketers who want a clean mind map or flowchart from a prompt.

Pricing: Free with monthly caps (50 board objects and 50 doc blocks a month); Pro $10 and Business $20 per editor a month billed annually, per Whimsical's pricing page.

Why it ranks third: Whimsical's MCP page says your AI can "create mind maps, wireframe outlines, and planning documents directly in Whimsical", and can search and read your files. It is a verified connector in Claude's directory and a plugin in ChatGPT, which means no Developer mode step. That is why it scores highest on simplicity.

It ranks below Storyflow and Miro because the campaign map needs tables for channels, moments, assets and measurement, and Whimsical's MCP page does not list tables or date fields among what the assistant builds. The Free plan's cap of 50 board objects a month may also be tight for this job. A seven-branch mind map with five sub-branches each is 43 nodes, so if each node counts as an object, one map uses most of a month.

Strengths:

• Mind maps created directly by the assistant
• Directory connector in Claude and plugin in ChatGPT
• Flowcharts and sequence diagrams for the customer path

Limitations:

• No tables or dated rows listed among the connector's capabilities
• Free plan capped at 50 board objects a month, with a watermark on exports
• Per-editor pricing

4. Notion

The verdict: choose it when the map has to become a database the team filters and assigns from, and nobody needs to see it as a picture.

Best for: teams whose briefs, tasks and wikis already live in Notion.

Pricing: Free plan available; Plus $10 per member a month billed annually ($12 monthly) and Business $20 ($24 monthly), per Notion's pricing page.

Why it ranks fourth: Notion's connector is strong at what Notion is. Its supported tools create pages, databases and database views including board, timeline and calendar, and they read and write comments. Notion's help page names Claude, Cursor and ChatGPT as supported. For the assets and moments layers, a Notion database is arguably better than a table on a canvas: it filters, sorts and has a calendar.

It ranks fourth because none of those tools creates a canvas or a mind map. What you get is a well-structured page, which is an outline again. The connections between layers become relation properties you have to click through, not lines you can see.

Strengths:

• Databases with sorting, filtering, timeline and calendar views
• Reads and writes comments
• Many teams already have it

Limitations:

• No canvas or mind map tool in the connector
• Some search and query features need a Business or Enterprise plan, per Notion's tool documentation
• Per-member pricing

5. Canva

The verdict: the pick when the deliverable is a good-looking one-page campaign overview for a slide or a wall, not a working plan.

Best for: marketers who need the map to look designed for a leadership update.

Pricing: see Canva's pricing page for current plans and prices.

Why it ranks fifth: Canva's connector listing for Claude shows a connector made by Canva and verified by Anthropic, with 17 tools that search, generate, import and export designs. For a finished graphic, that is the shortest path of the five. For a campaign map it is the weakest fit, because a design is a picture of a plan. The asset table inside it is not a table the assistant can read row by row and audit, and the next revision is a new design.

Strengths:

• Polished, designed output
• Export to common formats
• Widely known by non-designers

Limitations:

• A design, not a structured plan
• No mind map or table structure the assistant can audit
• We verified the Claude connector only; check Canva's own help pages for ChatGPT

Worked Example: A Three-Store Bike Shop's E-Bike Trial Campaign

What follows is an illustrative example. The shop, the numbers and the counts are invented to show the method, and none of it is a measured result.

Northbank Cycles is a three-store bike shop. It wants to sell commuter e-bikes to people who do not think of themselves as cyclists, using a free 48-hour home trial. It has $12,000 and six weeks, April 6 to May 17. The marketing lead works in Claude and has Storyflow connected.

The inputs we gave the assistant

We pasted six facts: the average e-bike sale is $2,400; the budget is $12,000; the dates are fixed; last spring's in-store test rides converted to sales at about one in four; the booking page converts 6% of visitors; and the email list has 4,100 local subscribers. We told the assistant to use only those facts and to bracket anything else.

The objective arithmetic

The owner's first objective was "get the word out about e-bikes". The interview turned it into a number by working backwards.

The objective on the board became: "Book 180 home trials between April 6 and May 17, to sell 45 commuter e-bikes." The 3,000 visits went to the measurement layer as a diagnostic, not into the objective.

The map the assistant built

Note the bracket in the message row. The "same time as driving" proof point was something the assistant offered, not something we gave it, so the instruction from step 2 made it a slot. Someone has to test three real routes before that line appears in an ad.

The budget split across channels

The budget was ours, so the assistant split it and we adjusted. The paid channels total $7,200. To bring 2,000 of the 3,000 visits, they have to average $3.60 a visit, and the remaining 1,000 have to come from the email list, the ambassadors and in-store QR codes. That $3.60 is a requirement the map exposes, not a forecast. If the first week comes in at $6, the map tells you which number breaks.

The five moments

The first draft had nothing between April 17 and May 8. Three weeks of silence in a six-week campaign was a hole, and the April 27 beat was added to fill it.

What the audit cut

The traceability audit reported four assets with no message: a general brand video, a "meet the mechanics" reel, a tote bag and a spring service discount flyer. Each was a reasonable idea and none of them told a car commuter to try their commute for 48 hours. All four were cut, taking the list from 22 to 18.

It also reported the opposite problem. The proof point "the bike is delivered" had no asset carrying it. One paid social variant was rewritten around delivery. That gap would not have been visible in an outline.

What the build cost in connector actions

Every read and every change through the connector counts as one action. In this illustrative run the count was about 15: two to find the project and board, one to show the board, one for the mind map, seven for the sections, one to read the board for the audit, and three edits afterwards. An invited free account gets 25 actions a week, so a map like this fits with room to revise. On Plus, Pro and Max there is no connector limit.

Prompts You Can Copy

Replace the bracketed parts. The prompts assume Storyflow is connected and that you have a project for the campaign. They are written to be pasted one at a time, in order.

The mapping prompts (in the chat, before anything is built)

The build prompts (Storyflow connected)

The audit and revision prompts

Two notes on the prompts. "Do not change anything yet" matters in the audit: you want the lists before the edits, so the cuts are your decision. And the last prompt is where a map becomes a pitch. The fuller method for that is in our guide to presenting a campaign concept built with ChatGPT or Claude.

ChatGPT or Claude: Which Assistant to Map With

Both work, and the Storyflow connector gives both the same tools. The differences are in setup and plan, not in the map you end up with.

Claude is the simpler start

Claude allows one custom connector on its Free plan, so you can connect Storyflow and build a map without paying Anthropic anything. Claude's pricing page lists Pro at $17 a month on an annual subscription or $20 monthly, which raises usage limits. Adding the connector is a settings screen and a sign-in.

ChatGPT works once Developer mode is on

ChatGPT needs Plus or above with Developer mode. After that the connector behaves the same way. If your campaign thinking already lives in ChatGPT, with projects and past conversations about the brand, that context is worth more than a simpler setup. Stay where the thinking is.

The practical answer

Map in the assistant that already knows the campaign. If you are starting cold and have no paid assistant plan, start in Claude. A longer comparison for planning work is in Claude vs ChatGPT for creative project planning.

What It Costs: A Solo Marketer vs a Team of Five

Prices are the vendors' published annual-billing rates in October 2026. The assistant's own subscription is separate and the same in every row, so it is left out.

What the table hides

Miro, Whimsical and Notion each have a free plan you can start on today, and Storyflow does not. If the test is "can one person try this for nothing this afternoon", Miro's Free plan with 3 editable boards and its connector included is the honest answer.

The table also hides connector limits. Miro caps tool calls per day by plan. Storyflow caps an invited free account at 25 actions a week and puts no connector limit on paid plans. Neither cap is likely to matter for a single map; both matter if the assistant is reading and revising boards every day.

The free path that exists on Storyflow today

One person on a paid plan can invite the rest of the team to the campaign board, and those people join free. An invited free account can also connect an assistant, within 25 actions a week. For a small team with one planner and several contributors, that makes the real cost one Plus subscription.

Decision Rules: Which Tool for Which Situation

You plan in ChatGPT or Claude and need the map to become the plan

Use Storyflow. The map, the references, the content plan and the pitch deck end up on one board the assistant can read. This is the situation the tool is built for.

Your team maps campaigns in a live workshop

Use Miro. If eight people are going to argue about the audience on a call with sticky notes, that is Miro's home ground, and its connector reads the comments afterwards.

The map is a mind map and a customer flow, and that is all

Use Whimsical. It is the fastest setup, and it builds mind maps and flowcharts well. Move to something with tables when you need dates and owners.

Everything else already lives in Notion

Use Notion for the assets and moments databases, and accept that the overview is a page. Some teams keep the visual map on a board and the task database in Notion, and that split works if one person owns keeping them in step.

Leadership wants one slide

Use Canva for the slide, built from a map that lives somewhere structured. Do not make the Canva design the source.

You do not need a tool at all

For a two-week campaign on one channel with one audience, write the seven layers as seven lines in a document. A map pays for itself when there are enough channels and assets that you can no longer hold the connections in your head. Our guide to why mind maps break past 100 nodes covers the opposite end of the scale.

Common Mistakes When You Map a Campaign With an Assistant

Mistake 1: Asking for "a campaign map" in one prompt

One prompt gets you the average campaign for your category: three personas, five channels, eight KPIs. It looks finished and contains nothing you decided. The interview in step 3 is slower by fifteen minutes and is the only part that puts your campaign on the board.

Mistake 2: Putting paragraphs in the mind map

A mind map node holds a label. If you ask for audience descriptions as nodes, you get either truncated labels or an unreadable web. Labels in the mind map, paragraphs in the sections.

Mistake 3: Letting the assistant set the budget and the dates

A plausible budget nobody agreed to gets approved by people who assume someone else checked it. Give the number or get a slot. The same goes for launch dates, baselines and any statistic in a proof point.

Mistake 4: Skipping the moments layer

A map without dates cannot be sequenced, and the team will sequence it by whichever asset is finished first. Even three beats (open, peak, close) change how the assets get prioritised.

Mistake 5: Listing assets before the message is settled

Assets are fun to list. If the message changes after the asset table exists, every row needs rechecking, and nobody rechecks. Build the layers in order. The audit exists because this mistake is common.

Mistake 6: Rebuilding instead of revising

When something changes, the instinct is to ask for a new map. A second mind map lands next to the first, and now there are two. Ask the assistant to read the board and change specific rows, and remove outdated elements yourself.

Mistake 7: Treating the map as the plan

The map shows what the campaign is and why each piece exists. It does not assign Tuesday's tasks. From the map, build the working plan: a content calendar, a production schedule, or a launch plan like the one in our guide to planning a product launch with Claude or ChatGPT.

When Storyflow Is Not the Right Choice

Storyflow is our product, and it is the wrong pick in these cases.

You need a free tool today

Storyflow is paid-only during early access, and its Free plan launches before the end of 2026. Unless a paid member invites you to their board, you pay from day one. Miro, Whimsical and Notion all have free plans now.

Your reviewers work in comment threads and you want the assistant to read them

The Storyflow connector does not read comment threads. If the review process is thirty comments on a board that the assistant should triage and answer, Miro's connector does that and Storyflow's does not.

You need the map to drive execution on its own

Storyflow does not publish or schedule posts, does not pull performance data, has no calendar and does not sort tables. Dates live in table cells and tickets. If you need a campaign calendar that reschedules itself or a dashboard fed by ad platforms, you need a marketing or project management system next to the map.

You need formal sign-off

There is no approve button and no versioned approval trail. For regulated categories or clients who require recorded sign-off on every asset, use a proofing tool for that step.

You work offline or mostly on a phone

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

Your organisation restricts custom connectors

Adding Storyflow to ChatGPT uses Developer mode, and adding it to Claude uses a custom connector. If your IT policy only allows connectors from an approved directory, check before you plan around it. Our guide to connector permissions and safety covers what to ask.

Campaign Map Template You Can Paste Into Your Assistant

Paste the table below into ChatGPT or Claude with the instruction "Fill this for my campaign using only what I have told you; leave unknowns as bracketed slots", then run the build prompts.

How to size the map

For a campaign with a budget under about $20,000, a healthy map is small: one objective, two audiences, one message with three proof points, three to five channels, four to six moments, and fifteen to twenty-five assets. Those figures are a rule of thumb from the layers' own tests, not a benchmark. If your map is much larger, the audit will usually find the excess.

Where to start if you would rather not use a connector

You can build the same seven layers by hand, or with Storyflow's built-in agent, starting from the AI marketing campaign planner or the AI mind map generator. The method in our tool-agnostic guide to mapping a marketing campaign applies unchanged.

The Bottom Line

A campaign map is seven layers and the lines between them, and its job is to show you which assets have no reason to exist before you pay to make them. An assistant is good at drafting the layers and bad at keeping them anywhere useful. Put the two together: do the thinking in ChatGPT or Claude, and have the assistant build the map on a board it can read back.

For that job we recommend Storyflow, with the limits stated above: no free plan yet, no comment reading through the connector, and no execution features. If one of those limits is your requirement, Miro is the alternative we would pick first. Either way, run the audit. To set it up, start at the Storyflow MCP page.