Historically, one of the main segments of the product development services (PDS) market has been software product development for independent software vendors (ISVs). My colleague John McCarthy and I have just published a report that outlines how this market is undergoing a significant shift as it splits between serving the traditional ISVs and serving what Forrester refers to as “software-is-the-brand” companies.
Software-is-the-brand companies are those firms in industry sectors like financial services, retail, information services, and media and entertainment that are seeing more and more of their business value coming from their software-based products and services. This new segment will comprise the majority of growth in the software PDS market over the next four to five years.
This growth will occur as these companies increasingly require high-end product development capabilities for what, in many cases, were seen as traditional IT projects. My colleague Christine Ferrusi Ross recently wrote how technology has become the supply chain for these software-is-the-brand companies because it is the “raw material” that allows today’s products to be built. Frequently, however, these companies need help from service providers to acquire the appropriate skills and expertise to handle the current complexity and speed of technological change.
I’m part of a team called “sourcing and vendor management” (SVM). Forrester organizes its research teams by individual client roles, so my teammates and I all focus on helping clients who are sourcing and vendor management professionals. Wait a moment. Should that read “helping clients who are sourcing or vendor management professionals”? Aren’t they separate functions within a client’s organization? This is a frequent question from our clients, and one that causes a lot of internal debate within our team.
My view, formed from witnessing the experience of hundreds of enterprises, is that, at least in the software category, sourcing and supplier management should be very closely linked, but not via org structure and reporting lines. This is because:
· It is impossible to manage software suppliers effectively unless you can influence sourcing. The major players are so big and powerful that they usually have the upper hand in discussions about maintenance renewals and service levels. Even small software providers can build immovable, entrenched positions in their chosen niches. To have sufficient negotiation leverage to do a good job, the supplier manager must be able to credibly threaten to negatively impact the supplier’s ability to win future business.
· Sourcing is infrequent but intensive, whereas supplier management is continual. The former consumes huge amounts of time and effort for a relatively small period, which risks dropping the ball on monitoring while you’re immersed in a big negotiation, or missing opportunities on the sourcing side due to distractions from the ‘day job’. You therefore need different people handling each side, but collaborating closely with each other.
On August 6, 2013, the Indian rupee plunged to a record low of INR61.80 to 1USD. In fact, since January 2013, the Indian rupee has depreciated by 10% against USD and is expected to slide further as India is challenged by political gridlock, serious infrastructure bottlenecks, and decreased investor confidence, all of which are contributing to a slowdown in economic growth. The declining rupee leads directly to increases in the cost of doing business, which has risen by 8-10% over the past year.
The difficult economic landscape has forced Indian firms to look for new and innovative ways to grow their businesses, create efficiencies, and improve responsiveness. This is driving changes in how Indian business leaders view technology – with many increasingly viewing technology as a far more critical means to differentiate their organizations and drive business growth. The pressure is now firmly on CIOs to deliver technology-led business outcomes for their organizations. To exploit this opportunity, CIOs should do the following:
- Develop a ‘business outcomes’ matrix and map existing and planned technology projects against it to build credibility with business leaders: ROI templates are generally developed to gain approvals and are typically limited to cost savings, but very few CIOs actually link their IT spending to clearly defined business outcomes. Define what business outcome means to your organization (e.g., increase in sales, revenue, customer acquisition, customer satisfaction to name few) and map each of your projects against the matrix to prioritize those with greatest business outcomes. This will help CIOs win buy-in from business stakeholders on project funding and priorities, while ensuring that IT is viewed as an equal and capable business partner.