“We bought Dynamics 365 and nobody uses it.”
The licences renew every year. The rollout stopped somewhere after go-live. Your team keeps the pipeline that actually matters somewhere else.
What this usually looks like.
- 01
Reps run their real pipeline in a spreadsheet and update the CRM on Friday afternoon, if at all.
- 02
Forms are full of fields nobody fills in, and missing the one thing your team argues about every week.
- 03
Leadership reporting gets rebuilt by hand each month because nobody trusts what the system says.
- 04
The rollout covered sales and then stopped. Phase two was never scheduled, and the partner has moved on.
Why it happens.
Most Dynamics 365 rollouts are scoped against the product rather than the business. A partner configures what the platform ships with, runs a single training session, and leaves. Nothing in that sequence asks how your team actually wins work — so the system ends up modelling a generic sales process that nobody in your building recognises.
Low adoption is almost never a training problem. People use a system that makes their day shorter and route around one that makes it longer. When the data model doesn't match how deals really move, every record becomes an act of translation, and translation is the first thing dropped in a busy week. Once the data goes stale, the reporting goes with it, and the last reason to use the system disappears.
How we approach it.
Watch the work, not the org chart
We sit with the people who are supposed to use the system and follow real records end to end. The gap between the documented process and the actual one is where every adoption problem lives.
Fix the model before the interface
Tables, relationships, ownership and security get corrected first. Redesigning forms on top of a data model that doesn't match reality just moves the friction somewhere less visible.
Ship in slices your team can feel
One process at a time, each one making somebody's day measurably shorter. Adoption follows benefit; it does not follow a launch email.
What we'd actually build
Named here for the first time, because it follows from the diagnosis — not the other way round.
- Dataverse data model, security roles and ownership rework
- D365 Sales and Customer Service configuration around the real process
- Model-driven app forms, views and business rules
- Plugins and custom workflow where configuration runs out
- Data migration, deduplication and a trustworthy reporting layer in Power BI
- Integrations — telephony, marketing, e-signature — and Power Pages portals
- Website form + shared inbox
Both channels feed one pipeline, instead of two queues nobody reconciles.
- AI scoring and filter
Each lead is scored and screened, so spam and noise never reach a human.
Junk is discarded here — it never becomes somebody's work. - Routed to a KAM
The lead reaches the key account manager the inquiry actually belongs to.
- Accept or reject
The KAM makes the one judgement call the machine should not make.
Rejected leads route to Sales Ops to discard or reassign. - Owner set in D365
Accepted leads are written to D365 with that person as the lead owner.
From inbox to owner, without a human in the loop.
A manufacturer's leads arrived through two disconnected channels with no consistent routing. Ownership in D365 is now set the moment a lead is accepted, giving sales an auditable record of who owns what and why.
Read the write-upFind out whether that's really the problem.
A System Review is a fixed-fee, time-boxed diagnosis. You get written findings and a prioritised roadmap with effort estimates, and the fee is credited against any build that follows.