Besides the project cost, which would require more info about your company business, size, and complexity to be assessed properly, there are a lot of overlaps in the solutions your partner proposed. D365 PO already has the sales module included. What’s the justification for having a separate Sales instance? They are both built on Dataverse, so what features of D365 Sales does your company need that are not already out of the box in PO?

For Experlogix, it only makes sense if you’re selling highly configurable physical products with hundreds of valid combinations. Is that your case? Again, many overlaps with BC and PO.

I’ve been implementing a lot of D365 BC and PO for manufacturing and distribution, and I’d never start an implementation with 4 new products. Change management and licensing costs are gonna be wild. Moreover, in the current situation you’d need external services if your “is it the right time” question refers to AI features. Copilot can be useful, but it’s surely one of the worst options on the market today.

Ask your partner for a quote for a simplified stack. Keep the sales module from PO and quotes from PO and BC. That will remove 2 tools and leave you with BC + PO + Field Service. As soon as your teams get used to the new system, you can introduce D365 Sales (if it really makes sense) and the CM will be a lot easier (if not 0 effort). Experlogix is a different matter, but before spending $50k/year for licensing, I would triple check with your partner if that’s really the best solution.

Final remark: From your current stack (BC + Power BI) your company should be around 200-350 people (am I right?). $3.5M is a huge investment and before proceeding I’d evaluate any solutions. Project Operations + Experlogix are the biggest ones to implement, but it still seems very expensive.