signals
Catch product demand where it already happens.
Amend watches selected Discord, Slack, GitHub, support, portal, and in-app sources without turning every message into a task.
Users asked. You shipped.
Amend closes the loop.
Amend watches selected Discord, Slack, GitHub, Linear, support, and in-app sources, groups repeated customer demand, follows the work through shipping, and updates the people who asked.
Signals
what users keep asking for
Work
what GitHub and Linear say is shipping
Loop
who needs the update next
Product
Feedback is the input. The loop is the product.
Amend is not another voting board. It is product memory for teams that need to know what users want, what the team is building, and who needs the update when it ships.
threads
Turn scattered messages into demand threads.
Repeated asks, bug reports, confused users, votes, and account context roll up into one source-linked record.
shipping
Follow the work through GitHub and Linear.
Issues, PRs, releases, labels, and Linear status changes show whether the team is planning, building, or shipping the request.
follow-up
Update the right people when it ships.
Amend updates internal product history automatically, then queues public changelog, Discord, Slack, email, or widget updates by rule.
What changes
The same request stops showing up as a brand new problem.
Amend connects the messy places users talk with the places your team ships. Less copy paste. Fewer forgotten asks. Better follow-up when the work is done.
The mess
A user asks in Discord. Another opens a GitHub issue. Support hears it again.
Amend treats those as the same product signal when they are actually about the same thing.
The thread
One demand thread keeps the ask, the evidence, and the people waiting.
You can open a request and see who said it, where it came from, and whether work is already moving.
In Slack
Tag Amend like a teammate.
Ask what users want this week, capture a thread, or check whether a shipped PR needs an update.
In GitHub
Merged work can move the product story.
A PR or release can update internal history and prepare the right changelog, roadmap, or user follow-up.
For users
The person who asked should hear when it ships.
Amend can post quietly, react with a receipt, or wait for approval before anything public goes out.
Where Amend shows up
The same tool can play different roles.
Discord might be your public community. Slack might be your team room. Both can be places to listen, places to ask Amend questions, or places to post updates when you allow it.
Listen
Build
Tell
Weight
Request capturedDiscord
Can we export invoices?
Account: Northstar
Thread: billing exports
Work linkedGitHub
PR #428 billing export
Linear: ENG-214
Release: v1.4.0
Update readyWidget
Invoice export shipped
12 users waiting
Post allowed after review
Silent
Watch selected channels and save product signal without posting anything.
Receipt
React or reply when feedback is captured, so users know someone heard them.
Teammate
Let your team tag Amend in Slack or Discord and ask what changed, shipped, or needs follow-up.
Start with GitHub, Linear, Discord, Slack, portal, widget, SDK, and email forwarding. Add Intercom, Zendesk, Stripe, or HubSpot when the extra context is worth the setup.
The record
When someone asks why you built it, the answer is already there.
Original ask
the message, issue, ticket, vote, or widget event that started it
Grouped demand
the duplicate asks, source count, accounts, and people waiting
Build trail
the GitHub PRs, releases, commits, labels, and Linear issues tied to it
Update rules
where Amend can post, where it stays silent, and what needs approval
Follow-up
who heard back after launch and who still needs a reply
How it works
A normal week, with less product archaeology.
Amend keeps working after setup. It watches selected sources, groups real demand, follows GitHub and Linear, and helps the team update people when the work ships.
01
A real message comes in
Discord, Slack, support, portal, widget
Amend only watches the places you picked. A random chat thread does not become a roadmap item by accident.
02
Amend decides if it matters
requests, bugs, complaints, votes, confusion
Noise gets dropped. Useful product signal keeps the original words, source link, customer, and account.
03
Similar asks become one thread
duplicates, GitHub issues, Linear issues, PRs
Ten people asking for the same export turns into one demand thread with receipts, not ten separate chores.
04
Shipping updates the people waiting
roadmap, changelog, email, Slack, Discord, widget
When GitHub or Linear shows the work is done, Amend updates the record and follows your rules for public follow-up.
Internal records can update on their own. Public posts and emails follow your rules.
Read source trace docsPricing
Friendly pricing. No credit meter.
The core loop is included on every hosted plan. Higher plans raise projects, seats, signal volume, history, and processing priority.
Open Source
$0
self-hosted
Run Amend on your own infrastructure with your own provider keys and update policy.
- —Portal, roadmap, changelog, widget, SDK, API, and CLI
- —BYO GitHub, Linear, AI, email, Slack, Discord, and Stripe keys
- —No hosted usage limits from Amend
Builder
$19
per month
For solo founders, open-source projects, and tiny teams shipping in public.
- —All core features, including GitHub, Linear, Discord, Slack, portal, widget, SDK, roadmap, and changelog
- —3 projects, 3 seats, and 10k captured product signals per month
- —AI processing counts useful signals, not raw noise or tokens
Team
$49
per month
For small teams that need more projects, history, automation, and shared review.
- —Everything in Builder with 10 projects, 10 seats, and 75k captured signals per month
- —Higher automation volume, longer history, and priority processing
- —Team digest, Slack/Discord teammate mode, and review queue controls
Growth
$99
per month
For teams with real customer volume across support, community, and product.
- —30 projects, 25 seats, and 300k captured signals per month
- —Support integrations, account context, advanced history, and audit trails
- —Stripe, HubSpot, Intercom, and Zendesk-ready workflows
Scale
Custom
higher volume
For large communities, hosted platforms, or teams that need custom retention.
- —Custom signal volume, retention, processing, and white-label widget needs
- —Security review, migration planning, and priority support
- —Still built for modern teams, not Jira bureaucracy
Hosted plans count useful captured product signals, not raw messages or model tokens. Noise is free. Self-hosted teams can run Amend with their own infrastructure and provider keys.
Close the loop while the request is still fresh.
Connect the customer ask to GitHub, decide what to build, and send the update when it ships.