SaaS and the Micro ISV
[Last week I had the good fortune to spend a little time talking
with Gord Graham from WrappedApps on the subject of SaaS and the micro
ISV. His ElastX initiative may well alter the game for micro ISVs. Gord
has kindly contributed this guest post on the subject.]
What is the right model for
delivering MicroISV applications over the internet?
The Software-as-a-Service (SaaS)
delivery model for offering applications over the internet has really
caught fire…Salesforce.com drove big competitors in the CRM space
into extreme hardship (poor Siebel!), Google’s productivity applications
are being recognized as a great alternative to desktop suites. A friend
of mine with a traditional client-server app says that half the RFPs
they see now they can’t even bid on because they require delivery
over the internet on a subscription basis.
Five years back, everyone thought
that SaaS was going to enable software vendors to reach the small-and-medium
business market, but surprisingly the early adopters were large enterprises,
and that continues to be the focus of SaaS providers. And the reasons
are clear…large enterprises recognize that the total cost of ownership
of software goes way beyond paying the license fee…there are servers
to buy, update management for the operating systems and applications,
security management, performance management, and of course all the expensive
IT guys and gals to do this stuff. As well, many companies “lock-down”
their desktops and don’t allow their employees to install applications
so they can outsource desktop support to an off-shore call center.
So buying enterprise applications,
like CRM, ERP and HR, on a subscription basis was just the ticket…reduce
your IT headaches and have access anywhere, any time, over the internet.
Most microISVs still use the
shareware model for marketing their applications…download to your
computer for free, try it for a while, and maybe 1 or 2 percent will
decide to pay for a license. The SaaS alternative looks pretty attractive…nothing
for the user to install, no license keys to manage, and the stats on
customer retention by SaaS vendors like Salesforce.com is outstanding.
I think SaaS is a great opportunity
for microISVs, but they face several problems. Their apps usually weren’t
designed to be offered through a browser over the internet (that problem
can actually be solved quite easily), most hosting services that provide
the infrastructure for provisioning and hosting apps, subscription management,
and the like aren’t particularly interested in the relatively small
niche markets of microISVs, and SaaS marketplaces like AppExchange require
redevelopment of the app in a proprietary language that restricts you
to one marketplace.
But the biggest problem, I
think, is the subscription model. Subscription to an application still
requires the user to make a purchase decision based on the specific
app, make a payment transaction to subscribe, and make a psychological
act of commitment to it. Whenever you ask a customer to make an act
of commitment, particularly one that involves a purchase transaction,
you are going to experience a high attrition rate.
I think the right model for
microISV applications is what I call the “cell phone model”. For
my cell phone I pay a monthly fee that gives me a certain number of
minutes of talk-time (I’m not masochistic enough to have a Blackberry
yet). So it looks something like a monthly subscription, but when I
flip open my phone I can call any number in the world without “subscribing”
to it. I don’t have to make the decision to subscribe to Grandma’s
number, or subscribe to my girlfriend Sue’s number (God knows what
would happen if I ever let that subscription lapse!). I just dial a
number, and the phone company takes care of measuring my talk time and
remitting money to whatever carriers were involved in delivering the
call.
That’s what I think a SaaS
platform for microISVs should look like. The user creates an account
once, and then has immediate access to any microISV app in the library
at a reasonable hourly rate. The SaaS provider takes care of metering
usage, remitting usage fees to the ISV, and everything else.
Later this year we are going
to be launching a platform called ElastX based on this model
(the details won’t be available until July 7 on www.elastx.com).
Clearly, not all microISV applications
are appropriate for SaaS…some have to be run on the user’s computer,
or are in constant use so a pay-by-the-hour model isn’t feasible.
But there are thousands of apps that personal or small business users
might want to use for a couple of hours a week, and I think that SaaS
is a perfect distribution mechanism for them.

Gord,
The SaaS platform/subscription model you are suggesting seems
fantastic. I know that there are a few companies already in the SaaS
billing mediate/subscription space, for example eVapt. I was curious
how your services differ from eVapt’s and other SaaS subscription
managers.
I totally believe that SaaS is the way to go. The cost of customer
acquisition is enough to dictate that the model is the only way to go
for a mISV to be successful.
For subscription management, check out one of my mISV projects, RailsKits: http://railskits.com/
The SaaS Rails Kit makes it easy for people writing SaaS apps with
Rails to get subscription management, billing, etc. out of the box. It
was based on the work I did for my own mISV project, Catch the Best (http://catchthebest.com/), and various client projects.
Thanks for the comments, guys. Sorry it’s taken so long to
respond…I’ve been busy with the announcement of our ElastX
initiative. It really seems to be getting the attention of the media
and bloggers.
Landon makes a good point…there are quite a variety of vendors
supplying various SaaS utilities and components (including us!). From
dealing with a number of ISVs, I’ve found that they don’t really want
to assemble the components, select a hosting provider, manage the
hosting and other aspects of the deployment, etc…they just want
somebody to take care of it for them so they can concentrate on
building a competitive feature set in their software that their
end-users will value. The big word in the SaaS business right now is
“monetize”…i.e. the ISVs are asking “how are you going to help me
make money from my app?”, rather than “why are you asking me to spend
more money on additional tools, components and services?”. That’s why
in ElastX we make SaaS-enablement, hosting, and everything else free
for the ISV. When a happy and satisfied customer pays to use an
application, we all make money. Until then, we don’t try to make money
off of each other.
If you are writing a web app from scratch, there are a variety of
toolsets to choose from, as Benjamin points out. If I was doing it, I
might be tempted to go the route of a Force.com, as it provides you
with not only the tools for multi-tenancy and the other “SaaS stuff”,
but it gives you access to an existing marketplace to offer it on. The
drawbacks, though, are a) you have to develop the app from scratch (no
automated transformation of existing Windows apps), b) your app will be
SaaS-only (wouldn’t it be nice to have a SaaS version and a on-premise
version based on the same code stream?), and c) you are locked-in to
that one marketplace.
I guess my final comment is that the subscription model is deeply
flawed. I think it’s the wrong revenue model for most microISV
applications…too many purchase decisions for the consumer to make,
too many payment transactions to process, etc. I think the subscription
model became popular because enterprise ISVs were terrified to abandon
their perpetual license fee revenue for a true pay-as-you-go model. If
they could get the customer to commit to a 6- or 12-month subscription,
the revenue-shock wasn’t as bad. Most microISVs aren’t as addicted to
the big end-of-quarter site license deals, and I think they will
experience a significant revenue increase from the pay-as-you-go model.
Plus, I believe they could reconsider their fees for perpetual
licenses…I think that in trying to capture the market of occasional
users they have priced their perpetual versions too low.
I just wanted to let everyone know that the ElastX ISV Beta Program
is now open! If you think you would like to be a part of the beta
program, visit our forum at http://www.elastx.com/forum to register for the
forum. Once you register, you can post links to your application for us
to wrap.