
Feedjolt
65 posts

Feedjolt
@feedjolt
The simple way to collect, prioritize, and ship customer feedback. Flat pricing. Unlimited users. Built for dev teams. Feedjolt!
Katılım Nisan 2026
30 Takip Edilen4 Takipçiler
Sabitlenmiş Tweet

Paying $400/mo for feedback boards because Canny charges per end user?
We built the flat-priced version. Unlimited users. Built for dev teams.
Launching on Product Hunt soon ⚡
🔔 here: producthunt.com/products/feedj…
English

This is the long tail of "we'll get to your feedback soon." Years of user investment, feature requests, workarounds.
Salesforce acquired it, absorbed it into the portfolio, and now it's Slack/Agentforce or nothing.
The feedback that was filed in Quip's own roadmap tracker: gone. The users who filed it: migrating. No one deliberately buried the product; it just slowly stopped being anyone's priority.
English

Your changelog is a renewal argument. Most teams write it for the team that built the features.
Before your next renewal call:
1- Pull every feature shipped in the last 90 days
2- Cross-check against open requests from that account
3- Highlight the overlap
"We shipped 4 things you asked for this quarter" is a different conversation than "here's what's new."
The changelog is already there. Most CSMs just never read it from the customer's perspective.
English

The amount of engagement activity itself is a substitute; what matters are the conversations people have in person and the comments that come through six months later during sales visits.
When it comes to optimization, there’s always the danger of sacrificing the more meaningful but harder-to-measure element for something easy to count.
English

This episode had fewer views than most, but it's by far the episode people mention most when I ask for their favorite recent episode.
JodiJefferson@JodiJefferson
One of the more practical conversations I’ve come across recently on compensation was between Jacob Warwick and @lennysan on Lenny’s Newsletter.
English

"What's your most requested feature?"
Wrong question.
Votes are a popularity contest. Vocal users vote. Power users vote. The person who churned six months ago because of a real pain? They didn't vote.
Better question: which requests came from accounts that expanded?
Upvotes measure enthusiasm. Account trajectory measures value.
Build for the second one.
English

The $19/month plan gets you one roadmap. One.
Unlimited boards. Unlimited posts. Unlimited votes. But two roadmaps — say, one for your web app and one for your API — that's the $79/month plan.
Roadmaps aren't a premium feature. They're a thinking tool. Charging 4x to think in parallel is a pricing decision dressed as a product decision.
Worth knowing before you scale.
English

@ideaplanio The “read 6 months of feedback” task is where most new PMs learn that it’s scattered between emails, Slack DMs, Intercom support tickets, and a Notion doc that someone made up in Q3.
But Day 60 rolls around before the synthesis.
English

@houseofmartech The third issue that no one calls out is that of sending information back. Regardless of whether the team communicates well and executes well, the user who requested something will not be made aware that their request was fulfilled.
English

Collecting customer feedback and acting on it are two separate problems. Most teams solve them separately, then wonder why the roadmap doesn't reflect what customers said.
houseofmartech.com/blog/customer-…
English

The same feature request is in 4 of your inboxes right now. Sales has one. Support has another. Your CSM has a third in Slack. The PM sees one upvote on linear.
We built Feedjolt because of this → @marcllopart/the-feedback-graveyard-customer-feedback-dies-in-seven-inboxes-91a83419407a" target="_blank" rel="nofollow noopener">medium.com/@marcllopart/t…
English

How to triage feature requests without a dedicated tool:
1- Tag each request by outcome, not feature name ("faster export" → reduce time-to-value).
2- Track frequency AND recency old asks decay.
3- Note who's asking: churned user, power user, or prospect. Weight accordingly.
4- Watch for requests that stopped coming in. That's either solved or a churned segment.
Takes 20 min/week. Most teams skip it and wonder why Q3 missed.
English

Your roadmap isn't a plan.
It's a list of things you've already decided not to question.
The dangerous part isn't shipping the wrong feature.
It's shipping the right feature for a reason that stopped being true three quarters ago.
Feedback loops exist to catch that. Most teams don't have one.
English
Feedjolt retweetledi

Shipped: rolling sentiment analysis on every feedback post.
Every 6 hours @FeedJolt classifies new feedback, positive, neutral, negative: automatically.
The chart is a stacked area. Not a count. A trend.
Took 4 model-config iterations to get JSON-mode stable (force JSON + temp=0 was the fix).
19 days to @ProductHunt . This is the last AI feature before launch.
English

“Everything around you that you call life was made by people no smarter than you.”
Agency isn’t about outsmarting the system, it’s about starting to make things.
Tinker. Build. Ship. Repeat.
@mschoening @lennysan
English

The tragedy is that users feel it before the company does.
Feedback starts piling up with no movement. Roadmap goes dark. Customers stop bothering to ask. That silence is the diagnosis, not the NPS score.
We built @FeedJolt for teams who want to catch it early, not after the reviews turn.
English

I've started using a new term: Tragedy Apps.
Apps you loved 18 months ago. Still functional. Still shipping.
But … they just haven't been able to keep up in the Age of AI. And that means they have quietly fallen almost hopelessly behind.
Descript is one for us. There will be hundreds more.
Much more on The Agents Episode #004 … Out Now!!
Jason ✨👾SaaStr.Ai✨ Lemkin@jasonlk
A new The Agents!! youtu.be/GgVtyglwL1Q?si…
English

The feedback tools that charge per seat assume your team is the bottleneck.
It's not. Your customers are.
Seat-gated feedback tools are just portals with a monthly invoice. Customers don't log into portals. They send emails, slack threads, and support tickets.
That's where the real signal lives. That's why it keeps getting lost.
GIF
English

The flip side: leaner, IC-heavy teams are more dependent on good async customer signal infrastructure.
When you don't have 5 PMs running calls, the feedback loop has to be built into the product itself. You close the loop or you fly blind.
That's exactly the problem we're solving at @FeedJolt .
English


Your roadmap is not a promise. Stop building it like one.
The best roadmaps are short, opinionated, and wrong in useful ways.
They invite argument. They don't close conversations, they open them.
A roadmap that survives all feedback unchanged wasn't built for customers. It was built for the board deck.
English

The tool you use to collect customer feedback charges you per customer who gives it.
* 100 users with opinions? $79/mo.
* 1,000 users? $579/mo.
* 3,000 users? "Contact sales."
The more your product grows, the more it costs to listen to it.
That's the tracked-user trap. It's wild that this is the default.
English

Worth knowing: if self-hosting is not for you, then @FeedJolt is the managed service, one flat price for unlimited seats, and no Canny per-seat billing!
Same cycle: feature request → product roadmap → release notes → feedback loop closure.
Launching on @ProductHunt May 26 if you’re interested.
English

Found Quackback today.
Open-source alternative to Canny, UserVoice and Productboard.
It helps you collect feature requests, show roadmap, publish changelog and close the feedback loop.
Big plus: Slack, Linear, Jira, GitHub, Intercom, Zendesk, Zapier, Make, n8n integrations.
Repo: github.com/QuackbackIO/qu…
English

How to run your monthly feedback review in 20 minutes:
1- Filter to requests from accounts >$10k ARR only
2- Group by theme, not feature name
3- For each theme: one sentence on the job-to-be-done
4 - Flag anything blocking renewal conversations
5 - Kill everything else until next month
You're not building for votes. You're building for retention.
English


