ホーム / Skills / SNSコンテンツ / X のポスト・スレッド作成(X Thread Writer)
SNSコンテンツ

X のポスト・スレッド作成(X Thread Writer)

AIBarsMITSkill の言語: 英語
ライセンス確認済みスクリプトなし低リスク
デモ実行記録 · claude-sonnet-5-5 · 2026年10月
Turn these notes into an X thread for SaaS founders, in a plain and honest voice, no hype: - In March we moved our app's billing from monthly plans to annual-only. - From our dashboard: revenue per new customer went up 31%. Churn in the first 90 days went from 9.8% to 6.1%. Support tickets about invoices dropped from 120 a month to 45. - The downside: new signups dropped from about 210 a month to about 170. - We offer refunds within 30 days, no questions asked. - Our lesson: the signup drop was real, but the customers who stayed were a better fit. We would do it again, but not for a product with no existing customer base.
Skill: x-thread-writer

Assumptions and open questions

  • I assumed a character limit of 280 per post. Check your account's limit.
  • I used "we" and kept your numbers as given. I added no claims about total revenue, because your notes only give revenue per new customer. Fewer signups at a higher value per customer may or may not net out ahead. If you have the total figure, add it. It would be the first question a founder asks.
  • Your notes don't say how long the data covers or whether anything else changed in that period. Add that if you can.

Shape: A thread. It's a trade-off with several numbers and a conditional lesson, which a single post would flatten. Eight short posts.

First-post options

  1. A result: "We moved to annual-only billing. Signups dropped about 19%. Here's why we'd still do it again."
  2. A contrast: "Annual-only billing cost us about 40 signups a month. It also cut early churn from 9.8% to 6.1%."
  3. A plain statement: "In March we dropped monthly plans. Here's what happened, including the part that got worse."

I recommend option 3, which is the plainest. It's used in the thread below, with the numbers following in the next posts.

Thread

1/
In March we dropped monthly plans and moved our SaaS billing to annual-only.

Here's what happened, including the part that got worse.

2/
The downside first.

New signups fell from about 210 a month to about 170.

That's roughly 19% fewer people signing up. The drop is real, and we didn't find a way to explain it away.

3/
What went up: revenue per new customer, by 31%.

4/
Churn in the first 90 days fell from 9.8% to 6.1%.

Fewer people are leaving early.

5/
Support tickets about invoices fell from 120 a month to 45.

Fewer billing cycles means fewer invoices to question.

6/
We also offer refunds within 30 days, no questions asked.

So paying upfront isn't a one-way door for a new customer.

7/
Our lesson: the signup drop was real, but the customers who stayed were a better fit.

We'd do it again.

8/
One caveat. We wouldn't do it for a product with no existing customer base.

If you're considering it, what would you want to know first? Happy to share more detail.

Edit notes

  • Post 2: I added "roughly 19%" (calculated from 210→170, about 19.05%). Cut it if you'd rather not add a derived number.
  • Post 5: "Fewer billing cycles means fewer invoices to question" is my explanation, not something in your notes. Keep it only if it matches what you saw.
  • Post 6: "isn't a one-way door" is my framing of the refund policy. Cut or reword it if it doesn't match your reasoning.
  • Dropped any hype words and emojis to keep the voice plain.
  • All posts are well under 280 characters.

Extras

  • Image: a simple before/after table of the four metrics (signups, revenue per new customer, 90-day churn, invoice tickets). Alt text: "Table comparing monthly billing and annual-only billing: signups 210 to 170 a month, 90-day churn 9.8% to 6.1%, invoice tickets 120 to 45 a month, revenue per new customer up 31%."
  • Pinned reply idea: share how you announced the change to existing customers, if you're comfortable doing so.
  • Follow-ups: (1) how the 30-day refund policy has worked in practice, if you have the refund rate. (2) What you'd check before switching if you're an early-stage product.

Pre-posting checklist

  • Confirm each number against the dashboard.
  • Make sure post 8's caveat reflects your actual reasoning.
  • Decide whether to add total revenue, since the thread is stronger with it.

I checked every number against the notes: 31%, 9.8% to 6.1%, 120 to 45 and 210 to 170 are exact. The 19% drop in signups is the model's own calculation (40 of 210 is 19.05%) and it flags this in its edit notes. One line in post 2 (we didn't find a way to explain it away) is the model's own wording, not in the notes. Every post is well under 280 characters. Nothing was posted.

できること

アイデア、記事、メモを、X 向けの単発ポスト、スレッド、いくつかの代案に変えます。テーマ、1 つの要点、読者、トーン、アカウントの文字数上限を聞いて適した形を選び、単独で成立する最初の投稿案を 3 つ出し、スレッドを順に組み立てます。フック、背景、1 投稿 1 ポイント、具体的な転換点、そして 1 つの呼びかけを添えた結びの要点です。推敲では、各投稿を文字数上限と照らし、余計な言葉を削り、元の素材に根拠のない内容を外し、削った点を一覧にします。代替テキスト付きの画像案、固定する返信、続きの投稿案も添えます。エンゲージメント狙いの煽りは避け、数字や引用を作ることもありません。

出力

前提、選んだ形、最初の投稿案、番号付きのスレッド全体、推敲メモ、補足、投稿前のチェックリスト。

こんな場面に

X で分かりやすく誠実な投稿やスレッドを書きたい創業者、クリエイター、マーケター。

補足とリスク

低リスク:指示のみのファイルで、スクリプトはなく、ネットワークにも接続せず、ファイルも書き込みません。書くのは文章で、投稿やアカウント連携は行いません。X が現在どう投稿を表示するかは分からないため、リーチは約束せず、文字数の上限はアカウントによって異なります。架空の課金方式変更のスレッドで一度試用し、すべての数字をメモと照合しましたが、何も投稿していません。偽のエンゲージメント、作り話の引用、表示のない広告投稿を避けるよう促します。AIBars 制作(MIT)。