7 articles from December 2007
- Web 2.0 apps: Driving expectations for SaaS ISVs
-
in 2008 your customers will more and more expect you to offer your business applications via SaaS — whether you are ready to or not.
A long time ago (or so it seems) a similar tale unfolded as customers forced ISVs to shift applications from character mode to GUIs. The pressure for change did not come from the ISVs. I am sure you also had managers who thought GUIs were a backward step in productivity for business applications. Product managers often claimed “our users do not want a mouse.”
- Nozbe: TOS for SaaS GTD solution fails to build trust
-
For day-to-day task planning and management I use a light version of David Allen’s Getting Things Done (GTD) method.
Earlier this year I saw a reference on the ZDNet Office Evolution blog to a new SaaS GTD tool called Nozbe from apivision.com. I was reminded of it when lifehack.org included Nozbe in their 11 Top New Web Apps of 2007.
Over the holidays I thought I would give Nozbe a try and see if it could replace my current Microsoft Outlook solution. My initial impression of the site was positive, until I clicked on the Terms of Service link at the bottom of the Nozbe home page.
- Trust: SaaS ISVs need trust architecture to survive
-
If you are trapped underwater the Rule of Threes says you can survive 3 minutes without air. Your top priority is clear and simple: find air to breathe, and quickly.
What should your top priority be when rebuilding your ISV to survive and profit from the shift to SaaS? Reading press and analyst reports on SaaS you might think your top priority should be building a scaleable back-end platform. Or, maybe your priority should be to select the right rich-client development tool.
These are certainly important issues, but they are not your top priority. Your top priority in rebuilding your ISV is to create your SaaS Trust Architecture. It really is as clear and simple as that.
- Head in the sand: Lies ISVs want to believe about SaaS
-
You know the shift to SaaS is life-threatening for your future as an ISV — you are doing something about it and reading ISV Survival! Still, you will need to convince colleagues who have not understood the risk your ISV is facing from Software as a Service.
A good place to start is Rick Chapman’s presentation: The SaaS Tsunami: An Analysis of why and how Software as a Service is changing the market.
- Connections: ISVs, Software as a Service and survival
-
Trapped underwater and no air to breathe? Lost in the mountains and no shelter for protection? Stranded in the desert and no water to drink? Stuck in a wasteland and no food to eat?
What should you do if you are in one of these life-threatening situations?
First thing: understand your situation and set priorities. This might seem obvious; sadly, the news regularly reminds us otherwise. People often set the wrong priority and the price they pay is their life.
- ISVSurvival.com: The first survival tip
-
The ISV Survival blog will contain survival tips posted on a regular basis. These are shorter items that link to other websites, blog posts, news articles etc. I hope the survival tips will help you rebuild your independent software vendor (ISV) to survive and profit from the shift to Software as a Service (SaaS).
- ISVSurvival.com: The first article
-
The ISV Survival blog is about what Software as a Service (SaaS) means to independent software vendors (ISVs) who will be forced by the market to adopt a new business model that exposes them to the financial and reputational risks of running production applications.
Not found what you’re looking for? Then try the ISV Survival site map to explore by article title, category, tag, month and author.