.NET Tips and Tricks

Blog archive

The VistaDB Story

I think that a lot of developers working for someone else think about working for themselves either as an independent consultant (like me, for instance) or as the owner/vendor of a killer software product (I tried that once, too). Over the last few blogs I've talked about the history of a developer (Jason Short) who bought a software product in 2007 (VistaDB, reviewed here), significantly improved it, and started marketing it. You can read Part 1, Part 2, and Part 3 of the blog series.

In July of 2010, Jason decided to call it quits as the owner of the company. He described the problem in his e-mail announcing his withdrawal from the company:

I may hold on to VistaDB, but it will be relegated to a nights and weekends type of activity. There will be no more full time work on VistaDB from me.... I am planning to spend my free time on a more advanced engine.

This sums up the problem for many developers who consider marketing a product that they've created. Initially this is a hobby: something they can work on nights and weekends. After marketing the product for three years, that hobby phase is starting to look attractive to Jason again.

In the hobby stage, as Jason notes, the developer has a lot of flexibility,

Items that don't interest me... will be dropped like a hot rock.... [I] know I could improve performance probably 10x over what it is today, but not without massive design changes. If this is a hobby/research project then I will make those changes... but without a way to make money on it there is little point in developing it as a commercial product.

But Jason also points out what changes when you become a commercial product vendor. As a product vendor Jason says he has to be "worried about backward compatibility... all the crazy upgrade paths." And that doesn't include customer support, advertising, maintaining the customer forums, and all the other requirements of being a real company.

This is the dilemma: developers start building a product as a hobby but when they move to selling it, the effort required by the product increases exponentially. Becoming a commercial product requires committing to at level of work moves the product out of the hobby, "nights and weekends" mode. The product now requires a fulltime commitment. And, if the developer doesn't make that time commitment, the product won't be able to keep its customers. But that commitment means the product has to produce enough revenue to support the developer... and any additional staff that the product now requires. As VistaDB's story demonstrates, it's an unusual combination of product and developer that will be able to make the leap from hobby to commercial product.

It's too bad, because VistaDB remains, I think, a great product. Hopefully, some smart company will buy it and continue its story.

Posted by Peter Vogel on 07/26/2010 at 1:16 PM

comments powered by Disqus

Reader Comments:

Fri, Oct 1, 2010 Kendall Miller Baltimore.MD

Great news for VistaDB users - VistaDB is not over by a long shot! We acquired it in September and are hard at work right now on a new version with enhancements driven by the community's feedback. VistaDB complements our existing product family of .NET developer tools and we're in a great position to carry it forward because of the diversity we have with multiple products. You can read more from the press release (http://www.prweb.com/releases/2010/09/prweb4516664.htm). Jason has been great to share with us his lessons learned and experience so we are in the best position to carry forward with the core mission VistaDB was designed to achieve.

Thu, Aug 19, 2010 Peter Vogel Canada

Lynn: I can certainly see that providing cross platform support would be a compelling message to those shops supporting operating systems other than .NET--and a message that people are willing to pay for. Jason Short notes (quoted in a later blog) that it's finding that message that's one of the critical success factors in success.

Wed, Aug 18, 2010 Lynn Fredricks Beaverton, Oregon, USA

Hi Peter, A user of ours sent me a link to your article here. As a database vendor that serves the cross platform (including .net) development market, I can sympathize with Jason's experience. They key to prospering in a market that's got very mature players as well as free alternatives is to ensure that your product's unique features are valuable enough to get people to pay, and keep paying - for the original product, and also products that extend the infrastructure in ways that make sense. Our Valentina database (http://www.valentina-db.com) is a very fast columnar database - but if that were all there was to it, we wouldn't have lasted this long. Our cross platform message, multi-tool support, very modern API and reporting engine all pull in new customers too. The economy in the USA in particular is not helping either.

Add Your Comments Now:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Please type the letters/numbers you see above

.NET Insight

Sign up for our newsletter.

I agree to this site's Privacy Policy.