# X Launch Thread Pack — 10 Original Templates

**SKU:** `x-launch-threads`  
**Price:** $12 USD, paid in USDC on Base  
**Format:** 10 original thread skeletons with fill-ins, a posting checklist, and a fictional worked example  
**Audience:** US indie hackers launching a small paid product on X  
**Promise:** Draft 10 distinct launch threads without copying someone else’s tweet.

These templates are original. They are not scraped famous launches. Replace every `[BRACKET]`. Do not invent revenue, user counts, or waitlist size.

## How to use

1. Pick **one** template that matches what is actually true today.
2. Fill brackets with facts you can screenshot if asked.
3. Cut any line you cannot defend.
4. Post from the account that already talks to this audience. A cold launch thread is still a cold email with line breaks.

**Hard rules**

- No fake MRR, no “500 people waiting,” no borrowed screenshots.
- Name the product, the job it does, the price, and the link in the first 3 posts.
- Pin the thread. Reply to every question for 12 hours.
- If you have zero buyers in mind, do not use Template 1–3. Use Template 7 (search) or 9 (build log).

---

## Shared first post (adapt, then continue with a template)

```
I’m launching [PRODUCT] today.

It does one job: [JOB IN BUYER WORDS].

For [WHO], when [TRIGGER].

$[PRICE] one-time / [CADENCE]. Link: [URL]
```

---

## Template 1 — The honest constraint launch

Use when the product is small on purpose.

1. I’m launching [PRODUCT] with a constraint I will not remove in v1: [CONSTRAINT].
2. I kept seeing [WHO] spend [TIME/MONEY] on [WORKAROUND] every [CADENCE].
3. The workaround fails when [FAILURE MODE]. That’s the only job I took.
4. What it does: [3 bullets, verbs].
5. What it does not do: [3 bullets]. If you need those, don’t buy this.
6. How I use it on my own stack: [3 steps].
7. Price is $[PRICE] because [FLOOR LOGIC — hours or substitute]. Not because “value.”
8. If [OBJECTIVE CONDITION] is missing after you open the file, email me — I’ll refund.
9. Link: [URL]. If you buy, reply “got it” so I know delivery landed.

---

## Template 2 — The teardown-to-product launch

Use when the product came from a public teardown (your own).

1. Last [MONTH] I tore down how [WHO] publish [ARTIFACT]. The boring failure was [FAILURE].
2. I don’t need another [CATEGORY]. I needed [ARTIFACT] I could reuse on launch day.
3. [PRODUCT] is that artifact: [ONE SENTENCE].
4. Inside: [LIST 4 PIECES YOU ACTUALLY SHIPPED].
5. A before/after on a fake but realistic example: before [X], after [Y]. Screenshot in the next post.
6. [attach screenshot — your UI or doc, not someone else’s]
7. Price $[PRICE] · [RAIL]. I will not add a “pro” tier this month.
8. Not for: [WHO SHOULD NOT BUY].
9. [URL]

---

## Template 3 — The “I sold it to N people I already knew” launch

Use only if N is real and they opted in to be mentioned (or stay unnamed).

1. [PRODUCT] is live. I did not “go viral.” I asked [N] people I already talk to.
2. The ask was: “[ONE SENTENCE OFFER].” [N] paid. That is the whole distribution story.
3. What they were already doing: [WORKAROUND].
4. What I handed them: [DELIVERABLE].
5. What I changed after the first two sales: [ONE CHANGE].
6. Public price is now $[PRICE]. Same file.
7. If you are [WHO] and that sentence made you wince, it’s for you.
8. If you want a custom build, that’s a different SKU — don’t buy this expecting a Slack channel.
9. [URL]

---

## Template 4 — The changelog launch (shipping in public, then charging)

Use when you have 2+ weeks of public posts.

1. For [N] days I posted the build of [PRODUCT] in public. Today it has a checkout.
2. Day 1 problem: [PROBLEM]. Day [N] artifact: [ARTIFACT].
3. The posts were not a growth hack. They were my lab notes. The product is the notes, cleaned.
4. What you buy: [LIST].
5. What you already saw for free: [LIST]. Don’t pay if the free notes were enough.
6. $[PRICE]. Link: [URL]
7. Tomorrow I go back to building [NEXT]. This SKU is frozen for 30 days.

