.png)
The three engagements
They run in sequence if you need all three, which is the common case for a new platform. They are sold separately, scoped separately, and designed to end cleanly — because an engagement that only makes sense if you buy the next one is not a service, it is a hook.
BEFORE 1-4 weeks
Roadmap Planning
Current-state review, process and data assessment, module scope, integration inventory, and a costed plan with a platform recommendation. For organizations that have a problem but not yet a decision.
The output is a document you own. You can take it to any partner, including one that isn't us, and a reasonable number of people do exactly that.
DURING 3–12 months
Implementation
Deploying Dynamics 365, or migrating off Dynamics AX, SAP, Oracle, NAV, GP, QuickBooks, or Sage. Design, build, data migration, integration, testing, training, cutover — and intensive support through the first month-end close rather than a handover at go-live.
Ends with a working system and a team who can use it, not with a dependency on us.
AFTER Ongoing
Managed Services
Running the system once it is live: incident support, release management against Microsoft's two annual waves, allocated enhancement capacity, and governance. For organizations where the ERP is business-critical and nobody owns it full time.
Twelve-month minimum term, because the first two months are spent learning your environment and a shorter contract means neither side ever gets past that.
Which one do you need?
Most organizations arrive knowing the symptom rather than the service. These are the situations we see, and where each one usually goes.
Where you are
Start with
We're on Dynamics AX, NAV, GP, or an old CRM with no upgrade path
Depends on urgency. Managed Services to stabilise while you plan, or Roadmap Planning if the decision is close.
The system works but nobody can report on it
Power Platform and Power BI. Often a smaller problem than it looks.
A project has stalled and we need someone to take it over
A short assessment first. Occasionally restarting the design is cheaper than inheriting it, and we will tell you which.
How we work
How we work, across all three
These hold regardless of which engagement you buy. They are also the things most likely to be quietly dropped under schedule pressure, which is why they are written down here rather than left as culture.
1
Senior people, not a pyramid
Our consultants average more than a decade in Dynamics. The people in the scoping conversation are the people on the engagement. This is less common in this market than it should be, and it is the main reason we do not compete on day rate.
2
Scope before proposal
We would rather spend two weeks understanding an environment than produce a fast estimate that gets renegotiated in month four. Roadmap Planning exists as a separate, purchasable engagement for exactly this reason.
3
Your internal time, quantified
Almost every overrun traces back to internal availability rather than partner capacity. We put the hours your team will need into the plan, per phase, so it can be argued about at the start instead of discovered in month five.
4
Standard first, customization second
Every fit-gap item gets asked why the process exists before anyone asks how to build it. The most expensive extensions are the ones preserving a workaround for a limitation the new platform does not have.
5
We say no
If Business Central is right and Finance is not, if a migration should wait eighteen months, if managed services is the wrong purchase for your situation — we will say so. It costs us work occasionally and saves everyone considerably more.
6
Nothing designed to trap you
The roadmap output is yours. The implementation ends with a team who can run the system. Managed services is a twelve-month term, not a lock-in, and we will help you move support in-house if that becomes the right answer.
Who we work with
We are a specialist firm rather than a generalist one, and saying where we do good work is cheaper for everyone than finding out in month four.
A strong fit
Manufacturing, distribution and wholesale, logistics, professional services, and healthcare.
20–5,000 employees, in the United States or Canada.
Already invested in Microsoft 365, Azure, or Power Platform.
An executive sponsor in finance or operations, not only in IT.
Willing to change process where the platform is right and the process is not.
1
2
Not a fit
Organizations wanting the new system to reproduce every existing process exactly.
Projects with no named business owner and no allocated internal time.
Anyone looking for hourly contractor capacity rather than a scoped engagement.
Timelines requiring a full enterprise ERP live in under six months.
.png)
Frequently asked questions
COMMON QUESTIONS
Not sure which one
you need?
That is a normal place to start, and the scoping call exists for it. Forty-five minutes on your current system, what is forcing the timeline, and what a realistic budget looks like. You will leave knowing which of the three fits — including if the answer is none of them yet.
GET IN TOUCH
Let’s turn your Microsoft Dynamics roadmap into real results.
To learn more about our services or to schedule a consultation, please fill in your contact details and we will get back to you as soon as possible.