ARchitecting Your Analyst Relations Program
December 28, 2018

ARchitecting Your Analyst Relations Program

Kara Lira | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with ARInsights ARchitect

ARchitect is used by the Global Analyst Relations program at Capgemini. We are an eight-member team distributed across three continents. We use ARchitect in the following ways:
1. Manage interactions (briefings, meetings, events) with analysts
2. Manage projects (major research reviews) with analysts
3. Knowledge/content management (tracking coverage of Capgemini by analysts)
4. Reporting back to the business (activity and coverage reports)
Content is accessible to everyone on the global team allowing for transparency in activities. We can also report back to the business on our activities with the click of a button.
  • Consolidation of coverage. ARchitect's Premium Content is an ideal tool. Analyst coverage is centralized in ARchitect -- saving the step of visiting multiple analyst websites to track coverage. We are also able to run customized coverage reports.
  • Interaction creation and maintenance. ARchitect's Interactions allow us to track our interactions with analysts, collaborate on interactions, and keep have a record of everything we've worked on. We can run interaction reports (which can be provided to the business) and briefing documents to keep executives up-to-date on how we've engaged analysts.
  • Projects for project management. ARchitect's Projects enables us to track analyst major reviews (very complex interactions) that can take several months to complete. We can easily look at the status and results of all major reviews -- in addition to keeping track of any red-flag situations.
  • Customization. Interaction, Article (part of Premium Content) and Project entry forms can be customized. Additional details outside of the standard form can be tracked.
  • The ability to clone articles. Since we use this tool heavily for knowledge/content management, we are often creating several entries against the same report.
  • Get the sort feature working on the column headers in grid views.
  • Remove the duplicate status field in Projects (ARchitect has been in touch with me about this already).
  • ARchitect has enabled us to track and report back (with minimum effort) client references from the market analysts. Our ability to demonstrate direct sales support provides validation for the analyst relations program -- especially for those who have a hard time understanding the value of the program.
  • ARchitect has enabled us to provide real-time, customized reporting back to the business - demonstrating the efficacy of our program management.
  • At the most basic level, the ARchitect contract has paid for itself many times in person-hours. Having a centralized system means team members do not need to manually track their own activities in a spreadsheet. In addition, the time it would take to consolidate reports, or customize reports by topic, analyst, etc.
Prior to using ARchitect, we were using Salesforce. While we did have some customization added, it did not nearly have the robustness that ARchitect provides -- especially since it is designed for AR professionals. We've been using ARchitect for about 8 years and have never looked back. Some examples of vast improvements:
1. Analyst firms/bios. With Salesforce, we needed to maintain all analyst bios -- something that ARchitect does.
2. Analyst coverage. We used to track all analyst coverage by visiting multiple analyst websites and manually pasting into spreadsheets. We now not only get a feed of coverage that can be exported into Excel, but we can also customize reports by topic.
3. Reporting. Salesforce did not provide the same reporting capabilities that ARchitect provides.
ARchitect is now the core of our AR program. We leverage it for every aspect of our program -- interactions, projects and knowledge/content management. With a distributed team of 8 working on 3 continents, ARchitect helps keep us on the same page. We can run reports against all aspects of our program. NOTE: ARchitect is dependent on users entering their data. What comes out is only as good as what goes in. We established KPIs to ensure that team members are motivated to enter their activities into ARchitect.