I’ve recently been giving advice to some pre-launch startups about their user interface and initial set of features.  After re-reading one of the emails I sent, it seemed to me that the concepts are pretty universal and maybe apply to your project.

• Less Is More. If you can remove features from the service in the near term, it is beneficial for everyone.  Your developers will have less work, your users will have less learning curve, and you’ll more clearly be able to interpret early usage data.  If you’re not familiar with the term Minimum Viable Product, google it, might be helpful.
• Use Sensible Defaults. Whenever possible, pick something for the user, and only allow them to change it if they need to.
• Stub Future Features. To get better ‘interest’ data on specific future features, you can create links/buttons to non-existent features.  ie:  ’Click Here to Change the Answer Duration’ –> This feature is not yet implemented, but we want to see how many people would be interested in using it.  Would this feature be useful to you [Yes] [No] Leave us additional comments…  You can count clicks and get very direct comments about each prospective new feature.