I recently shipped a small SaaS, mostly during school breaks. This is my first project that I have taken from idea to deployment, onboarding, and real users.
The product targets early-stage developers and focuses on reducing initial setup and preparation when building new apps. It abstracts away some of the repetitive early decisions and boilerplate that tend to slow down first-time builders, especially around project structure, configuration, and “what should exist on day one”.
I have a small number of active users, but churn is relatively high, which suggests either:
the problem is not painful enough
the abstraction leaks too early
the UX or onboarding fails to communicate value
or the tool solves a problem that disappears after the first session
I would really appreciate technical feedback on:
whether the abstraction layer makes sense
if the mental model aligns with how you bootstrap projects
where the product feels opinionated vs restrictive
what would make this something you would actually keep installed
Thanks for reading. Direct, critical feedback is very welcome.
I have a small number of active users, but churn is relatively high, which suggests either:
the problem is not painful enough
the abstraction leaks too early
the UX or onboarding fails to communicate value
or the tool solves a problem that disappears after the first session
I would really appreciate technical feedback on:
whether the abstraction layer makes sense
if the mental model aligns with how you bootstrap projects
where the product feels opinionated vs restrictive
what would make this something you would actually keep installed
Thanks for reading. Direct, critical feedback is very welcome.