Skip to content
Team Nexa
All posts

Success storyIllustrative

How a 1,200-person manufacturer ran on one picture after an acquisition

After buying a competitor, the company had two ERPs, two sets of KPIs and a merged system still a year away. The agents built one shared model across both, so the leadership team didn't have to wait.

2 min read

  • Strategy
  • Finance
  • Operations

Illustrative story: a composite scenario built on sample data to show how the agents work. It is not a customer testimonial.

The challenge

The acquisition made sense on paper: a competitor with complementary products and two plants close to key customers. The hard part started after the deal closed. The combined company ran on two ERPs, with different charts of accounts, different product codes and different definitions of the same KPIs. One side counted order backlog from order entry, the other from confirmed production slots.

Merging the systems was planned for the following year. Until then, every combined number came from a spreadsheet the finance team rebuilt by hand each month, usually three weeks after month-end.

What they set up

  • The Finance agent read both ERPs, read-only, and mapped the two charts of accounts to one structure, which the CFO approved line by line.
  • The Operations agent did the same for inventory and open orders, and showed both backlog definitions side by side until the leadership team agreed on one.
  • The Strategy agent wrote a weekly integration page from the shared model: combined margin, inventory and order backlog, each figure split by legacy company and linked to its source system.
  • Nothing was written back to either ERP. The model sat on top of both, and the integration team kept working on its own schedule.

What changed

combined margin, inventory and backlog, instead of monthly and three weeks late
Weeklycombined margin, inventory and backlog, instead of monthly and three weeks late
agreed definition of order backlog across both companies
1agreed definition of order backlog across both companies
when the leadership team first saw combined margin by product line
Week 3when the leadership team first saw combined margin by product line

The early view changed some decisions. Combined inventory showed both companies holding the same slow-moving components, and the COO approved a plan to draw down one side's stock before reordering. Margin by product line showed the acquired company pricing two shared customers below the parent's terms. That reached the commercial team as a question now, rather than a surprise at year-end.

What's next

The ERP merge is still on its original timeline. When it lands, the shared model will point at one system instead of two, and the leadership team keeps the same weekly page it has been reading since the first month.

Keep reading

All posts
  • Use case

    From brief to action: how the agents handle follow-through

    A good brief tells you what changed. Then someone still has to send the email, update the plan and chase the owner. Here is how the agents take that part off your plate, with your approval at every step.

    • Strategy
    • Finance
    • Revenue
    • Operations

    2 min read

  • Use case

    Linking the product roadmap to revenue and cost

    Roadmap reviews talk about features. Board meetings talk about revenue. The Product & Tech agent connects the two, so you can see what each big bet is worth and what it costs.

    • Product & Tech
    • Revenue
    • Finance

    2 min read