Introducing a CRM: A Six-Phase Project Plan Your Team Will Follow

Why does the team not use the new CRM?

The sequence is familiar. A CRM, meaning software for contacts and sales opportunities, is bought and set up. There is a two-hour training session. In the first weeks everyone diligently enters data. After three months one person maintains the system conscientiously, two catch up when reminded, and the best salesperson keeps their own list.

The usual explanation is that the team is not disciplined enough. It falls short. People maintain a system when it helps them with their own work and fits what they do anyway. They work around it when it is extra work whose benefit lands with someone else.

Zablah, Bellenger, and Johnston described this relationship in a conceptual model as early as 2004. According to it, a CRM program consists of three elements: employees, processes, and technology. If they do not fit together, gaps arise between process and technology, between technology and employees, and between employees and process. These gaps create an inner contradiction among users, and its strength decides whether they adopt the system or resist it. It is a model and not a measurement, but it explains why good software alone solves nothing.

The central question, then: how do you introduce a CRM so that the team is still using it after three months? To answer it, we first present a project plan in six phases, then go through the phases one by one from goal and workflow to routine, and finally clarify what role you play as the owner.

A CRM has not been introduced once it is installed. It has been introduced once nobody misses the old list.

What does a project plan for a CRM rollout look like?

The following plan is called the six-phase plan here. Five of the six phases deal with goals, workflows, and habits. Technology comes in phase 4, and it is the shortest explanation in this article.

1. Goal and number

   You define which problem the CRM is supposed to solve and which number tells you that it has.

2. Workflow

   You settle the stages of the sales process, the owners, and the few mandatory entries.

3. Selection

   You use the workflow to choose the type of solution and test no more than two candidates.

4. Setup and data

   You map stages and fields and transfer only cleaned, current data.

5. Pilot and training

   Two or three people work with real cases for a few weeks, then the team is trained on these cases.

6. Cutoff date and routine

   The old list ends on a fixed day, and the CRM becomes the basis of the weekly sales meeting.

Phases 1 and 2: Which goal and which workflow do you define?

A usable goal describes a state in the company and names no product. “We are introducing a CRM” is not a goal. “Every quote is followed up within five business days” is one. The matching number is the share of quotes followed up, and you measure it once before the start, even if that is tedious manual work.

Next comes the workflow. You need five to seven stages, one owner per stage, and a verifiable result. The template is in the article on how to visualize your sales process. Why this step comes before the software is explained in the article on process before tool.

The most important decision in this phase concerns the mandatory fields. Every field that has to be filled in costs time for every sales opportunity. Five are enough to start.

• Customer and contact person
• Stage of the sales opportunity
• Expected order value, as a rough estimate
• Next step in one sentence
• Date of the next step and responsible person

Phases 3 and 4: How do you select, and what belongs in the setup?

A brief note is enough on selection, because the comparison of solution types is in the article on CRM for small businesses. What matters is the order: first the type of solution, then two candidates, then a test with five real sales opportunities. If you choose a work platform instead of a dedicated CRM, such as quik OS, a tool from a business partner of Owners Council for tasks, knowledge, and strategy, you go through the same six phases. The plan does not depend on the product.

For the setup, the rule is: as little as possible. The stages from phase 2 become the stages in the system, the five mandatory fields become mandatory fields, and one view shows all open sales opportunities with an overdue date. Everything else stays switched off.

Most of the work is in the data. Old lists contain duplicate contacts, former contact persons, and quotes that have been open for two years. If you transfer that unchecked, you start with a system nobody trusts.

• Transfer only active contacts: customers and prospects with contact in the past one to two years. The rest stays in the archive.
• Check open quotes individually: every transferred quote gets a stage and a next date. Whatever nobody is pursuing anymore is closed as lost.
• Clean up duplicates before the import: one customer, one entry. That is easier in the old spreadsheet than in the new system.
• Make one person responsible: a data transfer without an owner never gets finished.

Phase 5: How do pilot and training work so that the team comes along?

The pilot is the most important phase and the one most often cut. Two or three people work exclusively in the new system for three weeks, with all their current sales opportunities. Do not select only enthusiasts for it. A skeptic in the pilot finds the spots where the system gets in the way of everyday work before the whole team finds them.

