# 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](/implementation/implementation-timeline/pre-kick-off.md). 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](/implementation/alternative-deployments.md) for other approaches.

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

* [x] [Pre kick-off](/implementation/implementation-timeline/pre-kick-off.md)
* [x] [Kick-off](/implementation/implementation-timeline/kick-off.md)
* [x] API access ([Salesforce integration](/integrations/salesforce-integration.md) [Dynamics integration](/integrations/dynamics-integration.md))
* [x] Deployment of custom object & fields (see [Custom object](/custom-object.md))
  {% endstep %}

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

* [x] [Delete inoperational](/app/actioning/delete.md)
* [x] [Account matching](/account-matching.md)
* [x] Testing & refining configuration, including the [Active users](/app/configuration/active-users.md) and [Account risk](/app/configuration/account-risk.md)
  {% endstep %}

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

* [x] [Primary record selection](/primary-record-selection.md)
* [x] [Corporate hierarchies](/concepts/corporate-hierarchies.md)
* [x] Testing & refining configuration, including [Merge duplicates](/app/actioning/merge.md#how-field-values-are-merged) and [Account matching](/account-matching.md)
  {% endstep %}

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

* [x] [Account matching](/account-matching.md)
* [x] [Merge duplicates](/app/actioning/merge.md#deliberate-duplicates)
* [x] [Merge duplicates](/app/actioning/merge.md#how-field-values-are-merged)
  {% 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 [Actions](/app/actioning.md) workflow (see [Actions](/app/actioning.md))
  {% 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 [Actions](/app/actioning.md) 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](/app/configuration.md) the CRM Cleaning & Hierarchies to your preferences, [deploy](/custom-object.md) the data quickly to your CRM, and take [action](/app/actioning.md) 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](/kernel-fields.md).
{% 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](/app/configuration/account-risk.md) 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kernel.ai/implementation/implementation-timeline.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.