How we work
From development to payroll, we build Dynamics 365 around your business, not the other way round. We combine Microsoft's Success by Design method with a firm belief in taking the standard route first, using your own data early, and letting your people gain hands-on experience along the way.
Standard first · Your own data · Hands-on · Testing · Optimization · All the way · Independence · AI · Cost
Standard first, with room to optimize afterwards
We take the standard route first, because you rarely know exactly what you need until you have tried the workflows in daily operation with your own data. Rather than guessing at customizations early in the project, we recommend a proper optimization project two to three months after go-live. There we go through every workflow we have touched. What works, we leave alone. Where it falls short, we develop and adjust deliberately, without trying to force the workflow into some other standard solution. The result is a solution that fits the way you actually work, built on experience rather than guesswork.
The frame around it all is Microsoft's own project methodology, Success by Design. Fixed reviews of the solution design along the way, where the solution is held up against Microsoft's recommendations, so risks are caught while they are still cheap to fix. The standard route is our way of practising it, Microsoft recommends the same order. Understand the business, use the standard, and build only where it is justified.
Your own data and workflows from day one
From the start of the project we work deliberately to get your own data into the solution, for example in an upgrade from AX, where we can move your products, customers and vendors across quickly. That means that after the first month you are working in workshops with your own recognizable data instead of demo data you have never seen.
Our workshops run in two rounds. In the first we cover every area, ask how you work in practice, and let your key users try the system for themselves straight away. Afterwards we go through scope, schedule and budget with you in detail. Does anything need adding, can anything come out? In the second round we go deep, often across areas, so you end up with a solution tested against your real workflows rather than one area at a time.
Hands-on experience rather than classroom training
We do not believe the best route to understanding a system runs through a classroom. So we do not build separate training into our projects. Instead your key users are at the table from the first workshop, working in the system with their own data the whole way through. That gives them solid, practical experience with Dynamics 365 long before go-live, and puts them in a position to train the rest of the organization themselves afterwards.
Testing and quality assurance
Once the setup is settled after the second round of workshops, we handle the configuration itself. Most of it only needs doing once, and your time is better spent going deep on your own workflows. You get the configuration documented, of course, so your own people can check it.
Instead we spend the time with you testing the whole solution. This is where automated testing comes in. We record your own workflows as task recordings and use them to run automated tests in Playwright, our preferred tool for the job. Combined with AI, that gives broader and more consistent coverage than manual testing alone can reach.
Optimization after go-live
Two to three months after go-live we run a proper optimization project. We place it after go-live on purpose, because the most valuable feedback only arrives once you have tried the workflows in daily operation with your own data, not while you are still in the middle of the project. Is a workflow taking too long? Has it become too heavy? Now you know precisely, and we can adjust without rushing.
The optimization project is not loose talk. We gather the feedback from your daily work, measure the workflows that weigh heaviest, and prioritize together with you. You get a concrete list, what can be adjusted in configuration right away, and what requires development, with effort and gain next to each item, so you can choose on an informed basis.
We stay with the project from start to finish
It matters to us that we stay with the project from start to finish. Those of us who are involved early, for example in the first conversations before kick-off, stay with the project all the way to the end. That way the same experienced people who have known your business since day one are also at the helm when you go live.
That stands in contrast to the classic model, where the project team hands over to a support team at go-live and all knowledge has to be retold in a long handover. That handover does not exist with us. The people who built the solution are the same people who answer you afterwards, and your history stays with people who were there when the decisions were made.
We make you as independent of us as we can
The most important thing for us is of course to deliver a solution that works. But it matters almost as much to us that you become as independent of outside help as possible, even when that costs us business in the short term. You should hold every option in your own hands and be free to pick the right partner for each task.
If there is something you think we are not the right people for, you will never hear a word of complaint from us. That is why we deliver everything with documentation, source code and a proper handover, so what we build makes you less dependent on any single vendor, including us.
AI in our work
We use AI throughout our work, not as a buzzword but as a standing part of the toolbox. We have had good results with agent-based development tools, where AI helps us write and review code. That means development tasks can often be done faster than before, and that you get more for your money.
We also use AI to capture what happens in workshops. Decisions and your deviations from standard are documented in a format AI can read. That means your processes are known to the assistant, when your own people later ask AI about a workflow, they get answers that account for your actual setup, not just the standard.
AI also comes up with test scenarios, spots gaps in design and code, and drives our automated tests. That frees us to concentrate on the parts that call for experience and judgment. The ground rules, including where code and data reside, are always agreed with you before we start.
You have a concrete example in front of you. The illustrations on this site were made with AI, following our own design guide. We use the tools where they make sense, and we say so when we do.
What will it cost?
We do not put a price on it up front. An estimate made before we have spoken is a guess, and a guess helps neither of us. So the first step is a conversation about where you stand. If you are already a customer of ours, that is a different matter. There we know both the solution and the business behind it, and we can usually put numbers on it straight away.
What we can tell you is how we calculate. We estimate per phase rather than giving one large number. Clarification, workshops, configuration, testing, go-live, and the optimization work afterwards. And we learn as we go. With every phase behind us we know more about your business, and the numbers for what lies ahead get correspondingly sharper. After the first round of workshops we review scope, schedule and budget with you and adjust before we build.
We invoice for time spent, and we speak up when a request costs more than it gives back. A fit-gap or a second opinion on an existing solution can be bought as a self-contained assignment, without committing to a project.