NorthMark
D365 stabilization and reimplementation × Q3 operations
Reach the CFO-level owner before the roadmap and partner roster are fixed.
A sharper reason to call
Not intent. Not a list of Dynamics users. Each account combines a live operating change with a specific ERP risk DAX can solve.
Open the brief
Click any company. See what changed, why it matters now, and what an SDR can say.
CECO closed Thermon on June 1, 2026. In an SEC-filed town hall, CEO Todd Gleason said both companies use Microsoft Dynamics 365. He called an uneventful first 6 to 12 months the first measure of integration success. He also said CECO would not force an ERP change.
CECO's August 10 filing says it is still integrating Thermon's operations, systems, controls, and people. It also says IT-control gaps from an earlier acquisition remain open. That gives DAX a reason to review the D365 handoffs before the integration goes deeper.
“They both run D365. The CEO says the next 6 to 12 months must be uneventful. Their latest filing says systems and controls are still being integrated, and an earlier acquisition still has open IT-control gaps. I would offer a narrow D365 coexistence review before those handoffs become fixed.”
A fixed-scope review of cross-company data, integrations, roles, reporting, and exception handling. Work beside the integration team.
Do not pitch a tenant consolidation or a SOX audit. The $40M+ cost target is company-wide and due by Year 3. It is not a D365 deadline. Confirm the technical D365 owner.
Meriton's current Project Ignite role says it is bringing more than 20 operating companies onto D365 F&O and Project Operations. The common template is still in build, the target is 80% standardization, and the team plans several entity deployments each year.
The role names PwC, UAT, data migration, cutover, and hypercare. A weak decision in integration, data, testing, or cutover can become the default for every operating company that follows.
“They are still building the D365 template that will be reused across 20-plus companies. If a data, integration, or cutover decision is wrong now, they can copy it several times a year. I would offer to test one rollout before it becomes the standard.”
Review readiness, integrations, data, and cutover for one operating company. Work beside PwC, not against it.
PwC is the named implementation partner. Do not pitch a replacement. Find the next rollout and the work that sits outside PwC's scope. AMG is a new company, but public sources do not say it is the next rollout.
On May 8, 2026, Martignetti announced an initial agreement to acquire RNDC's control-state operations across 17 states. RNDC filed Chapter 11 on July 26. Martignetti's current D365 F&O role names acquisitions, testing, cutovers, deployments, day-one needs, go-live readiness, vendors, and implementation partners.
The public evidence does not prove that the role owns the RNDC deal. It does show live acquisition-related ERP work during a fast-moving transaction. The useful call happens before the integration scope and outside-partner list are settled.
“They announced a 17-state agreement. The seller then filed Chapter 11. Now Martignetti has a live D365 role that calls out acquisitions, cutovers, day-one needs, and go-live readiness. I would reach them before the integration plan and partner list are fixed.”
A bounded acquisition-readiness review across entities, warehouses, pricing, inventory, state controls, data, and cutover risks.
Court materials still described the 17-state transaction as non-binding on August 4. No source proves a Q4 D365 cutover, an August 24 or 25 ERP deadline, or a December 31 transition deadline. Verify the binding status and D365 scope.
Each brief separates the public fact, the timing logic, the SDR line, and the point that still needs verification.
The full preview
D365 stabilization and reimplementation × Q3 operations
Reach the CFO-level owner before the roadmap and partner roster are fixed.
High-confidence match: D365 UAT × $53M plant expansion
Test cutover and stabilization before new equipment adds production load.
Three new plants × active D365 F&O development
Standardize costing, intercompany flow, planning, and plant rollout.
$24M defense program × president-owned D365 role
Scale regulated output without losing schedule or traceability control.
Second plant × upcoming D365 F&O implementation
Design the plant model before bad data and workarounds become permanent.
Retail expansion × D365 UAT and Phase 1 go-live
Keep rapid channel growth from becoming a fragile ERP launch.
US capacity growth × unsupported Dynamics AX estate
Move from AX dependency to a controlled D365 roadmap.
250,000 sq. ft. factory × Dynamics AX on the shop floor
Define the new-site ERP model before old plant logic follows it.
Sixth US factory × D365 work across buy-side and sell-side
Turn new capacity into one repeatable global operating model.
Global quality-system unification × D365 technical ownership
Stabilize the validated boundary between ERP, quality, and manufacturing.
Production-line expansion × D365 at plant-floor level
Connect plant growth to reliable manufacturing execution in F&O.
Product growth × active AX and D365 coexistence
Retire AX risk without destabilizing a growing medical-device operation.
The test