I am building a similar forms based framework/product. Here is what I have discovered is needed:
-Proper handling of an other field, like there is on paper forms. I.e. What is your favorite salad? a) Fruit b) Vegetable c) Other __________
-Ability to string multiple forms together in a workflow (kind of like a CRM). Form 1 must be completed before the user can move on to Form 2. However, when some or all of the fields are optional, there needs to be some type of trigger logic to mark the form in the workflow as completed. (I sort of saw this in the video, but it seemed that the forms were marked simply as steps and the end user could skip from Step 1 to Step 9)
-Sub-forms, both in terms of adding multiple contact addresses (for example) or switching from Sub-form A to Sub-form B in the context of a form workflow (you guys seems to have this)
-Permissions on every question and on every part (Form 1, Form 2, etc) in the workflow (you guys seems to have the question permissions down, but I'm not sure about the statistics)
-A rich query language to crunch statistics from every form field filled out (It seems your application outputs CSVs and leaves the user to crunch them in Excel)
-If a form is tied to an entity (say a Student, for example), the ability to assign that Student to a Teacher or an Administrator. (I did not see this)
-Ability for daily e-mail reports on what new forms have been created and updated and what new Students have been added to the system. (this was mentioned on the about section, but I did not see it in the video)
My forms framework does all this and more, but it took quite a bit of effort to build. I would be more than happy to talk specifics with you guys; my e-mail is in my profile.
I must warn you though, you are entering a rabbit-hole.