How to research a client's brand voice in 20 minutes without a style guide

The client sent over a brief at 2pm. Twelve product pages needed rewriting by Friday. When you asked about tone guidelines, they replied with a single sentence: "Just match what's already on the site."

That's the assignment. No brand book. No voice documentation. Just a URL and a deadline.

This is where most writers either waste three hours overthinking it or underthink it and hand in copy that sounds like a different company wrote it. There's a middle path — a focused 20-minute process to research brand voice without a style guide that captures what actually matters and skips what doesn't.

Why most style guides wouldn't help anyway

Here's the thing about the mythical style guide everyone wishes clients had: most of them are useless. They say things like "professional yet approachable" and "authoritative but not stuffy." Those descriptions could apply to 10,000 businesses.

The useful information — specific vocabulary, sentence rhythm, how they handle technical terms, whether they use contractions — almost never makes it into the document. Writers who've worked with detailed brand guidelines know the real voice lives in the published content anyway. The guide just points at it.

So when there's no guide, you're not actually missing much. You're just doing the analysis that would've been necessary regardless.

The 20-minute brand voice research process

Set a timer. Seriously. Without one, website analysis expands to fill whatever time you give it, and most of that extra time produces diminishing returns.

Minutes 1-5: Find the voice-rich pages

Not all website pages reveal voice equally. Product feature lists and legal pages tell you nothing. You need pages where someone made deliberate choices about how to say things.

Start with these, in order of reliability:

The About page — this is where companies try hardest to sound like themselves. The homepage hero section — compressed, considered, usually reviewed by multiple people. Blog posts written by founders or leadership — less polished but more authentic. Customer-facing emails if you can find them quoted anywhere. Avoid: FAQ pages (often written by different people), support documentation (usually stripped of personality), pages that look templated.

Minutes 6-12: Extract the actual patterns

Read those pages with a pen or a blank document open. You're looking for four specific things:

Sentence length patterns. Are they writing tight, punchy sentences? Long flowing ones with multiple clauses? A mix? Count a few. Note the rhythm.

Vocabulary choices. What words do they use that they didn't have to? "Purchase" vs "buy." "Assist" vs "help." "Leverage" vs "use." These aren't random — they reflect positioning. Write down 8-10 specific word choices that stood out.

How they handle complexity. When they explain something technical, do they use jargon confidently or translate everything into plain language? Do they assume knowledge or build it? This tells you who they think they're talking to.

Personality markers. Contractions or no contractions? Exclamation points? Humor? Direct address ("you") or third person? Questions to the reader? Em dashes or parentheses for asides? These small choices create tone.

You're not trying to catalogue everything — you're trying to answer: if I wrote a sentence and showed it to someone who knows this brand, would they say it sounds right?

Minutes 13-18: Build your working reference

Take what you found and write yourself a cheat sheet. Not a formal document — just enough to keep you consistent across multiple pages or a long article.

Format that works: three to five bullet points describing what you noticed, plus five to eight example phrases pulled directly from their site. The example phrases matter more than your descriptions. When you're stuck mid-sentence, you can glance at how they phrased something similar.

Also note what they don't do. If you didn't find any humor, that's a signal. If every sentence is under 15 words, that's a constraint. The absences tell you as much as the presences.

Minutes 19-20: Validate with one comparison

Find a competitor's website. Read one page. Notice how different it sounds — or doesn't. This sharpens your understanding of what's actually distinctive versus what's just industry-standard language.

If your client sounds exactly like their competitors, that's still useful information. Your job becomes matching the industry register, not a unique voice. Less creative, but faster to execute.

Where this process breaks down

Twenty minutes works when the client has enough published content to analyse. Sometimes they don't. A new company might have a three-page website with nothing but placeholder copy. A rebrand might mean everything published reflects the old voice they're trying to escape.

In those cases, you need to infer brand voice from website fragments and whatever context the client can provide — their competitors, brands they admire, how they talk in emails to you. It's less reliable, but most of what writers miss when researching a new client comes from not asking follow-up questions, not from lack of source material.

From research to writing

The temptation after doing this analysis is to write self-consciously. Checking every sentence against your notes. That produces stiff copy.

Better approach: read your cheat sheet once before you start writing. Get the voice in your ear. Then write the first draft without looking at it. Only reference your notes during revision, when you're checking whether a specific phrase fits.

If you've done the full website analysis before writing anything — understanding not just voice but products, positioning, and audience — the voice often comes naturally because you've absorbed the context it grew from.

What happens when you skip this

Writers who don't research brand voice produce one of two failure modes. The first: generic industry content that could appear on any competitor's site. The second: their own voice bleeding through, which sounds fine until the client reads it and says "this doesn't sound like us."

Both get you the same result — revision requests, sometimes extensive ones. Twenty minutes upfront saves hours later.

That's the gap BrandDraft AI was built for — it reads the client's website before generating anything, so the output references their actual terminology and matches their existing tone patterns instead of producing a generic version of the industry.

But whether you're using a tool or doing this manually, the principle holds: voice lives in the details of what's already published. Style guides describe it. The website demonstrates it. When one's missing, the other still works.