The 6 Documents Every Brand Launch Needs in 2026 (Positioning to Launch Week)

Key Takeaways

• Six documents, not one plan. Most launches fail on the asset matrix, which is the only one that connects a deliverable to an owner and a date.
• The two things always late are legal clearance and the website. Both have dependencies outside the marketing team, which is exactly why they are late, and both need to start at week one rather than week six.
• Lock positioning before you commission anything. Every asset produced against unlocked positioning gets remade, and remaking is where launch budgets go.
• The internal launch precedes the external one. Employees finding out from LinkedIn is the most common and most avoidable launch failure.
• Binet and Field's IPA work puts the long-run brand to short-run activation split at roughly 60:40. A launch plan that is all activation buys a spike and no brand.
• Notion or Airtable for the stack, Miro for the positioning workshop, and a real project tool only once you pass about forty deliverables.
• Launch week is a milestone, not the goal. Budget and staff the eight weeks after it, because that is when the brand is actually built.

Why Brand Launches Slip, and It Is Never the Creative

A brand launch that slipped by three weeks did not slip because the creative was late. It slipped because in week seven somebody asked whether legal had cleared the tagline for use in Germany, and nobody had asked in week one.

Brand launches are dependency problems disguised as creative problems. The creative work is the visible part and the part everyone tracks. The invisible part is a graph of dependencies where a trademark search, a domain purchase, a photography shoot, a website build, a packaging print run and an internal comms cascade all have to converge on one date, and most of them are owned by people who do not attend the marketing standup.

The six documents below exist to make that graph visible. Each one answers a question that, unanswered, becomes a three-week slip.

The Difference Between a Brand Launch and a Product Launch

These get planned identically and should not be.

A product launch introduces a new thing to an audience that already knows who you are. The work is mostly activation: announcement, demand generation, sales enablement, onboarding. The success measure is adoption, and it arrives in weeks.

A brand launch changes who you are, which means every existing asset, surface and habit is now wrong. The work is mostly replacement and re-education, the success measure is recognition and association, and it arrives in quarters.

The practical consequences:

• A brand launch has a migration problem a product launch does not: every business card, email signature, template, invoice, social profile, app icon and packaging SKU carries the old identity.
• A brand launch has an internal audience that matters more than the external one. If your own people cannot explain the new positioning, nobody outside will hear it consistently.
• A brand launch is measured over quarters, so a plan that ends on launch day has planned the wrong thing.

If you are running a product launch, the asset matrix and calendar below still apply; the internal launch pack and the migration audit are lighter.

The Six Documents

1. Storyflow

The verdict: useful for the positioning and territory stage that precedes the six documents, and not a launch tracker.

Best for: the stage where several positioning directions are being held against each other with reference material beside them.

Why it comes first. The work before the launch brief exists is comparative and visual: territories, competitor language, reference brands, and the argument for each. Storyflow's canvas holds images and text together, and its AI reads everything on the current board plus up to one Tactic and up to three documents brought in with an @-mention, so a board holding three territories and the research behind them can be interrogated as a set. Its story blueprints include structures such as AIDA that are useful when the messaging house is being drafted.

Where it loses: there is no dependency model, no critical path, no task assignment, no workload view and no status reporting. On the asset matrix and launch calendar, which are the two documents that decide whether a launch ships on time, it is not competitive with Airtable, Asana or Monday.com, and this article recommends those instead. Storyflow is paid-only during early access; the Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now. Plus is $7.99/mo annual, Pro $14/mo annual, Max $39/mo annual.

Best for in this stack: the positioning and territory work, alongside or instead of Miro.

2. The Launch Brief

Two pages, written first, signed off by whoever controls the budget.

It answers: what is changing and what is not, why now, who this is for, what success looks like at 30, 90 and 180 days, what the budget is, what the immovable date is and why, and who decides when there is disagreement.

That last item is the one that gets left out and the one that costs the most. A launch with three stakeholders and no named decision-maker resolves every disagreement by escalation or by compromise, and compromise in brand work produces the beige middle that nobody chose.

Also name what is explicitly out of scope. A brand launch attracts adjacent projects the way a house move attracts decluttering, and an unbounded scope is the second most common cause of a slipped date.

3. The Messaging House

One page. This is the document every other piece of copy is derived from, and if it does not exist, each writer invents their own version and the launch sounds like six brands.

The standard structure:

• The brand idea at the top. One line. The thing you want to be understood for.
• Three pillars underneath. The three supporting arguments. Three, not five, because nobody remembers five.
• Proof points under each pillar. Facts, features, numbers, credentials. This is the layer that keeps the pillars from being adjectives.
• The boilerplate. The paragraph that appears in every press release and every partner listing, written once so it is not rewritten badly under deadline.
• Words we use and words we do not. The most practically useful section, and the one that survives longest.

