Paul Miller

The Cloud of Data


Understanding SaaS business models in conversation with Adam Gross of Salesforce.com

Adam GrossSalesforce.com [CRM] is often held up as proof that the Software as a Service (SaaS) model works. Ten years old, and with over $1Bn in revenue last year, Marc Benioff‘s company certainly shows that SaaS isn’t just a passing fad.

More recently the company has begun to diversify from its heritage as the provider of an on-demand CRM application, seeking to nurture an ecosystem of add-ons and enhancements through the AppExchange and offering third party developers access to the underlying Force.com Platform.

In an effort to understand the company’s views on the evolving SaaS and PaaS markets I recently spoke with VP for Developer Marketing, Adam Gross, and the result has just been released as a podcast.

 

Show notes available on TalisNodalities blog

Delivery of both application and platform could create significant tensions, as business decisions made to advance the application potentially cannibalise revenue from the platform ecosystem, and vice versa. We discuss some of these issues during the conversation, with Adam going so far as to suggest that ‘nothing would stop’ a third party using Force.com to build an application that competed directly with Salesforce itself.

Have a listen, and see what you think.

Image of Adam Gross © Salesforce.com

Reblog this post [with Zemanta]

Article Tagged: , , , , , , ,
View Comments

Chatting with Sinclair Schuller about making it easier to deploy SaaS applications

Image representing Apprenda as depicted in Cru...
Image via CrunchBase

I’ve written before about Sinclair Schuller and the work he’s doing at Apprenda. Yesterday, I recorded a podcast to continue some of our earlier conversations in more public form, and this is now available here.

Have a listen, and see what you think about the need for intermediaries such as Apprenda to bootstrap the move toward SaaS application deployment.

Reblog this post [with Zemanta]

Article Tagged: , ,
View Comments

Does SaaSGrid speed the process of delivering SaaS applications?

As mentioned in my previous post, I recently spoke with Apprenda CEO Sinclair Schuller ahead of this week’s announcement of SaaSGrid.

The formal release is perhaps deliberately ironic;

“In an industry flooded with buzzwords and numerous companies jumping on the platform bandwagon, Apprenda cuts through the SaaS platform clutter and draws a bold line with SaaSGrid. SaaSGrid is a powerful cloud operating system that abstract SaaS intricacies into the SaaSGrid software layer and provides ISVs with the necessary online tools to manage their SaaS business and application offerings. SaaSGrid drastically slashes time to market for ISVs by automatically weaving a SaaS architecture into their non-SaaS web applications while providing significant long term value via web-based application management capabilities.”

Sinclair’s blog post is more straight-talking;

“For anyone unfamiliar with SaaSGrid, it’s a cloud operating system (literally) that makes writing and commercializing SaaS offerings with Microsoft .NET very easy. It removes quite a few headaches from the architecture and engineering perspective, and provides a tightly woven business services layer for managing operational and customer facing aspects of your business. So, if you’re building a SaaS offering and are planning (or looking for a reason to) to use a .NET based language and stack, look no further!”

Bob Warfield is also amongst those covering the news, over on SmoothSpan. Bob gets right down to it, commenting that;

“Apprenda calls SaaSGrid a ‘Cloud Operating System.’  I don’t know if I would call it that or not, but at the very least it is a SaaS platform that offers a lot of benefits not unlike Force.com from Salesforce, but with some key differences.  First and foremost in my mind, is that there isn’t much of anything proprietary about SaaSGrid.  It’s a framework that makes it easy for .NET developers to move their applications to a SaaS Cloud-based delivery vehicle.  Looking at the services provided by the framework, it isn’t hard to see that Schuller & Co. have had experience building SaaS applications before (in fact quite a few of them), because it solves many of the SaaS-specific problems I’ve seen in my career as well.”

He continues, echoing my own initial impression that the most important piece of this might not be the technical infrastructure at all;

“SaaSGrid covers two bases.  First, it offers plumbing and delivery infrastructure services.  In my mind that’s the “Cloud Operating System” piece.  But, at least as interesting is their Business Engine, that helps simplify a lot of the operational aspects of SaaS.”
(my emphasis)

