01 / PLANNED
Keep the source attached
Planned draft records would link each customer-facing statement to the issue or release that supports it.
Release communication · Early research
Publish the change your customers need to understand.
A planned release-note review workspace for small software teams. Connect shipped work to accurate customer updates, audience checks, and publication approval.
Get early access ↗In research · Join the waitlist · No payment required
Designed around product managers and founders turning frequent releases into useful customer updates.
Concept preview · fictional example
| Update | Availability check | Review |
|---|---|---|
| Bulk export | Team plan only | Needs product review |
| Faster search | All workspaces | Copy approved |
| API field change | Migration required | Needs developer notes |
Illustrative sample data. This is a product concept; these features are not available yet.
MADE FOR THE WORK IN BETWEEN↗
THE FRICTION
A merged ticket describes the implementation, but customers need to know what changed for them. Drafts lose the source link, skip availability limits, or reach people who cannot use the feature yet.
THE PRODUCT WE’RE EXPLORING
ReleaseThread, in three parts.
ReleaseThread would turn selected shipped work into a review queue. Each draft would retain its evidence, audience, availability, and approval state before anyone publishes it.
Three planned capabilities we want to validate with early users.
02 / PLANNED
Check availability
A proposed review step would record rollout dates, supported plans, and known limits before publication.
03 / PLANNED
Approve the audience
Planned audience labels would help reviewers choose which customers need the update and which details belong in internal notes.
AN INTENDED WORKFLOW
A clearer next step.
Less work around it.
A focused approach for product managers and founders turning frequent releases into useful customer updates.
- 01
Select shipped work
A future pilot would begin with manually supplied release links; repository integrations would be evaluated separately.
- 02
Write for the affected customer
Draft the outcome, availability, and required next step, with the source still visible.
- 03
Review before publishing
Have an owner approve the text and audience, then export it to your existing publishing process.
HELP SHAPE THE FIRST VERSION
A better workflow starts with your experience.
Join the ReleaseThread waitlist for early-access updates and an optional research conversation.
This product is in research. Planned features and integrations are not available yet.
NO PAYMENT · NO COMMITTED LAUNCH DATEYOU’RE ON THE LIST
Thanks for raising your hand.
Your signup has been received for ReleaseThread. There is no confirmation email to look out for.
Manage your data ↗GOOD TO KNOW
A few useful answers.
Can I publish a changelog today?
No. ReleaseThread is a research waitlist. Draft generation, integrations, approvals, and publishing are planned, not live features.
Will updates be posted automatically?
The proposed first version would require explicit review and export. Joining the waitlist does not connect a repository, contact customers, or publish anything.
How is this different from a public changelog page?
The concept focuses on the work before publication: traceable claims, availability checks, and audience approval. Existing changelog products already cover hosting and distribution.