Re: viability assessment (was: Re: [service-orientated-architecture] Re: XML Tuple Spaces as Middleware)

Fri, 14 Apr 2006 09:57:51 -0700

I evaluate the viability of any company, including an "open source company", based on its business model, current technology solution, vision, management team, sales and marketing strategy, partnership strategy, support/services strategy, customer base, customer satisfaction, revenue pipeline, brand recognition, market opportunity and rate of growth, competitive landscape, captial reserves, run rate, VC commitment, time-to-profitability, and various other factors.

Anne

On 4/11/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
Hi Anne,

> Before joining Burton Group, I used to recommend products from small,
> innovative, startup software vendors much more than I do now. My
> enthusiasm for the startups has been tempered by the general
> resistance I get from Fortune 500 companies that are typically
> unwilling to bet the success of a project on a company of questionable
> viability. It's a market force that cannot be ignored. Now, whenever I
> recommend an innovative startup, I always include a viability
> assessment.

I'm curious .. how does a company being an "open source company" affect
your viability assessment?? I'd also appreciate if you would address how
you evaluate the "open source"ness of a company ... as you know there
are varying levels of open source companies.

Disclaimer: I run an open source middleware company (WSO2) .. hence have
a biased view on this topic for sure!

Sanjiva.







Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/service-orientated-architecture/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
YAHOO! GROUPS LINKS



Reply via email to