Research supports this approach. In a qualitative study based on 18 interviews in business-to-business sales, fourteen of them with sales directors and sales managers (Belaid and Ben Moallem, 2026), the adoption of digital tools was driven mainly by perceived usefulness: time savings, a better overview of open opportunities, and more reliable follow-up. The most frequent barrier was duplicate administrative work, because personal notes, Excel lists, or email folders kept running alongside the CRM. A second barrier concerned training. Where it was limited to a technical demonstration at launch, employees knew where to click, according to the respondents, but not why the system improved their work.

The authors describe four levers as effective: training, leaders who use the tool themselves, colleagues from the team who act as contact persons and role models, and a rollout in stages. Your pilot covers two of them, because the pilot users become exactly these contact persons. The findings are assessments from interviews, mostly from industry and technical services, and not statistically tested relationships.

A survey of 198 small and medium-sized enterprises in the Chinese province of Zhejiang on the adoption of social CRM (Wang and colleagues, 2024) names expected benefit, expected effort, and attitude toward the system as direct determinants. For your pilot, a simple test question for every participant follows from this: what did the system take off your hands this week? If nobody has an answer, the setup is not finished yet.

Phase 6: How do you make the CRM a routine?

On the cutoff date the old list ends. It is stored read-only and no longer maintained. From this day on, one rule applies, and the owner personally sets the example: the sales meeting only discusses what is in the CRM. Anyone who has not created a sales opportunity there cannot bring it up in the meeting.

Whether the rollout holds is shown by a simple count after four to six weeks. You compare how many sales opportunities actually exist in the company with what is in the system.

The meeting itself needs a fixed agenda, as described in the article on weekly planning in the team. What you can derive for forecasts from well-maintained data is covered in the article on pipeline management in small and mid-sized companies. Extras such as automatic reminders only come now; more on that under automating sales.

What role do you play as the owner in a CRM rollout?

In a small company, the owner's behavior decides more than any training concept. A survey of 102 micro-firms in the Portuguese estate agent sector (Franco and Garcia, 2018) examined what drives the successful implementation of information technology. In early 2015, around 1,500 firms with no more than ten staff were contacted; about seven percent responded, a little over half of them owners. Internal factors, more precisely organizational aspects, enabled successful implementation and had the greatest influence on the firms' performance. The items behind this included employee involvement, a shared awareness of the need for change, and knowledge of the overall business process. External factors such as outside IT consultants and networking showed no statistically significant influence on performance. The study covers one industry in one country, the response rate was low, and performance rests on the respondents' own assessment. It still warns against handing the rollout over to a service provider.

A workshop with 31 practitioners from process projects at small and medium-sized enterprises (Lückmann and Feldmann, 2017) points in the same direction. They named project integration, project controlling, and stakeholder management as the most important areas for project success.

• You use the system yourself. If you ask for the status instead of looking it up, the team learns that word of mouth still counts.
• You protect the five-field limit. Every request for another field crosses your desk.
• You use the data visibly. Decisions in the sales meeting refer to the overview in the system.
• You praise maintenance and not only closed deals. Whoever hands over cleanly makes vacation cover and onboarding possible.

If you have been the most important salesperson yourself so far, the rollout is also the moment to move your knowledge about customers from your head into a system. The article on systematizing founder-led sales describes how to do that.

The next step

1. Phrase the goal as a state in the company and measure the matching number once by hand.
2. Write the stages of your sales process on one page and define five mandatory fields.
3. Name two or three people for the pilot, including a skeptical one.
4. Put a cutoff date in the calendar on which the old list ends.
5. Decide who cleans up the data and by when.

With these five points the first two phases are almost done, and you have not touched any software yet. That is the right position from which to begin the selection.

At the start we asked how to introduce a CRM so that the team uses it for good. As the model by Zablah and colleagues suggests, this depends less on the software than on the fit between employees, process, and technology. The six phases follow from this, with few mandatory fields, a pilot with real users, and a cutoff date on which the old list ends. The CRM has only been introduced once nobody misses that list.