Feedjolt
Feedback boards, roadmap and changelog at one flat price
39 followers
Feedback boards, roadmap and changelog at one flat price
39 followers
Feedjolt is a customer feedback board for B2B SaaS teams. Customers post and vote on requests on public or private boards, and you share what's planned and shipped on a public roadmap and changelog. Feedjolt's AI flags likely duplicates for a person to review, and agents work the board over MCP with the permissions a person grants. It connects to Slack and Linear, at a flat price per workspace with unlimited boards, posts and contributors.
We were customers of a feedback tool before we built one. At our last B2B SaaS, customer feedback lived in 4 places: Slack threads, an Excel sheet nobody updated, email, and partial roadmap notes. We shipped the wrong things. Repeatedly. So I built the thing I wished existed.
What's in v1:
⚡ Public + private feedback boards
⚡ Slack triage → Linear ticket in one click
⚡ AI-suggested merges
⚡ Roadmap publishing + changelogs
⚡ Flat pricing, unlimited end users. No per-user trap.
Why I'm here today: I want B2B SaaS folks to roast it. Specifically, what's missing for your feedback workflow, and what would make Feedjolt your daily driver vs. Canny / Productboard?
Free for indie + small teams. Paid tier is flat $39/mo (no end-user counter).
Drop a comment with your worst feedback tool horror story. I'll trade you a 30-day Growth upgrade for the most painful one.
— Marc
@luodaint The "we shipped the wrong things, repeatedly" origin is the honest version of why this category exists, feedback doesn't fail at collection, it fails at the loop back. So the roast, since you asked: AI-suggested merges are great until they're wrong, and a bad merge silently buries a signal under an unrelated one. Two users said different things, the model decided they're the same, and now the smaller cohort is invisible. What's the undo/audit on a merge? And the part Canny/Productboard both fumble: when you ship something from feedback, does the original requester automatically hear "you asked, we built it"? That single closed loop is what turns a feedback tool into a retention tool. Collecting is the easy 80%, closing back is the 20% nobody does well. Upvoted.
@artem_fedorovich , you phrased it better than me. "Fails at the loop back" is precisely how it works.
On AI Merge: it’s AI suggested but not auto done. A human has to confirm each suggestion. Every merge will have an audit trail, and the unmerge brings back the original post and the original voters, no secret burying. Though "collapsing of two cohorts into one" is a possibility, there’s a plan to warn about it when it comes to cross-cohorts merge.
On the closed-loop part: yes. The original requester and all the people who voted will be sent an email saying, "you asked, we delivered the product." That’s the product itself, not an added bonus.
Thank you for the upvote.