How to write a launch tweet that gets likes

Most launch tweets get four likes, two of them from the founder's co-founder and mom, and then disappear into the timeline forever. The product might be good. The tweet is usually the problem.

On makers.page specifically, the tweet is not just a nice-to-have. It is the entire mechanic: you quote-tweet the day's launch post, and your rank is the like count that quote tweet earns. A vague launch tweet does not just underperform, it caps how far your product can climb before the board resets. So this is one place where "write a better tweet" is not vague advice. It is the whole game.

This is the anatomy of a launch tweet that gets likes, why the mechanics are different from a regular tweet, and what to change if yours is falling flat.

Why most launch tweets get 3 likes and vanish

Open any founder's launch tweet and you will usually find one of these patterns:

• The feature list. "Introducing X: real-time sync, dark mode, API access, and more." Nobody likes a spec sheet.
• The humble-brag with no context. "Just shipped something I'm really proud of 🚀" with a link and no screenshot. The reader has no idea what they are looking at.
• The thread that front-loads nothing. Six tweets deep before you learn what the product actually does.
• The purely informational announcement. Correct, complete, and completely unlikeable, because there is nothing in it a reader reacts to.

None of these are bad because the product is bad. They are bad because they give the reader nothing to respond to. A like is a tiny act of agreement or admiration. If the tweet does not give someone a reason to feel either, they scroll past.

What the X algorithm actually rewards in 2026

Worth being honest about this, because it changes how you should optimize.

Public analysis of the ranking system in 2026 puts a reply at roughly 27 times the weight of a like, and a full back-and-forth conversation (a reply plus your reply to it) at around 150 times the weight of a like. Rich media, video, screenshots, GIFs, gets meaningfully more distribution than plain text. Posts that make someone stop scrolling and read a thread, or click into replies, get pushed further than posts people glance at and swipe past.

That means the tweet that maximizes reach and the tweet that maximizes raw like count are not always identical. Reach comes from starting a conversation. Likes come from saying something specific enough, or showing something visual enough, that people want to co-sign it publicly without necessarily typing a reply.

For most founders posting a normal update, chase the conversation, replies compound into reach. But if you are specifically optimizing the like count itself (which is exactly what a makers.page leaderboard rank rewards), you want a tweet built to be instantly, visibly agreeable: the kind of tweet where liking it is a lower-effort action than replying to it, but people still want to register that they saw it.

Good news: the same underlying ingredients, a strong hook, real specificity, and visual proof, drive both replies and likes. You are not choosing between two different tweets. You are choosing which one you emphasize slightly harder.

The anatomy of a launch tweet that works

Strip out the fluff and a launch tweet that performs has four parts, usually in this order.

1. A hook that states the outcome, not the feature

Compare:

Introducing TaskFlow: a new project management tool for teams.

versus:

I got tired of watching my team lose two hours a week to status update meetings, so I built a tool that replaces them with a 30-second async check-in.

The first sentence describes a category. The second describes a specific, felt problem and a specific fix. Readers like tweets that sound like they were written by a person who has actually lived the problem, not a press release.

2. One concrete, specific detail

Numbers, mistakes, timelines, or exact customer language make a tweet feel real. "It's fast" is forgettable. "It cut our onboarding time from 12 minutes to 90 seconds" is not.

If you do not have a customer metric yet, use your own build story instead: how long you spent, what you scrapped, what surprised you. Specificity is the actual ingredient, not the category of detail.

3. Visual proof

A screenshot, a short screen recording, or a before/after image consistently outperforms a text-only tweet, roughly 3x by most engagement studies. This is not because people read the image carefully. It is because a visual gives the eye somewhere to land before the reader decides whether to keep scrolling.

Rules for the screenshot:

• Use the real product UI, not a mockup or stock illustration
• Crop out browser chrome and unrelated tabs
• If it is a screen recording, keep it under 15 seconds and make sure the first 2 seconds show something happening, not a static loading state
• One strong image beats four mediocre ones in a carousel

4. A CTA that asks for one specific thing

"Check it out" asks for nothing in particular, so it gets nothing in particular. Better options:

• "Would love feedback from anyone who's dealt with this."
• "Try it free, link below, tell me what breaks."
• "Curious if other [specific role] have the same problem."

A CTA phrased as a question does double duty: it is a request for action and a soft invitation to reply, which is exactly the kind of engagement the algorithm rewards most.

Timing: when to actually post

Engagement velocity in the first 30 to 60 minutes is one of the strongest signals in how far a tweet travels. A tweet that gets 15 replies in the first 10 minutes will outperform one that slowly accumulates 50 likes over 6 hours, even if the second one ends up with a higher total.

Practical implications:

• Post when your actual audience is online, not at a generically "optimal" time from a blog post written for a different timezone. If your early followers are US-based indie founders, a 7 to 9am ET post usually beats a midnight post.
• Be present for the first hour. Reply to every comment immediately. Early replies signal to the algorithm that the tweet is generating conversation, which is the multiplier that matters most.
• Do not post and disappear. A launch tweet posted right before a meeting, with no one watching it for the next two hours, wastes the exact window where velocity is decided.
• Warm the well beforehand. If a handful of people you know will be online at your post time, a heads-up DM ("posting in 20 minutes, would appreciate an early read") is not manipulation, it is priming the first replies that make the tweet look alive to everyone who sees it afterward.

