A year ago, I took the leap and went solo! Building apps for myself and clients has been an amazing journey, but it also comes with its challenges. One of the biggest? Juggling customer feedback from all those different channels.
That's why I'm thrilled to announce SaaSy Help, a tool designed specifically for solo developers like us to centralize, organize, and master customer feedback!
SaaSy Help goes beyond simple aggregation. Here's how it empowers you:
🔌 Connect all your apps: No more jumping between accounts or platforms!
🗃️ Centralized Feedback: See everything in one place, making it easier to identify trends and prioritize fixes.
🗂️ Topic-Specific Boards: Organize feedback by feature, bug type, or any other category with customizable boards.
🧠 Built-in Knowledge Base: Create guides, FAQs and documentations for your apps in a searchable knowledge base to empower users and save you time.
📝 Detailed Changelogs: Track every update and improvement you make, keeping users informed.
🧭 Transparent Roadmap: Share your development plans and gather valuable user input on future features.
I am working on a lot more features which you can find under SaaSyHelp.com and will be developing and supporting the app as my main project.
This is a solution born out of my own frustrations and I'm confident that SaaSy Help will be your one-stop shop for managing customer feedback and building a thriving solo dev business.
P.S. Let me know in the comments what challenges you have faced when managing user feedback!
Congrats on the launch! I'm particularly excited about the centralized feedback feature—how does SaaSy Help ensure that no feedback slips through the cracks, especially during peak activity periods?
Great Question @vasily_kolosov1
When users attempt to create an issue, they are presented with any existing/known issue to “vote” on. This is achieved through the integrated Search Engine. If the users wish to create the post anyways, a new post will be created but will be hidden to other users.
This is vulnerable to duplicate posts at peak activity but the feature is setup this way for the following reasons:
1. There are often nuances to user behaviour that is helpful for understanding the user’s behaviour. Summarising posts to merge them to a single post removes these nuances.
2. Developer Clarity is very important, allowing the developer to analyse incoming posts/issues one by one, allows them to build a better mental model of their app and the issue at hand.
I am working on extending the Posts functionality and I will be adding a comments section and a merge posts option that will summarise the selected posts into a single one.
I like to do things properly and so this will also include a mechanism to preserve the context of each merged post without cluttering the dev/user experience but still only visible to the developer.
Report
Hey, nice one. I use reviews for marketing, usually it takes a lot of time to gather them from all platforms.
SaaSy Help
SaaSy Help
SaaSy Help
SaaSy Help
SaaSy Help
SaaSy Help
SaaSy Help
SaaSy Help