From Chartered Accountant to Enterprise Architect: Rohit Bansal on Building a Dynamics Career

What does it take to deliver Dynamics 365 Finance and Operations at true enterprise scale, without losing users, control, or the upgrade path?

In this episode of The Catch Up Podcast, host Phillip Blackmore speaks with Rohit Bansal about a non-linear career journey from ACCA-qualified finance professional to enterprise architect working on some of the largest global programmes in the Dynamics ecosystem.

Rohit shares hard-won lessons from an early AX 2009 implementation that went badly, and why negative project experiences can become a practical playbook for what not to do next time. They explore the reality of moving from end user to partner, the cultural differences between client and consultancy priorities, and why the strongest programmes keep key responsibilities in-house, particularly process definition, testing, and training.

They also dig into how the product has evolved from AX into D365, why heavy customisation now creates recurring pain through frequent updates, and how the ISV ecosystem helps organisations stay closer to out-of-the-box. Finally, Rohit explains how his current programme measures success after go-live, using adoption dashboards and bug trends to spot where rollout teams need to adjust.

• (00:00) - Welcome to The Catch Up Podcast
• (02:16) - From Finance Controller to AX 2009 Project Lead
• (04:33) - The Bad Partner Lesson and Moving Into Consulting
• (07:07) - Why Methodology Matters and How Partners Differ
• (08:29) - End User Versus Partner: The Culture Shock
• (10:53) - Why Consulting Accelerates Learning Across Clients
• (12:25) - Users Make Projects Succeed or Fail
• (14:23) - Why Contracting Made Sense for Enterprise Programmes
• (17:12) - How D365 Became an Enterprise Rollout Platform
• (21:35) - What Clients Misunderstand About Handing Over Delivery
• (24:07) - ISVs, Customisation and the Forced Update Reality
• (34:20) - Measuring Success: Adoption Metrics and Bug Trajectories
• (36:25) - AI Agents, Upskilling and the Future SA Role
• (38:44) - What Makes a Great Solution Architect
• (41:19) - Pre-Project Strategies: Process, Data, Testing and Training

Rohit Bansal: Rohit Bansal is an enterprise architect in the Microsoft Dynamics ecosystem with a background in finance and accountancy. In this episode, Rohit describes moving from an ACCA-qualified finance career into Microsoft Dynamics after serving as an internal project lead on an AX 2009 implementation, then progressing through partner work and contracting into large, multi-country D365 Finance and Operations programmes.

Episode Insights:

• Users determine whether an ERP programme succeeds. Project plans matter, but adoption on the floor makes or breaks the outcome.
• Large programmes work best with a blended model. Clients should retain process definition, training, and testing to avoid conflicts of interest.
• The shift from AX to D365 changed the fit. D365 F&O suits large enterprise rollouts but often prices out smaller organisations.
• Heavy customisation is harder to justify now. Frequent service updates increase regression testing and code merge effort.
• A global template with controlled localisation supports a sustainable support model and upgrade path.

Action Points:

1. Retain ownership of process definition: Define your global processes before the programme starts, ideally before partner selection. Use these processes to drive solution design, not the other way round. Expect local teams to describe different ways of working, and use the global model to converge.
2. Separate assurance from delivery: Keep testing and training in-house where possible, even when implementation work sits with a partner. Avoid asking a partner to test their own build without independent scrutiny. Use a blended approach that leverages partner skill while retaining unbiased validation.
3. Control customisation to protect the upgrade path: Assume you will take frequent platform updates and plan for continuous regression testing. Prefer proven ISVs over bespoke build when an established solution exists. Reserve custom code for true competitive advantage, not convenience.
4. Design an adoption dashboard before go-live: Decide what adoption looks like per function, such as AP, AR, supply chain, and production. Track month-on-month operational volume and compare sites to spot where training or process clarity is failing. Share progress visually with users to reinforce value and momentum.
5. Treat rollout architecture as global-first: Build a global template with limited, controlled localisation. Challenge any request that makes the core model work for only a subset of the enterprise. Protect live sites by assessing how local changes affect current and future deployments.

The Catch Up Podcast brings you candid conversations with industry leaders, consultants, and change-makers from the Microsoft Dynamics and tech ecosystem. Hosted by Phillip Blackmore, Sales Director at Catch Resource Management, each episode dives into the real stories behind business transformation, career pivots, and scaling success. Expect thoughtful interviews, practical insights, and honest reflections.

Brought to you by Catch Resource Management, a leading UK recruitment specialist for Microsoft Dynamics and ERP talent, this podcast is your inside track to the people shaping the future of enterprise technology. Tune in for new episodes and stay ahead of the curve.

The Catch Up Podcast is produced by Story Ninety-Four in Oxford, UK.