How to write a launch listing people actually click

People scan, then decide

Nobody reads a leaderboard. They run their eyes down it looking for something that is about them: their job, their problem, their stack. A listing earns a click when it passes a three-part test in that scan:

1. Can I tell what it is? A category people already know: an invoicing tool, a screen recorder, a CRM.
2. Is it for someone like me? A named group of people, not “teams” or “everyone”.
3. Why would I care? One concrete result: hours saved, a step removed, money collected sooner.

Every part of the listing has a job in that test. The name and tagline answer the first two, the screenshot proves the third, and the description and maker comment are for the people who already clicked and are deciding whether to try it.

The parts of a listing

The name: say it, then explain it

You probably have a name already, and it is probably fine. Names rarely make a launch; unclear names sometimes break one. Two checks are worth doing:

• Can people spell it after hearing it? If someone mentions it in a call, the listener should find it with one search. Swapped letters and missing vowels cost you every word-of-mouth visit.
• Is it the same everywhere? The listing, the website title, the logo and the domain should match, so a visitor who clicks through knows they landed in the right place.

Do not put the description in the name (“Inkwell – AI Invoicing for Freelancers”). That is what the tagline is for, and a stuffed name looks like an ad in a list of products.

The tagline: who it is for and what changes

The tagline does more work than anything else on the page, and 60 characters is less room than it sounds. A shape that works for almost every product:

[What it is] for [who] that [the result they get]

You will rarely fit all three in 60 characters, so drop the weakest part. If the category is obvious from the result, drop the category. If the audience is obvious from the category, drop the audience. Never drop the result.

Taglines that lose the click

• “The future of invoicing.” Says nothing about who it is for or what happens.
• “An AI-powered all-in-one platform for modern teams.” Four buzzwords, no category, no person.
• “Finally, invoicing that doesn’t suck.” Funny once. It tells the reader how you feel, not what they get.

Taglines that earn it

• “Invoices for freelance designers who get paid late” (50 characters). Category, person and problem.
• “Get paid in half the time, without chasing clients” (50 characters). The result, with the pain removed.
• “Turn a Figma file into a client invoice in a minute” (51 characters). The workflow, made concrete.

The first screenshot is your real headline

Most people never read the description. They read the tagline, look at the first image and decide. So the first screenshot is not decoration: it is the proof that the tagline is true.

• Show the result, not the settings page. For an invoicing tool that is a sent invoice with a “Paid” stamp, not the account screen.
• Use real-looking data. “Lorem ipsum” and “Test User 1” make a product look unfinished. Invent a believable customer and fill the screen with their work.
• Crop to the part that matters. A full-browser screenshot shrinks to a blur in a list. Crop to the one panel that shows the result, and make sure the text is readable at thumbnail size.
• Add one short label if it helps. “Reminders go out on their own” above the reminders panel is fine. Five arrows and a paragraph is a slide, not a screenshot.

Order the rest of the images the way you would demo the product: the result first, then the two or three steps that get you there, then anything else. A short video helps if it shows the product working in the first five seconds; skip the logo animation.

The description: answer the next five questions

The people who read the description have already decided they are curious. They are now looking for a reason to say no, so the description’s job is to answer their questions before they leave to go and find the answers elsewhere. In order, those questions are almost always:

1. What problem does this solve, in words I would use?
2. What exactly does it do? Three things, not twenty.
3. Is it for someone like me, and who is it not for?
4. What does it cost, and what is free?
5. Who made it, and will it still be here next year?

Here is a template that answers them in that order. Keep each part short; a description that fits on one screen gets read.

[One sentence on the problem, in your customer's words.]

[Product] [does the main job] so you can [result].

• [Feature 1, written as what the user gets]
• [Feature 2]
• [Feature 3]

Made for [specific group]. Not a fit if you [who should look elsewhere].

[Free plan / trial / price]. [What happens to their data if they leave.]

Built by [who you are, one line]. [What's coming next, one line.]

Saying who it is not for feels risky, but it is one of the most persuasive lines you can write. It tells the right people you understand their situation, and it saves you support emails from the wrong ones.

The maker comment: why you built it

On LarkLaunch you can write the first comment on your own launch when you submit it, and it is posted as soon as the launch is saved. Visitors trust a launch with a founder in the thread, and the first comment sets the tone for everything after it.

You have 280 characters, so skip the feature list (it is already in the description). Say why you built it, and ask for one specific kind of feedback. Specific questions get answers; “Let me know what you think!” gets silence.

I built [product] after [the moment the problem hit you]. It [the one result] for [who].

I'd love feedback on [one specific thing: the onboarding, the pricing, a feature you're unsure about]. I'll reply to everyone today.

Then keep that promise: reply to every comment, including the critical ones, on the day they arrive. A thoughtful answer to a sceptic convinces the dozens of people reading the thread silently.

One listing, before and after

Here is a made-up invoicing tool for freelancers, as many founders would first write it and after the changes above.

Nothing about the product changed. Every edit makes it easier for the right person to recognise themselves, and harder for anyone to misunderstand what they would get.

Where the click lands

A great listing that sends people to a confusing homepage wastes the click. Before launch day, open your site as if you had just read your own tagline and check that the first screen says the same thing in the same words. If the listing promises “invoices for freelance designers” and the homepage says “financial operations for the modern workforce”, people assume they clicked the wrong link.

Two quick checks help here. The meta tag generator shows how your page looks when the link is shared on X, LinkedIn and Slack, which is where many launch-week visitors will first see it. And the UTM builder tags the link on each listing, so you can see which directories actually send sign-ups and not just visits.

Mistakes that cost the click

• Describing the technology instead of the result. “Built on GPT” is how it works. People click for what it does for them.
• Writing for everyone. A tagline that fits every product on the leaderboard fits none of them.
• A first image of your logo. People know what logos look like. Show them the product.
• Hiding the price. “Contact us” on a small tool reads as “expensive”. If there is a free plan, say so in the description.
• Launching and leaving. A listing with unanswered questions in the comments looks abandoned by lunchtime.

The checklist

Questions founders ask