Buying Software v Building
Don’t Re-Invent the Software Wheel!
As discussed elsewhere on our site, personal and business software choices that are available today come on a broad spectrum between the limitations of standard software, extending existing solutions, or deciding to have a bespoke system built for you from scratch.
Ironically, because all these options are now so readily accessible, it is easier than ever to commit to the wrong choice, specifically to have fresh software built and not really look into your options for buying software that could do the job as well or even better when that would actually serve you better.
However an honest look at what is already commercially available should include any limitations that directly conflict will your needs, rather than just getting carried away with all the fancy things they say it can do.
If there are no genuine conflicts, buy it. Don’t spend money building a solution to a problem when what’s already there isn’t broken!
Did you know? When America first went into space they took pens that could write in zero gravity and reportedly took more than $1,000,000 to develop. The Russians took pencils…What would you have done?…Don’t develop what you don’t need.
OK So You Can Afford It, But Can You Honestly No Just Buy Software That Already Does What You Want?
If you are going to pay someone to modify or build something for you, let it be because your genuine fundamental needs could not be met by buying software that is already out there, not just because you saw someone else’s bells and whistles and suddenly wanted some too.
Unless, of-course you are very rich and have money to burn, or this is your personal pet project. In which case you are in the luxury leisure market and you’ll find no end of software developers who will be happy to build whatever you want; “Of course, Sir should have exactly what Sir Wants! And would Sir like that gift wrapped?”.
For the rest of us, starting with existing software solutions off the shelf makes most sense.
If an existing software effectively meets a genuine need, and any genuine conflicts arising from using it can be worked around, then it’s a valid buying choice, go for it.
Then, MAYBE…see if you can pay someone to add one bell…OR…one whistle…if you’ve been very good AND if they promise not to break anything in the process.
When you are looking through a list of software product descriptions, recommendations and buying guides; Rather than focusing on all the things various products might do, to save yourself from getting carried away, try looking for the real deal breakers…
“Who is this NOT for?” or “Why would this not be for us”… because it doesn’t matter what it does if YOU can’t use it for some reason i.e. security, legislation, scalability, expertise, legacy dependency, or any other specific requirements peculiar to you or your company.
Don’t get sucked into buying something because of all the things it does that you don’t need. Obvious, but “this one’s got this really cleaver button that…we don’t need…yes, but it’s so cool!”