Company One-Liner Framework

A one-liner's job is narrow: let a stranger repeat back an accurate version of what you do, five minutes after hearing it once. It doesn't need to be memorable, clever, or persuasive — it needs to be repeatable without distortion.

• It's not a mission statement — those describe intent, not what the company does today
• It's not a tagline — those are built for recall, not accuracy
• It's not a feature list — those describe the product, not the problem it solves

Every stable one-liner is assembled from the same components, in some order. Skipping one is usually why a one-liner sounds fine but doesn't stick.

Customer

Named specifically enough that it excludes someone. 'Businesses' or 'teams' excludes no one and therefore tells a listener nothing.

Problem

The situation causing pain, described in the customer's language — not 'lack of our product,' which is a circular way of describing a problem.

Mechanism / category

The kind of thing you are, so a listener can place you among things they already understand, even roughly.

Outcome

The concrete change that results, stated plainly — without inflating it into a guarantee or a number you can't defend on the spot.

1. Name the customer as specifically as you can — role and company type, not a broad category.
2. State the problem in the customer's own language, not internal product language.
3. Name the category so a listener knows what kind of thing they're evaluating.
4. State the outcome without leaning on a number you can't stand behind if asked.
5. Combine the four into one sentence and read it aloud to someone outside the company.
6. Cut anything they had to ask you to explain.

Almost none. A one-liner states what you do and for whom — it isn't where you make your case. Proof belongs in the conversation that follows, where it can be explained and defended.

• Buzzwords like 'revolutionary,' 'AI-powered,' or 'next-generation' that describe enthusiasm, not the product
• A stacked list of features instead of a single problem and outcome
• Vague outcomes such as 'better,' 'faster,' or 'smarter' without saying at what
• A specific stat you couldn't defend on the spot if someone asked for the source
• Direct comparisons to named competitors — those belong in a sales conversation, not the one-liner
• Humor or wordplay that trades clarity for cleverness

The difference between a weak and a stronger one-liner is almost always specificity in the customer and the problem — not better wordsmithing.

Weak: "We help businesses work smarter with AI."

Stronger: "We help mid-size warehouse operators replace manual shift scheduling with a system that accounts for real-time absences."

Weak: "The all-in-one platform for modern sales teams."

Stronger: "We help B2B sales teams keep their pitch deck, objection answers, and proof points aligned across every rep."

Weak: "Revolutionizing how companies hire."

Stronger: "We help fast-growing companies replace ad hoc reference checks with a documented, repeatable screening step."

• ☐A stranger can repeat it back correctly after hearing it once
• ☐Every claim in it could be explained further in one more sentence if asked
• ☐Nobody had to ask what a specific word meant
• ☐It doesn't depend on a stat you'd need to look up to defend
• ☐Sales, marketing, and the founder would all agree to use it today, unchanged

The same four components can be trimmed or expanded depending on the channel — what shouldn't change is which customer, problem, or outcome is being claimed.

• LinkedIn bio — trim to fit character limits, but keep customer and problem intact
• Pitch deck slide — expand the mechanism into a fuller phrase or sentence
• Sales opener — a spoken version, contractions and a conversational tone are fine
• Elevator pitch — add one supporting sentence after it, not a new claim inside it

• Writing it for insiders who already understand the category, instead of strangers
• Optimizing for cleverness over clarity
• Letting each department maintain its own informal version
• Treating it as permanent even after the ideal customer has narrowed or shifted
• Adding a stat before it's actually been verified

1. Say it out loud to five people outside the company.
2. Note anything they asked you to explain further.
3. Note anything they repeated back incorrectly.
4. Revise only the specific part that caused confusion.
5. Re-test the revised version before treating it as approved.

A one-liner earns its usefulness by staying the same across every conversation, not by being rewritten to fit the moment. That consistency has to be maintained deliberately, or it erodes the same way any other shared fact does.