Resource
Field Notes from963+ Projects
We have not published formal studies or survey reports. What we can share honestly are observations from delivering 963+ projects over 10+ years: why ERP rollouts stall, how scope creeps and where data migration hurts.
A note on what this page is
Many software companies publish reports full of survey percentages. We do not have a survey, a panel or a research team, so we will not give you numbers we cannot back. This page holds patterns we keep seeing across projects in more than 20 industries. Treat them as the opinions of practitioners, not as measured results.
Why ERP rollouts stall
Stalled rollouts rarely fail on technology. They stall on people and process, and the same few causes repeat.
- No single owner on the client side. When accounts, stores and sales each give separate instructions, every decision waits for a meeting.
- The old process is copied instead of questioned. Paper registers with duplicate entries get rebuilt as duplicate screens.
- Training happens once, at the end. Staff who first see the system on go-live day go back to spreadsheets within a week.
- Go-live is set to a calendar date, not to readiness. Rushed cutovers leave half the branches on the old tool.
How scope creep starts
Scope grows quietly. A client sees the first demo, remembers a report they forgot to mention, and asks for it as a small addition. Each request is reasonable alone. Twenty of them move the delivery date by months.
What helps is a written module list agreed before development, a short demo every two weeks, and a rule that new requests are priced and scheduled separately rather than slipped in. Projects with that discipline feel slower at the start and finish earlier.
Where data migration hurts
Migration is usually underestimated. The software is new, but the data is old and carries every shortcut taken in the past: customers entered twice with different spellings, items without units, ledgers with unexplained opening balances.
Our advice is to start cleaning before development ends, to migrate a small branch or one financial year first as a rehearsal, and to keep the old system readable for a while after cutover. Opening balances should be agreed with your accountant in writing before anyone clicks import.
Other patterns we see
Mobile apps built without a backend plan need rework once admin screens become necessary. Websites launched without a content owner go stale. Automation added on top of messy data amplifies the mess. In each case the cheaper path was a short planning step at the start.
If you want these lessons applied to your project, a call costs nothing. Our guides section and case studies give more concrete examples.
Frequently asked
The questions the team asks
- Do you publish research reports?
- No. We have not published formal studies or survey reports, and we would rather say so than invent statistics. This page shares plain observations from our delivery work.
- Can I see real project examples?
- Yes. Our case studies and work pages describe delivered projects. Ask on a call if you want one close to your industry.
Have a project in mind?Let’s scope it together.
Tell us the outcome you need. You get an approach, a rough timeline and next steps within one business day.