Tagline & One-Liner: Write the Single Sentence Your Whole Company Hangs On

Every founder gets stuck on the same eight words. The homepage hero. The pitch deck slide one. The Twitter bio. The "what do you do?" answer at a dinner party. Most founders write five drafts, settle for one that's slightly cringe, and tell themselves they'll fix it later. Twelve months later it's still on the homepage, still slightly cringe, still stopping prospects from converting.

A good one-liner does three things in eight to fifteen words: names the audience, names the outcome, and gives the reader enough specificity to self-qualify. A great one is also surprising — it earns the second sentence. Done well, the right line lifts every other surface — homepage, deck, ads, sales calls, support docs — because they all start from clarity. Done badly, every downstream piece of marketing is rebuilding clarity that should have been settled upfront.

This guide is the playbook for writing a tagline and a one-liner that actually work — without falling into "AI-powered platform for everyone" purgatory.

What Done Looks Like

By end of the exercise:

A tagline (3–6 words) on the homepage hero
A one-liner (8–15 words) under the tagline / in the deck / in cold emails
A 30-second "what we do" answer for verbal intros
Both validated against 5+ prospects in your ICP without explanation needed
A documented "this is the line" so the team stops rewriting it

This pairs with Value Proposition (one-liner is the value prop's tightest expression), Ideal Customer Profile (the line names the ICP — vaguely or precisely), Brand Voice (tone is consistent across surfaces), Landing Page Copy (one-liner is the headline), Pitch Deck (slide 1 is your one-liner), and Founder Story (your story explains why the line, not just what it says).

Tagline vs One-Liner — They're Different Jobs

Founders often conflate these. They're not the same.

Help me distinguish the tagline and the one-liner clearly.

**Tagline (3–6 words)**

A tagline is a brand mark — something that lives next to your logo. Its job is to be memorable, not informative. The reader doesn''t learn what you do from a tagline; they remember a feeling.

Examples:
- Stripe: "Payment infrastructure for the internet"
- Linear: "Built for modern software teams"
- Notion: "One workspace. Every team."
- Vercel: "Develop. Preview. Ship."
- Figma: "Nothing great is made alone"

A tagline can be aspirational, oblique, or vibes-driven. It''s the rhythm next to the logo.

**One-liner (8–15 words)**

A one-liner is informational. Its job is to make a reader who has never heard of you understand who you''re for and what you do, in one sentence, with enough specificity to self-qualify.

Examples:
- Linear: "Linear is the project management tool for high-performance teams shipping software"
- Cal.com: "Cal.com is open-source scheduling infrastructure for individuals and teams"
- Plausible: "Plausible is privacy-friendly Google Analytics built in Europe"
- Resend: "Resend is the email API for developers who care about deliverability"
- Stripe Atlas: "Stripe Atlas helps founders incorporate, hire, and run a US business from anywhere"

The one-liner sits under the tagline on the homepage. It carries the explanation; the tagline carries the feeling.

**Most founders need to optimize the one-liner first.**

The tagline is downstream. Without a working one-liner, the tagline is decoration on something nobody understands. Get the one-liner sharp; the tagline emerges later (or stays vibes-y, that''s fine).

Output:
1. The current tagline (if any) and current one-liner
2. Which one is the bigger problem right now
3. The decision: focus on the one-liner first

The biggest unforced error: writing a clever tagline before a clear one-liner. "Move at the speed of thought" sounds great but tells nobody what you do. Sharp the one-liner first; let the tagline catch up.

The One-Liner Formula That Works

There's a structure that produces working one-liners reliably. Use it as a starting point; iterate from there.

Help me draft a one-liner using the proven formula.

**Formula 1 (the workhorse)**:
"[Product] is the [category] for [audience] who [pain or aspiration]"

Examples:
- "Linear is the project management tool for high-performance teams shipping software"
- "Stripe Atlas helps founders incorporate, hire, and run a US business from anywhere"
- "Plausible is privacy-friendly Google Analytics built in Europe"
- "Cal.com is open-source scheduling infrastructure for individuals and teams"

**Formula 2 (job-to-be-done)**:
"[Product] helps [audience] [verb] [outcome] without [pain]"

Examples:
- "Resend helps developers send transactional email without deliverability headaches"
- "Loops helps SaaS teams send onboarding emails without a marketing degree"
- "Hyperline helps B2B SaaS teams handle billing without writing custom code"

**Formula 3 (the comparison)**:
"[Product] is [competitor or category], but [differentiation]"

Examples:
- "Plausible is Google Analytics, but privacy-friendly and lightweight"
- "Linear is Jira, but built for engineering teams who care about speed"

Use Formula 3 sparingly — it''s direct but invites the customer to compare you point-by-point. Best for products with clear, defensible differentiation.

**Formula 4 (the outcome lead)**:
"[Outcome] for [audience]"

Examples:
- "Postmark: Reliable email delivery for transactional and marketing emails"
- "Tally: Forms made simple, free for everyone"

Lighter; works for products where the outcome itself is interesting.

**Try all four. Compare. Pick the one your ICP responds to.**

For my product:
1. Define the audience precisely (per [Ideal Customer Profile](ideal-customer-profile.md)) — not "everyone," not "B2B SaaS"
2. Define the outcome / pain in the customer''s words (from [Customer Discovery Interviews](customer-discovery-interviews.md))
3. Apply each formula
4. Read each variant aloud — does it sound like something a real person would say?
5. Test 3 variants on 5 prospects (per the validation step below)

Output:
1. Three variants from formulas 1, 2, and 4
2. The audience and outcome statements feeding each variant
3. The variant I''m starting with

The single biggest improvement: specifying the audience. "For everyone" is a dead end. "For high-performance teams shipping software" is alive. The line is sharper as the audience narrows; resist the urge to broaden it for fear of excluding buyers.

What Makes a One-Liner Bad

Most bad one-liners share the same patterns. Learn to recognize them.

Audit my one-liner for the common failure modes.

**Failure mode 1: Generic AI/ML/platform language**
- "AI-powered platform for X"
- "The all-in-one solution for Y"
- "The future of Z"
- These say nothing. The reader gets no signal about audience, problem, or differentiation.

**Failure mode 2: Buzzword stacking**
- "End-to-end agentic data orchestration platform leveraging next-generation embeddings"
- Each word individually OK; together = nobody understands.

**Failure mode 3: "For everyone"**
- "For teams of any size in any industry"
- A tagline that includes everyone repels everyone. The good ones name a specific audience and trust the reader to know if they''re in it.

**Failure mode 4: Inside-out language**
- "Powered by our proprietary inference engine"
- The reader doesn''t care about your stack. They care about their outcome.

**Failure mode 5: Aspirational vagueness**
- "Unleash your team''s potential"
- "Reimagine your workflow"
- These are not one-liners. They''re placeholder cliches.

**Failure mode 6: Trying to land too many points**
- "The CRM, project tracker, and customer support tool that integrates with everything for B2B SaaS teams who want one place for all customer data"
- 27 words covering 5 things. Cut to 12 words covering 1 thing.

**Failure mode 7: Excessive cleverness**
- "We don''t do email; we do conversations" (when you... actually do email)
- Cleverness without clarity is just confusing.

**Failure mode 8: Wrong-level abstraction**
- "We help you build better software" (true of any dev tool ever)
- "We help you ship faster than your build pipeline can keep up" — tighter, more specific

For my current one-liner:
1. Run it against the 8 failure modes
2. Note any that apply
3. Rewrite to fix them

Output:
1. The failure modes my current line falls into
2. The rewrite that fixes them
3. The two variants I''ll test against the original

The most common failure: generic language that could describe any product in your category. If you swap your product name for a competitor''s and the line still works, your line is too generic. Add specificity.

Test It Against Real People

A line that sounds great in your head and a line that works on a stranger are different lines. Test before committing.

Help me run the one-liner test.

The five-prospect test:

Find 5 people who match your ICP — ideally not customers yet, ideally not friends.

For each:

**Step 1: Show, don''t explain**
- Show them just your one-liner (no logo, no context, no demo)
- Ask: "What do you think this product does? Who is it for?"
- Don''t coach them; let them stumble

**Step 2: Score the response**

Score 1: They got it right without help. ("It''s [accurate description] for [right audience].") This is what good looks like.

Score 2: They got the audience right but the function wrong, or vice versa. The line is partially working.

Score 3: They got both wrong, or said "I have no idea." The line is broken.

**Step 3: Probe**
- Ask: "Would you click through to learn more, or would you scroll past?"
- Ask: "What about this language stuck out — positively or negatively?"
- Ask: "What would you have called this kind of product?"

**Step 4: Aggregate**
- 4+ Score 1s of 5: ship it
- 3 Score 1s of 5: tighten and re-test
- 2 or fewer: rewrite from scratch

**Anti-patterns to avoid in testing**:
- Asking your friends (they''ll be polite, not honest)
- Asking your investors (they want to like it)
- Showing the website (the rest of the page can carry weak copy; the line should work alone)
- Coaching when they get it wrong ("Well, what we mean is...")
- Treating one yes as validation

**Variations to test**:
- Test 2-3 variants in parallel; you can compare which lands better
- For each variant, fresh prospects (don''t test the same person on multiple variants — biases them)

Output:
1. The list of 5 prospects + how to reach them
2. The 2-3 variants you''re testing
3. The interview script
4. The aggregation rule for "ship vs rewrite"

The single biggest gap between founder confidence and reality: what you think the line says vs what a stranger reads. A founder who hasn''t tested with real strangers is shipping on hope. The 5-prospect test is one afternoon; the bad-line tax compounds for years if you skip it.

The Tagline (After the One-Liner Works)

Once the one-liner is clear, the tagline can be looser. It''s allowed to be vibes; it''s not allowed to confuse.

Help me write the tagline.

The tagline patterns that work:

**Pattern 1: Compressed value prop**
- Stripe: "Payment infrastructure for the internet"
- Linear: "Built for modern software teams"
- Vercel: "Develop. Preview. Ship."
- Cal.com: "Scheduling infrastructure for everyone"

A tighter version of your one-liner. Same idea, fewer words.

**Pattern 2: Verbed action**
- Vercel: "Develop. Preview. Ship."
- Notion: "Write, plan, share."
- Resend: "Build. Send. Track."

Verbs only. Implies what the user does with you. Works when your product enables a clear sequence.

**Pattern 3: Aspirational mark**
- Figma: "Nothing great is made alone"
- Apple: "Think different"
- Slack: "Where work happens"

Doesn''t describe the product; sets a tone. Risky for early-stage startups whose audience doesn''t know them yet — most readers prefer to learn what you do before being inspired.

**Pattern 4: Category claim**
- Loom: "Async video for work"
- Zendesk: "Champions of customer service"

Stakes a position. Works for category leaders or wannabes; weak for products without category clarity.

**For most early-stage indie SaaS in 2026**:

- Use Pattern 1 (compressed value prop) — it''s the safest and the easiest to test
- Move to Pattern 2 or 3 after you have brand presence

**Anti-patterns**:
- Two-clause taglines with conjunctions ("Smarter X and faster Y") — usually one of the clauses is weaker
- Taglines with "the" + superlative ("The best...", "The leading...") — investors and prospects don''t believe you
- Taglines with adjectives ("Smart, fast, simple") — generic; could be anything
- Taglines that contradict the one-liner — confuses the reader

For my product, write 5 tagline candidates using Pattern 1 (compressed value prop). Rank by:
- Memorability (after reading once, can you recall it 30 seconds later?)
- Specificity (does it imply a category or audience?)
- Honesty (could a competitor truthfully use the same line? If yes, it''s too generic)

Output:
1. Five tagline candidates
2. The ranking
3. The chosen tagline
4. The plan to test it on the homepage hero with the one-liner below

The hardest constraint: memorability without information loss. A 4-word tagline that nobody can summarize after one read isn''t doing its job. Write five; pick the one that comes back to you 10 minutes later.

Where the Line Goes

Once the line works, deploy it consistently. Inconsistency dilutes the line every time it''s rewritten.

Where the one-liner shows up:

**Visible surfaces (matters most)**:
- Homepage hero (under the tagline)
- Pitch deck slide 1
- Twitter / LinkedIn / GitHub bio
- Email signatures (founders, sales)
- Cold outreach opening (per [Cold Outreach](../3-distribute/cold-outreach.md))
- Job postings (recruiting; first sentence)
- Product Hunt launch description (per [Product Hunt](../5-launch/product-hunt.md))
- About page first paragraph

**Indirect surfaces (matters too)**:
- Slack profile blurb
- Founder calendar event description
- Press releases first sentence
- Podcast intros (your own and guest spots)
- Investor updates
- App store listings

**Internal surfaces**:
- Team handbook / README
- Onboarding doc for new hires
- Hiring scorecard ("does this candidate understand what we do?")

**The consistency rule**:
- Same line, verbatim, across all visible surfaces in the first 6 months
- Variations only AFTER the line is established (and ideally only minor: "for X" / "for X teams" — not full rewrites)
- Update the line everywhere if you change it (don''t leave the old one floating)

**The version-control rule**:
- The line lives in your team handbook / Notion / GitHub repo as the source of truth
- Anyone editing the homepage / deck / bio pulls from there
- "What''s our one-liner?" should have a single answer, instantly

Output:
1. The full inventory of where the one-liner lives
2. The audit: are they all the same line right now?
3. The plan to update inconsistent surfaces
4. The source-of-truth doc and where it lives

The biggest dilution: letting each surface evolve its own one-liner. Six months later you have five slightly-different versions and the team can''t agree which is canonical. Write it once; deploy it everywhere; update everywhere when you update.

Update It (But Not Constantly)

The line will change as the product, market, or ICP evolves. Plan for the update; don''t resist it.

The update cadence:

**Quarterly check** (lightweight):
- Is the line still accurate?
- Does the audience description still match the customers we''re actually winning?
- Is the outcome still the right one to lead with?
- If yes to all: keep it
- If no: queue an update

**Annual rewrite** (deeper):
- Run the 5-prospect test again with current ICP
- Compare current line against where the product has gone
- Decide: minor tweak vs full rewrite

**Trigger-based updates**:
- Major pivot or new product line: rewrite
- New ICP segment dominates revenue: rewrite for them
- Competitive positioning shift: rewrite to differentiate
- Founder rebrand or name change: rewrite

**Don''t update**:
- Because you''re bored of the line (everyone is bored of their own line; customers aren''t)
- Because a new investor / advisor / friend suggested something
- Because you saw a competitor''s line and got jealous

**The consistency principle wins**:
- A merely-OK line, repeated for 18 months, beats a perfect line rewritten quarterly
- Brand recognition compounds with consistency
- Resist the rewrite urge unless trigger-based

Output:
- The quarterly check schedule (recurring calendar event)
- The next annual rewrite date
- The trigger list — what events would force an off-cycle rewrite

The discipline most founders lack: leaving a working line alone. The dopamine of a fresh draft is real. Customers never feel it; they feel the consistency.

What "Done" Looks Like

A working one-liner / tagline pair in 2026 has:

A clear, specific one-liner using one of the proven formulas
A tagline that supports (doesn''t contradict) the one-liner
Validation from 5+ ICP-matching strangers without explanation
Consistent deployment across homepage, deck, bios, outreach, and internal docs
A single source-of-truth document the team pulls from
A quarterly check + annual rewrite rhythm
A discipline of NOT rewriting until a trigger justifies it

The hidden cost of a weak line isn''t the homepage hero — it''s every conversation, email, deck, and ad downstream that has to compensate for it. A good one-liner makes every other piece of marketing easier; a weak one taxes everything. One afternoon writing it well saves a year of working around it.