Why should I buy from a small software company?
Jun 9 2009 :: by Alex
Imagine you've found an error in a product from some huge international software corporation, let's call it "MacroHard". I bet it has already happened to you a couple of times. Imagine you contact "MacroHard" to let them know about the error. Now think of the chances that this error would actually be fixed in a reasonable amount of time. The probability is close to zero, huh? Also think of the chances that MacroHard will contact you personally when it's fixed...
I'm not even mentioning feature-requests
(instead of errors). You must have already guessed - forget about 'em.
Along with the company size
, and brand recognition
, and other "big" stuff you get when you buy from a massive corporation, you should always ask yourself - "how can I affect the product development or at least the error correction in it?"
Here's an example from earlier this week:
>>>Wednesday (9:30 AM EST) — Customer:"Hi there. I've downloaded the latest version of Macro recorder, nice tool. But I need a feature that seems to be missing - or I was just too dumb to find it."Wednesday (9:35 AM EST) — Alex (Jitbit):"Hi. Thank you for the email. Can you specify what feature you miss exactly?"Wednesday (10:30 AM EST) — Customer:"Hi Alex. Thanks for the quick response. I want to edit the timeouts for several commands, but the tool doesn't allow editing more than one item at a time."Wednesday (12:45 PM EST) — Alex (Jitbit):"Hi. Looked into this and it seems to be an easy task, we're adding this to our next version that will be out within 24 hours, please stay updated to our version-history".Thursday (10:30 AM EST) — Customer:"Hello. We've downloaded the latest version, all OK. I think we'll be ordering some licenses later on today."Thursday (02:09 PM EST):"New Order for 2 licenses of Jitbit Macro Recorder"
Let's see a massive international software corporation do that.
by Alex. CEO, founder