Phase 0 >> Preparing for Kick-Off

What can I expect?

Setting the right expectations to start is important, and we want to ensure you have a successful experience! Please see below for what the team should plan for and be aware of as we approach kick-off with the integration project.

• Project Scoping + Kick-off Call:  
  • First, you'll be invited to schedule a call with your Vertify One Team and complete a form that addresses key integration questions, including team roles, lead workflows, and other pertinent information that will be needed to help inform the project. 
  • During the call, the teams will review the items below, including timelines, onboarding tasks, and will set up weekly calls to progress the project. 

• Team Roles + Responsibilities:
  • Vertify Admin - Just like you have administrators for the systems being integrated, you also need to have a person who will be the administrator for Vertify.  
    • This person is the primary point of contact for the implementation and will be trained by your Vertify team to configure, test, and support the integration with Vertify, both during and after go-live.
    • This person is responsible for partnering with the Vertify team for all training and tasks assigned throughout the onboarding. 
  • External System Admins - during the project, the team will need support from the administrators of the external systems being used (e.g., Marketo, Salesforce) for creation of custom fields or assistance understanding errors or workflow processes.
    • It’s critical that you have a clear understanding of how you will use both integrated systems. Your system admins can help provide feedback on this, including the following: when records should sync between these systems, what fields should be synced in each direction, and how often and how many records should move.  

• Timelines: 
  • An average integration project can take between 4-6 weeks.
  • You'll have full support from your Vertify One Team, and will have a lead data integration specialist and a dedicated customer success manager partnered with you during your onboarding.
  • If you are new to one of your systems (i.e., onboarding with Marketo), please be advised that we do not recommend starting the Vertify onboarding until you are about half-way through implementing the system being integrated with that team. 
  • Please note that additional time allowance should be factored in if additional resources are needed (examples: external system support, custom connector build).
  • Onboarding will kick off when the system credentials are provided, and we’re able to authenticate successfully. 

• Guided Onboarding: 
  • We provide guided onboarding, involving at least one primary point of contact from your team who will act as the Vertify point of contact and Admin as noted above.
  • To progress forward in the project, all action items assigned by the Vertify team will need to be completed prior to the next training session.
  • During the onboarding project, your Vertify team will train you on how to setup and use our product.

• Vertify Product Setup: 
  • The onboarding packages include services for the configuration of Vertify only. 
  • Regardless of the implementation type, it is the customer's responsibility to set up and configure the external systems being integrated. 
    • This includes things such as creating and setting up custom fields, establishing workflows, 
  • There are usually a small number of setup tasks to prepare systems for integration (e.g. establishing credentials or API tokens, setting up integration workflows, etc.) within the external systems to be integrated.  
    • Assistance will be provided should you have any questions.

Additional Considerations:

• Building and Keeping a Healthy Integration
  • What makes a successful integration project, and what happens after go-live? 
  • At Vertify, we believe it starts at project kick-off and involves communication with all key stakeholders of the project. What can make this formula so successful is that the project team works week by week towards the shared goal of a healthy integration.
  • The guided implementation process permits customers to see our solution as a framework from which to build, from a single one-to-one endpoint integration to a multi end-point, robust integration.  

• Managing Integration Risks
  • We want every customer to be successful, and customers that are engaged and appreciate these risks tend to avoid and manage them.
  • Here are some examples of the risks that integrating two or more systems could present to an organization:
    • Overwriting critical data
    • Accidentally exposing critical data to the wrong audience or users
    • Implementing changes and breaking the integration causing updates to not occur
    • Delaying the integration causing timed procedures to fire late or not at all
    • Not defining a source of truth for the data. What records and what fields in which system do we trust?
    • Integration historical knowledge lost with staff transitions
    • Untrained staff responsible for managing the integration
    • No staff responsible for managing the integration
    • No staff responsible for reviewing integration records in error condition
    • Skipping the testing stage when changing the integration
    • Hitting size or record count or API call limits in target systems
  • Getting a handle around these risks begins by acknowledging that they are possible when integrating systems. These risks are also highly dependent upon what is being integrated and how the integration is being managed.

Preparing for success!

We encourage our customers to adopt some key process steps early and throughout the life of their integration. Our goal with these recommendations is your success.

Phase 1 >> Discovery and Onboarding Phase