Hi all, developing a form builder to rival Typeform. I need advice on validating demand and targeting customers (developers vs businesses). Any suggestions are appreciated.
Hey SailingBreeze, this is such an intriguing project you’re working on. I really like the idea of merging functionality that appeals directly to developers and businesses, each with its own unique set of needs. What kind of features are you leaning towards for the developer side versus the business user side? It would be interesting to hear if you’ve already stumbled upon any early feedback from beta tests or developer communities. Also, have you thought about how you might differentiate your tool from Typeform in terms of customization and integration with developer workflows? The intersection between ease-of-use for non-techies and the power tools that developers crave is a unique space to experiment in. I’m really curious about your strategy and how you plan to validate demand while keeping both segments engaged. Would love to chat more about your roadmap and any challenges you’re anticipating along the way!
Having worked on similar developer tools, I found that early validation through focused pilot programs can work wonders. A rough prototype showcased to both developer communities and small business users helped in gathering diverse insights. In my experience, developers tend to appreciate granular API controls and self-hosted options, while business users value an intuitive interface with seamless integrations. Engaging both segments separately and incorporating their specific feedback early on can uncover mutually beneficial feature enhancements. This dual-pronged approach has shown significant potential in aligning product development with market needs.
hey sailingbreeze, try teaming up with dev influencers and building an open source commty. this can boost trust and bring real feedback from pros and newbies alike. real-world usage and word-of-mouth might validate demand in ways surveys cant capture.
Hey SailingBreeze,
This project sounds super exciting and like a real game changer! I was thinking about how to get deeper into customer validation early on. It’s fascinating to hear you’re targeting both developers and businesses, and I’m curious if you’ll consider some sort of community involvement right from the start. For example, creating a space where developers can share how they’d extend or integrate your solution might not only validate demand but also build a vibrant ecosystem around your tool. Have you explored any partnerships with platforms or forums where these communities already gather? Also, regarding the business side, it might be interesting to see how customization options can serve both simple needs and more complex workflows. I wonder if a modular design might spur some innovative use cases?
I’d love to know what you think about involving potential users in iterative testing sessions or maybe even an early adopter program. How do you envision balancing the technical rigor needed for developers with the usability checks that business users might require? Looking forward to hearing more about your plans and any insights you gather along the way!
I have built similar tools in the past and found that direct user engagement really speeds up refinement. My experience shows that early prototyping with clear developer documentation can win over a technically savvy clientele. However, it is equally important to offer a refined user interface for business users who prefer simplicity. Balancing detailed API support with an intuitive design ensures the tool serves both audiences effectively. Implementing a flexible beta program that provides real-time feedback from all user segments helped us refine functionality and secure early adopters.