The Catch Up Podcast

What if an ERP programme could be delivered in weeks rather than months?

In this episode of The Catch Up Podcast, host Philip Blackmore speaks with Matt Cull, founder and chief executive of Vannda, about a career that began with two university dropouts and a factory lab bench, and now spans global Microsoft Dynamics 365 transformation programmes. Matt explains why client-side ownership, executive sponsorship and proper backfill decide whether a project succeeds, and why the partner relationship works best as a tennis match rather than a handover.

The conversation then turns to AI. Matt argues the traditional Dynamics consultant role is almost gone, describes standing up working proof of concepts in hours, and makes the case that smaller businesses can now buy enterprise ERP and CRM at a fraction of the usual cost. He also takes the security question head on, at a point when 51% of UK firms fear staff are feeding company secrets into unauthorised AI tools, according to research reported in September 2026.

• (00:00) - Welcome to The Catch Up Podcast

Matt Cull: Matt Cull is the founder and chief executive officer of Vannda, the London-headquartered consultancy he co-founded in 2020 with Shaun Balding to design, deliver and rescue complex Microsoft Dynamics 365 programmes. His route into enterprise technology was anything but linear, moving from two abandoned university courses and factory work into bookkeeping, then into Baan ERP in the Netherlands in 1996 and a long run as an independent Dynamics contractor. Before Vannda he held Dynamics 365 Finance and Operations solution architect and consulting roles with organisations including Scania, Pinewood Studios, IBM and LexisNexis, covering multi-country rollouts. Vannda now runs teams across the UK, the United States, Mexico and Singapore, works with multinational and Fortune 100 clients, and is building a specialism in transforming large media and marketing agencies while productising fast, AI-assisted Business Central and Customer Engagement implementations for smaller organisations.

Episode Insights:

• The client-side team is eternally underestimated, and the cost of backfilling the people who make decisions is the line item most sponsors forget to budget for.
• A good partner relationship behaves like a tennis match, where each side returns the ball and someone is empowered to call it in or out.
• AI is already compressing implementation timelines, taking simple deployments from months to days and changing what an implementation partner is actually selling.
• The bigger threat to ERP careers is the disappearance of the entry-level process work where consultants used to learn systems thinking end to end.
• Building specific AI skills before asking questions gives better answers and burns fewer tokens than open-ended prompting.

Action Points:

1. Fund the client side properly: Price the client-side team, not just the partner quote. Work out which roles need backfilling and what that costs before the business case is signed. A programme with no decision-makers available is a programme that will drift.
2. Set your governance ground rules early: Agree who can say yes, no or not good enough, and how quickly. Treat it as a tennis match where both sides must return the ball. Escalation paths should be tested before the first difficult decision arrives, not during it.
3. Ask AI first, then act: Before you approach the market, brief an AI tool on your size, legacy landscape and constraints, and interrogate the problem. Build your own client-side assistant to support requirements, partner selection and planning. Do everything you would normally do, but faster and better informed.
4. Write skills, not just prompts: Matt's Mexican property law example shows the value of building a focused skill before asking the question. A narrow, well-contexted skill reduces token spend and cuts the risk of a wrong answer. Treat skill-building as a core team capability.
5. Close your shadow AI gap: Set clear rules on which tools staff may use and what data can go into them, and consider a gated or self-hosted model for sensitive work. This matters commercially, not just legally, given that 51% of UK firms fear employees are feeding sensitive data into unauthorised AI tools. Pair the policy with training so people stop working around it.

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. 

What has to be true before AI is any use inside an ERP system?

In this episode of The Catch Up Podcast, host Philip Blackmore speaks with Phil Mackison, D365 F&O Technical Capability Director at HCLTech, about a technical career that started by accident on the Isle of Man and ended up in enterprise Dynamics architecture.

Phil explains how he moved from mechanical engineering into report writing, why he backed Damgaard Axapta over SAP against his father's advice, and how the technical architect role changed when Dynamics moved from on-premise to the cloud. He is direct about what AI can and cannot do: applying best practice and checking documents, yes; automating processes on top of poor data, no. Gartner expects AI-enabled tools to account for 62% of cloud ERP spending by 2027, up from 14% in 2024, with data quality still one of the main blockers.

