Another day, another common tale that we keep running into...an unsuccessful in-house system
On at least about 50% of the sales opportunities that we encounter the potential customer has attempted to build a 'home-grown' system to move their paper-based system from paper to electronics and has run into massive headaches and problems. Many times these projects end up abandoned and often sour upper management to the idea of electronic field operations as a whole.
If you're in IT or operations for a field service company and are considering building your own system, or even if you already have made the investment and are weighing its current functionality, there are some factors that you should carefully consider before sinking any more funds into your own system. As I've been mulling over our experiences running into these situations, I've realized that each of these factors probably deserves an in-depth blog post of its own.
In addition to my own perspective then, I'm going to ask some other folks here such as IT architects and business analysts to share with you some of the reasons you may want to consider buying a solutions rather than building your own, and to share some of the scenarios and situations that we've encountered through our years of engaging with field service operations. This blog post will be the first in an on-going series of blog posts that I hope you find valuable. Please give me feedback at knaugle@liquidframeworks.com and help steer the conversation.
Post new comment