Why Partner Relationship Management (PRM) Fails Most of the Time

Published: Sept. 8, 2016, 10:27 p.m.

b'Over the past few years there has been a lot of excitement about partner relationship management (PRM) process development and automation. However, this segment hasn\\u2019t really grown as fast as the marketing automation platform (MAP) or customer relationship management (CRM) segments. What is holding back the growth in deployment of partner relationship management (PRM) automation? Here are some key factors that present barriers to deployment and are frequent causes of failure:\\n\\n \\tShort-term focus. Most channel organizations are busy managing activities by the quarter, and typically very few dollars are invested in mapping channel processes that require redesign and redevelopment to build out a state-of-the-art partner relationship management (PRM) infrastructure. The channel is a great way to go to market, but when the market changes (as it inevitably does) and organizations fail to remap their channel infrastructure accordingly, they struggle to stay relevant. We have seen this repeatedly over the years across multiple Fortune 1000 customers. Those who are adaptive and constantly redesigning their channel\\u2014not just quarterly, but whenever necessary and in anticipation of opportunities\\u2014tend to outperform those who are chasing market evolution.\\n \\tInadequate resources. It is one thing to remap a go-to-market model\\u2014e.g., by adding an OEM channel to sell via OEMs or adding franchises to increase reach\\u2014but without significant investment and patience these activities really doesn\\u2019t produce results. As a result, most deployments of partner relationship management (PRM) automation tend to be underfunded and underdeveloped. This leads to frustration within the channel sales and support organization and, of course, a poor partner experience.\\n \\tLack of a unified approach. The channel is a complex way to go to market. While it\\u2019s true that having a robust channel can not only increase reach but also provide a huge competitive edge, it takes time to develop relationships and competencies to truly be a channel leader. This is where a unified approach to partner relationship management (PRM) comes in. Organizations need to think carefully about how to set up partner onboarding, training, enablement and management by deploying end-to-end process steps, most of which should be fully automated to reduce variability and cost of operations. Having a unified approach also increases the self-service nature of the engagement, which not only reduces operating costs but also significantly increases partner satisfaction.\\n \\tHomegrown automation. Most organizations today have some way to automate their partner relationship management (PRM) activities. Too often, however, automation is achieved by using SharePoint or some other portal as a primary interface with a document library, deal registration and other homegrown applications tied to partner training, incentives management and so on. The total cost of ownership (TCO) for patchwork arrangements like these tends to be significantly higher than for the purpose-built partner relationship management (PRM) automation platforms like ZINFI and others provide today.\\n \\tLack of simplification. We have talked about the importance of simplicity and ease of use in many previous articles. Too often a channel program gets bloated with archaic partner recruitment policies, training, incentives and demand generation programs. Premier channel organizations systematically revamp their partner relationship management (PRM) initiatives to eliminate redundant and confusing programs and process steps. This is essential for keeping partner relationship management (PRM) fresh and relevant to the partner base. Keeping things simple also reduces costs and increases transaction velocities substantially.\\n\\nIn summary, a thoughtful approach with a passion for continuous improvement can keep your partner relationship management (PRM) program fresh and relevant to the partner base. However,'