ツイートのアイデア · Product launch
A launch tweet has one job: make the right person understand what you built and who it is for in the time it takes to scroll past. The ones that work name a specific problem, show the product doing something, and give one clear next step. The ones that flop open with "Excited to announce" and never say what the thing does.
このページのツイートはすべてオリジナルで、そのまま投稿しても、アレンジしてもかまいません。角かっこの部分は自分で埋めてください。
These templates cover the whole arc: the weeks before, launch day, showing the product, the update launches that come later, and the honest recap afterwards. Replace every bracket with something concrete. A real number, a real customer type or a real screenshot will do more than any adjective.
I've been building [your product] for [number] months. It does one thing: [one-line job]. Launching [day]. Want a link when it's live?
Two weeks to launch. Still deciding whether to cut [feature]. It works, but nobody in the beta used it. Probably cutting it.
Here's the problem I got tired of: [specific annoying task]. Every week. So I built a fix. Opening it up on [date].
waitlist is at [number] people and I have personally emailed every one of them. that part doesn't scale but it's the best research I've done
Screenshot from [your product], the screen I rewrote four times. Launching [day]. Tell me what's confusing about it.
If you [do specific task] more than once a week, I'd like you to try something before it launches. Reply and I'll DM you access.
Launch checklist, honest version: - landing page: done - pricing: changed it twice today - docs: half - confidence: depends on the hour
Building [your product] in the open for [number] weeks. Here's what the first version looks like versus today. Launch is [date].
One thing I learned from the beta: people didn't want [the feature I thought mattered]. They wanted [the boring thing]. The launch version is built around that.
Picking a launch date is the most stressful calendar decision I've ever made. It's [date]. Saying it here so I can't move it.
[your product] is live. It [does the job] for [who it's for], in [time or steps] instead of [the old way]. Free to try: [link]
Today I'm launching [your product]. It's for people who [specific situation]. If that's you, I'd love your honest feedback.
After [number] months of nights and weekends, [your product] is out. One feature, done properly: [feature].
It's live. [your product] turns [input] into [output]. That's the whole pitch. Link below.
Launched [your product] today. Built it because I needed it. Pricing is [price], there's a free tier, and I read every reply.
Shipping my first product today and my hands are slightly shaking. [your product]: [one-line description]. [link]
We just launched [your product] on [launch site]. If it's useful to you, a comment there helps more than you'd think. If it isn't, tell me why.
New thing: [your product]. You [simple action], it [result]. No account needed to try it.
[your product] is out. What it does: [one line]. What it doesn't do yet: [honest limit]. Who should try it: [audience].
Day one. [your product] is live, the signup form works (checked it eleven times), and I'm here all day answering questions.
Made a tool for [audience] who hate [task]. It's called [your product]. 60-second demo in the video.
launching [your product] today. it's small, it's focused, and it saves me about [time] a week. hoping it does the same for you
Before [your product]: [old process in one line]. After: [new process in one line].
Here's [your product] doing [task] on a real [file, page or account] in [number] seconds. No cuts.
The feature I'm proudest of in [your product] is the one you'll never notice: [invisible detail].
3 ways people are using [your product] that I didn't plan for: 1. [use] 2. [use] 3. [use]
A customer sent me this: [short paraphrased result]. That's exactly the use case I built it for.
If you've ever [frustrating moment], this is for you. [your product] handles it like this: [screenshot or GIF]
Most tools for [category] try to do everything. [your product] does [one thing] and stops there. On purpose.
Quick walkthrough of [your product] in 4 screenshots. Reply with the step that loses you.
What [your product] costs: [price]. What it replaces: [tool or hours]. I tried to make that math obvious.
Real example from today: [task] took me [old time] last month. With [your product] it took [new time].
New in [your product]: [feature]. You asked for it [number] times, so here it is.
Shipped [feature] today. It's the reason [type of user] kept churning, so I'm hoping it fixes that.
Small update, big relief: [your product] now [improvement]. No more [annoyance].
Changelog for this week: - [feature] - [fix] - [fix] - removed [thing nobody used]
The most requested feature in [your product] is finally live: [feature]. Took longer than promised. Sorry, and thank you for waiting.
[your product] [version] is out. Biggest change: [change]. Everything else is fixes you'll feel but not see.
Removed a feature today. [feature] was used by [number or share] of people and broke constantly. Less is easier to keep working.
We rebuilt [part of the product] from scratch. Same buttons, about [number]x faster. Try it and tell me if anything feels off.
Launch week numbers for [your product]: Visitors: [number] Signups: [number] Paid: [number] Not huge. Real.
Thank you to everyone who tried [your product] this week. [number] of you replied with feedback. I'm working through all of it.
What I'd do differently next launch: [lesson]. What I'd keep: [thing that worked].
Launch went quieter than I hoped. [number] signups. Going back to talking to each of them. That's where the next version comes from.
First paying customer for [your product] came in at [time]. I refreshed the dashboard about forty times to be sure.
One week after launch, the most common question is [question]. Answer: [answer]. Adding it to the homepage today.
Launch traffic is gone. Now the actual work starts: getting [number] people to use it every week.
Best feedback from launch week: "[short paraphrased feedback]". Already changed [thing] because of it.
[number] days since launch. What's working: [channel]. What isn't: [channel]. Doubling down on the first.
If you tried [your product] and didn't come back, I'd really like to know why. No pitch, just one reply.
自分らしい文体で作りたいですか?
ReplyKit は、あなたのテーマと文体をもとに X の投稿と返信を下書きします。空の入力欄を開けば投稿を3つ提案し、どの投稿の下でも返信を3つ下書きします。投稿ボタンを押すのは、いつもあなたです。
Chrome に追加(無料)