Looking for a Co-Founder for Surveys as Code Platform
Hi, I am Alex, and I am building Formulosity, a powerful Surveys as Code platform that lets you build surveys with Yaml.
Why build surveys with code you may ask?
- Version control: Survey files can be stored in a Github repository, which makes it easy to track changes and collaborate with others.
- Reproducibility: Survey files can be easily shared and reproduced, making it easy to reuse surveys or create variations of existing surveys.
- Automation: Survey files can be used to automate the creation and deployment of surveys, which can save time and effort.
What issues have you had with standard survey builders? I would love to hear your ideas, experiences, and feedback.
Project status:
The project is already launched, you can check it here - https://formulosity.com/
Trending on Indie Hackers
Hi Alex, interested to speak further. Where should I reach out to you?
Write me at [email protected]
I'm currently seeking a co-founder for an innovative startup focused on developing a Surveys as Code platform. This project aims to revolutionize how surveys are created, deployed, and analyzed by utilizing a code-driven approach, enhancing customization and scalability. The ideal co-founder should have a strong background in software development, especially with experience in SaaS platforms, as well as a keen interest in data analytics. Together, we’ll drive the product vision, build the technology, and establish a customer base. If you're passionate about transforming survey technology and eager to join a dynamic startup, let's connect and discuss this exciting opportunity further!
Hi Alex,
I would like to explore the opportunity of working with you.
Regards,
Neenu
Write me at [email protected]
Hi Alex,
I saw your post in indiehackers looking for a Co-Founder and I would like to explore the opportunity of working with you.
Regards,
Neenu
As a former Head of Growth for acquired in-app focused survey tool ... why? This sems about as useful as running your OS from a command line.
Versioning and reproducibility you mention are barely ever needed.
Most importantly, who is your customer ... who runs surveys in the org? It's the marketers, you think they will want to work without GUI? Devs barely ever run surveys. If they do, the problem is the content, targeting and result interpretation, not creating it.
You don't really gain anything by versioning a survey. Its not a landing page to split test.
Not to mention, you didn't even start, and the most critical part, the survey itself has a wrong UI. Hiding options under clickable dropdown is a massive friction. The no 1. stat all survey software try to compete on is % response rate. This would do badly.
Anyways, hope you consider the feedback and realign. Just think who your customer is first and if what you're trying to solve is a real problem — or it doesn't exist on the market yet, for a reason.
FYI, with that pricing you would destroy everyone on the market. Even with 200 monthly free reponses you would, not sure you would made any money though. But then again, you would have to build a normal visual builder for survey tool and catch up with all other standard features. Survey market is damn bloated, nothing reasonably free is usable. Either the tool is total crap, or the free plan is about 25 responses a month with bunch of other features crippled as well. Then again, perhaps for a reason. Once you have 30+ employee company, try to offer a big free plan, you'd go out of business.
Thanks for the feedback. The ideal customer is a small group of developers who need to develop a survey that can be automated. I myself had this problem, when you run into managing 100+ surveys created from the same copy and want some advanced configuration.
However, I agree, this may not be a big market, therefore this project can evolve in something else, by probably adding visual builder as well.
Best,
Alex