Home  ›  Services  ›  Change Management

A new system only helps when the way of working changes with it.

A CRM can be configured correctly while teams still rely on old spreadsheets, informal handovers and familiar workarounds.

Kongo helps sales, marketing, service and finance teams make the transition to new systems and processes, with a clear understanding of what is changing, why it matters and what is expected of them.

The change is not just on the screen.

A new sales process can change what counts as a qualified opportunity. An onboarding workflow can change when delivery takes ownership. A finance integration can change who checks the details before an invoice is raised. An AI agent can change which work a person performs and which decisions they need to review.

Those are changes to responsibilities and behaviour, not just software.

We work with the people affected to make those changes explicit and practical, rather than leaving everyone to interpret a new system for themselves.

Make the transition part of the delivery plan.

Give people a clear reason for the change.

We connect the proposed changes with the commercial problem they are intended to solve. People should understand the purpose, the implications for their work and what will remain the same.

Involve the people who know the work.

We identify the stakeholders and team representatives who need to contribute. Their input helps expose practical constraints, test assumptions and improve the process before it becomes the expected way of working.

Make responsibilities explicit.

We help define ownership, handover criteria, approval responsibilities and escalation paths. The team should know who acts next, not just which button moves a record to the next stage. We also work with managers on how they will reinforce the approach and respond when it is not followed.

Prepare for the transition.

We coordinate communication, readiness checks and the move from existing processes to the new approach. That includes identifying what needs to be ready, where support is required and which old workarounds should be retired.

Support the change after launch.

We help leaders and teams review what is working, address confusion and reinforce the agreed approach. Early feedback should inform sensible adjustments, rather than allowing a parallel process to quietly become the norm.

One handover. Several teams. A shared understanding.

Consider the move from sales to customer onboarding.

Sales needs to know what information must be complete. Delivery needs to know when it owns the customer relationship. Finance needs to know which terms have been agreed. The customer needs a clear next step.

The technology can support that handover, but the teams first need to agree how it works. If onboarding is held because information is missing, someone needs to own the correction. If an automated check flags an exception, someone needs to know how to assess it.

Change management connects those expectations with the process being implemented.

Look for evidence in the work.

We agree practical signs that the change is taking hold: handovers arriving with the required information, decisions following the agreed approval route and teams knowing where to take an exception.

These signals are more useful than treating a launch announcement or attendance at a training session as proof that the business has changed.

Shape the change while the solution is being designed.

GTM Advisory establishes the commercial direction. Integration and orchestration change how work is performed across systems. Change Management brings the people affected into those decisions and helps prepare the organisation for the transition.

Training and Adoption then develops the practical capability to work in the new way. Where AI is involved, governance helps establish the boundaries and responsibilities that people need to understand.

Feedback from the team can change the design. We do not treat change management as a communication exercise added after the technical decisions have already been made.

Common questions.

How is change management different from training?

Training helps people perform their work using the new tools and processes. Change management addresses the wider transition: understanding, involvement, responsibilities, leadership and reinforcement. They support each other, but they are not interchangeable.

Is this only for CRM implementations?

No. The same work can support changes to commercial processes, integrations, orchestration and the introduction of AI. Our focus remains on how sales, marketing, service and finance teams work together.

Can you help after a system has already launched?

Yes. We can examine where the intended approach and everyday practice differ, then help you address unclear ownership, process friction, communication gaps or capability needs.

Make the change work for the people doing the work.

Bring us the process or system you are introducing, and the teams it will affect. We will help you plan the transition alongside the delivery.