There is practical advice too: know why you are replacing the system, get your data catalogue in order first, and take your most respected internal person out of their day job to own it.

• (00:00) - Welcome to The Catch Up Podcast

Phil Mackison: Phil Mackison is D365 F&O Technical Capability Director at HCLTech, where he owns the technical methodologies used on enterprise Microsoft Dynamics 365 Finance and Operations implementations and handles recruitment and resourcing across the D365 Finance practice. He has more than 20 years in ERP, starting as a junior engineer on the Isle of Man before moving into report writing, then functional consulting in trade and logistics, then technical architecture. His delivery record spans Damgaard Axapta 2.1 through to Dynamics 365, including enterprise programmes at Capgemini and Hitachi Solutions, and his own specialism has been security and infrastructure. Phil is based in Worcestershire.

Episode Insights:

• Phil never did the engineering job he was hired for. Three weeks of typing in bills of materials turned into a report-writing role, and he never went back.
• The best consultants come from industry first, because they have stood on a factory floor doing stock takes and know how the business actually runs.
• Clients pay a lot of money for consultants on site, so the least those consultants can do is drop the acronyms and take the client with them.
• A workshop that collapses is not always about you. Phil was cleared out of a room over an invoice dispute, and now speaks to senior stakeholders before he presents anything.
• The move to cloud removed skills from the architect role, such as SQL clustering and disaster recovery, and replaced them with questions about data security and performance.

Action Points:

1. Start with why you are moving: Write down the actual reason for replacing the system, whether that is a burning platform, expansion or better use of data. Test every requirement against it. Reacting to pressure without a stated reason is how programmes drift into replacing what you already had.
2. Get your data catalogue in order first: Map what data you hold, what condition it is in, and what you want to keep. Decide early what happens to historic records and who owns the clean-up. Gartner expects only about 30% of organisations to have data good enough for advanced AI by 2027, so this is the work that decides whether AI helps you later.
3. Protect reporting in phase one: Reporting is routinely promised in pre-sales and then cut from delivery. Name the reports the business cannot run without, price them, and hold them in scope. If they slip to phase two, agree in writing what people will use in the meantime.
4. Appoint an independent advisor: Bring in someone who understands the implementation cycle and sits between you and the partner. Their job is to tell you when the recommended answer suits the partner more than the business. Every programme Phil has seen go really well had one.
5. Backfill your best internal person: Take the most respected person in the operation out of their day job, cover their role, and make them the subject matter expert. Keep them owning the system after go-live. People trust a colleague they have worked alongside for years more than an external consultant.

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. 

What does it actually take to move into AI with confidence?

In this episode of The Catch Up Podcast, host Phillip Blackmore speaks with Claire Purdue, Senior Solutions Engineer at Microsoft, about her non-linear route into technology and how the pre-sales role has changed in the era of Dynamics 365 and Copilot. Claire explains why customers no longer ask what a system can do, but how they can work differently, safely and responsibly, and why the answer starts with data foundations rather than a bolt-on.

With AI adoption among UK small and medium sized businesses rising from 35 per cent in 2025 to 54 per cent in 2026, according to the British Chambers of Commerce, the pressure to act is real, and so is the risk of acting without governance.

From reading body language on a Teams call to setting guardrails, auditability and ownership around AI, this conversation makes the case that as technology absorbs the repetitive work, the human side of the job matters more, not less.

• (00:00) - Welcome to The Catch Up Podcast

Claire Purdue: Claire Purdue is a Senior Solutions Engineer at Microsoft in the UK, working with customers across Microsoft Dynamics 365 and the wider Copilot and AI portfolio. Her route into technology was deliberately non-linear: a degree in maths, statistics and computing, a first job in software support, a move into consultancy, self-taught PRINCE2 study that took her into project management, and then a step into account management as the first account manager her software vendor ever hired. She moved into pre-sales, spent two years working on a construction CRM system in Canada, and joined Microsoft as a technical specialist on her return to the UK. She holds the MB-310 Microsoft Dynamics 365 Finance certification along with Microsoft Business Value Management Practitioner and Mentor recognitions, and has featured in Microsoft's My #MicrosoftLife series talking about life inside the Business Applications team. Her focus today is helping organisations move to AI with clear guardrails, strong data foundations and confident, human led change.

