Do users notice new features?
We're testing whether teams actually struggle to get shipped updates seen by the right users, not just published somewhere.
We're exploring a simpler way for small SaaS teams to turn shipped work into customer-facing release notes, update emails, and release-specific feedback without stitching together four disconnected tools.
Current validation path: GitHub import or manual release items, AI-generated first draft, then human review before publish or email.
We keep seeing the same pattern in small product teams: updates ship in one place, changelogs live somewhere else, announcement emails are manual, and feedback never makes it back to the release that triggered it. We want to know whether that fragmentation is painful enough to solve with one lightweight workflow.
We're testing whether teams actually struggle to get shipped updates seen by the right users, not just published somewhere.
We want to understand whether the current stack is usually changelog plus manual email plus scattered notes, or something even more improvised.
The strongest signal for us is whether post-release feedback is disconnected from the update itself and hard to learn from later.
We're now testing a narrower hypothesis: GitHub or shipped work can seed an AI draft, but a human should still review every field before anything is published or emailed.
They need a faster path from "it shipped" to "users saw it and reacted to it." That means one lightweight loop: import shipped work, turn it into a clear release, publish it, notify subscribers, and capture release-specific feedback in one place.
Start building for free, then add a site plan to go live. Account plans unlock additional features.
For weekly-shipping teams that need a public changelog and release email.
$29/month
Adds richer review workflows, more subscribers, and better collaboration.
$89/month
For larger product teams that need multi-workspace governance and higher volume.
$179/month