August 10, 2020 | 02 min read
Share:
Finding the right technology partner is not very different from trying to find a life partner. You have to find someone whom you can respect and trust. Someone who has your back in tough times and prioritises your happiness at all times.
While we have generations of wisdom to fall back on for finding a romantic partner, charting the Route-to-Market digitisation journey for emerging markets is new. It’s fraught with obstacles that are endemic to those markets. You’ll need a technology partner who has a deep understanding of the market challenges, has scalable solutions and is committed to helping achieve your business goals.
Starting with the delivery methodology, here are some fundamental tenets and approaches that your technology partner should follow and bring to the table.
Engagement model: Ensure your technology partner has bought into your RTM business goals and facilitates a business outcome-focused engagement approach.
Support model: Your technology partner should enable a localised support model designed in partnership with regional partners.
Config Vs Custom: It’s vital to access the robustness of the prospective vendor’s solutions. Retail ecosystems in emerging markets are very complex with multiple touchpoints. Technology solutions should factor these complexities with a light delivery model and offer a platform that can be customised as per your ground realities.
Change management: Your technology vendor must participate in the evangelisation of the new tech and have strategies that can increase adoption rates. Ideally, both you and your partner should develop a joint approach with a focus on RTM solution adoption.
In effect, your technology partner should be capable of a standard delivery method with standard processes across the RTM digitisation software lifecycle.
Engagement Process: Your technology partner should be completely focused on driving your business outcomes. You can assess the partner’s capacity to provide the necessary support in their engagement models across the pilot, go-live and ongoing stages of the project.
Pilot or Pre-Go Live Stage: The new tech should enable your teams to hit the ground running fast. It is possible only if the RTM platform is configured to mirror your processes. Ensure the tech partner offers train-the-trainer programs to accelerate the adoption of the new technology immediately after Go Live.
Typical timeline: 4 to 8 weeks
Go-live Stage: The success of your RTM digital transformation hinges on your adoption drives and change management. The right tech partner recognises the requirements and should handhold your users through the adoption process. The foundation for the adoption would have been set in the Pre-Go Live Stage itself. You can ensure success by creating evangelisation support KPIs for your tech partner and working with them to ensure 100% adoption rates.
Typical timeline: 8 to 12 weeks
Ongoing Support: The good news is that your ecosystem will change permanently in the digitisation journey. But it might take a while before the use of the new technology becomes second to breathing. It is a critical period for your RTM digital transformation. Have patience.
Until the use of the platform becomes a habit for your users, a committed technology partner will continue to provide ongoing support. It will include offering business analysis that can enable your teams to drive the right RTM actions. The partner should create a centralised tech support system with defined SLAs.
Typical timeline: Ongoing with weekly connects
Like any relationship, it requires both parties to be aware of the pitfalls and the hacks that can create a seamless engagement. Ultimately, your RTM digital transformation is the bigger goal and one that will bring high dividends for your brand.
We compared the strengths and weaknesses of top technology solution providers to digitise your downstream supply chains and route to market and created a competitive analysis report. You can download the report here.
Latest Posts
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
collect_chat_launcher_load | 1 month | This cookie is set by the provider Collect.chat. This cookie is used for enabling the chat function on the website. |
collect_chat_page_load | 1 month | This cookie is set by the provider Collect.chat. This cookie is used for optimizing the chat-box functionality by recognising the user. |
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookies is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
CONSENT | 16 years 4 months 14 hours 16 minutes | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_gat_gtag_UA_34263932_3 | 1 minute | This cookie is set by Google and is used to distinguish users. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
Cookie | Duration | Description |
---|---|---|
fr | 3 months | The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
yt-remote-connected-devices | never | These cookies are set via embedded youtube-videos. |
yt-remote-device-id | never | These cookies are set via embedded youtube-videos. |
yt.innertube::nextId | never | These cookies are set via embedded youtube-videos. |
yt.innertube::requests | never | These cookies are set via embedded youtube-videos. |
_fbp | 3 months | This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website. |