Why your brand sounds generic on social (and how to fix it)
Most social media content sounds the same because tools only know your tone adjectives, not your brand. Here is what actually makes a feed recognizable, and a practical way to build it.
Maya Chen
Founding team, Kanso Social
Yesterday I did a thing I do every few weeks: I opened LinkedIn, picked a random post from a brand I follow, covered the logo with my thumb, and tried to guess who wrote it.
I couldn't. It could have been any of maybe forty companies. Emoji hook, three bullet points, a question at the end "to drive engagement". I checked the brand's website afterwards and here's the frustrating part: they make genuinely interesting products. You would never know it from the feed.
I don't think this happens because social media managers lack talent. I've worked with too many good ones to believe that. It happens because the tools we hand them know almost nothing about the brands they write for.
The tone-adjective trap
Ask a team to define their brand voice and you'll usually get adjectives: friendly, professional, authentic, bold. Every AI writing tool happily accepts them. I've typed them into a dozen tools myself.
Here's the problem. Adjectives describe how words should sound, not what the brand actually knows. "Friendly and professional" fits a bank, a bakery, and a B2B analytics startup equally well. That's exactly why content generated from tone settings is interchangeable. The adjectives were never the thing that made you different. Your knowledge is.
A brand voice is not how you sound. It's what you know, repeated consistently until people recognize it.
When I look at feeds that do feel unmistakable, the ingredients are pretty consistent:
- Audience language. The words customers use for their own problem, which are almost never the words in your product docs.
- Product facts. The material, the process, the number. A concrete fact is impossible to confuse with a competitor.
- Proof. Results, reviews, specifics that only you can claim.
- Guardrails. The claims you never make and the topics you stay away from. These protect a voice more than any styleguide does.
None of this fits in a tone dropdown. I've looked.
Where brand knowledge actually lives
In most teams I've talked to, this knowledge exists. It's just scattered everywhere: positioning in a slide deck from 2024, product facts in a spreadsheet someone maintains reluctantly, the voice in the head of whoever has run the channel for the last two years, guardrails in a legal email nobody can find.
So every time someone writes a post, they have a choice: reassemble all that context by hand, or skip it. Skipping is faster. And that's how a feed drifts generic, one skipped step at a time. New writer, new agency, new AI tool: every handoff loses another layer.
A quick test
Take your last ten posts and remove the logo. Would a loyal customer know they're yours? If not, the posts are running on tone, not knowledge.
Building a working brand brain
The fix isn't a longer styleguide. I've written long styleguides. They get read once and then they sit there, describing the brand while everyone gets back to work without them.
What actually helps is turning that document into working knowledge, the kind that shows up inside every brief and draft. Here's the version of this I'd do this week:
- Collect the sources you already have. Your website, your product notes, and the ten best posts you've ever published. Approved content is voice in practice, and it teaches far more than voice in theory.
- Turn it into claims you can reuse. Not "we value quality" but "linen is washed before sewing, so it feels settled from the first use". One fact per line. If you can't verify it, it's not a claim.
- Write the guardrails down. Banned words, risky claims, comparisons you avoid. This takes an hour and prevents the most expensive mistakes.
- Feed decisions back. When an edit gets approved, ask what changed and why. "Lead with the ritual, not the product claim" is a lesson that should improve every future draft, not disappear in a comment thread.
The difference shows up faster than you'd expect:
| Running on tone | Running on knowledge |
|---|---|
| "Discover our beautiful new collection." | "Solace begins with washed linen, softened slowly." |
| Any brand could post it | Only you can post it |
| Needs heavy editing | Needs a quick review |
| Voice drifts with each writer | Voice survives handoffs |
Why we're building this into Kanso
This is, honestly, the whole reason Kanso Social exists. We're building it around a Brand Brain: a working store of your audience, voice, product facts, and guardrails that attaches itself to every brief, draft, and review. Not a smarter prompt. A system where the knowledge does the work, quietly.
The result we care about is simple. Fewer factual corrections. Fewer blank prompts at 9am. And a feed a loyal customer would recognize with your logo covered by a thumb.
Kanso Social is in private beta. If keeping a brand coherent across channels is your daily work, join the waitlist. We're building the first version with people like you.