Software goes live on a date. Work changes over months, one habit at a time. That gap is why two organisations can install the same system and get different results: one treats the rollout as a technology project, the other as a change to how people decide, record and report.
This guide is for the manager who has selected the software and now has to buy the human side of the implementation. It explains what change management should include, how to compare providers on evidence, and which terms protect the investment after the consultants leave.
What you are actually buying
Change management is not a launch email, a slide deck and two training days. It is a managed transition with five outputs: an agreed future state, a role-by-role impact assessment, communication and capability plans, evidence that people are ready, and a mechanism for fixing what the rollout breaks.
Training is one component. So is communication. Neither substitutes for decisions about who owns a process after go-live, which old reports are retired, and what a manager checks each week. If a proposal cannot describe those decisions, it is selling events rather than change.
Write the change statement first
Before approaching providers, write one page that answers:
- What is changing: the process, system and data that move from the current state to the future state.
- Who is affected: each role, location and shift, including people who only approve or read reports.
- What stops, starts and continues: the old spreadsheets that will be retired, the new fields that must be completed, the reports that remain.
- Why now: the business reason in plain language, including what happens if adoption is partial.
- Who owns the change: a named business sponsor with authority to settle process disputes, not a project coordinator who can only escalate.
This page becomes the brief. It also exposes a common problem early: the organisation has not decided how the future process works, so no provider can help people adopt it.
Deliverables and acceptance criteria
Ask every provider to price the same set of deliverables. Then judge the quality of the samples, not the labels.
- Stakeholder and impact map: groups, influence, impact severity and the specific behaviour that must change.
- Change network: named super-users or champions in each location, with time allocated and a clear role.
- Communication plan: audience, message, channel, owner and date, including Bangla and English versions where needed.
- Training plan: role-based curricula, practice exercises, assessment and refresher sessions, not a generic product tour.
- Readiness criteria: what must be true before go-live — data migrated, users trained, support desk briefed, reports validated.
- Adoption measures: the transactions, fields or reports that show whether the new process is being used.
- Hypercare plan: the first weeks after launch, with a daily triage meeting and a named owner for each issue.
- Reinforcement plan: how managers will check adoption at 30, 60 and 90 days and what happens when it slips.
For each deliverable, agree what "accepted" looks like. A communication plan is accepted when it names audiences and dates, not when a template is delivered.
Provider categories and what they are good at
Large consultancies bring method, templates and capacity. They also bring rates and rotation; the partner who wins the work may not run it. Ask for the named team and a continuity clause.
Implementation partners know the software and often understand the process gaps. Their change work can be strong when they separate configuration decisions from adoption work, and weak when the same person is measured only on go-live dates.
Boutique change firms can be excellent for training design, communications and coaching. They need a clear interface with the technical team, or they will document a process the system does not support.
Internal team plus a contractor keeps knowledge in the business and can be the most durable option. It requires backfill for the people doing the work and a contractor who teaches rather than performs.
The scorecard
Weight the criteria before reading proposals. A workable set for an SME rollout is:
- Method and evidence (25%): a clear approach, with samples of impact maps, training material and adoption reports from comparable work.
- Integration with delivery (20%): how the change lead works with the implementation team, and who resolves conflicting decisions.
- Sector and language fit (15%): experience with your type of operation, plus Bangla training and communication capability.
- Measurement (15%): specific adoption measures and a reporting cadence, not satisfaction scores alone.
- Capability transfer (15%): how the provider trains internal people to continue the work.
- Price transparency (10%): a clear unit, assumptions and change-control rate.
Score evidence, not claims. A provider that cannot show a redacted impact map or a real training workbook is asking you to buy a promise.
Pricing questions to ask
- Is the fee fixed by phase, priced per training day, or estimated in person-days? What assumption could change it most?
- Are content localisation, printing, venue, devices and backfill included?
- How many refresher sessions and hypercare weeks are included, and what does an extension cost?
- Who pays for travel and accommodation outside Dhaka, and how is it approved?
- What happens if the go-live date moves by a month? Is there a standby rate?
- Are the training materials and templates ours to reuse after the engagement?
Do not accept a percentage of project cost as the only basis for change work. It rewards a larger build rather than a better transition.
Red flags
- A catalogue of standard courses with no role impact assessment.
- No baseline measurement, so success can only be described in anecdotes.
- No line-manager role. Change that depends only on the project team fades after hypercare.
- "We will handle resistance" without a plan for the people who legitimately disagree.
- Communication treated as the whole engagement.
- No named change lead, or a lead shared across several concurrent projects.
- Exit terms that leave you unable to run training without the provider.
Pilot and hypercare
Pilot with one department or process before scaling. Set a baseline two weeks before launch: transaction volume, time per task, error rate and shadow spreadsheets. Run for a full business cycle, including month-end if problems appear there. Review the baseline weekly with the sponsor.
Hypercare needs a daily stand-up, a visible issue log and a rule that process questions are answered by the business owner, not the vendor. At the end, publish adoption numbers and remaining gaps. That report is the real acceptance test.
Exit with capability, not dependency
Require a train-the-trainer programme, editable materials, a recorded walkthrough for new joiners, and a handover of the plan and dashboard. Name the internal owner of each artefact. If the provider runs every session, the knowledge leaves with them.
Change work runs alongside Custom Software & Integrations delivery. The pricing page explains how implementation phases are separated. For the wider adoption context, read the guide to AI adoption in SMEs.
Sources
- Prosci, ADKAR change management model, accessed 17 November 2026.
- Kotter, 8-step change process, accessed 17 November 2026.
- Harvard Business Review, Leading Change: Why Transformation Efforts Fail, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.