What clients mean when they say "it doesn't sound like us"

The email arrived three days after you submitted the draft. Two sentences, no line edits: "Thanks for this — we need some revisions though. It doesn't really sound like us."

That feedback appears in almost every freelance writer's inbox eventually. Content doesn't sound like brand client feedback is the most common revision request — and the least actionable. What does "us" even mean? Which sentences missed? What would "sounding like them" actually look like?

The problem isn't that clients are being vague on purpose. They genuinely can't articulate it. They know their voice when they see it, but they can't reverse-engineer the components for someone who's never worked there.

What "off-brand" actually means in practice

When a client says the content feels off-brand, they're usually responding to one of three gaps. Sometimes all three at once.

The terminology gap. You wrote "customers" and they say "members." You mentioned their "platform" and they call it by its product name. You described a "subscription" and they've deliberately avoided that word for years because it implies recurring charges they don't want associated with their model. The client reads these and thinks "this person doesn't know us" — even if everything else is perfect.

This gap is the easiest to close but the hardest to spot without research. Most new client research focuses on industry and audience, not internal vocabulary.

The formality mismatch. Their About page uses sentence fragments and starts paragraphs with "And." Your draft reads like a press release. Or the reverse — you wrote conversationally for a brand that never uses contractions and addresses readers as "you" exactly zero times across their entire site.

Formality is harder to quantify than vocabulary. It lives in sentence length, punctuation choices, whether they use questions rhetorically. Reading three of their existing pieces usually reveals the pattern.

The perspective drift. You wrote about what the product does. They always write about what the customer gets. You centered the company as the subject of most sentences; they center the reader. This one is subtle. A client might not identify it consciously — they just feel like the article is talking at their audience instead of with them.

Why the feedback never includes specifics

Clients aren't being difficult when they send vague revision notes. They're experiencing a recognition problem, not an analysis problem.

Think about how you recognise a friend's voice on the phone. You know it immediately, but if someone asked you to describe the specific frequencies and speech patterns that make it recognisable, you'd struggle. Brand voice works the same way. The people inside a company have heard it so many times that recognition is instant — but articulation is almost impossible.

That's why "it doesn't sound like us" comes without examples or edits. They can't point to the sentence that broke the spell because the spell breaks gradually, across dozens of small choices they can't individually name.

The research most writers skip

Standard client research answers questions like: What industry are they in? Who's their audience? What are they trying to achieve with this piece?

Those are necessary but insufficient. The questions that prevent "doesn't sound like us" feedback are different:

What do they call their product? Not the category — the actual name they use. Do they shorten it? Does it have a trademark symbol they always include?

What do they call their customers? Clients, members, users, partners, guests? This single word appears dozens of times in any piece of content. Get it wrong and every instance signals "outsider wrote this."

What's their sentence rhythm? Short and punchy or longer and explanatory? Do they use lists or avoid them? Headers every 200 words or longer unbroken sections?

What perspective dominates? We-focused, you-focused, or product-focused? Count the pronouns on their homepage if you're unsure.

These details aren't in the brief. They're on the website, buried in existing content, spread across product pages and blog posts. Most writers scan this material for topic ideas. The writers who avoid voice mismatch are reading for something else entirely — patterns of language.

What to do before submitting the next draft

Pull up three pieces of content the client has already published and approved. Not guest posts or press releases — content that lives on their site and represents their voice.

Read them aloud. Not skimming — actually speaking the sentences. You'll hear the rhythm faster than you'll see it. Notice where you naturally pause, where the sentences feel long, where the tone shifts.

Now read your draft aloud. Does it sound like it belongs in the same family? If you can't tell, you're probably too close. Wait an hour and try again.

Check your terminology against their website. Every time you've used a generic industry term, search their site for it. If they don't use it, find out what they use instead.

Look at your sentence subjects. Who's doing the action in most of your sentences — the company, the product, or the reader? Match that ratio to theirs.

When the gap is too wide to bridge manually

Some clients have years of published content with consistent patterns. Reading enough of it reveals the voice. Other clients have a sparse website, inconsistent archives, and a voice that exists only in the founder's head. No amount of research uncovers what isn't documented.

That's the gap BrandDraft AI was built for — it reads the brand's existing pages before writing anything, so the output already uses their actual product names, customer terminology, and sentence patterns instead of your best guess at what they might want.

But whether you're using a tool or doing the research manually, the principle is the same: voice isn't about writing skill. It's about pattern recognition. The writer who sounds like the brand isn't necessarily better — they're better prepared.

Responding to vague feedback

When the revision request arrives without specifics, resist the urge to guess what they meant. Ask a question that gives you something concrete to work with.

"Could you point me to one or two pieces of existing content that really nail your voice? I'll use those as reference for the revision."

That question accomplishes two things. It gets you examples to analyze. And it shifts the client from trying to articulate their voice to recognizing it — the thing they're actually good at.

The revision will go faster, they'll feel heard, and you'll have a reference library for every future piece you write for them.