+1 480 485 7373
Microsoft Teams
The five Dynamics 365 engagement models at a glance
Scoped project
We deliver an agreed outcome, such as a Business Central go-live, against a written scope signed before work starts.
- ✓Clear deliverables and sign-offs
- ✓Partner carries delivery responsibility
- ✓Changes go through written change control
Phased rollout
We split the project into waves, for example finance first, then inventory and warehouse, then a second company.
- ✓Each wave is scoped on its own
- ✓Lessons from wave one shape wave two
- ✓Users absorb change in smaller pieces
Advisory and second opinion
A senior consultant examines a plan, a partner's proposal, a stalled project or a design decision, and gives a written view.
- ✓Independent of who delivers
- ✓Useful before signing a large contract
- ✓No configuration work included
Staff augmentation
Our consultants work alongside your internal team under your project management, filling specific skill gaps.
- ✓You keep control of priorities
- ✓Knowledge stays in your team
- ✓Delivery risk stays with you
Ongoing support
A standing arrangement for user questions, fixes, Microsoft update checks and small enhancements.
- ✓Someone who already knows your setup
- ✓Planned help around release waves
- ✓Separate from any project agreement
Strengths and weak spots of each Dynamics 365 engagement model
Combining Dynamics 365 engagement models over the life of a system
Few clients stay in one model forever. A common pattern starts with advisory work to test a plan. A scoped project or phased rollout delivers it, and ongoing support follows once the system settles. Later, a new acquisition or a warehouse expansion may call for another scoped piece of work.
Staff augmentation fits a different kind of company. It suits one with its own Dynamics administrator or developer who needs a second pair of skilled hands for a heavy period, such as a migration or a major integration. In that model we follow your standards and your backlog, and we write things down so your team can carry on without us.
Whichever of our Dynamics 365 engagement models you pick, we write the terms before work begins. We settle commercial details in the scoping talk, since they depend on the work, not on its label.
What stays constant in every Dynamics 365 engagement model
Senior people
The consultant you speak to is the one doing the work, for a full project or a single advisory session.
Written terms
We agree scope, responsibilities and the change process on paper first.
Documentation
We record configuration and design decisions so your system never depends on one person's memory.
Your data, your system
You own the tenant, the data and the extension code we write for you under the agreement.
Which Dynamics 365 engagement model should you choose?
Which model do most first-time ERP buyers choose?
Usually a scoped project, sometimes phased. First-time buyers rarely have an internal ERP lead. So it makes sense to hand delivery to a partner against a written scope. Consider a phased approach if the work spans several departments or companies and the business needs breathing room between changes.
Is staff augmentation cheaper than a scoped project?
Not necessarily, and cost should not be the main reason to choose it. With augmentation, you direct the work and carry the delivery risk. That only pays off if you have someone experienced to lead. Without that lead, a scoped project usually gets to a working system with less rework.
Can we start with advisory and then hire you to deliver?
Yes, although you are under no obligation to. Some clients use our written view to brief a different partner or to push back on an existing proposal. If you do ask us to deliver afterwards, the advisory work feeds straight into discovery.
Do we need an ongoing support agreement after go-live?
No, it is optional. Many companies find it useful because Business Central changes twice a year and staff turnover means new users need help. Others have a capable internal administrator and only call for occasional project work.
Can we switch models partway through?
Yes, with a written change to the agreement. For example, a client might move from augmentation to a scoped project if their internal lead leaves. Another might split a large project into phases once the first wave shows how much change the business can absorb. Moving between Dynamics 365 engagement models works best when we talk through the effect on responsibilities first.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.