One organization, many workspaces

Acme has six ways to price, and none of them is wrong

Acme Industrial Group is an illustrative company, and a familiar one. In three years it bought six companies: a consumables and tooling maker in Ohio, an engineered-systems business in Denmark, a components manufacturer in Germany that sells through dealers, a made-to-order equipment builder in Chicago, a distributor in New Zealand, and a fabricator in the United Kingdom. Each was the leader in its niche. Each came with its own ERP, its own currency, its own price lists and its own way of deciding what a customer pays.

That last part is the point. Northline prices consumables through a four-tier distributor matrix because that is how consumables are sold. Halvard Systems prices an engineered system per project because there is no list price for something built once. Keller Components gives its dealers twenty percent off list and a bonus at year end because that is what its dealers expect. None of these processes is a mistake. Each is the product of a market the company understood better than anyone else, which is why Acme bought it.

The trouble starts with the questions only the group can ask. What did Acme realize on last year’s price increases, across all six companies? What does Acme give Coastline Industries, a customer that buys consumables from Northline, components from Keller and a made-to-order line from Meridian, in total? When tariffs moved on European-made goods sold into the United States, which brands recovered the cost and which absorbed it? What is the group’s plan for next year, and which brand’s forecast is it built on? Six pricing processes can each answer their own version. None can answer the group’s.

The group also inherits four ERPs, six currencies and six definitions of margin. Every consolidated number is a spreadsheet, and every spreadsheet is somebody’s evening.

The wrong question: one system or many

Groups in Acme’s position usually reach for one of two answers, and both are the same mistake with the sign flipped.

Leave every brand alone. This is federation by default. It is fast, it respects the operating companies, and it is what the acquisition playbook says to do in year one. Its costs arrive slowly. Key accounts learn to negotiate brand by brand, and win. Price increases land in six sizes at six different times, so the group never knows what a “four percent increase” actually delivered. A cost shock is recovered in the brands with a surcharge process and absorbed in the ones without. The chief financial officer consolidates margin in a workbook that is wrong by the time it is read.

One process, one system, now. This is harmonization by mandate. It answers every group question in principle, eighteen months from now. In the meantime the program becomes the pricing strategy. Local knowledge is the first casualty: the engineered-quote discipline that made Halvard profitable is flattened into a configurator built for a different business, and the brand that priced best in the group starts pricing worst. Companies rarely say this out loud, but the brands know, and the best pricing people leave first.

Both responses share an assumption: that the unit of decision is the system. It is not. The unit of decision is the process. Some of Acme’s pricing processes must stay specific, because they are priced with knowledge that lives in one company. Others pay to be uniform, because they move money between companies or answer questions only the group asks. The job is to tell them apart, and to have a place to put each answer.

Specific where it must be, uniform where it pays. That is the whole design principle, and it is a process decision, not a systems decision.

The container: organization and workspaces

Revomo gives a group two nested objects to hold that decision.

An organization is the group. It holds one identity and role model, one set of standards (price-model templates, rules, playbooks), one rollup of results, and one line of lineage from any number back to the transaction that produced it. There is one organization for Acme.

A workspace is a bounded pricing world inside the organization: its own datasets, price models and price lists, rules and approval routes, currencies and calendar. A workspace can be a brand, a region, a business unit, a product line or a channel. What matters is not the label but the test: a workspace is the smallest unit whose pricing process is genuinely its own.

Two things follow. First, the boundary between workspaces is porous in exactly the ways a group needs and closed in the ways a brand needs. Identity, standards, lookups, the rollup and lineage cross it. Data feeds, price lists, rules, approvers and calendars do not. A key-account agreement held at group level can be read by every brand’s price list; a brand’s cost data is read by nobody the brand did not authorize. Second, the way you cut workspaces is a choice you make per group and can revisit. Try the five common cuts, including the hybrid most groups end up with.

Acme’s first cut is by brand, because that is where the processes and the ERPs are today. It will not be the last cut, and it does not need to be right forever.

Specific where it must be, uniform where it pays

Deciding per process needs a test that a leadership team can run in an afternoon. Four questions do most of the work.

1. Does the group need one answer? Increases, surcharges, key-account terms and the margin waterfall are group questions. An engineered quote for one customer’s system is not.
2. Is local knowledge decisive? If the people who price it well are the people who know the customer, the plant and the competitor down the road, the process is local.
3. Are the data structures compatible today? Not “could be after a project” but “are”. A process cannot be harmonized on data that does not yet agree on what a customer is.
4. Is there a group owner? A standard nobody holds is a document. A harmonized process nobody owns is a fight.

The answers sort each process into one of three places. Local: the process stays inside the brand’s workspace, untouched. Shared standard: the group publishes a template, a rule or a playbook once, and workspaces adopt it while keeping their own data and execution. Harmonized: the process moves into a shared workspace and runs once for the group. Work through Acme’s eight processes, one per application the group would run, or let the ledger show the answer Acme reached.

