Send us a message about this episode!

Six-month ERP implementations get a bad name because most "six-month" projects are really twelve-month projects with a six-month deadline glued onto the front. The software is rarely the problem. The problem is everything around it — decisions, data, scope creep, and the unwillingness to go standard.

In this episode, Pete, Emily, and Nirav walk through the five conditions that have to be true for a six-month ERP implementation to actually finish in six months.

What we cover:

  • Why a reliable internal team that can make decisions quickly is the difference between six and twelve months
  • How to spot whether your business is actually simple enough for a fast implementation — and what kills it (integrations, special pricing rules, custom reports)
  • The case for going standard with a clear MVP, and why customisation tolerance should be near zero
  • What to look for in a VAR who will challenge you instead of just nodding along
  • How to know if you've picked the right ERP for the timeline you want

If you've been handed a six-month deadline and you're trying to work out whether it's achievable or whether someone's set you up to fail, this one's for you.

Support the show

Rss Apple Podcaster
Podden och tillhörande omslagsbild på den här sidan tillhör Peter Nicholson | Nirav Shah | Emily Browning. Innehållet i podden är skapat av Peter Nicholson | Nirav Shah | Emily Browning och inte av, eller tillsammans med, Poddtoppen.