Episode Insights:

• Careers in the Microsoft ecosystem are rarely linear, and experience in support, consultancy and project management is exactly what makes a strong pre-sales professional.
• Saying you do not know, then following up, builds more trust than an answer invented on the spot, and credibility is the whole product in a pre-sales conversation.
• Relatability is the one trait every effective pre-sales professional shares, because customers remember the person who presented long after they forget the feature list.
• The buying question has shifted from show me what your system can do to how can we work differently, safely and responsibly, which makes AI readiness a strategy conversation rather than a demo.
• AI still needs ownership, usage boundaries and auditability, and it cannot compensate for poor data, so governance and data foundations come before capability.

Action Points:

1. Audit your data before you buy anything: Ask your team to review duplicates, structure and reporting quality in your current system of record. Treat a migration or AI project as the moment to clean house rather than a reason to lift and shift. Poor inputs will produce poor outputs no matter how capable the technology is.
2. Name the tasks you want to remove: Ask each team to identify the repetitive, manual work they dislike most. Use those tasks as the first AI use cases so value is visible quickly and scepticism has somewhere concrete to land. This turns an abstract AI strategy into a short list of measurable wins.
3. Set your guardrails early: Define usage boundaries, approval steps and auditability before you widen AI access across the business. Seventy-eight per cent of executives lack strong confidence they could pass an independent AI governance audit within 90 days, according to Grant Thornton's 2026 AI Impact Survey. Write the rules down while the estate is still small.
4. Treat output validation as a skill: Build the habit of checking AI output rather than accepting it. Microsoft's 2026 Work Trend Index found that 86 per cent of AI users treat output as a starting point rather than a final answer. Make that expectation explicit in your team's ways of working.
5. Bring your whole team with you: Do not confine a transformation programme to the C-suite or the project team. Put change management in place early, involve the people who will use the system daily and give them a say in decisions. Nobody likes being told what to do, and engagement is what turns a go-live into adoption.

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. 

What really happens behind the scenes of a multi-million-pound ERP programme, and why do so many still fail?

In this episode of the Catch Up Podcast, host Phillip Blackmore sits down with Elizabeth Foy, Head of Customer Transformation at 5Y Technology, to explore her journey from KPMG auditor to leader of large-scale D365 and SAP implementations. Elizabeth shares candid insights on the chaos that lurks beneath polished programme reports, the critical importance of change management, and why surrounding yourself with people who will challenge you is non-negotiable.

With research from Gartner indicating that more than 70% of ERP initiatives fail to fully meet their original business goals, Elizabeth's first-hand experience offers a practical counterweight to the optimistic demos and happy-path scenarios that so often mislead boards. From the dangers of watermelon reporting to knowing your pain points before you even invite an SI into the room, this conversation is essential listening for anyone embarking on, or already knee-deep in, a complex transformation programme.

• (00:00) - Welcome to the Catch Up Podcast

Elizabeth Foy: Elizabeth Foy is Head of Customer Transformation at 5Y Technology, where she leads the delivery of complex finance transformation and D365 implementation programmes. A Fellow of the Institute of Chartered Accountants in England and Wales (FCA) and ICAEW Business and Finance Professional, she holds a First Class Honours degree in Business Studies. Elizabeth's career began at KPMG, where she built a foundation in process mapping and audit before moving into industry roles spanning retail, logistics, software and manufacturing. She has led end-to-end ERP implementations across SAP and Microsoft Dynamics 365, combining deep finance expertise with hands-on experience in FP&A, business intelligence, and organisational change. She is a regular contributor on LinkedIn, writing about the intersection of finance, data trust and AI adoption.
 

Episode Insights:

