Send us a text

Summary
In this episode, Matt Flanagan breaks down one of the biggest patterns BlueHub sees across projects: rushing into new systems without proper preparation.

Drawing on real examples from recent client work, he explains why most projects don’t fail because of the software — they fail because the groundwork isn’t done.

Matt covers the decisions that should be made before speaking to vendors or consultants, the realistic timelines for change, and what good preparation actually looks like.

Key themes this episode:
• The rush to change – why pressure and pain drive bad decisions
• Building requirements – what your current system does well and where it falls short
• Setting realistic timeframes – why 30 days isn’t enough
• Involving the right people early – ownership, capacity and alignment
• Vendors vs consultants – understanding who does what
• The importance of clean data and cross-vendor coordination

Listen if you’re:
• Planning to change systems in 2025
• Feeling pressure to move fast but unsure where to start
• Involved in scoping or leading an implementation project

Next up:
Episode 3 – Post-Go-Live Drift: Keeping Momentum Once the System’s Live.

Connect & resources:
🔗 Follow Matt Flanagan on LinkedIn
🔗 Visit bluehub.co.uk
for insights and future sessions
🔗 Register for the BlueHub Cin7 Core 2025 Features Review webinar

Your host is Matt Flanagan.
Got a question for him reach out at [email protected]