Writing Product Copy That Sounds Human, Not a Committee

You will be handed a spec sheet — dimensions, materials, a bullet list of what the thing does — and asked to turn it into copy that sells. The naive failure mode isn't "too technical." It's writing that correctly swaps features for benefits and still reads like nobody. This lesson closes that gap.

Features vs. benefits is the floor, not the ceiling

"Features vs. benefits" is the first thing every copywriting guide teaches: don't say what the product is, say what it does for the customer. That rule is necessary. It is not sufficient, and treating it as the finish line is why so much copy — human and AI-written alike — still sounds hollow.

Business — why stopping at "benefits" still fails. A generic benefit is a feature wearing a costume. "Durable" is a benefit claim, technically. It is also unfalsifiable, forgettable, and identical to what every competitor's listing already says. A benefit only lands when it is specific enough that the reader can picture the moment it matters.

Technical — the fix is specificity, not vocabulary. Don't reach for a punchier synonym for "durable." Reach for the scenario. Take the spec field and ask: durable compared to what failure, in what situation? Then write that situation.

The right column isn't more creative. It's more concrete. If a claim could appear unedited on a competitor's page for a completely different product, it's still a feature in disguise — go one level more specific until it's true of this product only.

Establish a voice before you write a sentence

Business — why voice has to be decided before drafting, not during. Without a fixed voice, an agent defaults to the flattest possible register — safe, adjective-heavy, interchangeable with every other listing on the internet. Voice isn't decoration applied after the facts are assembled; it's the filter that decides which facts to lead with and how the sentence is built. Skip it and every draft has to be re-voiced by hand afterward.

Technical — derive voice from 3 reference adjectives, then translate each into a concrete rule. Pick exactly three adjectives that describe how the brand would talk if it were a person at a dinner party. Three is enough to be specific and few enough to be usable as a checklist on every sentence. Two examples, same product category, wildly different output:

Given the same fact — "charges a phone five times" — voice one writes: "Five full charges before you need an outlet. That's not a spec, that's a Tuesday." Voice two writes: "FIVE phone charges. One battery. Outlets are optional now." Same fact, same claim, structurally different sentences. If two products in different voices could swap paragraphs and nobody would notice, the voice rules aren't specific enough yet — tighten them until the two adjectives sets produce genuinely different sentences on the same input.

The read-aloud test

Business — why this catches what proofreading misses. Silent reading lets awkward phrasing slide past because the eye pattern-matches on word shape, not sound. The ear doesn't. A sentence that looks fine on the page ("Elevate your everyday carry experience") sounds absurd spoken aloud, because no person says it to a friend.

Technical — the mechanical version of the test. Before shipping a draft, read every sentence as if saying it out loud to a specific person (a friend, a coworker — pick one and hold them constant). Flag any sentence that fails one of these:

1. Would you actually say the words in this order? "Elevate your everyday carry experience" fails. "This clips onto your belt so you stop losing it" passes.
2. Could you say it in one breath at a normal pace? If not, the sentence is doing too much — split it.
3. Does it sound like ad copy or like a recommendation? A recommendation ("this is the one that actually survives a diaper bag") reads as trustworthy. Ad copy reads as something to be defended against.

If you can't picture a specific human saying the sentence to another specific human, rewrite it. This is the highest-leverage edit pass available, and it's nearly free — it requires no new facts, only re-hearing what's already written.

AI-copy tells to eliminate on sight

These patterns are specific enough to grep for, mentally or literally, before a draft ships:

• Needless intensifiers. "Incredibly durable," "truly exceptional," "genuinely innovative." The intensifier does the work the specific proof should be doing. Delete it; if the sentence goes limp, the underlying claim was never concrete enough.
• Empty hype verbs. "Unleash," "elevate," "revolutionize," "unlock," "transform." These describe no action a customer can picture taking. Replace with the literal verb: not "unleash your creativity" but "sketch, cross out, and start over without wasting paper."
• Equal-weight feature dumping. Listing eight features in one paragraph, each given the same one-clause treatment, is copy written by someone who hasn't decided what matters. A human recommending a product leads with the one thing they'd tell a friend first, then mentions the rest briefly. Pick the hero benefit — the single fact most likely to close the sale — and give it the most space.
• Symmetric sentence rhythm. Three sentences in a row of identical length and structure ("It does X. It does Y. It does Z.") reads as generated, because real writers vary rhythm without thinking about it. Break the pattern.
• Claims with no failure mode implied. "Reliable," "quality," "premium" describe the absence of a problem without naming it. Name it: not "reliable stitching" but "won't blow out the seam on flight three."

Before/after — same spec, two voices

Spec line: "20,000mAh battery, USB-C PD 65W input/output, weighs 340g."

Generic first draft (fails the checks above): "This incredibly powerful power bank features a massive 20,000mAh battery and will truly revolutionize how you stay charged on the go. Its lightweight design and fast charging make it the ultimate travel companion."

That draft has an intensifier ("incredibly," "truly," "ultimate"), an empty hype verb ("revolutionize"), and zero specific proof — "massive" and "lightweight" are both unfalsifiable. It also fails the read-aloud test; nobody describes a battery to a friend that way.

Voice: confident, warm, a little dry. "20,000mAh, which in practice means five phone charges before you go looking for an outlet. It's 65W, so it charges your laptop too — not just phones. At 340g it rides in a jacket pocket without you noticing it's there."

Voice: playful, loud, exclamation-heavy. "20,000mAh! That's FIVE phone charges from one battery! 65W means it juices up your laptop too — no more fighting over the one outlet at the gate! And it's 340g, so your jacket pocket won't even know it's in there!"

Same spec line, same three facts, same specific proof (five charges, laptop-capable, jacket-pocket weight) — the voice difference is entirely in sentence length, punctuation, and how loudly the facts are delivered, not in which facts got chosen. That's the test for whether a voice framework is actually working: the facts stay identical, the sentences don't.

Checklist before shipping copy

1. Every benefit claim has a specific, falsifiable detail behind it — no adjective standing alone.
2. The three voice adjectives were chosen before drafting, and at least one sentence would clearly fail if written in the other voice.
3. Every sentence has been read aloud to an imagined specific person and survived.
4. No needless intensifiers, no "unleash/elevate/revolutionize"-class verbs, no equal-weight feature dump.
5. One hero benefit gets the most space; everything else is a supporting mention.