2026 Q3 in review: an RSS feed
Our response times would improve without adding headcount. It would remove the last manual step before we can automate this. It was the first thing our new hires tripped over.
Common pitfalls
Right now this costs us roughly two hours a week. Our response times would improve without adding headcount.
- Enable an RSS feed.
- Enable changelog email previews.
How it works
Happy to test a beta build if that helps. It would pay for itself in the first month.
Next steps
A rough first version would already be a big improvement. The current flow takes six clicks; it should take one.
curl -sS https://api.example.test/v2/posts \
-H "Authorization: Bearer $BULLETIN_API_KEY"
What changes
This has come up in three separate customer calls this month. Our ops team has a runbook step purely to work around it.
Limits
It would remove the last manual step before we can automate this. Customers ask about this on nearly every onboarding call.
- integrations