One-liners that work

The one-liner is the highest-leverage sentence you will write. It’s the tweet, the header, the answer at the dinner party, the thing your first hundred users repeat on your behalf. Most builders write it last, as an afterthought. It should be written first, and everything else generated from it.

Five compressions, applied in order, get you there.

“AST parsing across module boundaries” is how it works. “Delete dead code with one command” is what happens. Nobody buys mechanisms. Lead with the after-state; the mechanism is the FAQ’s job.

“Powerful, seamless, intelligent”: every product claims these, so they carry zero information. Verbs can’t lie as easily: delete, catch, ship, stop, never. If your one-liner has an adjective doing the heavy lifting, you haven’t found the verb yet.

Clever earns a smirk. Specific earns a click. “Know where your money went before it’s gone” beats any pun about budgeting you’ll ever write. When in doubt, choose the sentence that could only describe your product.

Take your current description and ask “so what?” until the answer is something a human wants. “It writes tests”, so what?, “bugs get caught in CI”, so what?, “you ship Friday without fear.” Stop one step before it becomes generic. That’s your altitude.

Delete a word. Still true? Delete another. The sentence is done when removing one more word makes it false or vague. “Never lose touch with the people who matter” survives this test. “A smart relationship management platform for your personal and professional network” does not survive contact with anyone.

Then say it out loud to a friend and watch their face. The face is the metric. If they ask a curious question, ship it. If they nod politely, compress again.