Start / Skills / Social-Content / X-Posts und Threads schreiben (X Thread Writer)
Social-Content

X-Posts und Threads schreiben (X Thread Writer)

AIBarsMITSprache des Skills: Englisch
Lizenz geprüftKeine SkripteGeringes Risiko
DemoEchter Lauf · claude-sonnet-5-5 · Oktober 2026
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.

Was es tut

Macht aus einer Idee, einem Artikel oder Notizen einen Einzelpost, einen Thread oder mehrere Alternativen für X. Es fragt nach Thema, der einen Kernaussage, Zielgruppe, Tonfall und dem Zeichenlimit des Kontos, wählt die passende Form, liefert drei eigenständige Varianten für den ersten Post und baut den Thread Schritt für Schritt auf: Hook, Kontext, ein Punkt pro Post, ein konkreter Wendepunkt und ein Schluss mit Kernaussage und einer Aufforderung. In der Überarbeitung wird jeder Post gegen das Limit geprüft, Füllwörter fallen weg, alles, was die Quelle nicht stützt, wird entfernt, und die Streichungen werden aufgelistet. Dazu kommen eine Bildidee mit Alternativtext, eine anzupinnende Antwort und Folgeideen. Es vermeidet Engagement-Köder und erfindet nie Zahlen oder Zitate.

Ergebnis

Annahmen, die gewählte Form, Varianten für den ersten Post, der vollständige nummerierte Thread, Anmerkungen zur Überarbeitung, Extras und eine Checkliste vor dem Posten.

Gut für

Gründer, Kreative und Marketer, die klare, ehrliche Posts und Threads für X schreiben wollen.

Hinweise & Risiken

Geringes Risiko: reine Anweisungen ohne Skripte, ohne Netzwerkzugriff und ohne Dateischreibzugriffe. Es schreibt Text und veröffentlicht nichts und verbindet sich mit keinem Konto. Es kennt die aktuelle Ausspielung von X nicht und verspricht keine Reichweite; das Zeichenlimit hängt vom Konto ab. Einmal mit einem fiktiven Thread zur Umstellung der Abrechnung getestet, alle Zahlen wurden mit den Notizen abgeglichen; es wurde nichts gepostet. Es warnt vor gekauftem Engagement, erfundenen Zitaten und nicht gekennzeichneten bezahlten Beiträgen. Original von AIBars (MIT).