Write an X launch thread people can finish

The first post has to work alone

Plenty of people never open the second post. The first one should name the project and the person it is for. "Ledger — local-first expense tracking for indie hackers who close the month in one sitting." is a first post. "Excited to announce" is not, and a naked URL is not.

If someone quotes only that post, they should still know what you made. Write it first, then write the rest of the thread so it earns the click.

One job per post

A thread that gets finished is a short argument, not a changelog. Five to eight posts is enough. More than that and you are publishing a blog post in the wrong format.

• What it is, in one sentence.
• The problem, in the reader's words.
• Who it is for, and who it is not for.
• One or two features a person can picture. Not a tour.
• How to try it: a command, a homepage, or the repository.
• What you want back: a bug, a correction, or a look. Not a demand for reposts.

Stay inside 280 characters

A standard post stops at 280 characters. Longer posts depend on a paid plan the reader may not have, and they break the rhythm. Count the characters with the link included. If a post is over, cut adjectives, not the noun.

Repo2Launch will not emit a post over 280 characters, so the draft you copy is already inside the limit. The limit is not the same thing as a good sentence. Read each post out loud. If you run out of air, it is still too long.

The link is not the hook

The first post is the one that gets quoted. A link in it is fine when the sentence still makes sense if nobody clicks. If the link is the whole post, you have no hook. Later posts can carry the repository and the landing page. Label them. "Source" and "Page" are clearer than two bare URLs.

Do not hide the repository. People who launch open source want the file tree, and they will look for it. Put it in the thread on purpose.

Sound like the person who built it

Write the way you talk about the project to a friend who codes. Specifics beat a tone. "Receipts land in five apps and the month never quite closes" is something a user recognizes. "Revolutionize your finances" is something they scroll past.

Skip the hashtag stack. One tag is noise on a launch thread. Five tags look like an ad. You do not need a meme, a fake scarcity line, or a promise about how many people will star the repo.

After it is up

Stay for the replies for an hour if you can. Answer "how is this different?" with the difference. If a reply shows that the thread described the wrong thing, fix the wording or the README, whichever lied.

A quiet first hour is not a reason to delete the thread. Deleting it trains you to launch only when you already know it will be loud.

How Repo2Launch fits

The free preview drafts the thread from the README and the files that explain the product. You can copy one post or the whole thread from the kit page. The $19 kit lets you regenerate that thread twice, in a punchier, calmer, technical, or playful tone.

It will not post for you. If a sentence is wrong, change it before it goes out. The README is the source, and READMEs omit the caveat you would have said in person.