Show HN: I Built a Customer Feedback Tool (usefeedlyst.com)
Hey HN,
I've been making products for almost a year now. I always started projects and stopped after 2 weeks because I lost motivation. But this time, I’m determined to release it – even if it’s not perfect yet!
Let me introduce Feedlyst: a customer feedback tool where you can create boards, let customers submit & upvote feedback, and turn ideas into action.
I hope this tool will be helpful for you! Would love your feedback!
Raphael
35 comments
[ 2.9 ms ] story [ 80.3 ms ] threadKey example: "login is broken!" Could be the captcha didn't load, captcha was blocked by their ad blocker, they are rate limited, they used the wrong email, they used the wrong password, they don't have an account, they aren't on the right website, etc.
I've found the most success with collecting these requests internally, watching what bubbles up and then refining that into a solid use case - then present that to existing clients to vote/weight.
I'm more interested in gaining experience and getting tips on what I can do better for future projects!
The initial product is 5% or less
My costs are actually relatively low, I pay 5 euros a month for my VPS and the domain is only 7 euros a year... I can manage that!
Let's be optimistic and assume the following over the next year: - You get 100 paid users from initial launch. You'll need an advertising budget to gain more. - And 500 free users over time because they'll keep coming.
Can you support 600 users with $1000 for a year? And this is not about vps costs, it's your time as well, you'll need to manage the vps and respond to customer tickets whether it's bug fixes, performance issues, or feature requests.
I think $10/first year is reasonable to test out your SaaS idea, you'll pay a lot out of pocket, but it'll give you the chance to evaluate and workout your pricing model over the first year.
Taking this to extreme degree — could wire up a GitHub/`claude` workflow that automatically generates pull request implementations of top-rated features (e.g. with branch previews hooked up so you can just try it and approve)
I'm based in Austria. And we only use Stripe (payment processing) and Resend (email service).
One question... why do my users need to give you their email to leave a request?
Is there a way that I can send them through with a token that is valid for a time to leave the request?
About the email: I use Resend. Could you give me the board ID and a time when you requested a magic link, then I'd be happy to take a look at it. Sorry for the little problem, it shouldn't happen :D
I see about the follow up comms, makes sense. Would still prefer if leaving the email was optional for the request leaver. I realise this complicates things :)
I will try to find a way to both being able to leave the email and reduce spam!
in a matter of minutes when I wrote, some one replied and added me to beta to test the feature. at that time I said there s a market for this kind of things after all
so good product, nice UI, keep up the good work ( after all what matter you shipped something and you are writing history )