A point of view on turning Dynamics 365 from a CRM application into the customer intelligence layer connecting brokers, employers, acquisitions, service teams and the next phase of growth.
Explore the thesis
Flores is recruiting a senior internal owner for Dynamics 365 CE, Dataverse and Power Platform: administration, configuration, integrations, releases, support and continuous improvement. That tells us CRM is important enough to require durable platform ownership.
But Flores is also an acquisition-led benefits platform. Each acquired book can introduce employers, brokers, products, relationships, service history and data that must eventually operate as one company. The strategic question is not simply who administers CRM. It is how CRM accelerates integration and growth.
Turn every acquired customer and broker book into a usable relationship graph quickly.
Map acquired brokers, employers, products, ownership, renewals and relationship history into a common Dataverse model without waiting for every operational platform to be fully migrated.
See the relationship, product footprint and whitespace around every broker and employer.
Connect Broker → Brokerage → Employer → Plan → Product → Participant context with opportunities, implementations, service and renewals. Give account teams a commercial view while benefits administration remains in the systems built to administer it.
Tell account teams where the next growth opportunity is instead of asking them to hunt for it.
Use product holdings, broker relationships, renewal timing, service signals and patterns across similar employers to identify whitespace and recommend the next action. Start with explainable, governed AI tied to measurable commercial outcomes.
Flores has expanded through acquisitions including ProBenefits, Leave Solutions, Group Dynamic, London Health and Streamline HR. The opportunity is to make each acquired relationship more valuable by connecting the commercial context earlier, identifying product whitespace and giving teams one view of the customer.
Who influences the relationship?
What do they use today?
What should Flores do next?
Plans, claims, payments, eligibility and administration.
Governed broker, employer, relationship and product context.
Sales, account management, service and commercial workflow.
Whitespace, risk, summaries and governed next-best actions.
Map D365/Dataverse, integrations, broker and employer hierarchies, acquired-company data, account workflows, backlog and the top commercial friction points.
Establish Broker 360 and Employer 360, normalize product relationships and prototype one acquisition-whitespace / next-best-action use case.
Put the model in front of a focused account team, measure expansion signals and adoption, harden governance, and onboard the permanent D365 administrator into the operating model.
Immediate fractional leadership at the $10K/month starting model, with specialists added only if needed.
Estimated annual base-market range for the senior D365 role; actual Flores compensation is not publicly confirmed.
*Market estimate, not a published FloresHR salary. The permanent hire remains part of the recommended model.
Jason Wickman brings 25+ years around CRM, marketing, sales and service technology, including 12 years at Microsoft. Instead of staffing a large team, Jason owns the business outcome and adds D365, Power Platform, data or AI specialists only where required.
Prepared specifically for FloresHR by Jason Wickman and Agilidy.
Compare notes with Jason