# How we roll out a CRM: eight steps — Auspex field notes

> How Auspex rolls out a CRM — eight steps from team interviews to post-launch support. Why we don

Source: https://auspex.company/en/blog/how-auspex-rolls-out-crm/

[Blog](/en/blog/) / Field Notes

# How we roll out a CRM: eight steps.

By: Andrew Maryasov · Jun 18, 2026 · 6 min read

A CRM rarely fails because of the software. It fails when the system is rolled onto the business from the top down, without anyone working out how the team actually operates — and a month later everyone has quietly gone back to Excel and chat apps. At Auspex, over ten years and fifteen hundred projects, we've boiled the rollout down to eight steps, where configuring the system is only the fifth. Here's what it looks like from the inside, with no marketing gloss.

![Eight-step CRM rollout: conversation, process audit, system choice, scope in writing, setup, training, test period, ongoing support](/images/blog/rollout-8-steps-en.webp)

## 1\. A conversation first, not a demo.

We start not by demoing the system, but with interviews: we get to know the team, how they work, and what they actually need. Three questions pull everything else along — which tasks are painful, what's blocking growth, where clients slip through the cracks. Most companies have never written their process down, so half a project's value is created right here, before the first field is configured.

## 2\. We look at how the business actually works.

We break down how work moves: sales, communication, service, document flow. Every business is different here, and the CRM has to adapt to it, not the other way around. We don't automate a broken process — first we agree on the process, then we build it in the system.

## 3\. We pick the system to fit the job.

We choose the solution that meets the needs, not the one with the longest feature list: from the number of employees to specific sales funnels and the level of automation this particular team needs. Sometimes that's Bitrix24, sometimes Uspacy, Pipedrive or monday — the process decides, not the brand.

## 4\. We spell everything out before we start.

Before we touch a single setting, we put together a clear, transparent proposal: what we'll do, by when, and for how much. We start only after it's approved — no surprises halfway through the project.

## 5\. We configure the system.

We create the portal, add the employees, build the funnels, automations and integrations. We connect telephony, open channels, apps and services — exactly what the team uses day to day. This is the step the client pictures when they say “roll out a CRM” — and it's the fifth, not the first.

## 6\. We train the team.

A CRM only works when the team knows how to use it, so training isn't optional for us. We run it on real work scenarios, not a general tour of the interface, and show how to get the most out of the system.

## 7\. We give time to test, and stay alongside.

After configuration, we leave the team time for a test drive and stay beside them while they get up to speed. The first days surface every habit the design didn't catch — and we quickly fine-tune wherever it's worth optimizing or automating.

## 8\. We stay in touch.

A CRM is a living organism that changes along with the business. So launch isn't the finish line for us: from routine tweaks to building custom solutions, we stay open to new tasks as the business grows into them.

## Why we do it this way.

Notice the pattern? Seven of the eight steps are about people and process, and only one is about the configuration itself. More often than not, what stalls a rollout isn't the technology — it's the process no one dares to pin down, the decision that keeps getting postponed, and dirty data. Take those out of the loop and the system works from day one.

Once the process is in place, the next step is taking the routine out of it. Custom AI agents for a client's specific process are built by our sister brand Grow2.ai (grow2.ai) — and a CRM rolled out through these eight steps gives them a solid foundation.

If someone promises you a serious CRM “turnkey in three days” — ask exactly what they're leaving out. Usually it's the audit, the data cleanup or the training — the very part that makes the system work.

Andrew Maryasov Founder, Auspex

Founder of Auspex. Implementing CRM and automating business processes since 2015 — 1,500+ projects.

[amaryasov.expert →](https://amaryasov.expert)

## Frequently asked

How long does a rollout take?

For a single team with reasonably clean data — about 30 days, with a four-to-six-week range for normal friction: holidays, peak season, data that turned out dirtier than promised. The bottleneck is almost never the software, but cleaning the data and changing people's habits.

Do we have to switch the messaging apps and telephony we already use?

Almost never. We integrate the CRM with what you already have — telephony, WhatsApp, Telegram, web forms, email — so leads and messages land in the system automatically instead of getting lost. The CRM becomes a unifying layer, not a replacement for the tools you're used to.

And what if we have no documented process at all?

That's normal — most teams have never written one down. The first two steps are exactly about this: we map how the work really flows and agree on the process before configuring anything. Without that, a CRM would just cement the existing mess.

Who do we need on our side during the rollout?

One person who makes decisions and responds within the day, access to your current data, and a few hours from the people who actually do the work. The biggest accelerator is a project owner on your side who can say “yes” without convening a committee.

## Business automation digest

2–3 emails a month — what actually works in CRM and automation.

No spam. Unsubscribe in one click.

[Free CRM audit →](/en/contact/)

↳ FREE AUDIT 30 min · free · ↓

## Ready to Get Your Sales Under Control?

Free process audit — 30 minutes, and you'll receive:

1,200+ companies since 2015 · 30-day median go-live

01 A map of where you're losing leads

02 Priorities: what to automate first

03 An implementation plan for 2-4 weeks

We'll call within 24 hours. The plan is yours, even if we don't work together.