---

## Template 5 — The replacement launch

Use when they already pay for a messy stack.

1. If you currently glue [TOOL A] + [TOOL B] + a spreadsheet to do [JOB], that’s the job.
2. [PRODUCT] replaces the glue, not the tools. You still use [TOOL A].
3. Workflow: [STEP] → [STEP] → [DONE].
4. Limits: [LIMIT]. I would rather list limits than demo-magic them.
5. Price $[PRICE] vs the glue cost I kept hearing: [THEIR COST — only if they told you].
6. Install/use time: [MINUTES]. If it takes more, I failed the copy, not you.
7. [URL]

---

## Template 6 — The anti-course launch

Use for a checklist/script/worksheet (like this pack).

1. This is not a cohort, a community, or a 4-week course.
2. [PRODUCT] is a [FILE TYPE] you finish in [TIME].
3. You will produce [NAMED ARTIFACT] or you didn’t use it.
4. Sections: [1] [2] [3] [4]
5. I left blanks. If you publish the blanks, that’s on you.
6. $[PRICE] one-time. No upsell email sequence.
7. [URL]

---

## Template 7 — The search-shaped launch

Use when people already search the job-to-be-done.

1. People ask “[SEARCH PHRASE]” and get threads that sell a lifestyle.
2. I wrote the missing artifact: [PRODUCT].
3. It answers: [Q1], [Q2], [Q3].
4. It refuses to answer: [OUT OF SCOPE].
5. Skim the TOC: [6 HEADINGS].
6. $[PRICE]. [URL]
7. Quote-tweet with the search phrase if this is what you were looking for.

---

## Template 8 — The pairing launch (two SKUs, one thread)

Use only if both SKUs exist and prices are real.

1. Two files, one job: pick [SKU A] if you need [JOB A]; pick [SKU B] if you need [JOB B].
2. Do not buy both unless [CONDITION].
3. [SKU A] — $[P1] — [ONE LINE]
4. [SKU B] — $[P2] — [ONE LINE]
5. I will not bundle them this week. Bundles hide which one worked.
6. Links: [URL A] · [URL B]

---

## Template 9 — The failed-path launch

Use when you tried the long way and killed it.

1. I spent [TIME] trying to make [GRAND PRODUCT]. I killed it.
2. The only piece people asked for was [SMALL PIECE].
3. That piece is now [PRODUCT].
4. I am not “pivoting a startup.” I am selling the piece.
5. Contents: [LIST]
6. $[PRICE]. If you wanted the grand product, it does not exist.
7. [URL]

---

## Template 10 — The quiet Tuesday launch

Use when you refuse launch-day theatrics.

1. No waitlist. No 24-hour discount. [PRODUCT] is $[PRICE] today and Tuesday.
2. Job: [JOB]. Who: [WHO]. Time to first win: [MINUTES].
3. File: [FORMAT]. You can read it without an account.
4. Payment: [RAIL]. I fulfill over email with the file (or a repo path).
5. If this thread is the first time you’ve heard of me, lurk. If you’ve been in the replies, the link is [URL].

---

## Worked example (fictional product — do not copy numbers as real)

Product: **Inbox Friday** — a markdown weekly-review script for US solo founders who already live in Gmail. Price $12. No users claimed beyond “I used it for 6 weeks on my own inbox.”

Filled Template 10:

```
No waitlist. No 24-hour discount. Inbox Friday is $12 today and Tuesday.

Job: run a 25-minute Friday email review without a new productivity app.
Who: US solo founders who already live in Gmail.
Time to first win: one Friday.

File: markdown. You can read it without an account.

Payment: USDC on Base or card, your choice when I enable it.
I fulfill over email with the file.

If this thread is the first time you’ve heard of me, lurk.
If you’ve been in the replies, the link is [URL].
```

---

## Posting checklist

- [ ] First three posts include product, job, price, link
- [ ] Every number is true or removed
- [ ] Screenshot is yours
- [ ] “Not for” line is present
- [ ] Replies you will actually honor (refund, support window) match your terms
- [ ] Calendar block: 12 hours of reply time
- [ ] You sent 10 private notes to people who already asked about this — the thread is not the only distribution

## After 48 hours

Write three lines, privately:

1. Clicks:
2. Questions I had no answer for:
3. The sentence I will change next time:
