Customer feedback to Linear issues.

How it works

1. Feedback lands in Crumb, from the in-app widget, a forwarded email, Slack's /crumb command, or the API. It's tied to the account that sent it and that account's ARR.
2. You decide it's worth building. The inbox shows the dollars behind each request, and related requests group into one initiative, so you can see that four accounts worth $186k are waiting on the same thing.
3. Push it to Linear from the thread sidebar. On Crumb Cloud (Team and up), the issue is drafted for you from the feedback plus your recent Linear ticket titles, so it reads like the rest of your backlog. Tweak it and send.
4. Status syncs back by webhook. Linear stays the source of truth for whether the work is done. Crumb stays the source of truth for the customer relationship.
5. The loop closes itself. When the item hits Shipped, every customer who asked or followed it hears back by email or right in the widget.

Crumb and Linear's Customer Requests

Linear has its own Customer Requests feature, which links requests to issues and can store a customer's revenue, tier, and size. It's a good fit if your feedback already arrives through Intercom, Zendesk, Front, or Slack and your product team lives in Linear.

Crumb covers the parts outside engineering's backlog:

• Customers send feedback from inside your product through Crumb's widget, already tied to their account. No support tool needed in the middle.
• ARR stays current on its own through HubSpot or Salesforce sync, on Crumb's Team plan.
• Raw feedback stays out of Linear. Crumb holds every request, groups related ones into initiatives, and only the work you decide to do becomes an issue.
• The customer hears back. Replies and status changes reach the person who asked, by email or in the widget, and a public roadmap shows what's coming.

Setup

Crumb Cloud: connect Linear in one click from your workspace's integrations, on the Team plan and up.

Self-hosted: bring your own Linear API key, and the same push and status sync run on your own infrastructure. See the docs for details.

Works the same with Jira and GitHub

Crumb pushes to Jira and GitHub with the same flow. For GitHub, your repo's README and file tree give the AI draft extra project context.

Frequently asked questions

Does the Linear integration work when I self-host Crumb?

Yes. On self-host you connect Linear with your own API key and the ticket push and status sync work the same way. On Crumb Cloud it's a one-click connect on the Team plan and up.

Does Crumb replace Linear?

No. Linear stays the source of truth for engineering work and its status. Crumb owns the customer side: who asked, what their account is worth, and telling them when it ships.

Who writes the Linear issue?

On Crumb Cloud (Team and up), AI drafts the title and body from the feedback thread plus your recent ticket titles, so it reads like the rest of your backlog. You review and edit before it's sent. Without AI you write it yourself, same as any other issue.

Can I link several customer requests to one Linear issue?

Group related requests into an initiative in Crumb, and every customer following it hears back when it ships. You see the combined ARR of everyone waiting on it before you push it to Linear.