Lock this before any copy is commissioned. Every asset written against unlocked messaging gets rewritten, and rewriting is where launch budgets quietly go.

4. The Asset Matrix

A table, and the single most important document in the stack.

One row per deliverable. Columns: asset, channel, format and spec, owner, reviewer, dependency, due date, status, and where the file lives.

This is where a brand launch becomes real, because it is the moment the abstract phrase "refresh our channels" becomes 68 rows and someone realises there is a fortnight of work nobody scoped. A typical mid-size brand launch produces somewhere between 40 and 200 rows.

Build it by walking surfaces rather than by brainstorming assets:

• Owned digital: website pages, app, email templates, transactional emails, social profiles and banners, blog, help centre.
• Owned physical: signage, packaging, print collateral, uniforms, vehicles, stationery, trade stand.
• Sales and service: deck templates, one-pagers, proposal templates, email signatures, call scripts, invoice templates.
• Paid: ad creative per platform and format, landing pages.
• Earned: press kit, boilerplate, executive bios, photography, logo pack for partners.
• Internal: slide template, document templates, intranet, onboarding materials.

The dependency column is what makes this document a plan rather than a list. An asset with an unresolved dependency has no real due date, and sorting by dependency rather than by due date shows you the actual critical path.

5. The Launch Calendar

The asset matrix arranged in time, working backwards from the immovable date.

A workable default shape for a mid-size brand launch, counted back from launch day:

Two rules that hold across almost every launch:

• Anything printed or manufactured sets the real date. Digital can move by a day; a print run cannot. Work the schedule backwards from the longest physical lead time, and find that number in week one.
• Do not launch everything at once. A brand launch sequenced across a week gets several moments; one fired in a single hour gets one, and any asset that is not ready has to be held for weeks rather than for a day.

6. The Internal Launch Pack

Everything an employee needs to understand and repeat the new brand, delivered before the external launch.

It contains: the story of why the change happened, the messaging house in plain language, what changes for each team specifically, the assets they need immediately, a set of answers to the questions people will actually ask, and a named person to ask when the pack does not cover it.

That question set matters more than the rest of the pack. The real questions are rarely about the brand. They are "does this mean my email address changes", "do I need to redo my client proposals", and "are we being acquired". Answer those directly and the launch has advocates rather than rumours.

Run the internal launch at least two weeks before the external one. Employees who learn about a rebrand from a customer or from LinkedIn become its least persuasive spokespeople, permanently.

7. The Sustain Plan

The document teams skip, and the reason so many rebrands feel like they never landed.

Launch week produces a spike in attention and almost no change in what people believe. Association forms through repetition, which means the twelve weeks after launch matter more than the week of it. The sustain plan covers what runs in those weeks, who owns it, and what the budget is, and it should be written before launch because after launch everyone is tired and the budget is spent.

Binet and Field's IPA Databank work is the useful reference here: the long-run brand-building to short-run activation split lands near 60:40 across categories. A launch plan weighted entirely toward activation buys a spike in attention and no lasting brand association, which is exactly what a rebrand needs to build.

A Worked Example: A B2B Rebrand Over Fourteen Weeks

A 40-person software company changing name, positioning and visual identity at once. Three people on the launch, none of them full time on it.

Weeks 14 to 11, positioning. The document that took longest and produced the least visible output. It went through four versions because the second and third were descriptions of the product rather than positions against an alternative.

Weeks 10 to 8, messaging and identity. Messaging derived from the positioning, which is the order that works. Doing them in parallel, which the team initially planned, produces a messaging document that argues with the identity.

Weeks 7 to 5, the asset list and the migration audit. The audit found 340 surfaces carrying the old name. Eleven were outside anyone's control: partner directories, a conference listing, two app-store entries, review-site profiles. Those eleven took longer than the other 329.

Weeks 4 to 2, production. Website, sales collateral, templates, email signatures, social profiles, contract templates.

Week 1, sequencing. Internal first, customers second, public third, on three consecutive days rather than one.

What went wrong. The app-store entries needed review cycles nobody had scoped, and one took eleven days. The launch shipped with one store still carrying the old name for a week.

What the team would repeat. Running the migration audit in week 12 rather than week 7. The audit is cheap to run and its findings have the longest lead times, which is the argument for doing it early rather than when it feels relevant.

Total effort. Roughly 220 person-hours across fourteen weeks, over half of it in production rather than in the thinking that the team expected to dominate.

The Migration Audit Nobody Scopes

One extra artefact that is not a template but decides whether the launch feels finished.

