# Implementation timeline

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](https://docs.kernel.ai/implementation/implementation-timeline/pre-kick-off "mention"). Kernel completes a full transformation of your CRM in 30 days or less. If not, we will waive the implementation fee.

{% hint style="info" %}
The timeline guarantee requires that you fulfil the [#user-requirements](#user-requirements "mention") in a timely manner.
{% endhint %}

## Timeline: Your first 30 days with kernel

The following is a typical CRM integration. See [alternative-deployments](https://docs.kernel.ai/implementation/alternative-deployments "mention") for other approaches.

{% stepper %}
{% step %}
**Day 0: CRM Access/Kick-off**

* [x] [pre-kick-off](https://docs.kernel.ai/implementation/implementation-timeline/pre-kick-off "mention")
* [x] [kick-off](https://docs.kernel.ai/implementation/implementation-timeline/kick-off "mention")
* [x] API access ([salesforce-integration](https://docs.kernel.ai/integrations/salesforce-integration "mention") [dynamics-integration](https://docs.kernel.ai/integrations/dynamics-integration "mention"))
* [x] Deployment of custom object & fields (see [custom-object](https://docs.kernel.ai/custom-object "mention"))
  {% endstep %}

{% step %}
**Week 1: Account-level cleaning**

* [x] [delete](https://docs.kernel.ai/app/actioning/delete "mention")
* [x] [account-matching](https://docs.kernel.ai/account-matching "mention")
* [x] Testing & refining configuration, including the [active-users](https://docs.kernel.ai/app/configuration/active-users "mention") and [account-risk](https://docs.kernel.ai/app/configuration/account-risk "mention")
  {% endstep %}

{% step %}
**Week 2: CRM-level cleaning**

* [x] [primary-record-selection](https://docs.kernel.ai/primary-record-selection "mention")
* [x] [corporate-hierarchies](https://docs.kernel.ai/concepts/corporate-hierarchies "mention")
* [x] Testing & refining configuration, including [#how-field-values-are-merged](https://docs.kernel.ai/app/actioning/merge#how-field-values-are-merged "mention") and [account-matching](https://docs.kernel.ai/account-matching "mention")
  {% endstep %}

{% step %}
**Week 3: Business logic**

* [x] [account-matching](https://docs.kernel.ai/account-matching "mention")
* [x] [#deliberate-duplicates](https://docs.kernel.ai/app/actioning/merge#deliberate-duplicates "mention")
* [x] [#how-field-values-are-merged](https://docs.kernel.ai/app/actioning/merge#how-field-values-are-merged "mention")
  {% endstep %}

{% step %}
**Week 4: Actioning the data**

* [x] Guided enablement sessions in Kernel's UI with a Kernel solutions engineer
* [x] Surgical updates using the [actioning](https://docs.kernel.ai/app/actioning "mention") workflow (see [actioning](https://docs.kernel.ai/app/actioning "mention"))
  {% endstep %}
  {% endstepper %}

## User requirements

### Customer ownership

Due to the important nature of this exercise, Kernel requires that you allocate <mark style="color:$primary;">¼-½ FTE</mark> for the first 30 days.

The allocated resource must be a RevOps analyst or CRM administrator with sufficient access and permissions. See [actioning](https://docs.kernel.ai/app/actioning "mention") 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](https://docs.kernel.ai/app/configuration) the CRM Cleaning & Hierarchies to your preferences, [deploy](https://docs.kernel.ai/custom-object) the data quickly to your CRM, and take [action](https://docs.kernel.ai/app/actioning) 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.

{% hint style="warning" %}
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.
{% endhint %}

{% stepper %}
{% step %}
**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](https://docs.kernel.ai/kernel-fields).
{% endstep %}

{% step %}
**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.
{% endstep %}

{% step %}
**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`.
{% endstep %}

{% step %}
**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.

{% hint style="info" %}
This is often not required for territory & headcount planning.
{% endhint %}
{% endstep %}
{% endstepper %}

### Risk tiering

For additional control, you can use the [account-risk](https://docs.kernel.ai/app/configuration/account-risk "mention") 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.