AI ShareCONSULTING

Are You Ready for an ERP Project? 7 Questions Before You Sign the Contract

Before you request an ERP proposal, clarify what you want to change, who will make decisions and how you’ll check the result. These seven questions will help you prepare for your first conversation with an implementation partner.

In this article
  1. What business problem are we solving?
  2. How do our processes work today?
  3. What should we keep, and what should we change?
  4. Who makes decisions, and who does the work?
  5. How clean is our data?
  6. How will we know the system works?
  7. What happens after go-live?

1. What business problem are we solving?

Write down three to five measurable outcomes. For example, “We want to close the month in four days instead of ten” or “We want to see available stock by warehouse without consolidating spreadsheets manually.” Use these outcomes to compare proposals and evaluate the project.

2. How do our processes work today?

Document the main workflows, from order through delivery and invoicing, from purchasing through payment, and across production and month-end close where relevant. Record where teams use Excel, where they re-enter data and where errors or delays occur.

3. What should we keep, and what should we change?

An ERP comes with standard workflows. Customisations can increase implementation and upgrade costs. Decide which processes serve a genuine business need and where your team can adopt the system’s standard way of working.

4. Who makes decisions, and who does the work?

Name an executive sponsor who can make decisions and key users who know how each department operates. Set aside time for them to discuss workflows, validate requirements and test the system. Agree who makes the call when departments have different priorities.

5. How clean is our data?

Look for duplicate item records, customers with multiple codes and unconfirmed balances. Create a migration plan that specifies what to transfer, who cleans the data and how you’ll check that the migrated records are accurate and complete.

6. How will we know the system works?

Define test scenarios and acceptance criteria before implementation. An invoicing test might start with a discounted order that has been partially delivered. The expected result is an invoice that covers the delivered quantity and applies the agreed discount.

7. What happens after go-live?

Plan support for the first two to three months, follow-up training and a way to prioritise issues. Agree what must work on day one and what can go into the next phase.

Conclusion

Your answers give you a common basis for briefing implementation partners, comparing proposals and accepting the system before launch.

Preparing for an ERP project? We can help clarify your processes and requirements before you choose a supplier.

Request an initial discussion

Like this:

Like Loading…