[timnuwin]

Hey Michael,

Thanks for the taking the time to give constructive feedback. I will try to make it more clear that the licenses are on a per-year basis, as well as visibly making the text on the homepage more clear. I have heard the term "on premise", and I agree I should use a more common phrase. I will update the language / terms later tonight. That will make it more official.

How do you think I should make it clear that you can create a free online account to test out the software yourself, or would you prefer a video?

[michaelbuckbee]

You should make it much, much simpler to try out. Ideally hack it to where it's a single click to log in as some demo user.

Right now you're asking for 9 pieces of information before you even let people see what / how it looks.

Another thought, you could let people do a one-click deploy to Heroku from a private repo or something to make it less burdensome to roll out. This is sort of a middle step between on premise and full automated.

[tim_nuwin]

This is very good advice. I will work on creating a 1-click demo account. I have the developer board up for anyone to see, but having the demo account will transition users using the software faster vs creating an account. I like the heroku deploy idea. I'm actually working on setting up cloud-formation scripts so you can launch w/ Chef + EC2.

[tim_nuwin]

Hey Michael,

Thanks again for the advice, I have added a 1-click login to the demo account on the landing page.