What we hear from PMs
You shipped the feature. What happens next?
Customers ask about features that shipped six weeks ago
They never heard the announcement, so they never tried it. Support fields the same question on repeat. Adoption metrics for that feature look like it was never built.
The changelog update is three weeks overdue
You meant to write it the Monday after the launch. PMM is buried. So it sits, and the next launch piles on top, and the longer you wait the harder it gets to write up.
You don’t want to be the writer
You want to ship great products and watch customers use them. The story-shipping part is overhead, not the craft you signed up for.
You’re worried AI copy won’t pass your bar
A generic update that sounds like every other AI feed is worse than no update. You won’t ship anything that makes the company sound like ChatGPT.
What changes
Tell customers what you shipped, without writing it from scratch
You connect your repos once. PersonaBox surfaces the customer-facing merges, drafts each announcement in your company’s voice, and runs on the cadence you set. You review every draft.
Surfaces the features worth announcing
PersonaBox watches your repos and surfaces the customer-facing PRs your squad merged. You stop digging through merged-this-week reports. The next feature to announce is already on your dashboard, ready to draft.
A real first draft, not a blank doc
You stop writing the changelog from scratch on a Sunday night. PersonaBox drafts each announcement from the PR itself, you read it, edit a sentence, and ship. The work that used to take an hour takes ten minutes.
In your company’s voice, not ChatGPT’s
Bring over your personas, value props, and brand voice once. PersonaBox uses them on every draft so the changelog, the email, and the social post all sound like your company. PMM signs off because it’s on-message.
On the cadence you set
Schedule a weekly changelog update, a monthly announcement email, and the social drops to go with each launch. PersonaBox drafts each one from the PRs that shipped, you review, the customers who would use it hear about it.
Where PMs start
The work that’s on your plate, drafted for you
Three artifacts cover most of the announcement loop. A public What’s New page shows the pace. A product email reaches your subscribers directly. Social posts cover the customers who’d first hear about it on LinkedIn or X.
What’s New page
A hosted What’s New page that updates itself
A public changelog at your domain. PersonaBox writes the entry for each launch, you approve, it goes live without a deploy. Customers see what shipped without you writing it Sunday night.
See the use case →
Product update emails
Announcement emails to your subscribers
Drafted from the merged PR, sent from your verified domain to your subscriber list. No marketing handoff, no two-week queue. The customers who would use the feature hear about it the week it ships.
See the use case →
Launch social posts
Launch posts for LinkedIn and X
Persona-framed drafts in your voice, with on-brand images rendered from your real product UI. The launch post ready to go the day the PR ships.
See the use case →
The customers who’d use it should know it shipped
Connect your repos, bring over your messaging, and PersonaBox handles the first drafts. You stay in the loop and review every word.