Holding companies · multi-brand groups · buying group holdcos · family offices · sponsor-backed platforms
You own several companies. They are each rebuilding the same thing.
Every company in your group sells branded goods, and every one of them solved it alone. Different store platform, different configurator, different fee stack, different reporting shape. Nobody set out to buy four versions of the same software. It happened one acquisition at a time. This page is about what happens when they run on one system instead, and why that is a faster return than any of them fixing it individually.
| Separately | On one system | |
|---|---|---|
| Platforms paid for | One each | One |
| Configurator projects | One each | None |
| Group-wide sales view | A quarterly deck | A screen |
| Cross-company catalog | A meeting | A push |
The thing nobody has priced
Four companies solving one problem four times is not four costs. It is four ceilings.
The duplicated license fees are the least of it, and they are the only part anybody usually counts. The real cost is that each company is capped by the same manual work, separately. Each one builds customer stores by hand, so each one can only serve as many customers as its people have hours for. Each one prices product by product across its own store estate. Each one runs its own seasonal push, or skips it. Each one reconciles rebates from its own exports.
None of that shows up as a line item. It shows up as growth that did not happen, in four places at once, and it is invisible in a monthly report because nothing is broken. Everyone is simply busy.
Consolidating the platform removes the duplicate spend, and it also removes the ceiling from all of them on the same day, which is why the return arrives faster than a per-company fix and why it compounds with every company you add afterward.
- One catalog, pushed across brands. Products from one company appear in another company’s stores, with the right price list and the right margin, without a negotiation each time.
- One ledger for the group. Every online sale, every company, every channel, on one screen. What sold, what it made, and what is owed to whom.
- Volume that attributes. Purchase orders raise on each company’s own supplier accounts, so tier volume and rebates land where they are earned rather than pooling under an intermediary.
- Nothing rebuilt per company. A new holding is configured, not implemented. The configurator, the catalog and the ledger already exist.
- One security review, not one per company. Enterprise buyers put your companies through the same assessment separately today.
The part that decides it
An acquisition is live on the same system in weeks, not in next year’s budget.
The reason platform consolidation gets deferred across a group is that everyone has watched it eat a year. That happens when the plan requires every company to migrate before any of them sell. We do it the other way around.
| Stage | The usual portfolio program | Here |
|---|---|---|
| Day one | Discovery, scoping, a statement of work | One company’s customer store built live on the call, from a pasted web address |
| Week one | Nothing is selling yet | Order ingestion pulls what every company sells on its existing tools into one view. The group sees the whole picture before anything has moved. |
| The migration | All companies, all stores, one date, one very bad weekend | Stores come over from a list, in batches, per company, on each company’s own schedule. The old system keeps running underneath. |
| The next acquisition | A new integration project and a new platform contract | Configured onto what already exists |
| If it does not work for one company | The whole program is at risk | That company keeps what it had. Nothing was turned off. |
Suppliers connect over PromoStandards, the standard the industry already agreed on, so a company’s catalog is a configuration rather than a build. That is the difference between a portfolio program measured in quarters and one measured in weeks.
What each company keeps
Consolidating the plumbing is not consolidating the businesses.
The fastest way to make a portfolio-wide platform fail is to make the operating companies feel acquired twice. Every company on this system keeps the things it would fight you over.
Its name, its domain, its email sending from the store’s own name. A customer of one company never sees another company’s brand and never sees ours.
They stay that company’s customers. There is no shared shopper pool and no cross-selling of one company’s buyers to another unless the group decides to build that deliberately.
Its account numbers, its negotiated pricing, its rebate agreements. The group gets visibility into the volume. It does not get handed the relationship.
Its floor, its machines, its layout and raster software, its enterprise system. We hand off to production. We do not replace it.
Each company settles through its own payment account. Money does not route through the group unless the group wants it to, and it never routes through us.
A company that wants to go first goes first. A company that wants to watch, watches. Adoption inside a group works the way it works inside a franchise system, which is to say not by mandate.
What the group gets that no company gets alone
Four questions you currently answer with a deck.
| The question | Today, across the group | On one system |
|---|---|---|
| What did we sell online last month, everywhere? | Four exports, four shapes, assembled by a person, arriving late | One screen, live |
| Which products move, and where? | Each company knows its own half | By product, by company, by region |
| Are we hitting supplier tiers we already negotiated? | Argued after the fact | Attributed at the order |
| What would it cost to put company D on this? | A scoping exercise | A configuration |
There is a version of this that goes further, if the group wants it. Products from one company sold through every other company’s stores. A shared catalog with per-company pricing. One negotiated supplier position used across every holding. None of it is required, and none of it happens without the group choosing it. But once the companies are on one system, those become settings rather than projects, and that optionality is worth more than the software.