• Change management is the single biggest determinant of programme success or failure, yet organisations routinely leave it until the final stages before UAT, by which time rumour and resistance have already taken hold.
• Process mapping, often seen as mundane early-career work, is one of the most valuable skills a transformation professional can develop, because it builds the cross-functional understanding needed to bridge IT and business.
• Watermelon reporting, where status dashboards show green at board level while the programme is red underneath, is a recurring pattern that stems from a culture where teams are afraid to deliver bad news.
• Organisations that skip the upfront work of defining current pain points, target outcomes and clear guardrails almost inevitably see scope creep, budget overruns and misaligned expectations.
• Building a diverse programme team of blending auditors, super users, early-career professionals and senior practitioners creates the breadth of perspective needed to catch blind spots and sustain momentum.

Action Points:

1. Know where you are before you decide where you're going: Before engaging an SI or starting product demos, map your current pain points, data landscape and process bottlenecks at a high level. You do not need exhaustive process documentation, but you do need an honest picture of what is tripping the business up today so you can test every design decision against it.
2. Define your guardrails and communicate them early: Establish a clear project charter that states what the programme is and is not. Surface those guardrails regularly so that when someone requests a costly customisation, you can assess it against agreed boundaries rather than making ad hoc decisions that inflate scope and budget.
3. Bring change management in from day one: Do not wait until training is due to start communicating. Craft a clear message about why the programme exists and what it will enable, then identify credible champions at each site who can carry that message into teams. If you leave a communication void, rumour and fear will fill it for you.
4. Seek out the challengers, not just the cheerleaders: Recruit team members and super users who will push back and ask difficult questions. Yes-people feel comfortable but hide risk. The person who says "yes, but what about this?" is often the one who saves the programme from a costly surprise at go live.
5. Build traceability from strategy to go live: Create a golden thread that links your stated objectives to requirements, configuration, testing and training. This traceability gives you the evidence to demonstrate progress, defend decisions and catch drift before it compounds into a programme-level problem.

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. 

What does it really take to build a Microsoft Dynamics consultancy that grows year on year, treats people like the product and stays sane through the AI bubble?

In this episode of The Catch Up Podcast, host Phillip Blackmore is joined by James Brentley, founder of AgileCadence, for a candid conversation that traces his journey from teenage Flash developer at Sheffield Hallam, through early Axapta days at eBecs, projects at Tribal Group, Stemcor and the landmark Dentsu Aegis programme, to launching his own firm in 2012.

They explore why James walked away from London to build a remote-first consultancy long before that was normal, how a near-burnout reshaped his definition of success, and why values like transparent, authentic and generous now sit at the core of every commercial decision. Against a backdrop where BCG forecasts 50 to 55 per cent of US jobs will be reshaped by AI over the next two to three years, James offers a refreshingly human take on AI: not as a faster typewriter, but as a way to release cognitive load and deepen client relationships.

• (00:00) - Welcome to The Catch Up Podcast

James Brentley: James Brentley is the founder and owner of AgileCadence, a Microsoft Solutions Partner for Business Applications headquartered in Perth, Scotland, specialising in Microsoft Dynamics 365, licensing, Azure and managed services. After early roles at eBecs, Tribal Group, Stemcor and Dentsu Aegis, he founded the firm in 2012 (originally trading as T3 Synergy) and has grown it into a team serving around 40 SMB and mid-market customers across the UK, with reported year-on-year growth in the region of 25 per cent and around 80 per cent of revenue coming from repeat business. AgileCadence opened a permanent Aberdeen office in 2025 and was recognised at the UK's Best Workplaces Awards 2026.

Episode Insights:

• Walking away from a stable career to build something of your own does not require a perfect plan. eBecs gave James a working blueprint that showed grit, determination and a clear culture could build a serious tech business in a regional UK town.
• Burnout is part of the journey for many tech professionals, but the answer is rarely to leave the industry for good. James left for the outdoor sector, learnt the grass really is greener but the money is not, and returned to build a more sustainable career.
• A clear, lived set of values, transparent, authentic, generous, fun, empathetic and exceptional, has become AgileCadence's commercial filter for choosing customers and projects, not just an internal poster on the wall.
• AI risks becoming an AI-to-AI loop of emails and documents that strips out genuine value. The opportunity is to use it to release cognitive load and deepen human relationships, not replace them.
• Microsoft's own narrative is shifting from Copilot as a faster typewriter toward Copilot Cowork and agentic capabilities, which makes how leaders frame AI to their teams more important than which licences they buy.

