The group grew. The access model did not.
What does industry-depth work actually mean?
Industry-depth multi-company work means companies, chart structures, access, and reporting that match how the group actually operates — not a duplicated database per entity.
Services groups and multi-company manufacturers often arrive with one Odoo and five unofficial books. The hard part is estate shape: which company owns which master, who sees which invoice, and how migration preserves that without a second year of cleanup.
We implement and migrate multi-company estates and multi-branch service networks. Apex Group is the named multi-company exemplar. Endurance shows multi-branch network growth on one platform. Delivery routes to Odoo Implementation and Odoo Migration. Strategy ambiguity routes to ERP Modernization.
Does any of this sound familiar?
Each company keeps a spreadsheet because shared masters cannot be trusted.
Access rights were copied until nobody can explain who sees what.
A migration quote ignores inter-company flows.
Branches behave like separate businesses inside one legal entity.
Reporting for leadership is a manual consolidation.
A previous partner proposed “one company first” with no written estate plan.
If you recognised three of these, you do not need another company form. You need an estate model that survives the next acquisition.
What this looked like when it had to hold.
Apex Group · multi-company estate shape
Multi-company implementation and migration where the modernization was the estate itself — companies, access, and a platform that could hold growth — not a feature catalogue.
Read the Apex case study →Endurance · multi-branch network on one platform
DSA operations across a 20+ branch multi-state network on one Odoo estate — proof that multi-location services growth is an access and product problem, not a second database.
Read the Endurance case study →What an industry engagement covers, and what it does not.
In scope
- Multi-company design: masters, access, inter-company, reporting.
- Migration and implementation paths that preserve estate shape.
- Multi-branch services operations on one platform where that is the model.
Not in scope
The interesting engineering starts when company two is no longer an exception.
We build for groups that outgrew a single-company assumption. How we work is on How we work.
How an industry engagement runs.
-
01
Situation call
What breaks in operations, what cannot pause, and whether something is already failing users.
-
02
Estate map
Name the processes, systems, and conflict cases that define this vertical.
-
03
Options on paper
Implement, migrate, integrate, product, process-only, or rescue first. Each option carries what you give up.
-
04
Recommended path
One primary recommendation and the conditions under which we would change it.
-
05
Hand-off into Services or stop
You keep the write-up. Delivery lands on a named Service, Solution, or Product page — not a vague phase two.
Questions we get first.
Is this ERP Modernization?
Modernization is the strategy page when replace vs evolve is unclear. This page is multi-company proof.
Do you only do manufacturing groups?
No. Apex is a manufacturing group exemplar; Endurance is a multi-branch services network. The estate problem is shared.
What if the estate is already failing?
Start at Rescue & Stabilization.
What does this cost?
Scoped after the situation call, in writing, before work starts.
Get a multi-company path that survives the next entity.
Tell us how many companies and what reporting cannot trust today. We will say implement, migrate, or rescue first.