Hiring for a Dynamics 365 project? You’re probably stressed, behind schedule, and one spreadsheet away from existential crisis.
And while your D365 partner is talking about solution design, gap fits, and dual-write integration… you still don’t have a proper internal team in place.
Relax. Breathe. And whatever you do: don’t commit any of these 7 deadly sins.
❌ 1. Hiring IT Generalists to Do ERP Work
ERP isn’t “just another system.”
You need D365 specialists- not folks who built a SharePoint site once and now think they can handle Finance & Operations.
🧠 D365 is complex. Each module is its own world. And you should bring experts in for the most critical business functions for your company: finance, supply chain, production, warehousing, retail.
This is not the place for guesswork.
👉 What to do instead:
- Hire Functional Consultants with module-specific experience
- Vet resumes for actual project delivery, not just system exposure
❌ 2. Hiring After the Project Starts
Your implementation partner is ready. The kickoff is booked.
And you’re still posting job ads?
🚨 By the time you realize you need help, the good contractors are already gone. You’ll either overpay- or worse, hire the wrong person in a panic.
👉 What to do instead:
- Start hiring 3–6 months before kickoff
- Lock in talent early, especially for Finance, SCM, and Testing
PS- if you are hiring to save a project gone bad: it’s not too late. And you are not alone.
Rescue Experts have helped turn shipwrecks into super yachts. You just need to know where they are! Hint: we have many in the Community.
❌ 3. Prioritizing Culture Fit Over Capability
This isn’t a corporate happy hour. It’s a multi-million-dollar transformation project.
You don’t need someone “who fits the vibe”- you need someone who knows how to fix your problems, period.
👉 What to do instead:
- Hire for capability and delivery record, not just personality
- Let your contractors mentor your FTEs, not the other way around
PS- we do agree that if you can hire contractors that have both capability and culture fit, then you should. There is a universal “no d**ks” policy in the Community…
❌ 4. Paying Below Market Rates
Want senior-level expertise at junior-level rates?
Good luck. The best D365 contractors know their worth– and they’re not cutting their rate in half to help you. If they do: seriously question their experience / motive for doing so.
👉 What to do instead:
- Budget $150–$200/hr for high-quality consultants
- Think long-term: one good hire beats three mediocre ones
PS: you can get a senior contractor at better rates than junior consultants from your Microsoft Parner… let that sink in…
❌ 5. Over-Relying on Your Microsoft Partner
Your partner is there to deliver the system: not to run your business for you. They run a “for profit” business model based on services and billable hours. More problems = more hours…
They won’t own adoption, internal processes, or long-term success. That’s on you.
👉 What to do instead:
- Build an internal team that understands your business
- Use contractors to bridge gaps in capability, not accountability
❌ 6. Confusing Job Titles with Skillsets
“ERP Project Manager” means nothing if they’ve never led a D365 rollout.
“Functional Consultant” means what, exactly?
👉 What to do instead:
- Ask for project-specific examples in D365
- Use a recruiter (hey 👋) who knows the difference between a Finance lead, a solution architect, and someone who just clicked around in a sandbox
❌ 7. Thinking One Hire Will Solve Everything
ERP hiring is like assembling a Formula 1 pit crew.
Put the Wheel Gun Operator (tire changer!) in the shoes of the Chief Mechanic and watch all hell break loose. Or worse: ask one person to do both!
It’s the same when you hire for a “techno-functional” resource.
👉 What to do instead:
- Build a balanced team of:
✅ Project Manager
✅ Solution Architect
✅ Functional Leads (Finance, SCM, Production, Warehousing etc.)
✅ Technical Developer or Integration Expert
✅ Tester / Change Manager
PS: there are a VERY small handful of consultants globally that are experts in one or more fields technically AND functionally.
The Community homes some of these, but even they will tell you it makes most business sense to have someone else to support them.
🧠 Final Thoughts: The Right Team = Project Success
Dynamics 365 doesn’t fail because of software.
It fails because of people. OR bad hiring decisions.
Both are in your control.
If you want to avoid the 7 deadly sins, here’s the summary:
✅ Plan early
✅ Budget realistically
✅ Work with someone who knows the D365 ecosystem inside out
🔗 Need help hiring smart for your next D365 project?
We’ve got the network, the insights, and the A-players.
👉 Let’s talk.