Original Summary

solo dev here and this is mine, so take my enthusiasm with some salt. mid 2025 i was building another saas and i was too busy shipping features to listen to users. feedback came in through emails, form submissions, the occasional dm, and i kept telling myself i'd get to it later. i didn't. i built what i thought was right instead of what people actually needed. when i finally sat down and read months of it, the patterns were obvious. people had been telling me exactly what was wrong. i just never looked at all of it in one place. so i've been building FeedSense around my 9-5. what it does: - connects to where feedback already lands: an in-app widget, intercom, zendesk, slack, a csv, or a webhook - reads every message and groups the same complaint written ten different ways into one issue, with a count - gives you a prioritized brief: what came up most, what's spiking, what to fix first the thing i got most wrong while building it: i spent weeks on sentiment and emotion scores. then three discovery calls with people who own feedback at other companies: none of them made decisions off a sentiment score. they decided off how many times the same thing came up, so that's what it leads with now. honest limit: under a couple hundred messages a month, you can still read them all yourself. the free plan covers that size. it's live with a free plan, paid from $49/mo: find here . if you click through, the most useful thing you could tell me is the first spot that confused you. and a question back: where does your user feedback actually pile up, and when did you last read every single piece of it?   submitted by   /u/canhigher23 [link]   [comments]

  • 情报分类：开源项目与落地
  • 分类依据：内容涉及项目实践、创业、副业或变现
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/25 02:10:21