How to Use AI to Write a Company Bio That Sounds Human

Why AI company bios sound fake

A generic prompt produces generic copy because you have asked the model to guess. It does not know your founding year, your customers, or whether you are the wry kind of company or the earnest kind — so it produces the statistical average of a business website, which is filler.

Here is the same landscaping company, described twice. Nothing changed except what the model was given first.

The second version contains no cleverness. It contains a founding year, a count, and one specific commitment — facts the model was handed, arranged in the rhythm of two sample paragraphs it was told to copy.

The invented-award problem deserves its own warning. When your notes are thin, a model produces something plausible to fill the gap — the same behaviour behind AI hallucination in any other work task. On an About page it stings more, because a fake founding date is the kind of error a customer can catch.

The Company Voice File, explained

The Company Voice File is a single document holding three blocks — a Fact Sheet, two Voice Samples, and a Ban List — that you paste at the top of every bio request so all your copy comes out of one source. It is the approach we teach at PromptPeakAI for any writing task where consistency matters more than cleverness.

Each block does one job, and they are not interchangeable:

• The Fact Sheet removes the model’s excuse to guess. Dates, numbers, names, what you actually sell.
• The Voice Samples give it a pattern to copy — sentence length, warmth, how formal you are.
• The Ban List closes off the filler vocabulary it reaches for when it runs out of anything real to say.

The middle block does the heaviest lifting, and it works for a reason worth understanding. Showing a model two examples before making your request is a technique called few-shot prompting. The DAIR.AI Prompt Engineering Guide documents it as in-context learning and few-shot prompting, where examples in your message steer the output without anyone retraining anything.

In practice that means describing your tone rarely works, and demonstrating it almost always does. “Write in a warm, conversational tone” is an instruction the model has to interpret. Two paragraphs of your actual copy are not.

How to Use AI to Write a Company Bio

Four steps, once. The first three build the file and take about twenty minutes; the fourth is the part you repeat forever in a couple of minutes.

Open a blank document and write down everything true about the business without trying to make any of it sound good. Founding year and founder. What you sell and to whom. Real numbers you can defend. One thing you deliberately do differently. If you do not know a number, write “unknown” rather than a guess — that word is load-bearing later.

If your source material is a messy pile of old copy, a transcript, or three years of email, let the model do the sorting first.

You are helping me build a factual reference sheet about my company. You are not writing marketing copy.

Below is raw, unsorted material about the business.

RAW MATERIAL:
[paste your notes, old About page, interview transcript, or anything else you have]

Pull out only concrete, checkable facts and sort them under these headings:
- Founded (year, by whom)
- What we sell, and to whom
- Numbers we can prove
- What we do differently
- What we deliberately do not do

Rules:
- Use only information present in the raw material above.
- Do not add adjectives, benefits, or claims of any kind.
- If a heading has no supporting fact, write "unknown" under it.
- List anything ambiguous under a final heading called "Check these".

Find two paragraphs — a hundred words each is plenty — that already sound the way you want to sound. Your own writing is best: a good email to a client, a paragraph from a proposal, the one page of your site you do not hate. If you genuinely have nothing, borrow from a company you admire that is not a competitor, and use it only for rhythm.

What matters when you pick:

• Sentence variation. Samples with a mix of long and short lines produce output with the same mix.
• Distance. Formal or friendly, plain or literary — the samples set this far more reliably than an adjective does.
• Concreteness. If your samples name real things, the output names real things.

List the specific words you never want to see. Being explicit about what to avoid is one of the most reliable controls you have, and negative constraints work across every kind of AI writing task, not just bios. Here is a starting block — add whatever your own industry overuses.

BAN LIST — never use any of the following:

Words: passionate, seamless, empower, testament, dedicated to excellence, world-class, innovative, solutions provider, best-in-class, thought leader.

Structures:
- No rhetorical questions.
- No sentence that opens by naming the industry ("In the world of logistics...").
- No sentence longer than 25 words.
- No paragraph that ends on a summary of itself.

If a banned word is the only accurate choice, use the plainest alternative instead and flag it to me.

Paste all three blocks into one document with clear headings. Keep it somewhere you can reach in five seconds, because a file you have to hunt for is a file you stop using. You can store it as project knowledge in Claude Projects so it loads with every chat in that workspace, or keep it in a plain note you paste from.

Either way, the file is now the reusable asset — the prompts below are only requests that sit underneath it. It is the same reason a well-built context block improves every AI task you run.

Copy-ready prompts for three jobs

