Back to Blog

CRM Implementation: A Six-Step Plan for Small Teams

What to decide, in which order, and who owns each step, from the first list of questions to the review two weeks after launch. With a checklist, a five-week timeline and an honest answer on consultants.

Benjamin WagnerBenjamin Wagnerby Benjamin Wagner
CRM ImplementationCRM Implementation ChecklistCRM Consulting

CRM implementation is the work between buying a CRM and the day your team opens it before anything else. For a team of up to about 20 people on a self-serve CRM, plan five weeks: one week to agree what the CRM must answer and how deals move, one to model and import the data, one to connect channels and train, and two weeks of daily use with one named owner fixing what breaks. The software settings take hours. The agreements and the data clean-up take the rest.

Customermates publishes this guide, and the worked example near the end uses Customermates. The plan itself works with any CRM.

At a glance

Timeline
About five weeks for 2 to 20 people on a self-serve CRM. Larger rollouts with ERP integrations and several departments take months.
Where time goes
Agreeing stage definitions and cleaning data. Configuration is the short part.
Order of import
What you sell, then organizations, then contacts, then deals, so every link has something to point at.
Consultant
Worth it for a large suite, many users, regulated data or ERP integration. Usually not for a small team with one sales process.
Germany
If you have a works council, involve it before rollout: a CRM can fall under co-determination as a system able to monitor performance.

For the Customermates example, compare the small business CRM workflow with the agency CRM workflow before choosing your lists and owners. Include everyday browser and mobile tasks from the CRM app evaluation in the rollout test.

The plan in six steps

Every step ends with something you can point at. If a step produces no written output, it has not happened yet.

StepOutputOwnerTypical time, 5 to 15 people
1. Define what the CRM must answerA list of 5 to 10 questions, each with the field or view that answers itWhoever runs sales, with the founder2 to 3 hours
2. Model records and the pipelineRecord types, stage list with entry rules, 5 to 10 custom fieldsCRM ownerHalf a working day
3. Clean and import dataOne cleaned workbook per record type, imported in orderCRM owner plus one helper2 to 4 working days
4. Connect channels and integrationsMailboxes and other channels connected, at most two integrations liveCRM owner1 to 2 hours per channel and integration
5. Roles, training, launchRoles assigned, one 60 to 90 minute session on real deals, a launch dateCRM owner1 working day
6. Review after two weeksA short list of fields to drop, stages to rename, views to addCRM owner with the team1 hour

These are planning figures for a self-serve CRM, not measurements. A CRM project with several departments, an ERP connection or tens of thousands of messy records needs its own estimate.

Step 1: Define what the CRM must answer

Skip the feature wishlist. Write the questions you want answered on a Monday morning, then name the field or view that answers each one:

  • Which open deals have no next step agreed? A "Next step" date field, and a view filtered on empty or past dates.
  • What is in the pipeline this quarter, and what is it worth if stages are weighted? A stage field with a probability per stage.
  • Where did our last 20 clients come from? A "Source" Single choice field.
  • Who talked to this client last, and on which channel? The activity timeline, or a connected inbox.

Anything that answers none of your questions stays out of the first version. This one rule prevents most of the scope creep that sinks CRM projects. If you have not chosen a system yet, use the same list to compare candidates; the guide to choosing a CRM turns it into a scorecard.

Step 2: Model records and the pipeline

Decide what a deal is in your business. For an agency it may be a project, for a recruiter a placement, for a consultancy a mandate. Then write the stages, each with a rule for entering it, so two people put the same deal in the same column:

StageEnter whenExample probability
QualificationFirst call booked, budget and need not yet confirmed10%
Demo or workshopA meeting with the decision maker happened25%
ProposalA written proposal was sent50%
NegotiationThe client asked for changes to scope, price or terms70%
WonSigned100%
LostDeclined, or no answer after the agreed last follow-up0%

Five to seven stages are enough. Probabilities are your own estimate per stage; they turn deal values into a weighted pipeline, not a prediction. Add a "Lost reason" Single choice field early, because it is the field people regret not having after six months.

Step 3: Clean and import data

Most teams start from spreadsheets, an old CRM export and a few mailboxes. Clean before you import, never after:

  1. Export everything into one workbook per record type.
  2. Delete records nobody has touched in three years unless they are clients.
  3. Merge duplicates. Sort by email address and by company name; most duplicates sit next to each other.
  4. Make values consistent: one spelling per country, one format per phone number, one value per dropdown option.
  5. Import in dependency order: what you sell, then organizations, then contacts, then deals. A deal row that names an organization can then be linked to it.
  6. Import ten rows first, check them in the CRM, then import the rest.

If your data still lives in a sheet, the Excel CRM template shows a layout that imports without retyping.

Step 4: Connect channels and integrations

Connect the mailboxes and messaging accounts where client conversations already happen, so the CRM shows them without anyone copying text across. Limit integrations to two at launch, usually email and one system you cannot work without, such as accounting or a form tool. Every further integration is a separate small project after the two-week review.

