7
Roast my product so I can move on - I need closure with my SaaS app
r/microsaas
8/15/2025
Content Summary
The author of the post is considering moving on from their SaaS product, StackTracer, after a month of minimal user growth. They built it as a solution to their own problem of managing and documenting a software portfolio but have not found much interest from other developers. Comments suggest that they may need to pivot to a different pain point, validate the problem first, or be more patient. Some suggest reusing the existing functionality for a new purpose, while others advise continued engagement with the community.
Opinion Analysis
Mainstream opinion suggests that the product lacks validation and needs more time or a pivot. Many commenters believe that the author should focus on solving a clear pain point before building a solution. There's a debate between those who recommend pivoting quickly and those who encourage patience and persistence. Some suggest that the product could be improved by integrating with GitHub or focusing on automation. Others argue that the author should continue engaging with the community and gathering feedback rather than giving up immediately.
SAAS TOOLS
| SaaS | URL | Category | Features/Notes |
|---|---|---|---|
| Notion | https://www.notion.so | Productivity | Used for onboarding and documentation |
| GitHub Wiki | https://docs.github.com/en/github/writing-on-github | Code Management | Used for onboarding and documentation |
| StackTracer | http://stacktracer.io | Software Portfolio Management | Dashboard with team/org access, no active users yet |
USER NEEDS
Pain Points:
- Difficulty in gaining user traction for a SaaS product
- Lack of validation for the product idea
- Challenges in acquiring feedback from potential users
- Uncertainty about whether the product solves a real problem
Problems to Solve:
- Managing and documenting software portfolios
- Needing a centralized solution for developer onboarding
- Finding a way to generate useful documentation automatically
Potential Solutions:
- Pivoting to a different pain point (e.g., automated user management)
- Syncing documentation with GitHub repos
- Reusing existing functionality from the current app for a new purpose
GROWTH FACTORS
Effective Strategies:
- Building a functional product with reusability in mind
- Focusing on solving real developer pain points
- Engaging with communities like r/webdev, IndieHackers, and ProductHunt
Marketing & Acquisition:
- Leveraging Reddit communities for feedback and exposure
- Posting quick demos to gather interest
- Using DMs to reach out to developers for feedback
Monetization & Product:
- Uncertainty about whether users would pay for GitHub integration or documentation tools
- Importance of validating the problem before building the solution
- Need for more patience and persistence in growing a SaaS business
User Engagement:
- Engaging with users directly via DMs and forums
- Building a community around the product through Reddit and other platforms
- Regularly sharing updates and demos to maintain interest