Every Division Runs Its Own System. You Need One

A company moves to one central system by agreeing a common process and a common set of data first, then building one web application that every division uses, with the differences that truly matter kept as settings. Divisions are brought on one at a time, with their data migrated as they join. The technology is the easier half. The agreement about how things will be done is the half that decides whether it works.

Signs this is your problem

• Company-wide reports are built by hand from each division’s numbers.
• Divisions cannot see each other’s customers, stock or capacity.
• The same job is done differently in every location.
• A customer deals with two of your divisions as if they were strangers.
• You are opening or acquiring another location and dread adding one more system.

How companies end up with a system per division

It happens naturally. Each office solved its own problems with its own spreadsheet or program. A company was acquired and kept what it had. A manager brought a favourite tool from a previous job. Each choice made sense locally. Together they mean:

• No company-wide report without days of manual consolidation.
• The same customer set up differently in each place.
• No way to move work or staff between divisions without retraining.
• Several systems to pay for, maintain and secure.
• No standard way of doing anything.

What has to be decided before anything is built

• Which process wins. Usually the best of each, agreed by people from every division.
• What is truly different. Local taxes, regulations or product lines are real differences. “We have always done it this way” usually is not.
• Common definitions. One customer list, one product list, one meaning for each status.
• Who can see what. A division sees its own work. Head office sees everything.

We run this as part of business analysis, with every division in the room. It is the most valuable part of the project.

What one system gives you

• Company-wide figures at any moment, with the ability to drill into any division.
• One version of each customer, product and price.
• Standard processes that can be taught once and measured fairly.
• Work and people that can move between locations.
• One system to maintain and secure.

How Keene Systems handles it

1. We study how each division works. And where they differ for good reasons.
2. We agree the common process and data with all of them. Before design begins.
3. We build one application with roles and settings for each division. In stages.
4. We bring divisions on one at a time. Migrating their data as each joins.

The next step is a short, no-pressure conversation. Book a call with Lance Keene or use the form on this page.