For EU teams, data protection belongs in this step. A cloud CRM processes personal data on your behalf, and Article 28(3) GDPR requires a contract with the processor that sets out the subject matter, duration, nature and purpose of the processing. Sign the vendor's data processing agreement before you import real client data.

Step 5: Roles, training, launch

Give each person a role that matches what they need to see. A common small-team setup: founders and the CRM owner see everything, everyone else sees all clients but only the deals assigned to them. Keep it simple at launch; tight permissions mostly produce "I can't find it" messages.

Train on your own deals, not a demo. One session of 60 to 90 minutes is enough when everyone moves their own five open deals through the stages during the session. Pick a launch date after which the old spreadsheet becomes read-only. Without that date, two systems run in parallel and the CRM loses. The CRM training guide has a session outline.

In Germany, check one thing before launch: under § 87 (1) no. 6 BetrVG, a works council has a say in introducing technical systems designed to monitor employee behaviour or performance. Activity histories and per-person pipeline views can fall under that. If you have a works council, involve it in step 1.

Step 6: Review after two weeks

Look at what people actually filled in. Drop fields that stayed empty, rename stages people kept confusing, and add the two or three views that people asked for. Then decide on the next integration. This review is the step most teams skip, and it is where a CRM gets trimmed to the way the team works.

CRM implementation checklist

Before configuration

  • One named CRM owner with time set aside for five weeks
  • 5 to 10 questions the CRM must answer, each mapped to a field or view
  • Stage list with an entry rule per stage, plus a Lost reason field
  • Works council involved, if you have one
  • Data processing agreement signed with the vendor

Data

  • One workbook per record type, duplicates merged, values made consistent
  • Test import of ten rows checked by hand
  • Full import in order: offerings, organizations, contacts, deals

Launch

  • Mailboxes and channels connected for everyone who talks to clients
  • At most two integrations live
  • Roles assigned and tested with a non-admin account
  • One training session on real deals
  • Old spreadsheet set to read-only on launch day

After two weeks

  • Empty fields removed, confusing stages renamed
  • Missing views added
  • Next integration chosen, or consciously postponed

Do you need a CRM consultant?

A CRM consultant plans, configures, migrates and trains for you. On a large suite that is often money well spent. On a small team with a self-serve CRM it mostly buys the six steps above, done by someone who does not know your clients.

Hire a consultant or partner ifDo it yourself if
You are rolling out a large suite with many modulesYou use a self-serve CRM with standard objects
More than about 50 users across several departmentsUnder about 20 users with one sales process
ERP, telephony or data warehouse integration is in scopeEmail plus one or two integrations cover it
Regulated data shapes the architectureStandard GDPR obligations apply
Nobody internal can own the project for a monthOne person can spend a few hours a day on it

Some vendors build onboarding into the price. HubSpot's pricing page lists a required one-time onboarding fee of $1,500 for Sales Hub Professional and $3,500 for Enterprise, on top of the subscription. Both HubSpot and Salesforce run partner directories: the HubSpot Solutions Directory, where partners earn tiers based on client results and can hold a CRM Implementation accreditation, and AppExchange consultants for Salesforce.

There is no reliable public benchmark for hourly or daily consulting rates, so get two proposals and compare what they deliver. A good proposal names a written output for each phase: a requirements document and stage definitions after planning, a configured test system and a migration plan after the build, and trained users plus a handover document after launch. Be careful with these patterns:

  • Pure time and materials with no cap, especially for the planning phase.
  • A system recommendation before anyone has talked to the people who sell.
  • "We will refine requirements during the build."
  • No data migration in scope, which returns later as a change request.
  • No handover plan, so the team cannot change a field without calling the partner.
  • An undisclosed reseller relationship with the CRM vendor. Ask directly.

If you are unsure, run the first two steps of this plan internally before asking for proposals. Either you find you can finish it yourself, or you get a far sharper brief.

Why implementations stall

The pattern is consistent: the problem is rarely the software.

  • Too much at once. Marketing automation, service desk and ERP sync all in phase one. Start with sales and client conversations only.
  • No owner. The project sits with "everyone", so stage definitions are never written and nobody fixes the first annoyances.
  • Dirty data imported as is. People find three versions of the same client on day one and go back to their spreadsheet.
  • Updating the CRM is extra work. If people must copy emails and messages in by hand, entries stop after a few weeks. Connect the conversations instead.

Worked example: implementing Customermates for a six-person consultancy

