If you’re putting together an internal business case for Dynamics 365 Customer Engagement, you probably know the procedure: quantify the problem, set out the costs, show a return. What sometimes catches people out is what’s specific to Dynamics 365 CE. There are things that look straightforward on paper but have a habit of surfacing later, usually at the point where a number on your business case suddenly doesn’t match a number on the quote.

Here’s what’s worth knowing as you start the process.

Licensing is more complicated than the headline price suggests

Microsoft’s licensing model for Dynamics 365 CE is tiered, and the difference between licence types is significant enough to change your numbers considerably.

Full user licences cover people who’ll be working in the system day-to-day, such as your sales team managing the pipeline, and customer service staff handling cases. Team Member licences are cheaper and cover people who need read access or occasional light use, but they come with real limitations on what those users can actually do. Getting the balance wrong in either direction inflates your costs unnecessarily or leaves you short of access at go-live.

The question to answer early on is: who actually needs to do what in this system? Not “who will have a login” but what tasks are they performing, and how often? That distinction drives the licence count, and the licence count is one of the bigger cost levers in the whole project.

Scope is where costs can climb

Dynamics 365 Customer Engagement is a suite of applications: Sales, Customer Service, Field Service and Customer Insights. They share an underlying platform, but they’re distinct products with distinct implementation requirements.

The risk in a business case is treating CE as a single item when it isn’t. If Sales is the priority – and for most organisations it is – then the scope, cost and timescale for Sales alone is what your business case should reflect. Every additional module adds complexity, cost and implementation time.

This isn’t an argument against ambition. It’s an argument for being precise about what’s in scope for phase one. A business case that bundles Sales, Customer Service and Customer Insights into a single implementation is likely to be underestimating both the cost and the time to value. You can read more about this in our article on prioritising the different CE modules.

Data migration might be more work than you think, so budget for it properly

If your organisation has customer data in a legacy CRM or spread across multiple systems, migrating that data into Dynamics 365 CE is a substantial piece of work in its own right. It’s also one of the areas that can be undercosted in an initial business case.

The issue isn’t just data volume – it’s also quality. Before data can go into a new system, it needs to be assessed, cleansed and mapped to the new data model. Duplicate records need resolving. Incomplete records and changing fields need to have decisions made about them. This takes time and it needs resource, either internal resource or consultancy time. A business case that treats data migration as a footnote tends to hit problems later.

Customisation looks appealing but gets expensive

Dynamics 365 CE is configurable out of the box to a degree that surprises people who haven’t used it before. The core Sales and Customer Service functionality often covers the majority of what an organisation needs, without a line of custom code.

The pressure to customise usually comes from one of two places: either existing processes that people want to replicate exactly in the new system; or requests that come in during the project as more stakeholders get involved. Both are understandable, but both need managing.

Heavy customisation adds cost, implementation time and – crucially – ongoing maintenance overhead. Every custom element is something that needs reviewing and potentially reworking when Microsoft releases updates. A business case that assumes a heavily customised implementation is also assuming a higher total cost of ownership over time, not just a higher upfront number.

The better framing for a business case is: what does the standard Dynamics 365 functionality give us, and what is the business case for departing from it? That shifts the conversation from “we need to build this” to “is the cost of building this justified by the benefit?”.

The Outlook and Teams integration changes how people work – and that has a cost

One of the genuine strengths of Dynamics 365 CE is how it integrates with Microsoft 365. Sales and customer service teams can update records and manage a pipeline without leaving Outlook. That’s a real adoption driver.

But it’s worth building the change management implication into your business case, not treating it as a benefit that arrives for free. People need to understand what’s changed about how they work, not just that they have access to a new system. Organisations that plan for this (with training, communication plans and time for teams to find their feet) tend to get better adoption than those that assume the integration will sell itself.

A question the board might ask

At some point in the approval process, someone who’s seen an IT project fail might ask why this project won’t end up like the last one. It’s a fair question, and a business case that doesn’t address it directly might stall.

The honest answer usually comes down to whether enough work was done upfront to understand the problem properly before any implementation started. A discovery phase, mapping the processes, understanding the data, talking to stakeholders, isn’t a nice-to-have. It’s what makes the numbers in the business case reliable rather than optimistic. It’s also what gives you something credible to say when the board asks how the scope and costs were arrived at.

Here at TrueNorth IT, our Discovery service is designed to give organisations the clarity they need before any implementation budget is committed. We look at what the data looks like, what the processes are, who needs what access, and what a realistic scope and cost picture looks like for your situation specifically.

If you’re building a business case and want to sense-check what you’re working with, we’re happy to have that conversation. No pitch, we promise!