Feedjolt

65 posts

Feedjolt banner
Feedjolt

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
Feedjolt
Feedjolt@feedjolt·
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
1
0
1
97
Feedjolt
Feedjolt@feedjolt·
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
0
0
0
45
Jason ✨👾SaaStr.Ai✨ Lemkin
The last, final echo of the time when Bret Taylor, CEO of Sierra and Chairman of Open AI was actually … co-CEO of Salesforce! Many may not even know this ;)
Jason ✨👾SaaStr.Ai✨ Lemkin tweet media
English
8
1
22
9.2K
Feedjolt
Feedjolt@feedjolt·
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
0
1
1
7
Feedjolt
Feedjolt@feedjolt·
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
0
0
0
11
Feedjolt
Feedjolt@feedjolt·
@marclou Search over user feedback and feature requests is a great one. Instead of "find the docs on X," you want "show me what users have asked about X." Same interface, different index, but it changes who opens it from devs to PMs.
English
0
0
0
61
Marc Lou
Marc Lou@marclou·
I just added this command palette to DataFast documentation 📚 It searches the docs only for now. Any other good use case? cmd+K to search
English
37
0
78
11.6K
Feedjolt
Feedjolt@feedjolt·
"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
0
1
1
11
Feedjolt
Feedjolt@feedjolt·
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
0
1
1
18
Feedjolt
Feedjolt@feedjolt·
@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
0
0
0
4
IdeaPlan.io
IdeaPlan.io@ideaplanio·
First 30 days as a new PM: - 15+ customer calls - Shadow support for a full day - Read 6 months of customer feedback - Map the stakeholder landscape Do not touch the roadmap until day 60. You have not earned the context yet.
English
2
0
0
7
Feedjolt
Feedjolt@feedjolt·
@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
0
0
0
2
Feedjolt
Feedjolt@feedjolt·
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
0
1
1
21
Feedjolt
Feedjolt@feedjolt·
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
0
1
1
23
Feedjolt
Feedjolt@feedjolt·
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
0
1
1
14
Feedjolt retweetledi
larsnow
larsnow@larsnow·
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
0
1
1
22
Feedjolt
Feedjolt@feedjolt·
The missing half: most teams collect the feedback, but never close the loop. Users stop sending it when nothing visibly changes. So the iteration signal dries up and you're left with gut feel anyway. Taste takes reps. Reps require users who still trust you enough to tell you things.
English
0
0
0
55
Notion
Notion@NotionHQ·
“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
10
19
144
21K
Feedjolt
Feedjolt@feedjolt·
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
0
0
0
13
Jason ✨👾SaaStr.Ai✨ Lemkin
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
19
2
28
10.6K
Feedjolt
Feedjolt@feedjolt·
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
0
1
1
52
Feedjolt
Feedjolt@feedjolt·
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
0
0
0
5
Jason ✨👾SaaStr.Ai✨ Lemkin
If your team is >truly< AI fluent, you should not have any managers who aren’t also ICs The era of a lead designer having 10 designers managed in kanban cards with 30 day turn-around times is just dead. Or it should be. Same with CMOs that don’t … market themselves. “No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams.”
Brian Armstrong@brian_armstrong

This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian

English
8
4
47
9.2K
Feedjolt
Feedjolt@feedjolt·
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
0
1
1
18
Feedjolt
Feedjolt@feedjolt·
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
0
1
1
20
Feedjolt
Feedjolt@feedjolt·
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
0
0
0
13
HK
HK@heyhk_·
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
1
0
0
111
Feedjolt
Feedjolt@feedjolt·
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
0
0
0
20