What if engineers could build qualitative feedback into products right from the start?
In our experience, this often gets neglected because all dev attention goes to building the actual product. And yet, no one would launch a product without usage analytics because its insightful and really easy to implement.
How would a solution for qualitative data look like?
Formbricks aims to:
- fill the gaps between usage analytics and 1:1 interviews
- keep dev attention at a minimum when leveraging best practices to gather qualitative data (Superhuman PMF, in-app interview prompts, onboarding & churn surveys, etc.)
- build one user profile from waitlist -> paying customer (like early user CRM)
It's different from micro-survey tools because:
- doesn't clutter UI (natively embeddable in user flows)
- specific analysis (e.g. for PMF survey) vs. generic visualisation of data
- open source (self-hostable, freely customizable, embedabble)
Hoi!
What if engineers could build qualitative feedback into products right from the start?
In our experience, this often gets neglected because all dev attention goes to building the actual product. And yet, no one would launch a product without usage analytics because its insightful and really easy to implement.
How would a solution for qualitative data look like?
Formbricks aims to:
- fill the gaps between usage analytics and 1:1 interviews - keep dev attention at a minimum when leveraging best practices to gather qualitative data (Superhuman PMF, in-app interview prompts, onboarding & churn surveys, etc.) - build one user profile from waitlist -> paying customer (like early user CRM)
It's different from micro-survey tools because:
- doesn't clutter UI (natively embeddable in user flows) - specific analysis (e.g. for PMF survey) vs. generic visualisation of data - open source (self-hostable, freely customizable, embedabble)
The ask: Please poke holes in it :)
Happy sundays!