08/06/2026
Choosing the platform for a CRM project can be tricky, as is walking into the board meeting and making the case for it.
Often, we talk to senior managers who already know their current setup isn't working. Maybe the data's all over the place, the team's working around the system rather than with it, and something needs to change. However, knowing that and being able to argue for a substantial investment from the CFO are two different things.
Here's what we've seen work in our Dynamics 365 projects:
Start with the cost of doing nothing. That's not just the cost of the new system, but the cost of staying where you are, such as missed opportunities and duplicated effort wasted on things that should be automatic. That's often a compelling number.
Be honest about risk. We all know that boards don't trust a business case that has no downsides. So set out the risks, including implementation time, data management and user adoption, and show you've got a plan for each one.
Tie it to something the board already cares about, such as growth targets or operational efficiency. Dynamics 365 needs to connect to a business objective that's already on the agenda, rather than appearing on the scene as a technology project looking for a problem.
And finally, get the scope right before you go in, because vague projects tend to get knocked back. A clear picture of what's in, what's out, what it costs and what it delivers in Year One is what gets go-ahead.
If you're working through a business case right now and want a second pair of eyes on it, we're happy to help. We've been around this loop enough times to know where the gaps usually are.
Get in touch with any of our team members.