This page is for people shipping a product, whether it is at $0 or long past it. It is not a playbook for fake build-in-public. If you post a revenue, user or churn figure, it should be one you would also stand behind in a due-diligence room. If you cannot, leave the number out and describe the decision.
The useful SaaS post is often a small, dated change plus the reason. A vague “we have been working hard on reliability” does less than “we cut the webhook retry window from 24 hours to 90 minutes, because support tickets were about delayed events, not failed ones.”
Post types that fit a product company
- A changelog in spoken language. What a user can do now that they could not do on Monday, and who should care.
- A pricing or packaging decision and the failed alternative. People reply when you show the trade-off, not the price table alone.
- A feature you removed, and the support volume or complexity that justified it.
- A support pattern. The ticket you keep getting, the docs you rewrote, the default you changed.
- A constraint of the product you will not pretend to cover. Honesty here is more useful than a feature matrix.
- A short build log with a date, a commit-sized unit of work, and what is still broken. No fake “day 47: $12,440 MRR” graphics.
Example posts you can adapt
Concrete-fact hook · example
We turned off CSV export of raw webhook logs today.
It was used by 11 accounts, and two of them were exporting 4 million rows at a time, which froze the workspace for everyone else. If you still need a dump, there is a dated export job under Settings → Data, limited to 90 days.
Question + list · example
If you are choosing a billing tool this quarter, these are the three questions I would ask before the demo:
1. Can you change a price without breaking existing invoices?
2. What happens when a tax rate changes mid-cycle?
3. Who owns the failed-payment emails — you or the tool?
We picked the boring answers, not the prettiest dashboard.
We delayed the public API by six weeks so we could remove a field.
The field was “plan_name”. It looked harmless. It would have locked our packaging to strings we already want to change. The API now returns plan IDs only.
Shipped this morning: you can now require approval from a second person before a workspace deletes a production dataset.
It is off by default. Turn it on under Settings → Safety. We added it because two customers asked after a close call, not because it looks good on a comparison page.
Support pattern · example
The ticket we answered 40 times in October was not a bug. People were pasting an API token into the “workspace ID” field.
We relabelled the field, added an example value, and rejected tokens with a specific error. Tickets dropped. The docs were not enough.
Pricing decision · example
We are not adding a $9 “lite” plan.
We modelled it. It would have moved the accounts that already write in for discounts, and it would have split support into two products we cannot staff. The starter plan stays at $29, with a 14-day trial, no card on day one.
Very short hook · example
If your churn email apologises twice, rewrite it.
Say what will be deleted, when, and how to export. That is the whole job of the email.
Week of 10 November: we replaced the home-rolled queue with the one our host already runs.
Result so far: retry visibility is better, and we lost the custom dashboard I liked. We still have a backlog of delayed jobs from the old system to drain. I will post when that number is zero, not before.
These are original example drafts, written for this page, for a fictional professional. They are not real posts from a real account, and they are not a promise of reach, clients or sales. Adapt the structure; replace every fact with one you can stand behind.
What to skip
Do not post someone else’s revenue screenshot style with made-up numbers. Do not dunk on a named competitor with claims you have not measured. Do not announce a waitlist with no description of the product. And do not use “we 10x’d conversions” without the baseline, the date range and what else changed in the same week.
Paste a ship note and a few of your old posts into the free X Post Writer if you want 10 tones of the same changelog. Then check every figure against your dashboard.