Raju, your question was so "big" I moved it to Strategy & Leadership.

Raju,

A lot to cover in what you have posted, but I'm starting here:

For someone to buy a product or service, they need a vivid and tangible understanding of what problem/need it solves.

Some of the issues you discuss above, including the text on your website is too conceptual for 99% people to get "it" - understand exactly what you offer and why they need it. It needs to be far more tangible. Perhaps dumbed down for the the exec who actually signs the cheques rather than the geek who sits in a cubicle.

By way of analogy, you can design a laser-guided GPS-positioned rodent-tracking and anihilation machine ... but if all people want to do is get rid of mice and they can buy a mousetrap for a $1.99, you are going to be fighting an uphill battle. You can talke about the merits of blue vs. red lasers till the cow's come home.

My main suggestion along the lines of Bruce, is to bring your value proposition into focus, so that someone (ideally someone who is an ideal fit for your product) to understand what you offer and why they need your solution described in one-minute or less.

A great way to also do this is via a case study. Get your foot in the door and first customers, and show via a Case Study how they specifically benefited from your technology.

---

Robert Dubicki

Ouch! There are so many problems with what you have going.

First, the product is horizontal. Going horizontal out of the box will kill you. You should follow the technology adoption lifecycle and come to the horizontal with customers from the verticals, and it should solve a client's problems, rather than be fascinating to a programmer. The technical enthusiast geek is not a market.

Second, having worked in the tool business for so many years, I can say that it is not a place to thrive. It will be an uphill battle.

Third, the comparison to C++ GUIs is culturally misplaced. The web's interactivity is not what a C++ programmer does. The web's focus on user centered design is not what a C++ programmer does. The number of C++ programmer is declining.

Forth, as for "revolutionary" sorry but it might be radical or continuous. Revolutionary is a bunk concept as a strategic process. It is marketing hype. Now, AJAX was radical, as it was old technology repositioned and allowed to evolve rapidly against it's competitors. I don't know if it created a new category or not, but it did if there are AJAX tools out there today. I wouldn't know. I'm not paying attention to AJAX. So how are you positioning yourself niche wise to be different from every other AJAX subsitutor, and substitutors are never category/market leaders. You can probably make a living in this space, but certain realities will impinge.

The origins of version 1.0 software is always suspect. You must build for a client and learn from them and from trying to sell the client visualization to the client's competitors in the client's vertical. This visualization cannot come from you, it must come from the client, and you have to be real careful in the sale and requirements elicitiation, not to confuse what you want to do or can do, with what will pay off for the client. It is this client that gates your success in the vertical. Version 1.0, typically means, no client/customer input and the designer doing his own thing.

One of the biggest barriers is any framework. They are tough to learn. They are so tough to learn that programmers are better off rolling their own, rather than understanding some third-party vendor. There is in some sense a standardization problem with frameworks and market leadership matters to the moon. A small complementor will run out of money competing with a big budget complementor. Neither will become a market leader in the primary vendor sense. The primary vendors do have the market leadership, investors, money, staff, cost structure, and increasing returns to push a framework as a standard. Nobody else can.

Anyway, good luck!

David Locke

Hi Raju,

I read your home page, and I get that you are doing something to make GUIs easier, faster and better. That certainly seems worthwhile, and I know GUIs are a pain to a number of our clients.

But you didn't tell me:

- What it works with.
With the caveat that I'm not technical... I was looking for you to say you're an add-on to something I recognize, like Eclipse. Hooking into a standard or a popular toolset would be a really smart move.

- How much it is going to cost (and how much I'm going to save).

- How hard it is going to be to learn.

- What else I'm going to have to do to use it effectively.

- What you want me to do next.

A couple other comments:
I wouldn't send people to another site to read an article that validates what you're saying, particularly not from the home page. They'll probably go read it and forget where they came from and never come back.

I'd avoid using the word "paradigm" if you can. Many technical people have a bad reaction to it.

Hope this helps!

It sounds like you are interested in building a business, which means attracting paying customers. To that end...

- I don't know what "Component paradigm" means.

- I don't know what "federated translation platform" means.

- I don't know why either of these terms, or any others you might "try out" would cause someone to write you a check.

Suggestion: Instead of trying to tell others about your solution and why they should buy it, consider asking the right questions (about value / pain / etc.) - and then listening intently to their answers. If they want it green, then paint it green!

My point? Telling is not selling. Listening is. Understanding is. Compassion for the pain you will solve is. They will "get" that you are truly interested in solving their problem (and will thus part with precious cash), once YOU know what they need, and why. No convincing needed. Just deep understanding.

Hope this helps!

Someone highly credible would notice our break through inventions. Since I am living in India I not able to meet and present decision makers in large US software companies. But once there is some traction, I will visit them.
Raju

---

Robert Dubicki

You don't give away software to early adaptors. You give away software to technical enthusiasts. Technical enthusiasts don't pay for anything. And, early adaptors are economic buyers, not developers.

If your problem was the inventors delimina the solution is fairly well described. Like it or not you are competing with outsourcing. And, you have a culture problem. C++ development can't be done on the web, so it is of little interest that you are building GUIs on the web if you are trying to sell that to C++ developers. Traditional software development and web developement are mutually exclusive worlds.

I won't go anywhere near a web service. Why commoditize myself right out of the box.

The next issue is do you support the "forms layer" that is being pushed as an emerging standard for website architecture?

David Locke