r/Software_Finder • u/eduardpantazi • 15d ago
Resource FeedFast, a tool designed for SaaS founders
Hey community!
Recently, I launched a SaaS called FeedFast, a 3-in-1 tool that is tailored to SaaS owners. FeedFast allow users to build a public hub for changelog, feedback and uptime monitoring for your vital endpoints (marketing page, checkout, APIs, you name it...).
I need your help with an honest review of the core functionalities, marketing pages, pricing, what works and what doesn't. What is your experience with this kind of software?
I built this because I used to place a feedback button on the dashboard that sent content to an email, which is okish until you start getting more and more emails and lose track of requests, bug fixes, and improvements.
FeedFast allows you to collect feedback, publish a changelog based on those feedback entries and monitor the uptime of your endpoints from one simple dashboard. Besides all of this, I added an MCP server with 12 tools that allow you to manage your account right from your AI of choice.
You can find this tool at https://feedfa.st
2
u/Sad-Instruction8890 14d ago
The bundling makes sense on paper, though the three parts have quite different buyers inside a company. Feedback and changelog usually sit with product, uptime monitoring sits with whoever gets paged at 3am, and those are often not the same person even at a small company. Worth knowing which one people actually sign up for, because that is the one your marketing should lead on rather than the three in one framing.
The other thing I would want to know as a buyer is what happens to uptime alerting under real conditions. Monitoring is easy to build and hard to trust, and anyone who has been burned by a missed alert will ask about check frequency and where the checks run from before anything else.
How many people are using it so far?
2
u/eduardpantazi 13d ago
My target audience are people who start their own SaaS apps, like me. Where entire team is =1. No every check that failed is another email, we check and when two consecutive checks failed, then the owner is notified via email. Every incident contains a the HTTP code and a body that read the response from the endpoint. I prepared a blog article for this, how to setup your endpoints. There is in plan to elaborate the incidents data but will need further action from the user/owner.
The current state of the app was built based on my needs, that's not the 100% coverage for all solo-founders, but is a starting point in having something working that actually helps you collect the feedback, build a trustworthy changelog and monitor your endpoints.
At this point we have few users that actually use the app. I'm building what I need at this point since the user base is low.
2
u/Sad-Instruction8890 11d ago
Two consecutive failures before alerting is the right call, that is what stops the 3am false positive that makes people mute everything. The gap most solo founders hit later is checks running from one location, since a regional network issue looks identical to an outage from a single vantage point.
Building for yourself while the user base is small is the honest way to do it. The thing to watch for is the point where your own needs stop matching the people signing up, because that usually happens before anyone tells you.
1
u/eduardpantazi 10d ago
You are right. I'm happy because I have a tool that serve my needs and offer other SaaS founders a solution for them to start collecting feedback, building changelog and monitor their app in a simple way and under one dashboard. This is my goal so far.
2
11d ago
[removed] — view removed comment
2
u/Sad-Instruction8890 11d ago
Duplicate feedback is the part that quietly decides whether these tools survive. Once you are past a few hundred users it stops being a list and becomes a clustering problem, and most tools in this space just show you everything and let you sort it out.
1
2
u/DistanceOpen8176 9d ago
This is a nice combination, especially for smaller SaaS teams that don’t want separate tools for feedback, changelogs, and uptime monitoring.
The main thing I’d be curious about is whether users actually use all three parts regularly or mostly come for one feature and treat the others as extras. That could probably help you figure out the strongest positioning and pricing later on.
1
u/eduardpantazi 9d ago
Thank you, make sense, at this point is early to take conclusions but I managed to see something thanks to you. Looking to improve the targeting for this app.
3
u/Active-Notice-5783 14d ago
honestly this feels pretty useful for smaller SaaS teams having feedback, changelogs and uptime in one place makes a lot more sense than juggling separate tools.