Bart

Software Engineer - Red Gate Software

9 Top tips for ISVs to get me to (maybe) buy your software

Published Wednesday, August 27, 2008 6:59 PM

I’ve been looking around, off and on, for a decent piece of test management software to replace the current piece of junk software that we use. This has involved visiting lots of ISV websites which have, frankly, made me miserable and ill-tempered. I'm starting to think that such a wondrous piece of software doesn't exist, but along the way I have compiled this list of nine top tips to help you people (ISVs) get it right, and which will help to persuade me to part with my cold, hard cash.

 

  1. Get your Google search ranking sorted out. I use Google to search: I don’t use Yahoo, or MSN LiveSearch (or whatever it’s called), or AltaVista, or that new ex-google-employee pretender to the throne (cuil?), because it’s crap. I probably would use cuil if the search results were better because I quite like the idea, but for now, no. Now some of those others have quite a lot of market share, but I use Google, which has the most, so you should probably make sure you’re appearing towards the top of the search rankings there. Admittedly, by the standards of many internet users I’m remarkably patient in that I’ll go through three or four pages of search results before I give up, however, if you don’t appear on page 1 I’m going to assume your product isn’t great before I even visit your website. There’s a chance you’re doing yourself a huge injustice here… although from what I’ve seen of test management tools, and the companies that make them, I seriously doubt it.

  2. For crying out loud put some bloody screenshots of the product on your website. Seriously. Hardly anybody does this and it baffles me. Is it because you’re too lazy, or are the products so butt ugly that you’re just embarrassed to subject them to the scrutiny of the world at large? I don’t want to have to download and install your product (assuming I even can, but I’m getting ahead of myself here) to find out what it looks like. Get this though, I don’t expect it to be a work of art necessarily (although pretty is nice), but I do expect it to look professional and like it might do what I want. Screenshots aren't the whole picture, and can be misleading, but they're a helpful extra layer of filtering. I admit that we (Red Gate) are not great at putting product screenshots on our website—somebody even wailed on me, quite justifiably, for not posting or linking to any screenshots in one of my previous posts, which I duly corrected. Generally we show one or two shots, but we’ve never done the gallery thing (IMO we should). Sure there are videos, and they do include a demo of the software, but when you’re looking to get an overview of what’s out there in terms of a particular type of product, and you're looking at ten different companies, it’s just nice to be able to click on a link and see a whole load of thumbnail screenshots that you can zoom in on; much quicker than watching videos. If it’s hard to get a glimpse of your software I’m going to assume it’s because it’s both ugly and crappy.

  3. Do not make me sign up to anything, or fill out any big forms, or ask to call me, just so's I can see a demo of your product. All you're doing is putting up barriers that make it less likely I’m ever going to try your product, let alone spend any money with you. Put a video, or even a series of videos, on your website instead. If every OAP and their yappy little highland terrier can work out how to post videos on YouTube it ought not to be beyond the wit of a bunch of so-called software companies to put some demo videos of their products on their websites. Come on kids, it’s not rocket science.

  4. If you do post up videos then make sure there’s actually a demo in there somewhere, and it’s not just a Powerpoint presentation with some gormless charisma vacuum pontificating on your philosophy of X, where X in this case is software test management. I don’t mind a bit of background at the beginning and a conclusion at the end, but I do expect you to get down and dirty with the software in there.

  5. If you post videos in multiple formats, make sure they all work. This is particularly poignant when you’re looking at test management software. If your website doesn’t work properly this does not bode well.

  6. It is not the year 2002. Internet Explorer market share is not 97%. It’s never likely to be 97% again. Nowadays, depending upon who you ask, it’s around 80% (and that might be a bit on the high side), and there are more people than ever on the web, so that 20% that don’t use it adds up to an awful lot of people. Geeks, who if you market test management software are likely a good chunk your target market, even if they have transmogrified into managers, are over-represented in that 20%. Please make sure your website works properly in all major browsers. And yes, I use Firefox.

  7. Don’t stop me from downloading your product. I don’t mind having to fill out a really short form, or one with lots of optional fields, and I don't mind captchas, but don’t constantly hound me afterwards, and definitely don’t make me talk to a sales person before I can even download your software. I just don’t want to. Not before I've even tried it. At this point I’m about a million miles away from making any kind of purchase, and more than that, your sales pitch isn’t going to be able to persuade me to do so anyway: if I buy anything at all it will be on the basis of how well your software works and whether it fulfils my needs. Now I know how this goes; you’re trying to sell to senior types, VPs and the like, people who will never actually have to use your software. You’re probably not that interested in lowly Project Managers and the like, and on the face of it this looks like a good ploy. But think about it like this: as I wend my way merrily up the corporate ladder, do you think I’m going to have more time, or less time? Do you think I’m going to have more patience, or less patience with this kind of guff? Exactly.

  8. It’s probably better if your website doesn’t look like it was designed somewhere behind the iron curtain, in the mid-80s. Again, a work of art isn’t necessary, but clean and professional is. And for goodness sake, drop the Times New Roman: it makes it look like it was designed by my gran. Sans serif fonts are the order of the day, both cleaner looking and easier to read. It takes about two minutes to knock up a style sheet that will banish all traces of Times New Roman from your site forever, which’ll be two minutes well spent believe me. And what's with all the dowdy colours? It doesn't have to look like the Merry Pranksters' schoolbus, but—I mean are you scared you'll die or something if you use a bright, cheerful colour here and there?

  9. Finally, make sure your software isn’t crap. It’s so obvious, it shouldn’t even need saying, but… well, clearly it does. I mean just look around. There’s plenty of great software out there, but there’s also this overwhelming torrent of gashware—not malware, I mean stuff that is actually supposed to be useful but isn’t—that you have to wade through sometimes in order to find it. It’s a side-effect of the low cost of failure, as pointed out by Cory Doctorow: there’s more good stuff, but there’s also more crud, however if you actually want to have a successful piece of software it needs to be good.

 

