Somewhere between kickoff and go live, things got complicated. Let’s take a look together.
In the middle of a Dynamics 365, Power Platform, or Copilot implementation that’s going wrong? Missed milestones, a growing issue list, or a team losing confidence are reasons to stop and take a look. You don’t have to wait for go live to ask for help.
Does a troubled implementation need a restart?
The dates keep moving. The build doesn’t match how your team works. Every meeting seems to add another question. We’ll listen to the people involved, look at what’s been built, and help you separate what can stay from what needs attention. The next step should follow what we find, not an assumption that everything needs to start over.
Is this you?
These are good reasons to pause and ask for a fresh look:
- Training that covered features, not how your team actually works.
- A backlog of known issues nobody owns.
- One or two power users carrying the load everyone else avoids.
- Customizations nobody documented, and nobody’s sure are still needed.
- Reporting that quietly moved back into spreadsheets.
If these sound familiar, bring them to the first conversation. We can discuss what needs investigation before recommending a recovery plan.
How it works: assess, fix, stabilize
Assess. A focused diagnostic across process, adoption, data, reporting, customizations, and integrations, plus interviews with the people who actually use the system every day. This maps the current state and ranks the highest-priority fixes.
Fix. The highest-friction workflow, adoption, data, reporting, or customization issues get addressed first, not everything at once.
Stabilize. The team gets retrained on the redesigned workflows, what changed gets documented, a maintained backlog gets handed off, and ownership of the next steps is agreed. Scope, pricing, and timing depend on the findings and are confirmed for your project.
Diagnostic checklist
Mark every item that’s honestly a “no”:
- [ ] Reports are trusted as-is, with no manual double-checking or rebuilding in Excel.
- [ ] Approvals and workflows run in the system, not over email or on paper.
- [ ] More than one or two people could explain how the system is actually configured.
- [ ] Every customization is documented, with a known owner and a known reason it exists.
- [ ] User permissions have been reviewed for the current build and intended rollout.
- [ ] The team was trained on how your business actually works, not just on generic feature tours.
More than a couple of unchecked boxes is a real signal, not a coincidence.
Get the full assessment
The Rescue implementation playbook has the full 12-point rescue assessment, the user adoption triage, and the 90-day reset plan template, available through a short request form. Download it to run the first pass yourself before a conversation, or skip straight to talking it through.
An illustrative rescue scenario
This is an illustrative scenario, not a verified customer engagement or a promised result.
A professional services firm recovers a stalled implementation
Imagine a services firm whose implementation has stalled because time and expense entry does not match its billing rules. A review could test whether the financial setup is usable, identify the billing gaps, and define a pilot with the people who enter time and raise invoices. The findings would determine what stays, what changes, and whether the planned rollout is realistic.
Let’s talk about what’s stuck.
Bring the project scope, current issue list, key deadlines, and what your team has already tried. We can start with what you know and identify what needs a closer look. You do not need a polished explanation of a difficult project. Book a conversation →