How do I keep non-technical teammates updated on what engineering shipped?
Keep non-technical teammates updated on what engineering shipped: a plain-language note for every merge, published where sales, support and leadership look.
To keep non-technical teammates updated on what engineering shipped, turn every merged pull request into a short, plain-language note and publish it in one place they already check, such as an internal updates page, an RSS feed in their tools, or a widget, instead of relying on Slack threads and memory. Engammo, a GitHub App, does this automatically: it writes a release note with AI for every merged PR and publishes it to a hosted updates page, a widget, an RSS feed and JSON endpoints.
This is for the people around engineering who need to know what changed but do not read pull requests: product managers, support and customer success, sales, marketing, and leadership. They do not want the diff. They want to know what a customer can do today that they could not do yesterday, and whether anything they promised is now live.
Why non-technical teammates miss what shipped
The information exists, but it lives in GitHub. Pull request titles are written for reviewers ("Refactor export serializer"), not for the account manager who needs to tell a customer the CSV bug is fixed. So people ask in Slack, and an engineer stops what they are doing to answer. Research by Gloria Mark at the University of California, Irvine found it takes around 23 minutes to get back to a task after an interruption. We covered the full cost in the engineering cost of poor release communication.
Weekly update emails and sprint demos help, but they depend on someone remembering to write them, and they arrive days after the change. A reliable system needs three things:
- Coverage: every change that shipped gets a note, not just the ones someone remembered.
- Plain language: each note says what changed for users, not how it was built.
- One place to look: the notes land where non-technical teammates already are, without asking engineering.
How Engammo delivers it
Process
- Install the Engammo GitHub App and pick the repositories to watch.
- Engineers keep merging pull requests as usual. No configuration files or CI pipeline changes are needed.
- When a PR merges, GitHub sends a webhook and Engammo reads the PR title, description, labels and a trimmed summary of the changed files.
- AI writes a title of up to 80 characters that states the benefit, a one-sentence description, and 3 to 5 bullets for non-technical readers.
- The note is tagged from your labels (features, fixes, breaking changes, security and more) and published.
- Anyone on the team can edit, regenerate or hide a note from the dashboard.
Where non-technical teammates see it
- An internal updates page: visible only to signed-in members of your workspace, for changes you are not ready to announce. Switch it to public when you want customers to see it too.
- An RSS feed: public updates pages have a feed that support, success and marketing can follow in the tools they already use.
- A widget: one script tag puts the latest notes inside your product or help center.
- JSON endpoints: pull published notes into internal dashboards and docs.
- Versioned notes: compile every change between two Git tags into one release note for a launch review or a leadership update.
- A Kommander assistant: generated FAQs can be synced to Kommander so it can answer "did this ship?" questions.
Stack, timeline and pricing model
Engammo works with repositories on GitHub.com, including GitHub Enterprise Cloud. Setup takes a few minutes, and each note is ready within seconds of the merge. Notes can be written in English, and the Team plan adds Italian and Spanish. Pricing is a monthly subscription, not a project fee: Starter is $29/month for up to 3 repositories, and Team is $79/month for up to 10 repositories with translations, an updates page without Engammo branding, and Kommander sync. Both include unlimited release notes and AI summaries and a 14-day free trial. Enterprise pricing is custom.
Use cases
Support and customer success
Support follows the RSS feed or the updates page and can see that a fix has shipped without opening a ticket with engineering. They can link the note in their reply, so the customer hears the same wording the team uses.
Sales and account management
Sales checks one URL before a call to see which requested features are live. Notes are written in plain language, so they can be quoted to a prospect without translating engineering jargon.
Product, marketing and leadership
Product managers and marketing get a running feed of everything that shipped, which is the raw material for launch posts and newsletters. Leadership can read a versioned note that compiles everything between two releases instead of asking for a status update. Teams with several repositories see what each one shipped in one dashboard.
Proof
Engammo is built by Gorilli. You can follow what we ship on the Engammo changelog, and see how a pull request becomes a plain-language note in how AI understands pull request context.
Engammo vs the alternatives
| Approach | Who writes the update | Covers every change | Where teammates read it | Effort per release |
|---|---|---|---|---|
| Engammo | AI, from each merged PR, with human edits when needed | Yes, every merged PR | Internal or public updates page, RSS, widget, JSON | None after setup; review notes when you want |
| Slack questions and threads | Whichever engineer is asked | Only what someone asks about | Scattered across channels | An interruption per question |
| Weekly update email or doc | A lead or product manager | What the writer remembers | Inbox or wiki | Collecting and writing, every week |
| Sprint demos and meetings | Engineers, live | Highlights only | The meeting, if you attended | Preparation and meeting time |
| An agency or consultant | The agency, from briefings | What they are told | Whatever channel they set up | Briefing the agency on each release |
| Developer changelog tools (GitHub auto-generated notes, Release Drafter) | Generated from PR titles | Yes, per release | GitHub Releases | Low, but written for developers |
If you also want a written announcement for headline launches, pair Engammo with an announcement tool. See the best changelog tools for SaaS teams for that comparison.
Tips that make the updates better
- Add a "User impact" section to your PR template. Engammo passes it to the model separately, and it is the part non-technical readers care about most.
- Label PRs consistently. A
feature,bugorbreaking-changelabel puts the note in the right category. - Start with an internal page. Let the team get used to the notes before you make them public.
- Point people to one link. Pin the updates page in your support and sales channels, and answer "did this ship?" with the link.
Ready to stop being the human changelog? See how Engammo works or start the 14-day free trial.
Frequently Asked Questions
How do I keep non-technical teammates updated on what engineering shipped?
Turn every merged pull request into a short, plain-language note and publish it in one place they already check, such as an internal updates page, an RSS feed or a widget. Engammo, a GitHub App, writes these notes with AI for every merged PR and publishes them automatically.
How much does it cost to keep non-technical teammates updated on what engineering shipped?
With Engammo, Starter is $29/month for up to 3 repositories and Team is $79/month for up to 10 repositories, with Italian and Spanish translations, no Engammo branding and Kommander sync. Both include unlimited release notes and AI summaries and a 14-day free trial. Enterprise pricing is custom.
How long does it take to set up?
Setup takes a few minutes: install the Engammo GitHub App and pick your repositories. There are no configuration files or CI changes, and each release note is ready within seconds of the pull request merging.
How do I choose the right tool or partner for keeping teammates updated on what shipped?
Check four things: whether it covers every change without someone remembering, whether it writes for non-technical readers, whether it publishes where your teammates already look, and how it handles your code and data. Tools that work from merged pull requests, such as Engammo, cover every change by default.
What makes Engammo different from a typical agency?
Engammo is a product, not an agency. Nobody needs to brief a writer: it reads each merged pull request and writes the note on its own, for a monthly subscription instead of a project fee. Your team keeps control and can edit, regenerate or hide any note.
How do you handle security and data?
Engammo does not clone or index your repositories and does not store raw diffs. When AI summaries are on, selected diff excerpts are sent to the AI provider to write the summary. Data is encrypted in transit with TLS and at rest, and internal updates pages are visible only to signed-in workspace members.