Action Points:

1. Pick a system you can secure, then commit: James's advice for any leader thinking about D365 Finance and Operations or another ERP is to choose a platform you can genuinely secure and stand behind, rather than chasing the greenest grass. Treat security as central, not bolt-on, and resist hopping between platforms in search of a perfect fit that does not exist. The competitive edge is in how well you implement and run it, not which logo you pick.
2. Use AI to release cognitive load, not to slash headcount: Map the routine, low-value work that drains your best people every day and apply AI there first. Reinvest the time saved into customer relationships, deeper discovery and quality of delivery, so your team becomes ten times better at what they already do. As Microsoft moves from Copilot to Copilot Cowork, build that mindset into how you measure productivity.
3. Make your values a commercial filter: Write down the three to six values you actually live by, then apply them to your sales pipeline and hiring as rigorously as you apply them to operations. If a deal would push you to break those values, walk away. Over time, the customers who share them deliver the repeat business that compounds growth and protects culture.
4. Always be on the right side of the bar: Use the framing James borrows from his Sheffield student days as a sense check on career and business choices. Ask whether each decision puts you closer to building durable value, optionality and choice for yourself, or further from it, and let that guide investment in skills, partners and equity over the next 12 months.
5. Invest in remote and human-centric ways of working: If you lead a consultancy or an in-house Dynamics team, design delivery models that do not depend on people being on site five days a week. Combine intentional in-person time for relationships and culture with high-trust remote working, so your team can build long careers without sacrificing family life or wellbeing.

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. 

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

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. 

How do you build a career in programme management when your path is anything but linear, and what separates a successful transformation from an expensive recovery job?

In this episode of The Catch Up Podcast, host Phillip Blackmore speaks with Musonda Veronica about moving from studying law into leading complex Microsoft Dynamics 365 programmes. They explore why communication is the core of delivery leadership, how to adapt your style to different stakeholders, and why integrity is what builds the trust programmes depend on.

Musonda also breaks down a practical distinction many organisations miss: Dynamics 365 CE delivery often demands an iterative, agile approach because of heavier customisation, while finance and operations programmes tend to suit more structured delivery patterns.

The conversation lands on the unglamorous foundations that keep budgets intact: clear decision ownership, dedicated SMEs, and change management that treats resistance as human rather than a problem to crush. This aligns with common ERP failure patterns such as under-committing internal resources, highlighted in Guidehouse analysis.

Click Here to Watch the Video Episode.

• (00:00) - Welcome to The Catch Up Podcast

Musonda Veronica Malama: Musonda Veronica Malama is a UK-based transformation programme manager and programme recovery leader specialising in Microsoft Dynamics 365 delivery. She is also a career coach and professional speaker, covering topics including leading successful teams, delivering high-stakes programmes, and inclusion in the workplace. Alongside hands-on delivery work, she mentors professionals moving into project and programme roles and speaks at industry events.

Episode Insights:

• Programme management is mostly communication: translate between technical teams and business stakeholders without needing to be the technical expert.
• Dynamics 365 CE programmes often require more iterative delivery because customisation tends to be higher than in finance and operations work.
• Readiness is not a slogan: programmes slip when decision ownership, resourcing, and governance are unclear at the start.
• The pace of decision-making predicts delivery outcomes: stalled decisions create delays that burn budget.
• Trust is an execution tool: integrity and early communication reduce churn, resistance, and rework.

Action Points:

1. Define decision ownership: Name a single accountable sponsor for the programme, backed by a small decision forum. Set a cadence where priority decisions get made quickly. Escalate unresolved items to that forum immediately, not after timelines slip.
2. Backfill your SMEs: Ringfence the people who know the real processes and give them time to contribute. Remove BAU load or provide cover so workshops and testing do not become optional. Treat SME availability as a critical path item, not a nice-to-have.
3. Choose a delivery model that matches the product area: Use a more iterative approach where customisation is high, particularly in CE work. Keep stakeholders close to demos and feedback loops so you reduce rework. Avoid forcing one template delivery model across all workstreams.
4. Build trust through visible integrity: Commit to a small set of deliverables and hit them consistently. Communicate bad news early, with reasons and next steps. Make reliability part of the programme culture.
5. Treat resistance as data: Assume uncertainty will surface as pushback. Involve impacted people early and show tangible benefits before go-live. Run simple, frequent communications that reduce speculation and corridor narratives.

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. 