Quote tweets change the math

A quote tweet is not a reply and it is not a like. It puts your commentary in front of a completely different audience, the quoting account's followers, while keeping your original context attached. That is why quote tweets compound differently: each one is a small, independent distribution event, not just a number added to your own tweet.

This is also the exact mechanic behind makers.page. The evergreen launch post from @alexcloudstar exists specifically to be quote-tweeted, and your product's public page and rank come from the like count your quote tweet earns. Which means the advice above is not abstract for anyone submitting there: your quote-tweet commentary is the launch tweet. It needs the hook, the specific detail, and ideally a screenshot, because it is competing for likes against every other quote tweet posted that same day.

A few things specific to writing a strong quote tweet, on makers.page or anywhere else:

• Your commentary should stand on its own. Someone scrolling their timeline may never click into the quoted tweet, so if your added text does not make sense in isolation, you lose them.
• Do not just restate the quoted tweet. Add something it does not already say: what you built, why, or a screenshot of it.
• Keep it short. A quote tweet with three sentences of setup competing for space with the original tweet reads as cluttered. One sharp line usually beats a paragraph.

Before and after: three real rewrites

Weak: "Excited to launch my new app! Link in bio 🎉"

Better: "Built a habit tracker that only asks you one question a day instead of six. Three months in and I've actually kept using it, which never happens with these apps. Link below."

The rewrite adds a specific mechanism (one question instead of six), a personal proof point (three months of actual use), and drops the generic enthusiasm that says nothing.

Weak: "TaskFlow v2 is here with a redesigned dashboard, dark mode, and 40% faster load times."

Better: "Rebuilt our dashboard from scratch because the old one took 4 seconds to load on a bad connection. New one loads in under a second. Screenshot of the before/after below."

The rewrite turns a changelog line into a story with a concrete before/after, and pairs it with the kind of screenshot readers actually want to see.

Weak: "Anyone else struggle with managing client invoices? I built something for that."

Better: "I once sent an invoice to the wrong client and it took three weeks to sort out. Built a tool that locks the client field after you've sent an invoice once, so that specific mistake can't happen again."

The rewrite replaces a vague pain-point question with a specific, slightly embarrassing story, which is far more likeable than a generic prompt, and it explains exactly what the product does along the way.

Common mistakes that kill launch tweet performance

A simple launch-day checklist

Before you hit post:

• Hook is one sentence, states the outcome or problem, not the feature list
• Includes one specific number, story, or piece of customer language
• Has a real screenshot or short clip of the actual product
• CTA asks for one specific thing, ideally phrased as a question
• Scheduled for a time your actual audience is online, and you are free for the next hour
• If quote-tweeting a launch post, the commentary makes sense without anyone clicking through

Reuse this before every launch tweet, not just the first one. Products with staying power keep launching, features, milestones, lessons learned, and each one is a chance to apply the same structure.

Where makers.page fits in

If you have not launched there yet: submit your product, then quote-tweet the day's evergreen launch post with a tweet built the way this guide describes. Once your quote tweet is found, you get a public product page, a dofollow backlink, and sitemap inclusion, no review queue, and your rank on the leaderboard is the like count that quote tweet earns.

It pairs naturally with the rest of a real launch, not as a replacement for it. Pair it with a directory listing strategy beyond just makers.page, and treat the tweet itself as one asset in the first-100-users push described in the zero-budget growth playbook. And if the pressure to keep posting starts to feel like a second job, this guide on building in public without burning out is worth reading before you commit to a daily posting habit you cannot sustain.

Frequently asked questions

How many likes counts as a "good" launch tweet?

There is no universal number, it depends on your existing audience size. A founder with 200 followers getting 30 likes on a launch tweet is a strong result. A founder with 20,000 followers getting 30 likes is underperforming. Compare against your own baseline engagement, not someone else's follower count.

Should I use a thread or a single tweet?

Default to a single tweet with a screenshot. Threads work when you have a genuine story with multiple beats, a mistake, a pivot, a specific build decision, but a single tweet with a strong hook and image usually outperforms a thread padded out to hit a length.

Does posting time actually matter that much?

It matters less than the hook and visual, but it is not nothing. The bigger lever is being active for the first hour after posting, not the exact minute you hit send.

Is it worth paying for X Premium before a launch?

Subscription status is reportedly one input among many in how the algorithm treats an account, but it is not a substitute for a tweet people actually want to engage with. Fix the tweet first.

What if my quote tweet gets zero engagement?

Check the checklist above first, most zero-engagement quote tweets are missing a screenshot or leading with the wrong sentence. If the structure is right and it still underperforms, the issue is usually audience size or timing, not the copy. Keep the tweet, try posting it (or a variant) again at a different time.

The honest summary

A launch tweet that gets likes is not a lucky roll. It has a hook that states an outcome, one specific and real detail, a visual, and a CTA that asks for something specific. Post when your audience is actually online, and stay present for the first hour, because velocity compounds more than total volume.

None of this requires a growth hack or a thread template copied from someone else's launch. It requires writing the same way you would explain the product to a friend who asked what you have been building, then adding a screenshot.

Submit your product on makers.page, write the tweet using this structure, and quote-tweet the launch post. The mechanics are the same whether it is your first launch or your fifth.

Related reading:

• How to get your first 100 users without a marketing budget
• Building in public without burning out
• Where to list your indie product