Somebody asks what you're building. You have about one sentence before they decide whether to keep listening.
Most first attempts fail, and they fail in a predictable way. You've been inside this thing for months, so you describe the machinery rather than the point.
You know too much
The core problem is that you and your potential user are in completely different positions.
You know how it works, why each decision was made, and what makes the clever bit clever. So you reach for that: "it's a habit tracker with adaptive scheduling and streak analytics."
They know none of it, and they're not looking for a habit tracker. They're thinking about the thing that annoys them. If your sentence doesn't connect to that, it slides past.
Use their words
The most useful copy tends to be borrowed rather than invented.
When you talked to people back in lesson 1.3, they described their problem in their own language. Those exact phrases are the best marketing material you'll ever have, because they're already what your customer says in their head.
Same with reviews of competing apps. People write, in detail, what's wrong and what they wish existed. That's not competitor research, it's a script.
The gap to watch for: you say "streamline your workflow" and they say "I keep forgetting to send invoices." Their version wins every time, because it's what they'd actually type into a search box.
Say what they get, then what it is
The pattern that works is leading with the outcome and following with the mechanism.
"Your inbox sorts itself" gets attention. "AI-powered email categorisation" gets a nod and no interest, even though it's the same product.
People buy the outcome and then reassure themselves with the mechanism. Leading with the mechanism means they never reach the part they cared about.
Worth checking your own sentence for this. If it describes what your app does rather than what changes for the person, try flipping the order.
The shape of a good line
A structure that reliably produces something workable:
For [specific person], [app] is the [category] that [what makes it different].
Filled in: "For freelancers who forget to chase invoices, Nudge is the tool that sends the awkward reminder for you."
Not poetry, and it does three things at once. Someone hears who it's for, what kind of thing it is, and why it's not the same as everything else. You can shorten it afterwards, but starting from a version that's complete beats starting from something vague.
Test it on strangers
The reliable test costs nothing. Say your line to somebody who doesn't know what you're building, then ask them to explain it back.
If they can, it works. If they hesitate, or repeat your words without meaning, or say "so it's like [something unrelated]," it doesn't. That reaction is information, not a failure.
Five people is plenty. And it has to be people who don't already know, which rules out anyone who's heard you talk about it.
Don't oversell
Tempting when you finally have something to show, and it backfires specifically.
Overselling gets people to try it who were never going to be happy, and they leave disappointed and sometimes write about it. You've spent attention to acquire churn.
A description that's accurate and slightly modest attracts fewer people who fit better. Especially early, when you want your first users to be the ones most likely to stay and tell you useful things.
A quick story. The best line I ever had for my app wasn't written by me. It came from a complaint someone made about the existing apps in that space: they show you a quote, ask you to journal, charge you fifty dollars a year, and skip the hard part.
That one sentence told me what to build and how to describe it. Everything I wrote afterwards was essentially an answer to it.
Which is the actual lesson. I sat and tried to invent taglines for a while and they were all fine and forgettable. The one that worked was overheard. If you're stuck on your description, you're probably reaching for invention when you should be reaching for your notes.
If you want help finding your line
Point three is the useful one. Every builder develops private vocabulary and stops being able to hear it.
Next: Where the first users come from →
Go deeper: Chapter 43, Messaging and Copywriting