Quote:
It is an on line C++ code generator. It's a binary alternative to SOAP. It is intended to be helpful in developing distributed applications with C++. There are two ways to use it: a web interface and a command line interface. The command line interface is a lot easier to integrate into a build environment than the web interface. Thanks for your comments.

Ok. So I think I finally understand what you are selling. That isn't clear AT ALL from your website. That mostly stems from the fact that your webpage is just a jumble of text with no real formatting.
* A code formatter like seen here on my blog would help to make your code snippets more readable. As would a non-black-and-white color scheme that emphasizes links and headings better to give a good separation of text.

* Specifying exactly what your tool does would be good. While it is somewhere in your page, and you've stated it here in the forums, it isn't obvious from your site. You need to really redo the "flow" of the page to Introduce->Compare->Try so that people can get all the information they need from the front page. Likewise, I could care less about your changelog when I visit the front page.

* Naming and grouping your links better would help the flow. Having "Web interface to ...." as one of the top links doesn't really do me any good, since I don't even know what I'm looking at yet. Secondly, since I don't know what I'm looking at I also don't know what I'm supposed to do on that page. After a proper introduction to the service, chaning the link to a "Try the web interface here..." would be a better introduction to that page.

* "Userguide! Oh god, now I need more files?" - What are these middle files? You don't even mention them when comparing your tool to Boost. The boost code is explicit, in my code, and readable. Your code "automatically" takes care of things, but until I clicked the "web interface" link, I had no idea I even had to write these other "middle files"(or maybe there were hints, but I still didn't know what they were supposed to look like).

* Comparing to boost? Could you supply the WHOLE pipeline somewhere? I know with the boost code all I need is that one file. With yours I see that it generated a file, but you don't supply how it did so (ie your middle file and the process to get that generated file). This is huge since it immediately seems your tool is more complicated, so the benefits need to outweigh that complication.

* Are your "middle files" more readable than the boost code? not sure they are.
* How can I tailor the output/input? The endianess of my files tends to matter when reading them from different platforms. Boost's version is explicitly written in my code, so I can do those transforms there.
* How can I tailor the output/input? Boost has a bunch of serialization methods, like XML, binary, text. Can I somehow do that with your tool?

* Consider changing the name of your tool "Middleware Writer" and "Middleware Writer Ambasador" sound like "buzzwords" to me. Pick something unique, related to serialization, and less wordy. Actually, the "less wordy" part goes for a lot of your descriptions of your tool. Again, people need to first know what it is you are selling?(serilization) How is it different(automatic)? how do you use it?(online) Don't confuse people by throwing all that information at them at once. Enterprise descriptions like "The command line interface is part of a three-tier architecture." read as "blah blah blah" to most people. However technically correct the statements might be. You need to walk people in piece by piece so they are sold before the complexity hits. Remember, your customers are idiots, and they are always right. If something else seems simpler, they are going to go look at that first.

Lastly, since you've posted about this a lot on the forums, I'd go back and look at all those posts. What questions do people have? How important are those answers? The more important the answers and the dumber sounding questions should be answerable on the front page of your site within a moments look at the page. If I have to search for more than 5-10 seconds to find the simple answers that will sell the product, then you just lost a customer.