How do you build the experience and skills needed to become a trusted solution architect in the world of enterprise ERP?

In this episode of The Catch Up Podcast, host Phil Blackmore speaks with Samit Roy, an experienced D365 Finance and Operations solution architect, about his two-decade journey from electrical engineering through Dynamics Great Plains, AX 2009, AX 2012, and into the modern D365 ecosystem. They explore the hard-won lessons from working across partner and end-customer environments, the importance of getting out of your comfort zone as a freelance consultant, and why solution architects must bring far more than product knowledge to the table.

With Microsoft Dynamics 365 recently named a Leader in three Gartner Magic Quadrant reports and research showing that effective project risk management can boost on-time completion rates by up to 90%, Samit explains why early engagement of a solution architect is critical, how to avoid common ERP pitfalls like poor data migration and unchecked customisation, and what separates good architects from great ones: curiosity, empathy, and the ability to ask the right questions at the right time.

From navigating the transition between product versions to putting yourself in the customer's shoes, this conversation offers a practical roadmap for aspiring solution architects and a reminder for organisations embarking on ERP transformation that investing in architectural expertise from day one pays dividends throughout the project lifecycle.

• (00:00) - Welcome to The Catch Up Podcast

Samit Roy: Samit Roy is an experienced D365 Finance and Operations solution architect with over 20 years' expertise in Microsoft Dynamics ERP implementations. His career began with Dynamics Great Plains in India before relocating to the UK in 2005 to work with Dynamics AX, progressing through AX 4, AX 2009, AX 2012, and into the modern D365 ecosystem. Samit has worked across both partner and end-customer environments, delivering complex, large-scale ERP programmes for multinational organisations in sectors including manufacturing, distribution, and professional services. His architectural approach combines deep functional and technical knowledge with a focus on business outcomes, change management, and long-term system sustainability. Samit transitioned to freelance consulting in 2011, working on implementations ranging from six-month projects to multi-year, multi-geography transformations, and is known for his pragmatic, empathetic style and ability to translate complex technical concepts into decision-ready language for boards and senior stakeholders.

Episode Insights:

• Becoming a solution architect requires at least a decade of hands-on experience across multiple projects, environments, and product versions—there are no shortcuts to building the breadth of knowledge and pattern recognition needed for the role.
• The best solution architects are not necessarily experts in every feature of the product but have deep core knowledge, broad business exposure, and the intellectual curiosity to ask incisive questions and understand what the client truly needs.
• Early engagement of a solution architect—ideally from the discovery phase—dramatically improves project outcomes by surfacing risks, guiding phased vs big-bang decisions, and ensuring design choices support long-term resilience, not just go-live.
• Common ERP pitfalls such as poor data migration, unchecked customisation, and performance issues can often be avoided with experienced architectural oversight that challenges assumptions and applies lessons learned from previous projects.
• Transitioning from a partner environment to freelance consulting forces consultants out of their comfort zone, accelerating skill development and building the self-reliance and troubleshooting instincts that define strong solution architects.

Action Points:

