Ship-day content kit: changelog entry, in-app modal, 3 tweet variants, LinkedIn post, customer email, and why-this-matters lines.
You shipped a feature on Tuesday and by Thursday nobody knows, because the changelog entry, the in-app note, the posts and the customer email all still need writing. This tool drafts the whole ship-day kit from a short description of what shipped: a changelog entry, in-app release notes with a primary action, three post variants for X (factual, hook-led, founder voice), a LinkedIn post, an email to users with subject and preview text, and a one-line 'why this matters' per feature that you can reuse elsewhere.
Brief used: “Product: Foglamp (made up for this example), error monitoring for serverless, alternative to Sentry but cheaper. Shipped this week: source map upload via CLI (was only via dashboard before), Slack alert grouping (one Slack message per error type per hour instead of one per occurrence), and a free tier bump from 5k to 25k events/month. Audience: backend devs running AWS Lambda or Vercel. Voice: dry, dev-flavored, no exclamation marks.”
## Changelog entry: June 3, 2026
**Source maps via CLI, Slack alert grouping, free tier 5x**
- `foglamp upload-sourcemap` now works from your CI. No more dashboard uploads on every deploy.
- Slack alerts now group by error type per hour. One message instead of 400.
- Free tier moved from 5,000 to 25,000 events/month. No code changes needed.
## In-app release notes modal
**Header:** Three things shipped this week
**Body:**
- CLI source map upload: wire it into your CI
- Slack alerts grouped by hour and error type
- Free tier now 25k events/month (was 5k)
**Primary CTA:** See the CLI docs
**Dismiss:** Got it
## Tweet variants
**Factual:**
Shipped this week on Foglamp:
- CLI source map upload
- Slack alerts grouped by hour
- Free tier 5k → 25k events/mo
No migration. Just shows up.
**Hook-led:**
Your Slack channel does not need to ping 400 times when one Lambda crashes.
Foglamp now groups alerts by error type per hour. One message. Same data.
**Founder voice:**
The number one piece of feedback for 6 months: "please stop spamming our Slack."
Fair. Shipped alert grouping today. Also CLI source maps and a 5x free tier bump because why not.
## LinkedIn post
Shipped three things to Foglamp this week, all of them from user complaints.
One: CLI source map upload. You used to have to upload via the dashboard every deploy. Now it is one line in your CI.
Two: Slack alerts now group by error type per hour. Instead of 400 pings when one Lambda misbehaves, you get one message with the count.
Three: free tier went from 5,000 to 25,000 events per month. No upgrade required: it just shows up next month.
Building error monitoring for serverless and the feedback loop is brutal in the best way. Users tell you exactly what is wrong, you fix it, repeat.
If error monitoring costs you too much today, the free tier is now large enough to actually try.
## Email to users
**Subject:** Slack will be quieter starting today
**Preview:** Plus CLI source maps and a 5x free tier bump.
Three things shipped this week:
1. **Slack alert grouping.** One message per error type per hour, instead of one per occurrence. Your channel will be noticeably quieter.
2. **CLI source map upload.** `foglamp upload-sourcemap`: wire it into your CI and stop the dashboard dance.
3. **Free tier is now 25,000 events/month** (up from 5,000). Nothing to do: it applies from the next billing cycle.
If any of this breaks, hit reply.
{{your_name}}
## Why-this-matters one-liners
- **CLI source maps:** ships source maps from CI so production stack traces are actually readable.
- **Slack grouping:** far fewer alerts on noisy services, the difference between a useful channel and a muted one.
- **Free tier bump:** small projects and side-projects can now use Foglamp without thinking about the bill.Static example. Your own run calls Claude live with your brief.
Solo founders and small SaaS teams shipping features weekly or biweekly who keep falling behind on announcing them. Especially useful if you have a changelog page that has not been updated in two months, or a Twitter account that goes silent between launches. Works for B2B and B2C: set the voice in the brief.
A complete ship-day pack in copy-paste markdown. Changelog entry sized for a docs page or dedicated /changelog route, with date, feature name, and short description. In-app release notes modal copy: header, body, primary call to action, dismiss action. Three tweet variants: one factual ("shipped X"), one hook-led (curiosity opener), one founder-voice (personal context). A longer LinkedIn post, formatted with short paragraphs for easy reading. Email-to-users with subject line, preview text and body, short enough to read on mobile. A why-this-matters one-liner per feature you can reuse in sales decks, support replies, and future announcements. Everything is ready the same day you ship.
You ship every Tuesday. Run this every Tuesday and your changelog, social, and email are done before lunch.
You shipped the thing you have been working on for two months. Get the full announcement stack so it does not die in your /changelog.
Run it batch-style on the 6 features you shipped this quarter but never announced. Use the changelog entries to rebuild your /changelog page.
The why-this-matters one-liners drop straight into sales decks, support replies, and onboarding emails to keep messaging consistent.
Yes. Say so in the brief and the voice adjusts: LinkedIn becomes optional, posts get warmer, the email gets shorter.
Yes. Describe one feature and the pack scales down: same structure, less content.
It writes the content. Posting time / strategy is closer to instant-content-strategy.
Speed and consistency. The kit covers six channels at once, while most founders stop after the changelog entry.