Two weeks before launch, walk every surface a customer can reach and record which ones still carry the old identity. Not the ones on the asset matrix, all of them: the invoice PDF, the transactional email footer, the 404 page, the app store listing, the calendar invite template, the on-hold music, the second-page favicon nobody has looked at since 2019.

A brand launch is judged by its worst surface, not its best one. The website can be beautiful and the automated receipt still carries the old logo, and the receipt is the thing a customer sees every month.

Assign this audit to someone outside the marketing team. People who built the assets cannot see the old ones any more.

Comparison Table: Where Each Document Should Live

The honest reading: no single tool is best at more than two of these, which is why almost every real launch runs on two tools plus a spreadsheet. The common and correct pairing is a document tool for the thinking and a database or project tool for the matrix and the calendar.

The Tools, Reviewed in Workflow Order

These are ordered by where they enter the work, not by overall quality. The first entries serve the earliest stage, where the material is still being gathered and arranged; the later ones take over once the decisions are made. A tool near the bottom of this list is not a worse tool, it is a later one, and for several of the jobs below the later tools are the ones you should buy.

8. Notion

The verdict: the best home for the documents, and adequate for the tracking, which makes it the most common single-tool answer for launches under about forty deliverables.

Best for: small and mid-size teams who want the brief, messaging house and internal pack to live where people will actually read them.

Why it ranks here. The launch brief, the messaging house and the internal launch pack are documents, and Notion is a better document than a spreadsheet row. Its databases handle an asset matrix competently, and the ability to have the matrix as a view inside the same page as the brief means people encounter the plan and the reasoning together.

Its published launch and campaign templates are genuinely useful starting points, which matters when the alternative is a blank page at week one.

Limitations: the database gets slow and unwieldy past a few hundred rows with several views, there is no real dependency or critical-path handling, and it will not tell you that a slipped photography shoot has moved eleven downstream deliverables.

Best for in this stack: brief, messaging house, internal pack, and the asset matrix up to moderate size.

9. Airtable

The verdict: the best asset matrix in the category, and a poor place to write a brief.

Best for: launches with more than about sixty deliverables, and any launch with heavy asset variants across channels and formats.

Why it ranks here. The asset matrix is fundamentally a relational problem: assets link to channels, channels to owners, owners to deadlines, and every asset exists in six format variants. Airtable models that natively, and its interfaces let a designer see only their queue while the launch lead sees the whole board.

Its calendar and timeline views turn the same records into the launch calendar without maintaining a second document, which removes the most common source of plan drift.

Limitations: long-form documents are unpleasant in it, so the brief and messaging house go elsewhere. Pricing rises quickly with editors, and complex bases become their own maintenance job.

Best for in this stack: the asset matrix and the launch calendar.

10. Miro

The verdict: where positioning gets decided, and where nothing should be tracked.

Best for: the workshop stage, before the six documents exist.

Why it ranks here. Positioning work is spatial and comparative. You are holding several possible territories against each other, mapping competitors on axes, and clustering the language customers actually use. That is a whiteboard activity, and Miro is the default for good reasons: templates for positioning canvases and brand strategy, and enough space for a full day's workshop output to remain readable.

Limitations: it is not a plan. Boards decay after the workshop, and a launch tracked on a Miro board becomes unreadable at about the point it becomes important. Move the outputs into documents the same week.

Best for in this stack: the positioning workshop and the competitive map.

11. Asana, Monday.com and ClickUp

The verdict: necessary once the deliverable count passes what a document can hold, and premature before that.

Best for: launches with more than about forty deliverables, several teams, and real dependencies.

Why they rank together. For this job the three are more alike than different. All three do the thing Notion and Airtable do not: model dependencies, show a critical path, reassign workload, and tell you what a slipped task broke. On a launch where a photography shoot feeds eleven downstream assets, that is the difference between finding out in week eight and finding out on launch day.

Choosing between them: Asana has the cleanest dependency and timeline handling, Monday.com is the most legible to non-project-managers and the easiest to get a marketing team to adopt, and ClickUp offers the most capability per seat with the steepest setup cost.

Limitations: all three are poor homes for a messaging house or a brief, so they run alongside a document tool rather than replacing it. And on a small launch the setup cost exceeds the coordination it saves.

Best for in this stack: the launch calendar with dependencies, and the sustain plan.

12. HubSpot

The verdict: where the campaign runs, not where the launch is planned.

Best for: the activation and sustain phases, and measuring what the launch produced.

Why it ranks here. HubSpot's campaigns object ties emails, landing pages, ads, forms and workflows to a single campaign and reports on it together, which is the correct structure for the sustain phase. If you already run marketing there, the launch's demand-generation half belongs in it.

Limitations: it does not plan a brand launch. There is no asset matrix, no dependency model, and no home for the brief or the messaging house. Teams that try to run the whole launch inside HubSpot end up tracking a rebrand in a CRM, which does not work.

