How to implement a new commercial process in phases (pilot, comparison, and deployment) without slowing down sales. Cleverea real case: +20% conversion.
Can you change your sales process without slowing down sales? Yes, if the change is done in phases: a small pilot, a data-driven comparison against the previous process, and a gradual rollout to the rest of the team. Nobody stops selling in the meantime, and each phase determines whether to move to the next.
Updated: October 2026 · Written by Pablo Pascual, co-founder of Vixiees.
Almost all sales directors know what process they want their team to follow. The problem comes on the day of changing it: the team has targets to meet this month, the pipeline cannot stall, and no one wants to be responsible for a week of lost sales from "trying something new."
Why most sales process changes fail
Most changes do not fail because of the idea, but because of how they are implemented. According to Beer and Nohria in the Harvard Business Review (2000), around 70% of change initiatives fail. What we see most in B2C sales teams is changing all at once: on a Monday, the new process is presented to the entire team, the tool is switched, and everyone is expected to follow it from day one.
What happens next is predictable:
Sales drop during the transition, because the entire team is learning at the same time and no one is selling like they used to.
There is nothing to compare against, because if everyone switches on the same day, you cannot know whether the new process works better or if it was simply a different month.
The team goes back to the old way as soon as monitoring relaxes, because nothing forces them to follow the new process.
Change management matters more than it seems: in research by Prosci, 88% of projects with excellent change management met or exceeded their objectives, compared to 13% of those with poor change management.
The Pilot-Comparison-Rollout (PCR) method: 3 phases in 8 weeks
A sales process change without stopping the team is implemented in three phases over about eight weeks in total. Each phase has a goal and a condition to move to the next, so the risk never affects the entire team at once.
Pilot (weeks 1 and 2). The new process is used by only 2 or 3 reps, ideally those most eager to try it out. The rest of the team continues selling in the exact same way. Goal: detect real process flaws at minimal cost.
Comparison (weeks 3 and 4). The pilot group's metrics are compared with those of the rest of the team and with the previous period: calls made, response time, follow-ups completed, and conversion rate. Goal: decide with data, not opinions, whether the new process works.
Rollout (weeks 5 to 8). If the comparison goes well, the process is rolled out to the rest of the team in cohorts. The pilot reps already know how to use it and help the others. Goal: get the entire team working the same way without a week of downtime.
The key is that the new process does not rely on the memory or willingness of each sales rep. If the system decides which lead to work next, through which channel, and with which script, as Next Task does, the process is followed even when the team is swamped. If it depends on each person remembering, the team goes back to their old habits as soon as oversight decreases.
Real case study: how Cleverea changed its process in 8 weeks without stopping sales
Cleverea is a Spanish insurtech with 20 sales agents handling thousands of leads per month from comparison sites and inbound campaigns. They had HubSpot and Aircall, but no system enforced the process the company had designed.
"Before, it depended entirely on what the rep decided."
Álvaro Sanz, CEO and founder of Cleverea
Compliance with their follow-up policies was at 0%, there were between 5 and 7 duplicate deals per customer, and higher-margin products were ignored. Changing 20 agents all at once was too risky, so they implemented it in phases, without a big bang:
Phase | Weeks | What Cleverea did |
|---|---|---|
Pilot | 1 and 2 | Vixiees for just 2 or 3 agents, on top of HubSpot and Aircall, without switching CRMs |
Comparison | 3 and 4 | Pilot metrics compared to the previous process |
Rollout | 5 to 8 | Full rollout to the rest of the team |
In the first two months following implementation, Cleverea achieved 20% higher overall conversion and 45% more calls with the same team, while eliminating seasonality in sales and productivity. All without hiring anyone else or leaving HubSpot.
"It would be a major headache if Vixiees disappeared."
Álvaro Sanz, CEO and founder of Cleverea
Data reported by Cleverea. See the full Cleverea case study →
What to measure in each phase to decide whether to continue
Each phase requires a single signal to decide whether to move forward: in the pilot, that the process is followed every day without supervision; in the comparison, that the pilot group matches or improves upon the rest of the team's conversion rate; in the rollout, that each new cohort reaches the pilot's numbers. Without that signal, the pilot drags on indefinitely.
Phase | What to measure | Signal to move forward |
|---|---|---|
Pilot | Whether the pilot reps follow the new process every day | The process is followed without constant supervision |
Comparison | Calls, response time, follow-ups, and conversion rate compared to the rest of the team | The pilot matches or improves upon the previous process |
Rollout | The same metrics, cohort by cohort | Each new cohort reaches the pilot's numbers |
If the team resists the change, the problem is usually not the process, but the timing. In resistance to change in sales, you can find the real cost of continuing to wait.
Do you want to change your sales process without stopping your team?
Vixiees sits on top of your existing CRM, decides the next touchpoint for every lead, and ensures the process is followed from the first pilot rep to the last one in the rollout.
Keep reading: how to add a sales execution layer without switching CRMs and how to clone your top performer's process.
Opinion from Pablo Pascual, co-founder of Vixiees: the most expensive mistake when changing a sales process is changing the entire team on the same day. Not only because of the drop in sales, but because you are left without a control group and you never know if the change worked. A pilot with 2 or 3 salespeople costs almost nothing and gives you the only answer that matters: whether the new process sells more than the previous one with your team and your leads.
Frequently Asked Questions
How long does it take to implement a sales process change?
With the phased method, about eight weeks: two of pilot, two of comparison, and four of rollout to the rest of the team. This is the timeline that Cleverea followed with 20 agents.
How many salespeople should participate in the pilot?
Between 2 and 3 is enough to detect real process failures without risking the month's sales. It's better if they are salespeople who are eager to try it.
Do you have to change CRM to change the sales process?
No. The process can be implemented with an execution layer on top of the CRM you already have. Cleverea kept HubSpot and Aircall throughout the entire change.
What happens if the pilot does not improve results?
The process is adjusted and the pilot is repeated before rolling it out. That is the advantage of doing it in phases: the failure only affects 2 or 3 salespeople, not the entire team.
