Posted by:Richard Smith July 10th, 2015

Enterprises have been slower to embrace mobile applications than consumers for a number of reasons including concerns over security, lack of people with the right skills and more. More often than not, when companies begin to explore the benefits of mobile applications, they start with sales and marketing. Frequently that will mean a catalog app of some kind to improve salesforce effectiveness and productivity.

When mobile first came on the scene, you would have no choice but to develop such an app yourself. Now; however, there are choices between build or buy that are available. So, in a series of blog articles I will be examining the factors that go into making a buy vs. build decision for a company that wants to put a B2B catalog app in the hands of its sales people.

Let’s start with a little discussion on what buy vs. build really is.

A B2B catalog app will require not just the mobile device itself (typically an iPad or Android tablet) but also a significant backend database. So typically, we are talking about buying a cloud-based service rather than a license for use of software installed on internal systems. And buy isn’t always just buy. There can be customization or integration work required. So maybe the choice is not just buy vs. build. It could also be buy and customize versus build. Really, the impact of a buy vs. build decision has to be considered on the complete lifecycle:

  • Requirements Definition
  • Acquisition
  • Customization
  • Integration
  • Implementation
  • Training
  • Maintenance

Want to know the key elements of a succesful enterprise mobility strategy? Download the infographic to know more!

Leave a Reply

Your email address will not be published. Required fields are marked *