A rule of thumb falls out of the ledger. Harmonize the money that moves between companies: key-account agreements, programs and rebates, surcharges computed from one index. Standardize the calendar: the annual increase runs on one playbook in one window, at each brand’s own percentage. Leave local what is priced with local knowledge: engineered and bid quotes, and price guidance, on the group’s data but inside the brand’s corridors.

One workspace, many views

The objection every brand general manager raises, and should, is this: “If list pricing is harmonized into one workspace, every brand sees every other brand’s cost and margin.” The answer is that harmonizing a process does not mean sharing a view of it. Two controls keep them apart.

Entity-level access decides which datasets, price lists, agreements and models exist for a person at all. A brand general manager is granted their brand’s price lists; the others are not hidden from them, they are simply not theirs. Presets decide, for the entities a person can reach, which rows and which columns they see. Both are enforced, not defaults. A regional finance lead sees Europe’s rows across every brand and cannot widen the filter. A sales representative sees list and floor and never sees cost or margin, and cannot add the column.

The implication is worth stating plainly, because it changes the workspace decision. The number of workspaces is a process decision, not a security decision. A group never has to split a workspace to hide a column, and never has to merge one to share a row. That is what lets “uniform” and “exposed” come apart.

Federate first, converge on purpose

Because a process can move between local, standard and harmonized without a rebuild, the order of operations changes. A group no longer has to decide the end state before it starts. Acme’s path has four stages.

Every stage is reversible. A workspace can be re-cut, by region instead of by brand, without reloading its data. A standard can be withdrawn. A domain that was merged can be split back if a brand turns out to need its own version after all. The group is never betting the pricing function on a design it made before it understood its own companies.

Acme, one year in

An illustration, not a measured outcome. Twelve months after the first workspace, this is what each person at Acme sees.

The chief financial officer opens one waterfall for the group, list to pocket, by brand, region and key account, built from six workspaces and four ERPs, with every number traceable to the invoice behind it. The consolidation workbook is gone.

The general manager of Halvard Systems still prices every system per engineered project, in Danish kroner, with the same approvers as before. Halvard adopted the group’s price-model template for its standard products because it was better than the one it had, and it ran the group’s increase playbook in the group window at a percentage it chose itself.

The key-account director holds one agreement with Coastline Industries. Six price lists read it. The rebate accrues once, on every qualifying invoice from every brand, and the claim at year end matches the accrual.

The finance lead for Europe sees three brands’ European rows in one view, with the tariff surcharge on goods shipped into the United States computed from one index table the group owns, and can see who approved every exception.

A sales representative at Northline sees list price and floor for their distributors in North America, nothing else, and gets an answer on a special price in the time it takes the rule to run, because the corridor is a rule and the exception is a route.

Questions to settle before you choose

For the leadership team, before any design work:

1. How many price lists does the group hold today, and who can name them all?
2. Which of our pricing processes move money between our companies?
3. Who owns key-account pricing across brands, and who do our largest customers think owns it?
4. Which company in the group prices best, and what would we lose if its process changed?
5. Which of our data structures agree on what a customer, a product and a margin are, today?
6. Who will hold each group standard, and what authority do they have when a brand declines it?
7. Which decision rights stay with a brand general manager, in writing?
8. What must a regional finance lead see across brands, and what must a sales representative never see?
9. Which acquisition arrives next, and how will it land on day one?
10. What group question can nobody answer today that a board will ask this year?

What to ask any vendor, including us:

• Can a workspace be re-cut later, by region instead of by brand, without reloading its data?
• Can a template, a rule or a playbook be published once and adopted by many workspaces?
• Can one workspace’s price list read an agreement held in another, or at group level?
• Is row- and column-level security enforced, or is it a saved view a user can change?
• Does the group view read the workspaces directly, or does it need a separate reporting project?

Frequently asked

Does a workspace mean a separate implementation? No. A workspace is a boundary inside one organization, not a second instance. It shares identity, standards, the rollup and lineage with every other workspace from the moment it exists.

Can we start with one workspace and split it later, or the reverse? Both. A workspace can be re-cut without reloading its data, and a merged domain can be split back. The design you start with is a starting point, not a commitment.

Do we lose the group view if the brands keep their own workspaces? No. The rollup reads across workspaces, and lookups let a price list in one workspace read an agreement in another. The group view is a property of the organization, not of harmonization.

Who owns the standards? Whoever the group appoints, and the appointment matters more than the tooling. A standard is a template, a rule or a playbook with a named owner and a version. Workspaces adopt it; the owner maintains it.

How does an acquisition land? In its own workspace, with its own ERP feed, price lists and approvers, in the first weeks. Nothing changes for the acquired company on day one. The group view includes it from the day its data is connected.