Bloom is now Rainbrand

By Tomas Ward

Published

Updated

4 min read

How to onboard a client brand into AI: an agency checklist

Collect the client's current sources, resolve conflicting guidance, create reusable brand context and check the first task. Keep the files, findings and unanswered questions in a handoff your team can use.

TL;DR

Collect the client’s current sources and usable files, resolve conflicts and make that context available to the agents doing the work. Check it on an upcoming deliverable, then hand over the sources, output, findings and open questions. Follow the client’s actual access and approval arrangements.

Leave onboarding with a usable task record

A folder alone does not identify the current logo, supported claims or what “warm” means. Fill this record as you work:

Client and brand reference:
Current sources and instructions for conflicts:
Reusable files and permitted use:
First task, audience and required copy:
Guidance and files supplied to the agent:
Output and checks performed:
Corrections made:
Unanswered questions and who can answer:
Any approval required by the client agreement:
How future brand changes will be reported:

Start with the first deliverable, then extend the setup for other formats.

Check how the material may be used

Before uploading:

  • Read the client agreement for AI use, confidentiality, tools and disclosure.
  • Identify the actual tools, plans and accounts handling sources and outputs.
  • Confirm who may access the files and answer brand/product questions.
  • Retain whatever client approval the account already requires.

Check account settings, not just product names. Anthropic’s commercial-data policy, for example, excludes default training on commercial inputs/outputs but describes feedback and opt-in exceptions. Sharing and memory settings matter too.

Collect sources for the work you are about to make

CollectInclude
Current guidanceGuide/date, positioning, voice, representative pages and approved/rejected work
Usable filesOriginal logo variants, colour values, fonts/licences, approved images and templates
Task factsProduct names/specifications, claim evidence, required lines, offer, dates and audience
Source priorityWhich source wins, and which files are retired

Ask only for what the upcoming task needs. Missing print colours need not stop an email; missing evidence for its main claim does.

In the US, FTC policy requires a reasonable basis for objective claims before publication. Leave unsupported claims unresolved and ask the client contact.

Turn conflicts into instructions

  1. Read the sources together and identify conflicts, vague rules and missing files.
  2. Ask whether each decision changes the brand or only this campaign.
  3. Record the instruction beside the source it replaces.
  4. Leave unanswered gaps explicit, with the work they affect.

The Markdown template helps turn answers into checkable rules.

Yumbun, a London bao brand, illustrates the source problem. Its menu-decoder Brief identified an older photograph’s prices and varieties as conflicting with the task’s supplied menu:

Older Yumbun counter photograph with Mushroom, Chicken and Salmon menu boards and a sign showing one bun for £3.50 or two for £6

Rainbrand’s Brief also treated food photographs as visual references, not proof of current fillings, and flagged missing product imagery. Confirm operational facts with their current owner before publication.

Create and inspect the client's brand

Rainbrand maintains guidance and assets that connected agents use. Setup is self-serve:

  1. Create an account, then connect Claude or ChatGPT.
  2. Confirm the connected account and intended team. The quickstart says new brands default to the personal account; list and name the team when appropriate.
  3. Upload local files, then add the client’s sources and resolved decisions.

Choose a team whose members may use this client’s material; shared agency access must not expose restricted files.

Ask your agent
Confirm the connected Rainbrand account and the team specified in our intake record. Add [the client brand] using the attached current guide, resolved rules, original logo and font files, and approved product imagery. Follow the resolved rules where sources conflict. Keep campaign offers and dates with the task. When ready, show the brand name, identity and guidance for comparison with the intake notes.

Inspect the returned identity and guidance against intake. For mistakes, prepare an edit, inspect its proposal and refine, apply or discard it. Only applying changes the active brand.

Keep reusable approved assets in the Brand Library; leave retired files and experiments out. Campaign requests stay with the job.

Check the first upcoming task

Choose a real deliverable containing a detail that could reveal a setup problem: a renamed product, restricted claim or required asset.

Ask your agent
Use [the client brand] from our intake record. Request a Rainbrand Brief for [the first deliverable], its audience and required copy. Use the approved product imagery and claim wording attached to this task. Show the guidance and selected assets before making the work, and identify any missing fact or file before continuing.

Read the Brief before production. Confirm the product, files and instructions, then make the work with the intended delivery tools.

Use Rainbrand Review on the finished work. For a graphic, submit its final image and expected copy; for pages or slides, capture each layout that needs checking. One image does not certify an entire deck.

FailureRepair
Wrong saved logo/ruleCorrect the brand, then request a new Brief
Task requirement missing from BriefClarify the request and retrieve again
Correct guidance ignoredRevise with the creation tools
Unsupported product factObtain evidence or remove the claim

Review returns findings; the agent’s tools make corrections. Repeat the affected check and retain unresolved findings alongside any required client approval.

Hand over what worked and what remains open

Complete the opening record with exact sources, files, Brief, output and corrections. Keep any required sign-off beside the file it approves.

Agree where future changes arrive. Apply lasting decisions to Rainbrand and request fresh Briefs; older Briefs and downloads stay unchanged, so identify active jobs needing an update.

Have the next person continue the task from the record. Their unanswered questions reveal gaps in the handoff. Managing many client brands covers keeping this useful across a roster.

  • 5 min read

    How agencies keep client brands separate across AI tools

    Client brands get mixed in two ways: an agent applies the wrong client’s guidance, or one client’s material turns up in chats and projects where it doesn’t belong. Here’s how agencies guard against both in the AI tools they already use.

  • 5 min read

    How agencies get client approval on AI-made brand work

    Agree the ground rules before the first draft, check the work against the client’s brand before they see it, tell them how it was made and what they’re deciding, and put each correction into their brand once.

  • 5 min read

    How agencies manage many client brands with AI agents

    Give each client job an explicit brand, current guidance and a handoff the next person can use. Keep brand changes separate from campaign feedback without replacing your delivery tools.

One brand, every agent.

Connect your agents