CRM Implementation: A 90-Day Plan

Why CRM implementations fail

Almost never for technical reasons. Modern platforms do what they claim, and competent implementers can configure them. Implementations fail because the company never decided what the system should represent, so the configuration encodes three people's differing assumptions and produces numbers nobody trusts.

The framing that prevents it: an implementation is a decision project with a configuration phase attached. The configuration is the easy part and the part everyone plans for.

Phase 1 — Decisions (weeks 1–2)

No configuration happens here. The output is a signed document.

• Object model. What accounts, contacts, opportunities, and any custom objects represent. In B2B the account is the primary object — building around contacts produces a duplicate problem that compounds for years.
• Lifecycle stages and the objective entry condition for each, plus which system sets it.
• Deal stages with exit criteria that someone who was not on the call could verify. If the criterion is a feeling, it is not a criterion.
• Deal creation trigger. If a deal is created at first conversation, your pipeline report is a conversation report.
• Source of truth per data point. For every important fact, one owning system and the direction the sync runs.
• Required fields only where a decision or routing rule depends on the value.

Phase 2 — Core build (weeks 3–5)

1. 01
   Objects, fields, and naming

   Build only what the signed model contains. Use consistent naming and fill in the description on every field — an undocumented field becomes an orphan within two staff changes.

2. 02
   Pipelines and stages

   One pipeline per genuinely distinct sales process, not per team or product. Multiple near-identical pipelines make every cross-motion report a manual reconciliation forever.

3. 03
   Validation that enforces the criteria

   Stage exit criteria enforced at the point of stage change. This is what converts your process from a document into a system, and it is the step most often deferred and never returned to.

4. 04
   Users, teams, and sharing

   Mirror how records are actually owned. Routing and reporting both inherit from this structure, so getting it wrong here propagates everywhere.

5. 05
   Two-axis lead scoring skeleton

   Fit and intent as separate scores rather than one blended number — a single score cannot tell you whether to nurture or to call.

Phase 3 — Migration and integrations (weeks 5–8)

The phase that overruns, every time, in every implementation. Three rules contain it.

• Set a cutoff and hold it. Records touched in the last 18–24 months migrate; everything older is archived outside the CRM. Importing a dead database makes it your problem again at a higher storage tier.
• Deduplicate before import, in a staging file. Merging at volume inside a live CRM is slow, lossy, and hard to reverse.
• Test every integration bidirectionally. For each connected system verify create, update, and delete behaviour in both directions. Delete behaviour is where the expensive surprises live, and nobody tests it.

A useful discipline: write down the record counts you expect after migration before you run it. Reconciling actual against expected catches silent truncation, which otherwise surfaces months later as a gap nobody can explain.

Phase 4 — Automation, reporting, adoption (weeks 8–12)

Adoption is a build task

Most implementation plans allocate a training session in the final week. That is not adoption work; it is a briefing. Adoption is the thing that determines whether the previous eleven weeks produced value, and it needs its own budget and its own sequence.

1. 01
   Train by role, not by feature

   An SDR and an account executive need different twenty-minute sessions. A single walkthrough of every feature teaches nobody what to do on Monday.

2. 02
   Remove every field a rep cannot confidently answer

   Do this before go-live. Each unanswerable required field is a daily reason to work around the system, and workarounds become permanent within a month.

3. 03
   Run the first four pipeline reviews in the CRM

   Leadership running the number from the system is worth more than any amount of training. If they use a spreadsheet, so will everyone else.

4. 04
   Publish an exception report weekly for the first month

   Records created outside the intended path, missing required fields, past-dated close dates. Visible, by team, with a named owner.

What to measure after go-live

• Required field completion at stage change — above 95%, or the fields or the training are wrong.
• Open deals with a close date in the past — under 5%, or the forecast is fiction.
• Records created outside the intended path — near zero, or a shadow process exists.
• Weekly active users against licences — above 90%, or adoption failed for a segment worth identifying.

Read these weekly for the first quarter. An implementation is finished when adoption holds, not when the configuration is complete — and the gap between those two moments is where most of the value is won or lost. Platform-specific detail is in HubSpot implementation and RevOps in Salesforce.