Pre kick-off

Work that can be done pre-sign/kick-off to start fast.

To start implementing Kernel we need a few key things that allow us to ingest the data from your CRM and also begin to work on using our AI to clean your data.

The following includes the steps that we recommend taking before our kickoff call so that we spend more time working on actioning and configuring Kernel to your use case.

Salesforce Access

Reach out to Admin

This is the most important part of the integration process. This is usually the part that takes the longest as it has a dependency on teams outside of RevOps. In order to get access to the CRM as fast as possible, we recommend touching base with your Salesforce admin team early in the process.

This documentation contains everything that your Salesforce admin needs to be able to set up Kernel. If they have any questions, we're happy to set up a call with one of our technical team members so that we alleviate any blockers.

Salesforce integrationInternal data requirements

RevOps

Ahead of the main kick-off, you should familiarise yourself with the expected timeline for implementation and ensure the respective resources are allocated ahead of time, alongside having alignment on the deployment approach. This will allow for a smooth implementation and ensure deadlines are met.

Implementation timeline

Basic Configuration

You will get access to the Kernel platform. This will allow you to start setting up some of the basic configuration for Kernel once we have access to your CRM. Below are the elements of the basic configuration that you can start to consider as a team prior to getting access to the app:

• Account identity

  • This is the process of deciding what element of master data (name, website, LinkedIn) actually represents this account.

  • The main question to ask here is: if I were to look at this account, all else being equal, what data point would I use to determine what the actual identity of the account is? Would you bias towards the account URL or the account name?

  • Kernel needs to understand this so that we can do basic account-level cleaning to ensure we are enriching and cleaning the correct entity.

• Deliberate duplicates

  • These are accounts within your CRM that deliberately have duplicates for various reasons.

  • The main reasons for this are to do with billing or links into your product

  • Kernel needs to be able to identify these accounts within your CRM so that we can ensure we do not merge deliberate duplicates but still merge accounts thatare genuine duplicates.

  • You will be able to configure the logic within the Kernel app to ensure we accurately capture these accounts.

• CRM specific elements

  • You have the best understanding of your CRM. We will run models that interpret the data and structure of your CRM. Your guidance on the best fields to use and the structure of objects helps in the deployment and application of Kernel data.

  • The sooner we understand the nuances of your CRM, the easier and faster it will be to deploy Kernel.

Account matching