Each prompt below assumes your Company Voice File is pasted directly above it. Without the file they will produce the same filler as any other prompt — the file is what makes them work.

The About page draft

Write the "About" section for our website.

Everything you need is in the Company Voice File above. Follow it exactly.

STRUCTURE:
Paragraph 1 — what we saw that made us start.
Paragraph 2 — what we do about it, and for whom.
Paragraph 3 — one specific commitment, stated plainly.

RULES:
- Use only facts from the Fact Sheet. If something is marked "unknown", write [CHECK] instead of guessing.
- Match the sentence rhythm and warmth of the Voice Samples. Do not reuse their content.
- Use none of the words on the Ban List.
- First person plural throughout: we, our.
- Three sentences per paragraph, maximum.

Standardised team bios

This is where the file earns back the twenty minutes. Twenty-five colleagues will send you twenty-five different registers — one writes a paragraph, one writes a CV, one writes a joke. The file turns all of them into one house format without flattening the people, which is the same problem as keeping one voice across content produced at volume.

Reformat the raw employee note below into our standard team bio.

FORMAT — exactly four sentences:
1. Name, role, and what they are responsible for.
2. Where they came from and one thing they did there.
3. One thing they are known for internally.
4. One human detail, stated dryly.

RULES:
- Third person. Match the Voice Samples above.
- Use only what is in the raw note. Mark gaps as [CHECK].
- Use none of the words on the Ban List.
- Do not upgrade anyone's job title or achievements.

RAW NOTE:
[paste what they sent you, however rough]

One person, three platforms

A founder usually needs the same story at three lengths — the site, a directory listing, a conference programme. Asking three times produces three slightly different companies, so ask once.

Using the Company Voice File above and the details below, write three versions of the same bio. Keep the facts identical across all three.

DETAILS:
[name, role, what they are responsible for, two achievements, one thing they care about]

VERSIONS:
1. Website bio — third person, 100 words.
2. Directory or programme listing — third person, 3 sentences.
3. Short line for a profile or byline — third person, under 25 words.

RULES:
- Same voice in all three. Only length and depth change.
- No word from the Ban List.
- Nothing that is not in DETAILS above.

The same file works on adjacent pages once you have it — a careers page, for instance, where writing a job posting with AI benefits from the same voice samples that made your About page sound like you.

What to paste and what to withhold

Your Fact Sheet is a company document, and some of what belongs in it should never go into a chat window. The line that matters is not free versus paid — it is which kind of account you are using.

On personal accounts across the major tools, whether your conversations are used to improve models is a setting you control, and the default is not always the one you would pick. Business and enterprise accounts are different: they carry a contractual commitment not to train on your organisation’s content. If you are handling anything genuinely sensitive, that distinction is the one to check with whoever administers your tools, and it is worth reading alongside what is actually safe to put into AI at work.

For a company bio this is rarely painful. Almost everything an About page needs is information you are about to publish anyway. The risk sits in the raw material — a strategy deck or an interview transcript you paste in for convenience usually carries far more than the bio requires.

What AI cannot write for you

The Company Voice File fixes the mechanics. It does not fix the harder half, and pretending otherwise is how companies end up with a beautifully written page that says the wrong thing.

One more question deserves a direct answer, because most people writing an About page are quietly worried about it. Drafting the page with AI does not put your site at risk on its own. Google’s own documentation on using generative AI content is explicit that it judges content by whether it is helpful and original, not by how it was produced.

What gets penalised is mass-produced filler with nobody accountable for it. A page built from your real facts, in your real voice, with you editing the result, is not that.

When the bio comes back wrong

Every failure below traces back to a missing or weak block in the file. Diagnose it that way and you stop nudging the model in circles.

Whatever comes back, run one final pass before the copy goes near your site. This is the step most people skip, and it is the one that catches the error a customer would have caught.

Check the draft below against the Fact Sheet in the Company Voice File above.

DRAFT:
[paste the bio]

List, in this order:
1. Any claim in the draft that is NOT supported by the Fact Sheet.
2. Any number, date, or name that differs from the Fact Sheet.
3. Any word from the Ban List that survived.

Do not rewrite anything. Report only.

Then read it aloud. If a sentence is one you would never say to a customer standing in front of you, cut it — that test catches things no prompt rule does.

The real return here is not the first bio. It is that knowing how to use AI to write a company bio this way turns a dreaded annual chore into a file you update in ten minutes when something changes, and every page that draws on it stays consistent without anyone policing it.