Dynamics 365
Most Dynamics projects fail on the same two things: too much scope at once, and data nobody cleaned. We phase the first and are honest about the second.
What we do
One app, one department. Live sooner, and the requirements for phase two get written by people with real experience.
Data cleaned before migration. Migrating a mess produces an expensive mess. We say what needs fixing first.
Configuration over code. Every line of custom code is something to maintain through every future update.
Training that sticks. People who were part of building it need far less training than people handed a finished system.
How we work
Half a day to settle scope before we price.
First app configured, data cleaned and moved.
UAT, go-live, then phase two on real experience.
What a delivery contains
Setting up the apps you will actually use, not the whole suite
A data model and fields built around your terms, not the template's
Migrating data from your current system, with an agreed scope of history
Integrations with ERP and the other systems that have to talk to each other
Reports and dashboards in place from day one
Training for the people who will use it, and for those who will own it
Documentation you own, so somebody else could take it over
What it costs
Two costs get conflated. The licence is a recurring per-user monthly cost to Microsoft: predictable and easy to look up. The implementation is a one-off cost to us to make the system fit the business. It is the second that varies, and it almost always varies because of integrations and data migration, not because of the number of users.
| Project type | Typical range |
|---|---|
| One app, standard setup | NOK 180,000-320,000 |
| With ERP integration and migration | NOK 350,000-600,000 |
| Several apps with history | NOK 600,000-1,200,000 |
| Group, several companies or countries | from NOK 1,200,000 |
If you want the price down, the quickest lever is usually to migrate less history, or move one integration into phase two. We wrote a whole article on what drives these numbers.
How long it takes
| Scope | Time |
|---|---|
| One app, standard setup | 2-3 months |
| With ERP integration and migration | 3-6 months |
| Several apps with history | 6-9 months |
| Group project | 9 months or more |
The most common reason a project slips is not the development. It is that the data in the old system is in worse shape than anyone thought. Set aside internal time for cleaning it early, that work has to be done by someone who knows the data.
When this fits, and when it does not
Fits when
- You have several systems that do not share a customer view
- Sales or service runs on spreadsheets today
- You are already on Microsoft 365 and want to build on it
- The process is 80 % standard and 20 % particular to you
Does not fit when
- The need is one bounded app, Power Platform is cheaper then
- The process is wholly particular and is meant to stay that way
- You have nobody to own the solution after go-live
- The current system works and the frustration is about routines
Questions we get
Do we have to take all of Dynamics 365?
No. Most start with one app for one department. It delivers value sooner, and it produces a better understanding of the requirements for the next phase than any workshop can.
Can we keep the ERP system we have?
Yes. We integrate with what you have. The ERP integration is usually the heaviest item in the project, but it is rarely a reason to replace the ERP.
Who owns the solution afterwards?
You do. Everything runs in your own Microsoft tenant, the configuration and code are yours, and we document as we go so somebody else could take it over.
What if the project turns out bigger than the estimate?
You hear about it when we see it, not when the invoice arrives. We put the choice in front of you: extend the budget, cut scope, or move something to a later phase.
Shall we talk this through?
Tell us briefly what you need and you get a concrete answer, and an estimate you can plan around.