1. Engage a solution architect from day one: Involve an experienced solution architect during the discovery and design phases, not as an afterthought when problems arise. Early architectural input shapes critical decisions around scope, phasing, data migration, and customisation, setting the foundation for long-term project success and helping avoid costly course corrections later.
2. Build broad experience before specialising: If you aspire to become a solution architect, prioritise gaining hands-on exposure across multiple projects, industries, and both partner and end-customer environments. Work in areas outside your core expertise—data migration, integrations, reporting—and take every opportunity to understand how different parts of the ERP ecosystem interconnect.
3. Challenge customisation requests with business-case scrutiny: Question every proposed customisation by asking whether it solves a genuine, enduring business need or simply replicates the old system. Ensure stakeholders understand the long-term cost, upgrade risk, and maintenance burden of custom code, and push for out-of-the-box functionality wherever possible.
4. Avoid common data migration mistakes: Do not start master data numbering sequences with leading zeros, as they will be dropped when data is extracted to Excel, causing chaos downstream. Plan data migration as a strategic workstream with proper validation, cleansing, and testing, and use purpose-built tools rather than direct table imports.
5. Adopt a phased approach for complex implementations: For organisations with geographical spread, multiple business units, or high complexity, resist the temptation to go live everywhere at once. A phased rollout allows teams to learn, adapt, and apply lessons from early deployments, creating a more controlled and manageable transition with better outcomes.

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 ...

Why do so many ERP and Dynamics 365 programmes go wrong, even when the technology is sound? 

In this episode of The Catch Up Podcast, host Phillip Blackmore sits down with experienced D365 Programme Director Mark Edwards to unpack what really makes or breaks complex transformation. Mark traces his journey from manufacturing engineering and production management into ERP, consulting and programme leadership, showing how hands‑on operations experience shaped his approach to delivery and change.

Drawing on decades of work across manufacturing, supply chain, chemicals, retail, rental, charities and more, Mark explains why vague contracts, missold projects and over‑reliance on partners leave clients exposed. He argues that too many organisations only bring in a programme manager after supplier selection, when much of the risk is already locked in. His perspective lands against a backdrop where industry research suggests that a majority of ERP programmes still fail to meet their original objectives, largely due to organisational rather than technical issues.

From defining a clear vision and target operating model to insisting on “out of the box” first and investing seriously in change management, this conversation offers a practical playbook for leaders planning their next transformation.

Click Here to Watch the Video Episode.

• (00:00) - Welcome to The Catch Up Podcast

Mark Edwards: Mark Edwards is a seasoned D365 Programme Director with a career that spans manufacturing engineering, production management, ERP consulting and large‑scale programme leadership. Starting in manufacturing engineering with GEC, he moved through roles in production management and supply chain before leading his first ERP workstream on a mid‑market system. He went on to join ERP vendor QAD as a manufacturing consultant, later moving into pre‑sales, marketing and running a consulting practice back to profitability through value‑based selling. Since then, Mark has delivered and overseen ERP and Dynamics programmes from multiple perspectives: as a vendor, as a management consultant, and as a client‑side programme leader. His experience covers manufacturing, supply chain, retail, rental, third‑sector charities and chemicals, with a consistent focus on clear vision, honest communication, realistic contracts and rigorous change management.

Episode Insights:

• Successful ERP and D365 programmes start with a clear, business‑led vision and target operating model, not with software features or vendor demos.
• Vague contracts and scopes of work create downstream conflict; precise deliverables and roles protect both client and partner.
• Clients must own the programme: partners bring solution expertise, but only the client can supply true process ownership and decision‑making.
• “Out of the box” should be the default; unnecessary customisation quickly multiplies risk, cost and long‑term complexity.
• Change management is a shared leadership responsibility, not a single person’s job, and must start well before go‑live.

Action Points:

1. Define a business‑led vision before talking to vendors: Bring your senior team together to answer why you are changing systems and what success looks like in business terms, not technology terms. Capture the key objectives, from risk reduction to productivity and customer service, and use them as the non‑negotiable brief for any vendor conversations.
2. Tighten contracts and scopes of work: Review existing or draft contracts to check how clearly outcomes, responsibilities and deliverables are defined. Challenge vague language around scope, roles and assumptions, and insist on documentation that spells out who does what, by when, and to what standard.
3. Build a client‑side programme spine: Identify and appoint internal process owners and workstream leads across planning, procurement, operations, finance and other core areas. Make them accountable for defining processes, signing off designs and owning change, rather than leaving all decisions to the implementation partner.
4. Apply the “out of the box” test to customisation: For every requested change to standard D365 or ERP behaviour, ask whether the same business outcome could be achieved using the default process. Treat customisation as an exception that requires a clear business case, not as the default response to “we’ve always done it this way”.
5. Make change management a line‑management duty: Position change management as a core responsibility for functional heads, not just the change manager or project team. Equip leaders with simple tools such as stakeholder maps, communications plans and early exposure to the new system so they can reassure their teams and sponsor adoption from the start.

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. 

