Skip to content

Content and brand voice

Every client draft is in their voice with Armbrain.

Every client draft is in their voice, on brand, built on their work, and yours to approve with Armbrain.

Each client's voice, word rules and past posts live in that client's mind, so Claude writes like them and you fix things once, not every time.

Start FreeWatch it work

See it work

Watch it remember.

Pick a demo. Each starts with a question and ends with an answer you can check.

More examples, each with a fictional client:

Fix a word once, for good
  1. Rewrite the Copperleaf Bakery Co. holiday email. Dana does not want the word "artisanal" anywhere. Say "baked this morning" instead, and make that a rule for every Copperleaf draft.
  2. switch_clientCopperleaf Bakery Co.
  3. store_correctionno "artisanal"use "baked this morning"
  4. search_memoryGoogle DriveHoliday email v2
  5. briefingcampaign_historyMailchimp2 past holiday sends

  6. Rule saved. From now on, Copperleaf drafts use "baked this morning" and never "artisanal".

    The holiday email had "artisanal" 3 times. All 3 are gone, and the new subject line is "Baked this morning, boxed for the holidays."

    It does not reuse either subject line from the last 2 holiday sends.

    Read the new version before you load it into Mailchimp.

Turn highlights into a draft
  1. For Fieldstone Software, turn my Readwise highlights on pricing into a newsletter draft from Jordan. It should sound like Jordan, not like me.
  2. switch_clientFieldstone Software
  3. mindbrand_voice_getFieldstone Softwaredirect, dry humor, no buzzwords
  4. search_memoryReadwise9 highlights on pricing
  5. search_memoryGoogle DrivePricing page brief

  6. The draft is ready: "Why we stopped charging per report," about 650 words.

    It draws on 5 of your 9 highlights and credits each author by name. The other 4 were about consumer pricing, so I left them out.

    The numbers match the pricing page brief in Google Drive.

    Check the quotes against the original sources and send it to Jordan for review before it goes out.

Plan emails that do not repeat
  1. Plan three fall emails for Ridgeline Outfitters. Don't repeat what we sent last fall, and point each one at a gear guide already on their site.
  2. switch_clientRidgeline Outfitters
  3. briefingcampaign_historyKlaviyo14 campaigns, Sep to Nov last year
  4. search_memoryWordPress6 gear guides
  5. mindbrand_voice_getRidgeline Outfitterstrail-tested, never salesy

  6. Here are three fall emails, each with a subject line and a one-line hook.

    1. Layering for cold mornings, linked to the base layer guide.

    2. Rain gear that packs small, linked to the rain shell guide.

    3. Winter boot fitting, linked to the boot guide.

    Last fall's 14 campaigns leaned on sales. None of these three leads with a discount.

    Check the plan with Maya before anyone writes the full emails.

Demo 1 of 4

Claude

Draft a post in the client's voice

  1. Switch to Northstar Studio and draft a blog post on how they run a design sprint. Match their voice and use what Maya said on last week's call.
  2. switch_clientNorthstar Studio
  3. mindbrand_voice_getwarm, plain, first person plural4 banned words
  4. search_memoryWordPress4 recent posts
  5. search_memoryGranolaMaya, Sep 24 call

  6. Here is a 900-word draft: "Five days, one decision: how we run a design sprint."

    It follows Northstar's voice: short sentences, "we" not "the team", and none of the 4 banned words.

    It links to 2 of their earlier posts and uses Maya's point that day three is for cutting ideas, not adding them.

    Read it and check Maya's quote with her before it goes to WordPress. Nothing has been published.

Fictional client example. Real answers use your data.

Plug every app into Armbrain

From style guide to final draft, one mind remembers it.

Armbrain reads from 31 apps today. Connect the places a client's words already live, and Claude drafts from their real work instead of a blank page.

and 25 more

See every integration

Try these

Copy a prompt. Swap in your client.

Paste one into Claude with Armbrain connected. Each links to the full use case.

  • Apps: WordPress, Granola.

    Change these first:

    CLIENTCOMPANY = Northstar Studio Armbrain, switch to CLIENTCOMPANY and draft a blog post on their spring launch in their voice. Use their last four WordPress posts as reference and show me the draft.

    Write in each client's voice
  • Apps: Google Drive, Notion.

    Change these first:

    CLIENTCOMPANY = Brightpath Learning Armbrain, set up CLIENTCOMPANY's brand voice from the style guide in Google Drive and the brand notes in Notion. Show me what you will save before you save it.

    Kick off a new client
  • Apps: WordPress, Google Drive.

    Armbrain, write a back-to-school checkup reminder for each of my health clients. Keep each in its own client's voice.

    Managing multiple clients
  • Apps: Granola, ClickUp.

    Change these first:

    CLIENTCOMPANY = Ridgeline Outfitters Armbrain, which blog posts and emails did I promise CLIENTCOMPANY this month, and which ones are still open?

    Keep every promise you made

Fictional client names. Replace with your own.

One mind per client

Every client keeps its own voice.

Say a client's name and Claude loads that client's voice, word rules and past posts, and nothing from anyone else. Switch clients by name and the voice switches with it.

Illustration. Client names are fictional.

Works where you work

Change AI tools. Keep every voice.

Armbrain works in Claude Desktop, claude.ai and Claude Code today, and in Cursor. Each client's voice and rules live in Armbrain, not inside one chat window.

  • Brand voices and rules come with you.
  • Corrections you taught once still apply.
  • Start with one client, then add the rest.

Built to be careful

You stay the editor.

Each client stays in its own mind. Apps are read for context, and Armbrain never publishes anything. You review and post every draft yourself.

Each client in its own mind

Every client gets a separate mind. Switch by name, and what you save for one client stays with that client.

Read, don't rewrite

Most connections only read. The few that add something, such as Notion recaps on pages you choose, say so on their own page.

Drafts wait for you

Follow-up drafts are shown to you for approval by default, and meetings are booked only after you confirm who is invited. You can change the email setting.

How we handle security Privacy policy Sub-processors

Questions

Questions, answered.

Does Armbrain publish to WordPress for me?
No. Armbrain reads your published posts so Claude can match the voice and link to earlier work. Every draft comes back to you in Claude, and you decide what gets published.
Is each client's voice and information kept separate?
Yes. Each client has its own mind, and its brand voice and working rules are saved there. When you switch to a client, Claude loads that client's context and nothing from anyone else.
How does it learn a client voice?
You describe it in plain words: tone, words to use, words to avoid, a few examples. Armbrain saves it with that client. When a draft misses, tell Claude once and save it as a correction, and that rule applies from then on.
Will it send emails for me?
Follow-up drafts wait for your OK by default. You can change that setting. All drafts are for you to review. Armbrain does not publish posts or send campaigns.
What if the app I use isn't listed?
Tell us which app you need at /integrations/request. Until then, you can paste text or upload a file into a client mind so Claude can use it.

Give every client a voice Claude remembers.

Save one client's voice today and read your next draft in it.

Start FreeSee pricing