A 30-60-90 day adoption plan.

Most CRM projects measure success on go-live day. The data is migrated, the pipelines are built, the training is done, and everyone celebrates. Then, quietly, people return to spreadsheets and WhatsApp threads, and a year later the leadership team asks why the new platform is not working.

The platform usually works. The adoption did not happen. This piece sets out the 30-60-90 day template we use after a HubSpot go-live. The day ranges are a planning frame, not a promise: a single-market team may move faster, a multi-country group slower. What matters is the order.

Why plan the first 90 days at all?

Because habits form early. In the first weeks after go-live, every user decides whether the new platform is where work happens or an extra place to report it. If managers still ask for the old report, people keep the old process. If the platform saves them time in week one, they come back in week two.

A 90-day plan forces three questions most projects skip: who supports users when they get stuck, how managers will run the business from the platform, and when you add automation without overwhelming people.

Days 1 to 30: how do you stabilise?

The first phase is about confidence. Users need to know the platform works and that help is close.

• Hypercare. A named support channel, daily at first, with someone who can fix configuration on the spot. Log every question; they are your backlog.
• Fix the friction. Remove fields nobody uses, shorten forms and correct the views people open every morning. Small fixes in week one earn trust for bigger changes later.
• Champions. One per team or market, given early access and a direct line to the CRM team. In multi-language markets, champions often explain things better than any manual.
• Switch off the old way. Set a date when the legacy system or spreadsheet becomes read-only. Without it, the old process never ends.

Measure active use: who logs in, who updates records, which teams lag. Do not chase perfect data yet; chase daily habit.

Days 31 to 60: how do you embed it?

The second phase moves the platform from a place people enter data to the place the business is run from. That depends on managers more than users.

• Run the meetings from it. Pipeline reviews, service stand-ups and marketing reviews use HubSpot dashboards on screen. No exported slides.
• Agree the definitions. What counts as a qualified lead, a committed deal or a resolved case, written down and reflected in properties and pipelines.
• Data quality routines. Weekly checks on duplicates, missing owners and stale deals, with owners for each fix. HubSpot's data quality tools help here, as we cover in clean data before agents.
• Second-round training. Short sessions by role, built on the questions logged in phase one, not a repeat of launch training.

Measure data quality and manager use: are the reports trusted, and are decisions made from them?

Days 61 to 90: how do you optimise?

Only now add more. Automation and agents built on a platform people do not yet use simply automate confusion.

• Automate the repeated steps users have complained about: task creation, handoffs between teams, follow-up reminders.
• Add a first agent on a narrow, well-defined use case, with an owner and limits. Our agent operating model sets out how.
• Review against the business case. Compare the measures you set before the project with where you are now. Be honest about gaps.
• Plan the next release. A roadmap for the next quarter, prioritised from the backlog, owned by the business, not the vendor.

Measure outcomes: speed to lead, win rate, resolution time, or whatever number the platform was bought to move.

Who owns the plan?

An executive sponsor who chairs a short fortnightly review, a platform owner inside the business who runs the plan day to day, and the implementation partner in support. The partner should be working itself out of the critical path by day 90. If it is not, capability has not transferred.

How does the plan change across markets?

For groups running one platform across several countries, the template applies per market, not once for the group. A common pattern is to run the full 90 days in the first market, then start the next market's stabilise phase while the first is optimising. The second market benefits from fixes already made, and its champions can learn from the first market's champions.

Language and working habits matter more than features here. Teams that run customer conversations on WhatsApp, Viber or LINE need those channels in the platform from the first phase, or the conversations stay on personal phones. Local champions, local-language guides and support hours that match the market's working day make a larger difference to adoption than any amount of central training. Plan for them from the start rather than adding them when usage stalls.

What usually goes wrong?

• Training replaces support. One launch session, then silence. People forget most of what they were shown before they need it.
• Managers opt out. If the leadership team keeps asking for spreadsheets, so will everyone else.
• Too much, too soon. Ten new automations in week two make the platform feel unpredictable.
• No end to the old system. Two systems of record means none.

Adoption is not a phase of the project. It is the project. Before go-live, set the date the old system becomes read-only.