What does it actually take to land a complex ERP or Dynamics 365 transformation without becoming another horror story? 

In this episode of The Catch Up, host Phillip Blackmore sits down with seasoned programme leader Chris Lalley to unpack the realities of delivering large‑scale finance and D365 projects in the real world. They explore how careers evolve from operational finance into programme leadership, why variety and curiosity matter, and how personal quirks like “dishwasher‑level” OCD can be a genuine asset in delivery.

Throughout the conversation, Chris returns to a consistent theme: technology‑enabled transformation is fundamentally about people, not platforms. That message is timely. Recent research shows that while ERP capabilities have advanced, 55–75% of projects still fail to hit their original objectives, with average cost overruns near 189%, largely due to organisational, not technical, issues. Chris explains how he approaches new engagements, from establishing vision and sponsorship to assessing team capability and rescuing “programmes in jeopardy”. For leaders about to embark on a D365 or ERP journey, this episode offers grounded, experience‑led guidance on what success really demands.

Click Here to Watch the Video Episode.

• (00:00) - Welcome to The Catch Up Podcast

Chris Lalley: Chris Lalley is an experienced ERP and finance transformation programme leader with a background that spans Big Five accounting, industry finance roles and large‑scale technology‑enabled change. Starting his career in operational finance at firms such as Arthur Andersen and Ernst & Young, he led major internal projects including a global PeopleSoft implementation and the establishment of an offshore shared service centre in Bangalore. That exposure to complex programmes sparked his move into full‑time project and programme leadership, where he has since delivered and recovered high‑stakes ERP and Dynamics 365 initiatives across multiple sectors. Drawing on years of hands‑on delivery, Chris is known for his focus on people, structure and sponsorship as the real levers of success in transformation.

Episode Insights:

• Successful Dynamics 365 and ERP programmes are driven more by people, clarity of vision and sponsorship than by the underlying technology stack.
• The first weeks on a programme should be spent meeting stakeholders, understanding their motivations and aligning ERP outcomes to business strategy, not rushing into Gantt charts.
• Change management is usually under‑invested, yet it affects not only employees but also customers when portals and digital channels are redesigned.
• Capability at the right time is non‑negotiable: under‑resourcing business analysts, architects or change leads early on slows delivery and magnifies risk later.
• Programme directors must be willing to say when “conditions for success don’t exist” and walk away, protecting both their own reputation and the client’s investment.

Action Points:

1. Define success in business terms before you start: Agree a clear vision, outcomes and measures of success with the C‑suite before mobilising your D365 or ERP programme. This includes how the transformation supports overall strategy, what benefits you expect and how you will track them over time. Without this foundation, scope, design and prioritisation quickly drift.
2. Invest properly in change management, not just technology: Treat change, communications and training as a core workstream with its own budget, leadership and methodology. Map who is impacted inside and outside the organisation, from finance teams to customers on portals, and design their journey through the change. Under‑investing here is one of the fastest routes to user resistance and poor adoption.
3. Build the right team and lock in key people: Identify the critical roles across business, partner and contractor resources, then secure the best people you can for a realistic duration. Use contracts and governance to minimise churn in key posts like solution architect, programme manager and lead BAs. Consistent faces and continuity of knowledge are vital for multi‑year ERP journeys.
4. Be honest about risk and willing to make compromises: Accept that large ERP programmes are hard, will involve setbacks and will require compromises on scope or design. Use structured risk management to surface issues early, and re‑baseline plans where necessary rather than pretending original timelines and budgets are still realistic. Adjusting course is a sign of control, not failure.
5. Protect your reputation by recognising “no‑win” conditions: If executive sponsorship is weak, decision rights are unclear, or one dominant leader overrides expert input on everything, recognise that the conditions for success may not exist. Have the courage to surface this clearly and, if necessary, withdraw. In a niche market, being associated only with realistic, well‑governed programmes is long‑term career insurance.

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.