Talking to Sinclair, it is clear that the rationale behind SaaSGrid comes from experience. He talks about work in the financial sector, higher education and elsewhere, in which the same basic pieces were necessarily duplicated. Each project, each deployment, required his team to almost start from scratch and to concern themselves with a plethora of background operations before they were able to concentrate on the actual task at hand.

As in other industries, the framework – the Platform – that Apprenda have developed is intended to remove some of that background complexity and to enable developers working on a given project to get on and develop the actual applications that need to be written. Sinclair said that SaaSGrid

“provides a new layer of abstraction that takes the burden of creating SaaS specific technology, architecture and business components off of ISVs shoulders”

Back in his blog post, Sinclair describes the proposition for a developer;

“Apprenda does not host applications for software companies. Instead, we enable existing hosters to offer independent cloud instances of SaaSGrid. This means that you can write an app and leverage SaaSGrid, but get to choose which Cloud Provider to publish your application to. You basically write code in Visual Studio in a single-tenant fashion, use our API for certain SaaS related duties, upload your app (UI, web services, database schema) to a SaaSGrid cloud of your choice, click a couple of buttons through a control panel and you’re up and running with a true multi-tenant, ready to accept money SaaS offering!”

A community portal provides documentation, support, and access to the basic building blocks such as an SDK that developers can download in order to develop their own applications.

Online tools that Sinclair walked through with me do a good job of tracking multiple versions of an evolving product, managing customers, etc. The Business Engine that interested Bob Warfield comes into play here, offering a remarkably straightforward process by which application developers can manage availability and pricing of ‘features’ and ‘securables’ within each application they release.

SaaSGrid has been in beta for the past six months, with around 30 companies involved in building network monitoring, CRM, HR and other applications. As might be expected, around 40% of beta customers originated in the US… but the beta programme extended as far as Namibia!

The first of these applications are expected to go live early in 2009, and Sinclair was also open to the idea of Apprenda-branded applications appearing as well in order to showcase SaaSGrid and (presumably) secure other revenue streams for the company.

The SaaSGrid user interface is currently only available in English, although currency information for pricing within applications is fully customisable.

Given Apprenda’s reliance upon Microsoft components such as .Net, Azure might be considered a threat. Sinclair appeared unconcerned, though, arguing that Microsoft’s Cloud offering is more concerned with technology even further down the stack. Azure, he said

“could be a resource to use, rather than competition.”

We shall see!

SaaSGrid, though, represents an interesting step forward for those application developers already comfortable with developing atop the Microsoft stack. Just as Talis has recognised with their Platform in the Semantic Web space, there is clear value in ‘doing the heavy lifting’ and enabling developers to get on with building their applications as quickly and painlessly as possible.

Reblog this post [with Zemanta]

Article Tagged: , , , , ,
Comments Off

Sinclair Shuller attempts to clean up the language of the Cloud

Yesterday’s blog post by Apprenda CEO Sinclair Shuller is an interesting attempt to clarify the hodge-podge of terms that tend to be thrown around almost interchangeably; Cloud, SaaS, PaaS and more.

Have a read, and see what you think.

I spoke to Sinclair recently, ahead of today’s announcement of their SaaSGrid offering, and there’s plenty more to share from that conversation when I get to it in my task list!

Reblog this post [with Zemanta]

Article Tagged: , , , , , , , , ,
View Comments

‘Reinventing the Wheel’ becomes world’s only growth industry ?

Square wheels !Hopefully the title of this post exaggerates the problem slightly, even in these recessionary times, but I am increasingly concerned by the extent to which the tech sector’s current and future behemoths squander finite effort on reinventing ‘context’ at the expense of excelling in delivery of their ‘core’ proposition.

The notions of core and context are, of course, most often associated with Geoffrey Moore, and one of his sites defines them, thus;

Core

“Any activity which creates sustainable differentiation in the target market resulting in premium prices or increased volume. Core management seeks to dramatically outperform all competitors within the domain of core. (Note this use of the term is unrelated to either core competence, which describes differentiated capability, or core business, which describes categories accounting for a high percentage of overall revenues.)”

Context

“Any activity which does not differentiate the company from the customers’ viewpoint in the target market. Context management seeks to meet (but not exceed) appropriate accepted standards in as productive a manner as possible.”

Writing in last weekend’s Financial Times, Gerrit Wiesmann tells us that;

