Skip to content
New researchSaaS marketing in 2027
marketinque

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.

Referral invite

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.

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

  1. Turn on generated release notes, which list merged pull requests and contributors.
  2. Group changes by label in .github/release.yml, and exclude bot accounts.
  3. Add by hand the people who reported the bugs or requested what shipped.
  4. 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

Sources

  1. GitHub Docs: Automatically generated release notes (read in full)

Compiled by The Marketinque Team to our editorial standards.

Make this concrete for your product

Try the free idea finder now, or drop your email and we’ll run plays like this for your product end to end.