BlogChoosing an ERP

How to prepare your company for ERP.

Good preparation comes down to three things: a mapped process, clean data and one person who makes decisions. Here are six steps you can start this week.

Why preparation matters so much

Most implementation delays don’t come from the software. They come from questions nobody in the company has a ready answer to. Who approves the discount? Which item code is correct? Which spreadsheet is the latest?

Each such question can stall the work for days. If the answers are ready in advance, implementation moves faster and costs less.

Preparation pays off even before you choose a system. With a mapped process and clean data, you compare vendors on the same terms and see who really understands your work.

1. Map the process and the unwritten rules

Take one real order and follow it from enquiry to payment. Write down who does what, in which program and where it waits. Describe how it actually works, not how it should.

Do the same for a delivery from a supplier and, if you manufacture, for one work order. Three pages are enough.

Mark the places where something waits: an approval, an answer from the warehouse, a signature. Mark the exceptions that happen at least once a month too. These are what take the most time later if nobody mentions them early.

Also write down the rules that live only in people’s heads. Which customer gets deferred payment. When a supplier order is placed. Who can change a price. Some will become system settings, and some will be dropped because nobody remembers why they exist.

The easiest way to find them is to ask “what happens if…”. What if the customer wants half the quantity? What if the delivery is late? What if the machine stops? The answers are your rules.

2. Choose one person to own the project

You need one person in the company who knows the process and has the authority to decide. It doesn’t have to be the owner, but they need the owner’s trust.

  • Answers the vendor’s questions within a day or two.
  • Gathers input from the warehouse, sales and accounts.
  • Makes the call when opinions differ.
  • Has at least a few hours a week set aside for the project.

Agree from the start how decisions outside this person’s authority will be made. For example, a change to pricing policy or to how suppliers are paid. If the owner needs to step in, they should know when and for how long.

If this person is also the busiest in the company, take some tasks off them for the duration of the project. Otherwise the project will wait for them.

3. Decide what goes first

Don’t launch everything at once. Pick the process that hurts most and start there. The rest follows in later stages.

Also write down what will definitely not be in the first stage. This protects the project from growing along the way.

A good first stage is visible to people and measurable. For example, orders and stock for a trading company, or work orders for a workshop. When the first stage works, the next ones go more smoothly because people already trust the system. How to choose what comes first is in the guide to choosing an ERP.

4. Clean the data before you move it

A new system is only as good as the data in it. If you bring over duplicates and wrong codes, you will have them in the ERP too.

  1. Items: standardise codes and names, remove duplicates and discontinued items.
  2. Customers and suppliers: check invoicing details and remove repeats.
  3. Units of measure: decide whether board is tracked in pieces, sheets or kilograms.
  4. Stock levels: plan a stock count close to the go-live date.
  5. Recipes and prices: check that what is recorded matches reality.

Share the clean-up among the people who know the data. Sales check customers; the warehouse checks items and units. The project owner keeps an eye on deadlines.

For example, a company with 1,200 items in a spreadsheet often finds that fewer are actually active. The clean-up takes days but saves weeks of confusion after go-live. More on moving data in from Excel to ERP.

5. Prepare your people

People accept a new system more easily when they know why it is happening and what they gain personally. Say it clearly from the start.

  • Explain which problem the system solves for each team.
  • Say openly what goes away: which spreadsheets, which manual reports.
  • Include one person each from the warehouse, sales and production in testing.
  • Plan training by role, in short sessions.
  • Pick a go-live date outside your busy season.

The people who take part in testing later help their colleagues. They know why the system works a certain way because they were there when it was decided.

Expect the first two weeks to be slower. People are learning new screens and old habits pull them back. If you say so in advance, nobody will conclude that the system doesn’t work.

6. Decide how you will measure success

Pick two or three numbers you want to improve and write them down today. For example, time from order to invoice, number of shipping errors, hours spent on the weekly report.

After the first three months, compare. That way you will know whether the implementation works, not just whether it is finished.

Choose numbers you can measure today, even roughly. If the weekly report takes, for example, four hours today and ten minutes after go-live, the gain is visible to everyone.

How we approach it

We go through these steps with you during the analysis, before the project price. We implement in stages, and you talk directly to the people who write the code. The process is described in how we work.

Frequently asked questions

How long does it take to prepare for an ERP?

It depends on the state of your data and how quickly decisions are made. Mapping the process can take a few days; cleaning the data often takes longer.

Do we have to stop work during implementation?

No. With a staged implementation the company runs as normal, and the new process takes over on an agreed day, usually after a stock count.

Who in the company should be involved in implementation?

One person who owns the project and makes decisions, plus one person from each affected team for testing.

Show us how you work today.

In 30 minutes we’ll find the process that costs you the most and see how it would look in Leanovix.

Book a demo