“We’ve been waiting for trains since 1840, the year a British parliamentary committee invented mass transportation by ruling that rail traffic should be exclusively in the hands of the companies that owned the track. It’s an odd notion now, but in the years before that decision, a debate raged about how to use rails. In the 1820s, the British railway visionary Thomas Gray called for a national network for use by private vehicles. He reckoned traffic in and out of London could be handled by 12 parallel ‘rail-ways’.”

Here, as elsewhere, ideas given serious consideration at the birth of an industry are superseded as that industry matures and sustainable business models begin to emerge.

There will always be areas in which technology companies invest their own human capital rather than buying in services and products from third parties. The traditional view, largely captured in Moore’s terminology, holds that companies gain most by focussing their own efforts upon the differentiating aspects of their business whilst making use of supporting services from third parties to enable concentration upon those differentiators. It will tend to be cheaper and ‘easier’, so the argument goes, to pay for commodity services from a third party rather than develop everything in-house from scratch.

In the early stages of any technological wave, there is an understandable tendency to develop and control far more of the stack within a single organisation. Various players enter a nascent market, and attempt to shape it to their needs at the same time as laying the foundations for what they hope will be a successful product or service. Without agreement on standards and specifications, there is very little interoperability. With an emphasis upon attracting and growing a customer base, there is little incentive to make it easy for users to compare offerings with – or move to – the competition. With a fluid understanding of the final product and its differentiating features, there is little clear understanding of that which will be ‘core’ as opposed to that which will merely be ‘context.’ Internal and external pressures encourage, and almost require, an approach that is closed and all-encompassing.

The problem, it seems, is in making that move from a nascent market toward the point at which certain aspects of the technology stack are fit for commodification; the point at which a healthy and competitive ecosystem can begin to emerge that increases customer choice whilst lowering development and running costs. Looking at aspects of the Cloud Computing and SaaS arenas, we must surely be reaching the point at which numerous homegrown technology stacks become increasingly counterproductive? In the Semantic Web space, too, that early burst of innovation is becoming unnecessarily expensive to maintain as one company after another continues to concern themselves with segments of the problem space that might easily be made a commodity.

Look, for example, at the number of Semantic Technology companies continuing to pour effort into building, scaling and maintaining a basic ontology. The ontology is rarely the point of the company. It is simply something they need to have in order to get on with the business at hand. How many of them are ‘wasting’ time recording the fact that Gordon Brown is the UK Prime Minister, or that Beverley is in East Yorkshire, which is in England, which is in the United Kingdom, which is in Europe?

A recent conversation with Hapax CEO Mark Redgrave confirmed the extent to which they are having to focus upon ontology construction with Amplify. Refreshingly, though, he was extremely open to the notion of gaining value from a more open and generic ontology upon which Hapax and others could build, add value, and compete. In the SaaS space, too, Apprenda CEO Sinclair Schuller has some interesting ideas with regard to enabling others to build their own Software as a Service offerings on top of a common platform that begins to look increasingly like a commodity. It will be interesting to see the extent to which the reality of his company’s SaaSGrid is able to match that vision.

I have spent (too much!) time in the formal standards making process, and would be the last to even consider suggesting that freeform innovation and commercial creativity be snuffed out in favour of protracted and painful rounds of negotiation, specification and never-ending compromise.

However, it seems apparent that early innovators in a given market (Amazon with EC2, Salesforce, etc) often see little incentive to open up and behave less proprietarily. It is in their interests for every competitor to have to reinvent all the wheels that those early entrants first conceptualised. The shift needs to be driven by their competitors, some of whom will be sufficiently successful that they disrupt the market conditions in which incumbents dominate to such an extent that customers are incentivised to consider switching.

A little reinvention is a good thing. It encourages creative thinking, and probably leads to refinement, iteration, and further innovation. Perpetuated at the expense of opening up a nascent market, it becomes a tool of monopoly and ultimately counter-productive for all concerned.

Perhaps it is only at this point that those at the top of a market segment are able to realise the benefits of letting go a little, and of relegating much of what they do to the status of mere context.

Image of a bicycle with square wheels © Michael Vroegop 2007, and licensed with a Creative Commons Attribution License.

Reblog this post [with Zemanta]

Article Tagged: , , , , , , , , , , , , , ,
View Comments
Rss Feeds