For founders & CEOs
Your team ships. Tell everyone — automatically.
Every week, a plain-English update of what shipped lands in Slack, in your inbox and on a public page for customers — built from your team's GitHub activity and tickets. Nobody has to write it.
Connect GitHub in 2 minutes · plans from $9/month · cancel anytime
# general
changelogfa.stAppFri 5:00 PM
This week we shipped
Three things customers will notice, one thing they won't.
Customers can pay by invoice
Annual-plan customers can request an invoice at checkout — the most-asked billing request this quarter.
Faster, more reliable exports
Large CSV exports no longer time out. 14 support tickets closed.
A shorter onboarding
New users land in a ready-to-use workspace; sample data loads in the background.
6 internal changes (dependencies, tooling) were left out.
Example — written and sent automatically
Sound familiar?
Your product moves fast. Almost nobody outside the repo can tell.
Customers assume nothing is happening. Your own team can't see their progress. And the “what we shipped” update gets written by you, on a Sunday night, from memory — or not at all.
What Friday looks like
One update. Plain English.
An example of the weekly update — each point is traced back to the real pull requests and tickets behind it. Dependency bumps and internal tooling are filtered out, not summarized.
What your team ships
11 merged PRs · last 7 days
feat: [PROJ-214] invoice payment at checkout
fix: csv export timeout on large datasets
feat: async sample-data step in onboarding
chore: bump dependenciesnoise · filtered
chore: refactor build scriptsnoise · filtered
2 linked tickets
PROJ-214Annual customers can't pay by invoice
PROJ-198Exports over 10k rows time out
What you receive
# general
changelogfa.stAppFri 5:00 PM
This week we shipped
Three things customers will notice, one thing they won't.
Customers can pay by invoice
Annual-plan customers can request an invoice at checkout — the most-asked billing request this quarter.
Faster, more reliable exports
Large CSV exports no longer time out. 14 support tickets closed.
A shorter onboarding
New users land in a ready-to-use workspace; sample data loads in the background.
6 internal changes (dependencies, tooling) were left out.
How it works
- 1Connect GitHub (or GitLab / Gitea) — and Linear or Jira if you use them.
- 2Every week or every release, the merged work and closed tickets become a short update, written in outcomes instead of file names.
- 3It lands in Slack for the team, in inboxes, and on a public changelog page for customers — the same week, told once.
Your developers install nothing and change nothing — no commit conventions, no extra fields, no process.
Make shipping visible.
Two minutes to connect a repo. Your first update covers this week.
Plans from $9/month · cancel anytime