Best for in this stack: execution and measurement of the activation half, and the sustain plan.

Recommended Stacks

• Startup or small business, under 40 deliverables: Notion alone, plus Miro or Storyflow for the positioning day. Do not add a project tool; it will cost more setup than it saves.
• Mid-size company, 40 to 150 deliverables: Notion for documents, Airtable for the asset matrix, Asana or Monday.com for the dependency-heavy production phase.
• Agency running a client rebrand: Airtable for the matrix because clients need read-only views, Notion or a shared drive for documents, and a weekly status export the client actually reads.
• Enterprise: whatever the PMO already uses for the calendar, with a genuine effort to keep the messaging house somewhere findable rather than inside the project tool.
• Marketing team already on HubSpot: HubSpot for the activation and sustain phases, and something else for the pre-launch production. Do not try to plan the rebrand in the CRM.

How to Measure a Brand Launch Without Lying to Yourself

Launch measurement goes wrong in a predictable way: the team reports the metrics that moved rather than the metrics that mattered, because the metrics that mattered move slowly.

Set the measures in the brief, before anyone knows what will happen.

At 30 days, measure execution rather than effect. Did the assets ship, did the migration complete, did employees receive and understand the change. Internal comprehension is the only meaningful outcome measure this early, and you get it by asking twenty people to describe the new positioning in their own words. If they cannot, nothing external will land, and you still have time to fix it.

At 90 days, measure recognition. Aided and unaided awareness among the target audience, branded search volume, direct traffic, and whether inbound enquiries reference the new positioning. Branded search is the most honest cheap proxy available: it is hard to game and it moves when people actually remember you.

At 180 days, measure association. Do people connect you to the thing the positioning claimed. This needs asking rather than analytics, and a small tracking study or even fifty customer conversations beats a dashboard.

Two traps worth naming:

• Launch-week traffic is not a result. It is the sum of your own promotion and it tells you what you spent, not what changed. Every rebrand produces it, including the ones that fail.
• Do not compare post-launch conversion to pre-launch conversion in the first six weeks. A new website changes conversion for a dozen reasons unrelated to the brand, and attributing the difference to positioning is how teams learn the wrong lesson.

The measure that predicts whether a rebrand worked, more than any other, is whether your own salespeople started using the new language unprompted. If they reverted to the old pitch by week six, the internal launch failed and the external one is decoration.

Frequently Asked: Brand Launch Planning Tool Brands

Which brands in brand launch planning tools are the most trusted?

Notion and Airtable are the two most trusted for holding a launch plan, with Airtable stronger on the asset matrix and Notion on the documents. Asana and Monday.com are the most trusted for dependency-heavy production schedules. Miro is the most trusted for the positioning workshop. HubSpot is the most trusted for running and measuring the campaign afterwards, and is not a planning tool.

Which brands in brand launch planning tools are known for fair and transparent pricing?

Notion has the clearest pricing of the group and a free tier that genuinely carries a small launch. Miro and Asana publish straightforward per-seat tiers. Airtable's pricing rises quickly with editor count and record limits, which is the line to read carefully. HubSpot is the least transparent, because launch-relevant features sit in higher marketing tiers with contract minimums.

Which brands have a strong history of consistent product performance?

Asana and HubSpot have the longest records of stability at scale. Airtable is reliable but slows noticeably on very large bases with many views, which matters if your asset matrix runs to several hundred rows. Notion's performance on large databases has improved but is still the weakest of the group for that specific use.

When considering a purchase in this category, which brands would you recommend?

For most launches, Notion plus a spreadsheet, and nothing else. Add Airtable when the asset matrix passes about sixty rows with format variants, and add Asana or Monday.com when deliverables have real dependencies across teams. Buying a project tool for a small launch is the most common overspend in this category.

Which brands in this category might be underrated?

A plain spreadsheet is underrated for the asset matrix; it does 80 percent of what Airtable does for a first launch and teaches you what structure you actually need. Miro is underrated for the migration audit, because photographing every legacy surface onto one board makes the remaining work impossible to ignore. And Google Docs remains a perfectly good messaging house.

The Bottom Line

Six documents, and the asset matrix is the one that decides the date. Build it by walking surfaces rather than brainstorming, fill in the dependency column honestly, and sort by dependency rather than by deadline to see the real critical path.

Then write the sustain plan before you launch, while there is still budget and energy to commit. Launch week produces a spike in attention and almost no change in belief, and the twelve weeks afterwards are where the brand is actually built. Teams that plan to launch day plan to the wrong milestone.

If you buy one tool, buy the one that holds the asset matrix well. Everything else in this stack can live in a document.