---
title: "How to roll out a positioning change to every asset | Rainbrand"
description: "A new positioning statement takes a day to approve and months to reach every page, deck, ad and profile that still says the old thing. Update the messaging source first, find every stale line, fix the most visible assets first, get people saying it, and recheck until nothing old is left. With the inventory from Rainbrand's own rename, including what it missed and what it kept on purpose."
url: "https://www.rainbrand.com/blog/roll-out-a-positioning-change/"
---

By Siddharth Borderwala

Published 17 Nov 2026

11 min read

# How to roll out a positioning change to every asset

A new positioning statement takes a day to approve and months to reach every page, deck, ad and profile that still says the old thing. Update the messaging source first, find every stale line, fix the most visible assets first, get people saying it, and recheck until nothing old is left. With the inventory from Rainbrand's own rename, including what it missed and what it kept on purpose.

## TL;DR

Change the messaging source before any asset: the new statement, boilerplate, proof points and a list of retired phrases with their replacements. Then find every asset that still uses the old lines, fix them in order of how many people see them, brief the people who talk to customers, and recheck with something that fails loudly until no old line is left.

## Where the old positioning lives

Lovable’s ad for a [Member of Technical Staff, Applied AI (Marketing)](https://jobs.ashbyhq.com/lovable/5757fd07-a192-4986-8cdc-1cded652d49d) describes the system it wants: “When the scope changes, the change propagates to every asset that mentions it.” Without that, a positioning change approved in a meeting and announced in a post can leave the old line in a sales deck, a review-site profile and the meta description of the pricing page for months.

The rollout guides that rank for this list the obvious assets. [GTM Playbook’s](https://discover.gtmplaybook.co/positioning-playbook) 30-day plan updates the homepage hero, core sales deck, outbound openers and demo narrative in its second week. [McMann and Tate’s checklist](https://www.mandtagency.com/post/brand-identity-rollout-checklist-that-works) asks for a master register of every touchpoint. Both are right. What they leave out are the places agents and AI assistants read, which now repeat your positioning to buyers and to your own team:

| Where it lives | Examples | How to find it |
| --- | --- | --- |
| Website | Hero, product pages, pricing, metadata, link previews, help centre | Crawl the sitemap or export the CMS |
| Sales | Decks, one-pagers, sequences, demo scripts, battlecards, proposals | Search the shared drive and the sales tool’s templates |
| Paid and social | Live ads, social bios, pinned posts, video descriptions | Export from each ad account and profile |
| Profiles you don’t host | Review sites, marketplaces, app stores, partner directories, LinkedIn | A list, since search won’t find them |
| Press and hiring | Boilerplate, press kit, job ads, careers page | The press kit and the applicant tracking system |
| Product | Onboarding, empty states, emails the product sends, error messages | Search the codebase and email templates |
| What agents use | Brand guidelines, prompt libraries, project instructions, templates | Each tool’s saved context, plus the brand they fetch |
| What AI assistants say about you | ChatGPT, Claude, Perplexity and Google answers to buyers’ questions | Ask them, and note which pages they cite |

The last two rows are new. An agent working from last quarter’s brand guidelines will keep writing the old positioning into every new asset, and an AI assistant that cites an old page can keep repeating it to buyers.

## Change the source before the assets

Write the new messaging down in one place, such as a [messaging framework](https://www.rainbrand.com/blog/brand-messaging-framework/), before anyone touches an asset, because every rewrite will copy from it. It needs:

- the new positioning statement and the one-paragraph boilerplate;
- the messaging pillars, each with its proof point and source;
- the phrases being retired, each with the line that replaces it;
- what isn’t changing, such as product names, identifiers or claims that still hold;
- the date it takes effect and who answers questions.

The retired-phrase list does most of the work later. It’s what an agent searches for, what a reviewer checks against, and what stops someone reviving the old line in a new campaign. The “isn’t changing” list matters as much, because a rollout can overreach, as the example below shows.

Then update the brand context your agents use, so new assets start from the new positioning. In Rainbrand, which gives AI agents a brand’s guidance and files, that’s a [brand edit](https://docs.rainbrand.com/guides/edit-brand): describe the change with the new messaging, inspect what Rainbrand prepares, apply it, and then request fresh Briefs, the guidance and files for each task. Saved Briefs and exported copies don’t update themselves. [How to update brand guidelines across all your AI tools](https://www.rainbrand.com/blog/update-brand-guidelines-across-ai-tools/) covers the copies outside it, such as uploaded guides, saved prompts and exported folders.

## Find every stale line

Searching by hand finds the obvious pages and misses the rest. An agent with access to your site export, shared drive or a folder of decks can do the search, provided it only reports and doesn’t edit:

Ask your agent

```
Here is our new positioning: [statement], [boilerplate] and [pillars], and the phrases we’ve retired, each with its replacement: [list]. Go through [the site export, sitemap URL or folder of decks] and list every place that still uses a retired phrase or describes us the old way, even in different words. For each, give the location, the exact old wording, the new line that replaces it, and what kind of asset it is. Don’t change anything yet.
```

Ask for “even in different words”, because old positioning rarely appears only as the exact retired phrase. Sales decks paraphrase it, and old blog posts explain it at length. Check a sample of the agent’s findings yourself before trusting the list, and add the profiles you don’t host from your own list. This paraphrase search is a recommended step: the rename example below didn’t need it, because the old name is one word, so it doesn’t show how well an agent finds a reworded message.

Then ask the AI assistants your buyers use the questions they ask, such as what you do and who you’re for. Note any answer that uses the old positioning and which page it cites. Those cited pages go near the top of the list.

## Decide what to change first

You won’t fix everything in a week, so order the list by what does the most damage:

| Priority | What | Why |
| --- | --- | --- |
| First | Homepage, product and pricing pages, live ads, active sales decks | Most buyers see them, and they contradict the announcement |
| Second | Pages AI assistants cite, profiles on review sites and marketplaces | Buyers read them before talking to you, and you don’t control the timing |
| Third | Email templates, onboarding, help centre, social bios, job ads | Seen often but by fewer people, and quick to change |
| Fourth | Old blog posts, case studies, archived decks | Rewrite the ones still getting traffic; mark the rest as dated |

Give each item an owner and a date, and keep the list where everyone can see it. A rollout without a visible list ends when people get busy, not when the old line is gone.

## A real inventory: renaming Bloom to Rainbrand

Rainbrand was called Bloom until [October 15, 2026](https://www.rainbrand.com/changelog). This rename tests the mechanics of finding and changing assets. It does not test a change of audience, category or value proposition. Below is what changed, what was missed, what was kept and how it was rechecked. The public record covers only part of it: the changelog announces the rename. The rest comes from Rainbrand’s internal change history, which isn’t public, so read it as our own account of the rollout.

| Surface | Old wording | New wording or decision | Changed |
| --- | --- | --- | --- |
| Site name and page titles | “Bloom” | “Rainbrand” | Before launch |
| Browser tab icon | Bloom icon | New mark, under a new file name | Before launch |
| Command people paste to connect an agent | Server named `bloom` | Named `rainbrand` | Before launch |
| API reference and the agent-readable index | “Bloom API”, “# Bloom” | “Rainbrand API”, “# Rainbrand” | Before launch |
| Product emails, such as the welcome email | “Welcome to Bloom!” | “Welcome to Rainbrand”, behind a switch | Switched at launch |
| Instructions sent to models | “Bloom appends routing tables…” | “Rainbrand appends…” | Launch day, after |
| API error messages | “…Bloom did not drop any assets.” | “…Rainbrand did not drop any assets.” | Launch day, after |
| Agent connections saved as `bloom` | Old name | Kept working | Not changed |
| Internal script and skill names | Old name | Kept | Not changed |
| Search engines’ record of the company | Bloom | Lists Bloom and Bloom AI as former names | Nov 10 |

A few rows are easy to forget. The browser icon would have kept showing the old mark to returning visitors, whose browsers had cached it under the same file name, so the new one went out under a new name. The emails were built ahead of time and switched on at launch, and the old templates were deleted the next day. And the instructions sent to models count as copy: a model told about “Bloom” writes “Bloom” back to users.

The kept rows were decisions, written into the team’s terminology guide: keep the old name only “where a reader needs the former name”, such as notes about the rename or older connections. Agents already connected under the old name kept working, so nobody had to reconnect.

### What the plan missed

The misses found after launch all turned up within two days, and most share a pattern: places a page crawl doesn’t reach.

- The afternoon of the launch, a sweep found the old name in the pricing page’s search and share description, buttons on the features page, and the setup prompt people copy into their agent. The model instructions and API error messages in the table were fixed in the same hour.
- One note was left on purpose. It sat inside a prebuilt sandbox image, and changing it would have failed the image’s build check, so the team renamed it two days later with the next rebuild.

The rollout also overreached once. On October 16, the new name turned up on the older connection address that existing customers still use, which was meant to keep presenting the old name. The fix put the old wording back there.

### How it was rechecked

The recheck didn’t rely on someone remembering to search. The public docs have a build check that fails if “bloom” appears anywhere outside a short list of allowed uses. Before launch the same check ran the other way and rejected “Rainbrand”, so the docs couldn’t go live early; it was flipped on launch day. Tests fail if the agent-readable index or any product email mentions Bloom, and one test checks both directions: the old connection address keeps the old name, and the new one shows the new name.

## Rewrite assets from the new messaging

Agents make rewriting fast, as long as each rewrite starts from the new messaging rather than from the old asset’s wording. For most existing assets, change only the lines the audit flagged and keep the layout:

Ask your agent

```
Request a Rainbrand Brief for [brand] for updating [asset] to our new positioning. Keep its layout, length and URL. Replace only the lines on this list from the audit, using the new boilerplate and pillars: [lines]. Show me each change as old and new text, and flag any claim the new messaging doesn’t support, before changing the file.
```

Rebuild from scratch only when the old message is the asset’s whole point, such as a campaign landing page or a pitch deck’s opening section, and keep the template so only the words and the images that carry the message change. Have a person approve anything public before it replaces the old version, and keep the old version live until the new one is ready, so nothing is left blank.

## Get people saying it

Assets are half the rollout. Salespeople, customer success and support repeat the positioning in calls and emails, and they’ll keep the old version until someone gives them the new one. GTM Playbook’s plan spends time on this, from the demo narrative to sales training. These are recommended steps, not results from the rename: it shows the copy-guide rule and the banner below, but nobody measured whether people adopted the new name in calls or emails. Before the change goes public:

1. Give everyone who talks to customers a short talk track: the new line, why it changed, and the two or three questions customers will ask.
2. Say plainly what hasn’t changed. Rainbrand’s copy guide tells anyone writing to customers that existing connections, API keys and links keep working, and never to tell anyone they’ve stopped.
3. Keep a visible notice for a fixed period. Rainbrand ran a rename banner linking to the changelog, set to expire on November 29.

A few weeks later, check what people actually say. Read a sample of sent sequences and support replies, and listen to a few recorded calls for the old line. Spoken positioning drifts back faster than written positioning, because nobody searches a call.

## Check that nothing old is left

Run the audit prompt again after each wave. The list should get shorter, and anything still on it after two waves needs a named owner rather than another reminder. Where you can, turn the retired-phrase list into a check that fails on its own, like the docs check above, so the old line can’t come back in a new page. For visual assets, a [Review](https://docs.rainbrand.com/guides/request-review) with the exact new copy checks that the captured image says what it should and still follows the brand.

Check the AI answers again a few weeks after the first wave. If an assistant still repeats the old positioning, look at the page it cites: if it’s yours, update it; if it isn’t, such as a review-site profile or an old article, ask whoever controls it. When Rainbrand measures AI answers, one that mentions the old name doesn’t count as a mention of the new one, even if it explains the rename.

## FAQ

### How long does a positioning rollout take?

The first wave, the assets most buyers see, can be done in a couple of weeks once the messaging is final. In the rename above, the misses found after launch were fixed within two days, but the long tail of old posts, profiles and AI answers takes months, which is why it needs a visible list with owners rather than a deadline.

### Should we update old blog posts and case studies?

Update the ones that still get traffic or that AI assistants cite, since buyers still read them. Leave the rest, with their original dates, so nobody mistakes them for current positioning.

### What about AI assistants that still describe us the old way?

Update the pages they cite, ask the owners of profiles you don’t control to update theirs, and check again in a few weeks. Answers may change as the pages behind them change, but each assistant’s provider decides what it indexes and retrieves, so the recheck is how you find out.

### How is a positioning change different from a rebrand?

A rebrand changes how the brand looks and often its name; a positioning change changes what you say about yourself. The rollout works the same way, an inventory, a priority order and a recheck, but a positioning change without a new name is harder to search for, because the old message is paraphrased rather than spelled the same way every time.

## More in Brand guidelines

[All 18 Brand guidelines articles](https://www.rainbrand.com/blog/topics/brand-guidelines/)

- 17 Nov 2026 18 min read

    ### [Brand guidelines examples: 12 real brand books and what to copy from each](https://www.rainbrand.com/blog/brand-guidelines-examples/)

    Twelve brand guidelines you can open today, from Mastercard’s logo rules to NASA’s 1976 standards manual, with the exact rule worth copying from each, which ones an AI agent can read, and what it took to correct an agent’s version of Starbucks.

- 17 Nov 2026 10 min read

    ### [Branding kit checklist: what to include, file formats and real examples](https://www.rainbrand.com/blog/branding-kit/)

    What a branding kit should contain, from logo files and colour values to fonts, templates and rights; what to agree with your designer; what real companies’ kits hold; and a bounded web sample kit, with its index, a template and an asset made from it.

- 17 Nov 2026 11 min read

    ### [Logo usage guidelines: what to include and how to write them](https://www.rainbrand.com/blog/logo-usage-guidelines/)

    Logo usage guidelines say which logo goes where, how much space it needs, how small it can go, which colours and backgrounds it allows and what never to do. See how Amazon and Strava write each rule, how AI tools get logos wrong, and a template to download.

## Connect Rainbrand.

Use Rainbrand with your agents, or embed it into your product.

[Use it with your agents](https://docs.rainbrand.com/mcp/getting-started) [Integrate it with your product](https://docs.rainbrand.com/getting-started/embed-into-your-product)

### ChatGPT + Codex

1. Open the Rainbrand plugin and add it.

    [Open Rainbrand plugin](https://chatgpt.com/plugins/plugin_asdk_app_6ac6e5030ec88191a88001f6dc0628ca)

2. Connect your Rainbrand account when asked. It works in ChatGPT and in Codex.

### Claude

1. Open the Rainbrand connector in Claude and add it.

    [Open Rainbrand connector](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Rainbrand&connectorUrl=https%3A%2F%2Fmcp.rainbrand.com%2Fmcp)

2. Select Connect, then sign in to Rainbrand.

You can also install the [Rainbrand Skill](https://docs.rainbrand.com/mcp/getting-started#standalone-rainbrand-skill) or the [plugin](https://github.com/rainbrandai/rainbrand-skills/releases/latest/download/rainbrand.claude-plugin.zip).

### Claude Code

1. Add Rainbrand's plugin marketplace in your terminal.

    ```
    claude plugin marketplace add rainbrandai/rainbrand-skills
    ```

2. Install the Rainbrand plugin, including its Skill and MCP connection.

    ```
    claude plugin install rainbrand@rainbrand
    ```

3. Start a new Claude Code session, then use /mcp to sign in to Rainbrand.

You can also [connect with MCP](https://docs.rainbrand.com/mcp/getting-started#claude-code-installation-options) or install the [Rainbrand Skill](https://docs.rainbrand.com/mcp/getting-started#standalone-rainbrand-skill).

### Cursor

1. Add Rainbrand to ~/.cursor/mcp.json.

    ```
    { "mcpServers": { "rainbrand": { "url": "https://mcp.rainbrand.com/mcp" } } }
    ```

2. Sign in from the Cursor CLI.

    ```
    agent mcp login rainbrand
    ```

You can also install the [Rainbrand Skill](https://docs.rainbrand.com/mcp/getting-started#standalone-rainbrand-skill) or the [plugin](https://github.com/rainbrandai/rainbrand-skills/releases/latest/download/rainbrand.cursor-plugin.zip).

### API

1. Create an API key in your account settings, then list your brands.

    ```
    curl https://www.rainbrand.com/api/v1/brands -H "x-api-key: $RAINBRAND_API_KEY"
    ```

Integrating Rainbrand into your app? [Read the API docs](https://docs.rainbrand.com/api).

The brand layer for agents

Rainbrand builds and maintains shared brand context for your agents and products

[Get started](https://www.rainbrand.com/auth/sign-in) [Read the docs](https://docs.rainbrand.com/)

[View pricing](https://www.rainbrand.com/pricing/)
