Ask anyone who's lived through a bad ERP rollout and they'll describe the same movie: a confident kickoff, months of configuration, a delayed go-live, and a finance team quietly keeping the old spreadsheets alive "just in case." The plot twist is always the same — the project was lost before it started, at scoping.
Here's how we scope ERP work so that movie doesn't get made.
Start with the flows, not the features
An ERP vendor demo is organized by module: inventory, purchasing, accounting. A business doesn't run in modules — it runs in flows. An order comes in, stock gets reserved, a delivery goes out, an invoice follows, money arrives. Somewhere in that chain is the pain that made someone google "ERP" in the first place.
So scoping starts by walking the actual flows:
- Where does information enter the business? Phone, WhatsApp, sales reps, a website?
- Who touches it next, and in what tool? Every re-typing step is a future error.
- Where does everyone stop trusting the numbers? That's usually the real project.
Decide what go-live means — per department
"Go live" is a dangerous phrase when it means everything, everywhere, on one date. We scope ERP rollouts as a sequence of small go-lives: inventory first (it anchors everything), then purchasing, then sales, then accounting. Each department gets a parallel-run period where the old system stays alive until the new numbers match for two consecutive weeks.
This isn't slower. It's the same work, minus the disaster recovery.
Price the data migration like a deliverable
Half of every ERP budget surprise hides in three words: "migrate existing data." Spreadsheets disagree with each other, product codes have three formats, and nobody remembers what half the customer records mean.
We scope migration explicitly: which records, from which sources, cleaned by whom, validated by which report, signed off by which person. If a quote you receive treats migration as a bullet point, add zeroes to it.
What you should demand from any vendor
Whether you work with us or anyone else, insist on:
- A written scope that lists what's out as clearly as what's in
- A phased rollout plan with parallel runs — never a big-bang cutover
- Data migration priced and specified as its own deliverable
- Training counted in the budget, per department
- Named support terms for after go-live
An ERP should end spreadsheet chaos, not memorialize it in a more expensive format. Scoping is where that outcome is decided.