I gave it a shot and wrote down some criticism. I run a small design/interaction/software agency. Sorry that these things always sound so negative, I hope it wi

I gave it a shot and wrote down some criticism. I run a small design/interaction/software agency. Sorry that these things always sound so negative, I hope it will help you. I see what you're going for and it might work well for a very specific audience. But I think it will be hard to reach people beyond those that "get" where this bare bones design stands for. One thing that could be better in my opinion is answering some very obvious questions directly on the homepage like - How does it exactly differ from other backup services out there? - Who would use this and who wouldn't? - A nice example of cost breakdown for a common setup - Is there any one successfully using this? - It feels like a one-guy shop. Should I trust that for my backups? Then, some random opinionated observations about your design choices: - It will most likely only attract a very specific audience, is that the goal? - All the information is very subdivided into lots of pages, lists and blocks. Some people may like it, from what I found out simpler one-page overviews work better. An example could be our versionsapp.com site, which obviously has a very different style going on. - It looks like an open source project page. I wouldn't expect to have to pay for something at a page like this. - The whole no-logo thing is a pretty bold statement, but could work against you. - The small serif font in the menu could be hard to read on some screens. I would make it bigger and/or non serif. - The design is very timeless, and therefore it's hard to see if this is something recent or not. Koen