I have not played with the product beyond the onboarding demo but I have to say the sign up was very impressive too and much to learn there for my own work.
Having worked with surveys over the years the problem I find is that testing takes longer and longer. Sometimes you are filling in a form and sometimes you will have an optional page, e.g. in a custom job application form you may have a page on education that only the person with a degree has to fill in, this implies two testing paths through the form and therefore doubles the time to test. So testing time goes up by the cube of form complexity, or so it seems.
Years ago it would take a whole evening to make a C90 compilation cassette of songs for someone. Just the interface of the cassette deck, turntable and other cassettes would mean that it would take 5-6-7 hours to put it together, even if you knew all the songs and knew what you were doing.
Nowadays if I want to put together a playlist for 90 minutes of music I could do that and think what I was doing to get it done in ten minutes, not hours. I wouldn't be using cassettes or record players or even CDs. Just tick boxes in a UI.
So the key thing for me is that how-long-does-it-take question and much like how with compilation cassettes you still had to play it back to test it, with a survey you need to do some testing, ideally with that test time not going up 'by the cube' of form complexity.