And that’s it. If you do the above there’s a chance I might spend some money with you, and if you don’t there’s virtually no chance whatsoever, which doesn’t bother me in the slightest, because there’s someone out there who will be doing it and it’ll be them that gets my money and not you.

by Bart Read
Filed Under:

Comments

 

RobertChipperfield said:

Amen!

One of the things that really gets me is when you have to "request" a trial of some software, which then needs to go away to be approved by someone before then e-mailing me two days later with a download link. When I want to try some software, I want to try it now. That's why I was on your website now, rather than in two days time :-)
August 28, 2008 3:36 AM
 

Adam Machanic said:

Yes, yes, and yes again!!!
August 28, 2008 12:19 PM
 

randyvol said:

"Software is crap"

Maybe I'm showing my age here, but I've been in the software development game for over 25 years.  Most of that time I worked on software development programs for manufacturers of large, commercial computers.

I remember a time when software was rigorously tested, thoroughly documented, and was not released until the development team could pass integration testing with the various 'platform and infrastructure' they claimed to run on.

To be sure, even then there were bugs, but usually they were annoyances, not fatalities.


Now it seems, vendors are in a rush to release software that is not very well tested, full of serious flaws, with obsolete documentation (sometimes not even documentation)!

Some helpful hints for any software vendors who read this spot:
1 - "Online help" is NOT documentation.
2 - Consider your audiences.  User manuals are fine for users; they are useless for administrators of the system  your products run on.  If you cannot handle a flood of support calls in 5 minutes or less (and most cannot), then do yourselves a favor and document how the in-house administration staff can 'take care of and feed' your products.
3 - Any 'product' that requires the customer to weed through endless trace logs in XML format to find 'errors' your product threw while processing data, then write scripts to fix those errors cannot be called, even in the loosest sense a product.  Products fail gracefully and provide the customer a set of tools to recover from the failure and continue on.  GET OVER IT, the customer's IT staff is not in any sense an extension of your engineering staff so you can debug & fix your hastily released garbage after the sale has been made.
4 - Any 'product' that fails due to 'bad data entry' is again, NOT A PRODUCT.  Products verify valid data entry PRIOR to attempts to process the data.
5 - Your distributor network is for SALES of your product; if the business plan includes an annuity stream from continuous customer service engagements to fix and customize your system then you don't have a product either.

I could go on, but I think I'm making myself clear.

I've heard people blame Microsoft for this trend - I don't think this is fair.  I've never, ever, had a Microsoft product that is as egregious as offender as some of the products from other vendors that have exhibited any and all of the failings listed
above.
   
