Name every contributor in the release notes, and tell them they are in
With each release, publish notes that name who contributed: the people who sent fixes, and, added by hand, those who reported the bug or asked for the feature. Then send each person the link. A release with someone’s name in it is one they have a reason to share and to come back to.
By The Marketinque TeamReviewed November 2026
BackedAt least one source behind this play is a platform’s own documentation, a law, a study or a dataset that we read in full, or a checked claim supports it.
In the wiki: Partnerships and referrals
Step 5.8.6 Credit contributors and reporters by name in every release in the SaaS launch checklist · phase 5, Compounding engine
The play
With each release, publish notes that name who contributed: the people who sent fixes, and, added by hand, those who reported the bug or asked for the feature. Then send each person the link. A release with someone’s name in it is one they have a reason to share.
How to run it
- Turn on generated release notes, which list merged pull requests and contributors.
- Group changes by label in .github/release.yml, and exclude bot accounts.
- Add by hand the people who reported the bugs or requested what shipped.
- Send each named person the link on the day it ships.
Watch out for
- Generated notes only pick up pull-request authors; reporters and requesters must be added by hand.
- Ask before naming a customer’s company.
- Credit only: no reward for sharing the release.
Best for
Plays like this one
- The tasteful "Made with" badge on everything users shareAttach a small, tasteful "Made with [product]" mark to everything users share — published pages, exports, reports, invite footers — linking to a landing page, with removal offered as a paid perk. Every artifact your users send becomes a working demo with a signature: the loop that grew Hotmail, Loom, and Calendly.
- Turn a quiz result into a collectible card with its real rarityMake each quiz or tool result a collectible card that shows how rare that result really is, with its own share image and link, and unlock a cosmetic variant on the first share. People share identity and rarity, and every shared card brings a new visitor to the quiz with a reason to find out their own.
- Ask each paying customer for one named introduction, right after a winRight after a customer says something worked, ask who else has the same problem, naming the kind of person you mean, and hand them a blurb to forward unchanged. Early customers mostly come one introduction away, and a customer’s introduction carries its own proof. Report back on every one.
- Trade your first five deliveries for an honest review and a write-upA new service has no proof, so give your first few deliveries free in exchange for an honest review and an anonymised before-and-after you may publish. Each one becomes a case card and a short thread, the label keeps it honest, and five real results persuade more than any claim on the homepage.
Sources
- GitHub Docs: Automatically generated release notes (read in full)
Compiled by The Marketinque Team to our editorial standards.