Write Your One-Liner

Why it matters

A one-liner is the sentence you’d say if a stranger asked “what do you do?” and you only had five seconds before they looked away. If it takes longer than that to land, most people won’t wait for the rest. This lesson is about compressing everything you’ve learned in Spark — the problem, the person who has it, what they do today — into one sentence that actually works on someone who has never met you.

The format is simple on purpose: “[Product] helps [who] [do what] without [pain].” Simple doesn’t mean easy. Getting a sentence that tight usually takes several rough drafts, because it’s tempting to hedge, add qualifiers, or try to describe every feature. A good one-liner cuts almost everything so the one true thing lands clearly.

You’ll test three versions on three of your ten people, not by asking “which do you like best,” but by seeing which one they can repeat back correctly a minute later. If they get it right, it worked. If they paraphrase it into something else, it didn’t, no matter how much you like the wording.

This is the Spark gate: your one-liner plus the ten real people you talked to. Passing it means you have a problem worth building for, said in a way people actually understand.

What to watch for

Michael Seibel - How to Plan an MVP

• Watch for how Seibel describes the problem and the customer in a single, plain sentence, with no jargon and no hedging.
• Notice what he leaves out of that first sentence; a one-liner is not a feature list.
• Skip ahead once you’ve got the one-sentence framing; the rest of the talk covers MVP scope, which is next module.

Start with Claude

Bring what you learned from your ten conversations. Claude should push your drafts to be sharper and shorter, not write the final sentence for you — you’re the one who has to say it out loud to strangers.

I'm writing my one-liner for the Spark gate of Make First, in the form: "[Product] helps [who] [do what] without [pain]." Here's what I learned from talking to 10 people about [the problem]: [I'll paste my notes].

Don't write the final sentence for me. Ask me questions about who exactly the "who" is, what the real pain is in their own words, and what "helps them do what" actually means in practice. Then react to my own drafts — tell me honestly where they're vague, too long, or full of jargon, and push me to cut words, not add them. Help me get to 3 tight alternates I can test on real people.