Finally, so that no one thinks I'm speaking about Red Gate, I've been using Red Gate products going on two years now, I DO NOT include Red Gate in my above grump.  Their products are very, very good.

September 4, 2008 8:23 AM
 

RickSchultz said:

Bart,

Couldn't agree more.  I'm an ISV (first product about 3 months away from release) and I really appreciate blogs like this that tell me what I need to do to attract your interest.  BTW, don't look at the website yet; it's more a place-holder right now (no product yet, so not pushing the website quite yet).

I'm curious about your thoughts - I'm planning to have my product on a "try before you buy" plan, with 30 days to try, and in order to minimize the "hit" on IT, I'm thinking of releasing it with as a virtual machine with all the necessary bits already on-board.  It's a standard client/server piece for the folks in finance (sorry, not a software testing solution; if you find a good one, let me know!).  Is that something you might find desirable, or does that just add to your overhead (ie needing to first install a virtual server & whatever other issues might arise)?

Thanks in advance.

Rick
October 15, 2008 3:44 AM
 

Bart Read said:

Hi Rick,


Sorry for the delay in getting back to you. I'm enormously bad at replying to comments on my blogs sometimes. It's supposed to send me email notifications but that doesn't seem to have happened this time.

Anyway...

I think try before you buy is a great way to work; it's certainly served us well. It really depends on your price point, but these days I don't think expecting people to part with their cash before they know what they're getting is a great business model whatever you charge.

As far as shipping a VM image goes, I probably wouldn't do that if it were me. Essentially you've got three groups of people here:

(1) People who always test *everything* on VMs.
(2) People who can't be bothered at all with VMs and just install it on their own machine.
(3) People like me who do a bit of both depending on what the software is: e.g., I wouldn't install a Visual Studio beta on my dev machine because I know it's pretty much a given that I'll need to do an OS reinstall, but I might install a dev build of Firefox on my own machine just to check out the new features, because I know the chances of it damaging the OS are vanishingly small.

People in group (1) will likely have virtual server etc installed, along with a battery of VMs that reflect their own system configurations, and this is important. People need to know that your software will work on their systems, but if you ship a VM image all you're telling them is that it works on your system.

My advice would be put together an installer than checks for and installs any pre-requisites necessary (obviously you need to warn the user and explain why), and then they can deploy it in whatever environment they see fit.

People who haven't already got virtual server &c. installed for this kind of testing likely won't want to install it just so's they can test your software.

Basically what I'm saying is remove every barrier you possibly can that might impede people from trying out your software.

Anyway, I hope that's of some help.


Thanks,


Bart
December 4, 2008 12:03 PM
You need to sign in to comment on this blog

About Bart Read

Bart has done many things since he started work at Red Gate Software Ltd in August 2004, but nowadays he's (mainly) the product manager for the .NET Developer Tools. He still feels like this is a bit like admitting you were cheering for the Empire whilst watching Star Wars, but for now he's along for the ride. In a previous incarnation he was a project manager leading the .NET Reflector Pro, ANTS Memory Profiler 5, ANTS Performance Profiler 4 & 5, and SQL Prompt 3.0 - 3.6 projects. He still occasionally writes some code and, in the past, has touched the code for most of the Red Gate SQL developer tools... some of them still haven't recovered from the shock. He was born and grew up in Dorset, was educated in Nottingham and London, and likes music and real ale. His photo is extremely misleading.


















<August 2008>
SuMoTuWeThFrSa
272829303112
3456789
10111213141516
17181920212223
24252627282930
31123456
Finding Stuff in SQL Server Database DDL
 You'd have thought that nothing would be easier than using SQL Server Management Studio (SSMS) for... Read more...

Mission Critical: SQL Server 2008 Performance Tuning Task List
 In which Buck Woody imagines how the US military would have tackled DBA checklists for... Read more...

Simple Query tuning with STATISTICS IO and Execution plans
 A great deal can be gleaned from the use of the STATISTICS IO and the execution plan, when you are... Read more...

Switching rows and columns in SQL
 When they use SQL Server, one the commoner questions that Ms Access programmers ask is 'Where's the... Read more...

Writing Efficient SQL: Set-Based Speed Phreakery
 Phil Factor's SQL Speed Phreak challenge is an event where coders battle to produce the fastest code to... Read more...