Sentence Economy

Every sentence must earn its space. If removing a sentence changes nothing, cut it. Most copy is twice as long as it needs to be. The reader feels the bloat without naming it.

Four tests for whether a sentence pays for itself:

Removal test. Delete the sentence. Does the meaning change? If not, cut.

Opener test. "In order to," "It is important to note that," "The fact is." These openers add nothing. Cut the opener; keep the point.

Length test. Over 25 words? Break at the strongest claim.

Restatement test. Does this sentence restate the headline above it? The reader already read the headline. Cut.

The dead-weight catalogue

| Pattern | Why it fails | Fix | |---|---|---| | "We believe that..." | Softens the claim | Just make the claim | | "X is a Y that helps you Z" | Indirect | "X does Z" | | "Whether you're an A or a B..." | Hedge that weakens positioning | Pick your audience | | "Our mission is to..." | Founder voice | User benefit is what matters | | "Designed to be..." | Tell, not show | Replace with a demonstration | | "Powerful yet simple" | Two dead adjectives | Show one specific quality | | "Featuring" / "With built-in" | Feature-leading | Lead with the benefit | | Restating the headline at end of section | Redundant | Cut entirely |

Every one of these patterns feels natural to write. They read as padding to the scanner.

The before/after

The 44-word version hedges, addresses everyone, and makes an unearned claim. The 9-word version shows what the product does. Every reader on earth prefers the second.

Why bloat happens

Three reasons copy gets long, none of them good:

Padding for "warmth." "Hi there! We're so glad you're here. We just wanted to share..." The padding doesn't add warmth; it adds drag. Warmth comes from voice and specificity, not word count. A sentence that says exactly the right thing in eight words is warmer than a paragraph that says nothing in forty.

Multiple sentences saying the same thing. "Easy to use. Built for ease. Designed with simplicity in mind." Three sentences, one idea, zero proof for any of them. Pick one. Prove it.

Restating the CTA above the CTA. "Click below to get started. [Get started]." The button label is the CTA. The sentence above it is a redundant instruction that the reader didn't need and didn't read.

The 25-word sentence test

Scan the copy for any sentence over 25 words. Most of them contain two ideas compressed into one. Split them. The reader processes short sentences faster, and the break between sentences gives each idea its own weight.

Every sentence must add new information

The strictest version of this rule: read two consecutive sentences. If the second one doesn't add information the first one didn't contain, one of them has to go. This catches the restatement pattern that accounts for most copy bloat.

"Our analytics are real-time. You'll always have up-to-date data." The second sentence restates the first. Cut it.

"Our analytics are real-time. See which feature drives retention before the user churns." The second sentence adds new information: what the user does with real-time data. Keep it.

When length is acceptable

Story openings in longform essays. The point is atmosphere, not density.

Founder letters that intentionally meander. The reader chose to read a personal letter; pacing rules are different.

Reference documentation where every nuance must be spelled out. A missing qualifier in API docs is a support ticket waiting to happen.

In short-form product copy, heroes, CTAs, error messages, and microcopy, economy is non-negotiable. Every word past the necessary ones competes for the reader's attention and loses.