Implementation timeline

Kernel looks to deliver value starting from Day 0. This is the timeline and commitments you can expect

We suggest preparation for Kernel implementation begins during procurement. We want Day 0 to hit the ground running, this requires some dependancies for your team. See Pre kick-off. Kernel completes a full transformation of your CRM in 30 days or less. If not, we will waive the implementation fee.

The timeline guarantee requires that you fulfil the User requirements in a timely manner.

Timeline: Your first 30 days with kernel

The following is a typical CRM integration. See Alternative deployments for other approaches.

1

Day 0: CRM Access/Kick-off

• Pre kick-off

• Kick-off

• API access (Salesforce integration Dynamics integration)

• Deployment of custom object & fields (see Custom object)

2

Week 1: Account-level cleaning

• Delete inoperational

• Account matching

• Testing & refining configuration, including the Active users and Account risk

3

Week 2: CRM-level cleaning

• Primary record selection

• Corporate hierarchies

• Testing & refining configuration, including How field values are merged and Account matching

4

Week 3: Business logic

• Account matching

• Deliberate duplicates

• How field values are merged

5

Week 4: Actioning the data

• Guided enablement sessions in Kernel's UI with a Kernel solutions engineer

• Surgical updates using the Actions workflow (see Actions)

User requirements

Customer ownership

Due to the important nature of this exercise, Kernel requires that you allocate ¼-½ FTE for the first 30 days.

The allocated resource must be a RevOps analyst or CRM administrator with sufficient access and permissions. See Actions for all user requirements.

We recommend involving your systems admin team during procurement to allow for a seamless start with Kernel.

Accelerated timeline

Kernel allows you to configure the CRM Cleaning & Hierarchies to your preferences, deploy the data quickly to your CRM, and take action on the data to delete bad accounts, correct data quality issues, merge duplicates, and build family trees.

Actioning the data is a critical step for bringing the CRM into a clean, workable state, but it is not required to use Kernel's data to make strategic decisions.

The accelerated timeline runs parallel to the existing implementation and is an opportunity to make use of Kernel's data if you're coming up against strict deadlines.

1

Deploy the data to your CRM

Kernel provides a set of cleaning fields that can be loaded into your Account object or into a separate custom object that mirrors your account. Refer to the minimum list of fields required here.

2

Filter out all accounts that are marked as Delete

If the cleaning action is Delete, it indicates that the company is out of business and/or the website is no longer functional. You can also use the Website verification and Operational status fields directly.

3

Filter out all accounts that are marked as Merge

Accounts marked as Merge have an identified duplicate in the CRM. You can use Kernel's tooling to merge accounts together automatically, but for planning purposes some customers coming up against a deadline find it easier to filter out all accounts from their account lists that are marked as Merge.

4

Associate parents in your CRM with a custom field

Customers can use the custom field provided by Kernel to identify parent-child relationships. Kernel recommends moving this into the CRM's native account hierarchy functionality.

This is often not required for territory & headcount planning.

Risk tiering

For additional control, you can use the Account risk to include accounts that are deemed high risk, such as existing customers and accounts with opportunities in pipeline. For example, an account may be marked as Delete, but if has existing opportunities some customers prefer to include this when creating reports for their account lists.