Here is the plan applied to Customermates, an open-source, AI-native CRM built in Germany, for a consultancy with six people who all talk to clients by email and LinkedIn. Every step below matches the current product; details are in the records documentation and the company settings documentation.

  1. Sign up and run the onboarding wizard

    After your profile, the wizard asks what to do first. "Set up my client workspace" has Mate build your lists, pipeline, dashboard and Knowledge Base pages from a few answers about your business. "Follow up client conversations" writes a follow-up playbook and opens Channels so you can connect LinkedIn or email. Invited people join as "Waiting for approval" until an admin assigns a role and sets them active under Settings › Members.

  2. Name the lists and the pipeline

    In Data model, open a list and change its Name and Plural name under General to rename Deals to Projects, for example. Stages are not preset: in Data model for Deals, add a Stage Single choice field with the options from your stage table (in the cloud, AI setup can create it) and enter a Probability % per stage to get a weighted pipeline.

  3. Add the fields from step 1

    Add custom fields: "Next step" as a date on deals, "Source" and "Lost reason" as Single choice. Customermates has no tags on records; Single choice fields cover that job and work for grouping on the board.

  4. Import one list at a time

    Use More actions › Add from file on each list. It reads .xlsx, .xls and .csv files and lets you map columns to fields; a Record ID column updates existing records instead of creating duplicates. Import services, then organizations, contacts and deals. Row and file size limits are in the records documentation.

  5. Set roles

    Keep the built-in Admin role for the two partners. Create one custom role for consultants: Read access All on contacts and organizations, Create, Edit and Delete with Read access Assigned on deals, so each person sees and edits only the deals they are assigned to.

  6. Connect inboxes and save views

    On Pro, each person connects one account in the unified inbox, usually their mailbox, so client conversations sit next to the contact. Connecting LinkedIn as well is a second account per person, which needs Business. Each person saves their own view, for example "My open deals, Next step empty or past". Do it once per person during training, or share one view with the whole team.

On Customermates Cloud, a routine can take over the Monday question from step 1. Routines run Mate, the in-app assistant, on a schedule and use hosted AI credits. An example instruction for a weekly routine every Monday at 8:00: "List my open deals where Next step is empty or in the past, with the last message from each contact. Do not send anything and do not change records." A routine runs as its owner and may send messages without asking, so an instruction that should only report must say so, as this one does. See the routines documentation for triggers and limits.

What this costs. For six people on Pro, which includes the unified inbox with 1 connected account per user and 5 routines per user, the subscription is €174 per month, billed monthly. If every consultant wants both their mailbox and LinkedIn in the inbox, Business includes 3 connected accounts per user and costs €414 per month for six people. Starter costs €72 per month for six people but has no inbox. Starter, Pro and Business include monthly hosted AI credits per active user; amounts are on the pricing page. Your first workspace starts with Pro free for 14 days without a credit card, enough to run steps 1 to 3 on your real data.

The plan exists to answer one question every Monday: who is waiting on us? With the inbox on Pro, the threads sit on the client record, Mate or your own AI client drafts the reply and the next step, and you review, edit and send. Start your 14-day trial.

FAQ

What is CRM implementation?

CRM implementation is the process of getting a CRM into daily use: defining what it must answer, modelling records and pipeline stages, cleaning and importing data, connecting email and other channels, setting roles, training the team, and reviewing the setup after launch. Choosing the system usually comes just before it.

How long does CRM implementation take?

For a small team on a self-serve CRM, about five weeks, of which two are live use with fixes. Salesforce's own guide says small businesses can need just a few weeks, while larger enterprises with complex integrations may need several months. Data clean-up decides the timeline more than configuration does.

What should a CRM implementation plan include?

For each step, an output, an owner and a date: the questions the CRM must answer, the stage list with entry rules, the field list, the import order, connected channels and integrations, roles, the training session, the launch date when the old system turns read-only, and a review date two weeks later. The six-step table above is a usable starting point.

What are the phases of CRM implementation?

Guides divide it differently: Salesforce lists nine steps, Pipedrive five, consultants often use plan, build and run. The content is the same: requirements, configuration, data migration, training and launch, then review. What matters is that each phase ends with a written output.

How much does CRM implementation cost?

The subscription is the visible part. Internal time for clean-up, configuration and training is usually larger for small teams. Some vendors add a required onboarding fee, for example $1,500 for HubSpot Sales Hub Professional. A consultant-led project adds day rates on top. The CRM cost guide breaks down the full calculation.

Is a CRM hard to learn?

The basics of a modern CRM take an hour: find a contact, move a deal, log a note. What takes longer is the agreement on how your team uses it, which is why the stage definitions and a training session on real deals matter more than the tool.

Third-party details checked on 8 October 2026 against HubSpot Sales Hub pricing, the HubSpot Solutions Directory, Salesforce's CRM implementation guide, AppExchange consultants, Pipedrive's CRM-Einführung guide, the GDPR on EUR-Lex and § 87 BetrVG.

Start from one description

One description. A workspace your agent built.

This is what setup builds from one sentence. Sample data, the real product.

  1. Describe your business

    One sentence about your team, your clients and how you sell.

  2. Mate builds it

    It asks a few questions, then creates the lists, pipeline, dashboard and playbook.

  3. Work in it

    Connect LinkedIn and email. Click through a finished example below.

Your description to Mate

We're a four-person strategy consultancy. Track clients, engagements and proposals, and help us follow up with prospects on LinkedIn.

Widgets built from the workspace's own lists and fields

Customermates for consultants

Every client conversation from email, LinkedIn and WhatsApp in one place. Mate sets up your workspace and drafts the follow-up, you review and send. Works with Claude, ChatGPT or any agent that speaks MCP.

Customermates

Follow up on every client conversation

Start with one channel and one client on Customermates Cloud, or self-host the open-source core.

✓ No credit card required ✓ First 14 days free