How to implement Endgame

How to implement Endgame

Last Updated: March 21, 2023

From start to finish

In the article, we’ll walk through all 6 major milestones from discovery to evaluation to go live and beyond.

① Discovery

How does your team operate today? What are your current and upcoming business priorities? What problems are you trying to solve?

We have a lot to learn about your business. By discussing these sorts of topics, we can get a better sense of data requirements and timeline for Endgame implementation.

After this discovery call, we’ll create a shared Slack channel for collaboration as we enter the next phase.

② Connect data

Once we receive your data, we’ll perform a data analysis. At the end of this analysis, we may have questions, recommendations, or requests for your data team. Often this process concludes without blockers.

③ Define and create workflows

Now that we have context on your business goals and an understanding of your data, we will work with you to build your product-led sales motion. This is often a highly-collaborative with rapid iteration. Ultimately the question is: How should your reps most effectively leverage Endgame in their day-to-day work?

Once workflows are agreed on, our team will build your Endgame configuration. We’ll handle this entirely, however we may have questions for your team along the way.

④ Demo with your data

The best part! We’ll give you a live demo of your data in Endgame. On this call, we’ll give you basic product orientation and a demo of the workflows we designed together.

After this call, you and your team can give Endgame a spin and immediately start customizing, experimenting, and creating new views.

⑤ Onboarding

At this point, Endgame is already live for your pilot team. When you’re ready, you can self-provision your full team. The Endgame team will be available to setup 1-on-1 or group onboarding sessions, tailored to your format preferences and schedule.

⑥ Recurring reviews

We’ll setup a regular cadence to review Endgame with you. What’s changed, what’s working, what’s not? We’ll also use this time to perform ongoing data audits, clean-up (e.g. removing under utilized views), and configuration review / sharing best practices.