The problem with disconnected systems
Sales works in CRM, finance works in the ERP, and in between people re-type products, prices and orders. That is slow, and it is where errors are born. A pricing decision based on stale procurement data, a work order that never reaches finance, an asset that exists twice. The cure is not a bigger spreadsheet. It is integration designed around your actual process.
How I build it
I design and deliver the connection between Dynamics 365 CE and the systems around it, choosing the tool that fits the job rather than the tool that happens to be fashionable.
- Dual Write for CE to F&O: products, pricing, customers, financial impact of field service work
- Azure Logic Apps and Azure Data Factory for flows to external and legacy systems
- Scribe where it is already in place and doing its job
- Work-order, product and pricing integrations as recurring specialities
Recent work
For an enterprise energy company I designed the flow that brings procurement data into CE, layers commercial conditions and margin logic on top, and carries an approval process to a complete sales price, integrated with their ERP landscape. For a housing corporation I designed the integration between their CRM and the ERP and property-management systems behind it. Different sectors, same discipline: agree on the source of truth, keep the flow simple, and make errors visible early.
Integration questions
Which integration tools do you work with?
Dual Write between CE and F&O, Azure Logic Apps, Azure Data Factory and Scribe. The choice follows your landscape and your team's ability to maintain it, not the other way round.
Our integration exists but keeps breaking. Can you help?
Yes. Reviewing and stabilising an existing integration is common work: mapping what actually flows, where it fails, and redesigning the weak links.
Do you also build the integration or only design it?
Both, depending on the engagement. I always design; delivery happens in your Azure DevOps cadence, alone or alongside your team.